*** menesis has joined #schooltool | 00:46 | |
*** menesis has quit IRC | 01:11 | |
*** menesis has joined #schooltool | 01:12 | |
*** jelkner has quit IRC | 02:31 | |
*** th1a has quit IRC | 03:20 | |
*** replaceafill has quit IRC | 03:25 | |
*** menesis has quit IRC | 03:40 | |
*** aks has joined #schooltool | 06:02 | |
*** menesis has joined #schooltool | 11:05 | |
*** menesis has quit IRC | 12:12 | |
*** ignas has joined #schooltool | 12:30 | |
*** yvl has quit IRC | 12:42 | |
*** menesis has joined #schooltool | 13:30 | |
*** menesis has quit IRC | 13:39 | |
*** menesis has joined #schooltool | 14:49 | |
*** krishnagiri has joined #schooltool | 14:56 | |
*** krishnagiri has quit IRC | 14:59 | |
*** th1a has joined #schooltool | 15:08 | |
*** krishnagiri has joined #schooltool | 15:13 | |
*** krishnagiri has quit IRC | 15:15 | |
*** yvl has joined #schooltool | 15:39 | |
*** replaceafill has joined #schooltool | 16:19 | |
th1a | replaceafill: Got a little feedback from Helder. He doesn't like the one-section only behavior of the accordion. | 16:20 |
---|---|---|
replaceafill | well, there's a hack | 16:21 |
replaceafill | to open them all | 16:21 |
th1a | The jquery page seems to suggest that you could just write your own. | 16:22 |
replaceafill | correct | 16:22 |
th1a | That might make more sense. | 16:23 |
th1a | Well, we could hack it to see how it looks. | 16:23 |
replaceafill | we could do that and use the same styles from jquery ui | 16:23 |
th1a | Hack the current one. | 16:23 |
replaceafill | sure | 16:23 |
th1a | Just to prototype. | 16:23 |
th1a | We can talk about it some more. | 16:23 |
replaceafill | ok | 16:24 |
* replaceafill updates the testing instance | 16:29 | |
*** aks has quit IRC | 16:32 | |
th1a | hi aelkner, yvl, menesis, replaceafill. | 16:32 |
yvl | morning guys | 16:32 |
aelkner | morning | 16:32 |
replaceafill | morning | 16:32 |
th1a | OK, you guys got my followup to yvl's workflow yesterday. | 16:32 |
th1a | Where I arbitrarily divided the list between yvl and aelkner? | 16:32 |
menesis | hi | 16:33 |
th1a | Yes? | 16:33 |
yvl | yes | 16:34 |
th1a | Make sense? | 16:34 |
yvl | hmm | 16:34 |
yvl | I'm pretty sure both Alan can also do the top part | 16:35 |
yvl | sorry, I meant - Douglas, Alan, and I can do these things | 16:36 |
yvl | probably Alan and Douglas will do most of the stuff after the cutting point | 16:36 |
yvl | simply because they're on the same timezone | 16:36 |
yvl | and it's easier to get feedback | 16:36 |
th1a | So... what are you suggesting? | 16:37 |
yvl | well, basically keep doing what we were doing | 16:38 |
yvl | decide who does what every day | 16:38 |
yvl | for another week | 16:38 |
yvl | it would be nice if Alan and Douglas ported some more views by themselves | 16:38 |
yvl | because that would make drawbacks more obvious | 16:39 |
th1a | aelkner? replaceafill? | 16:39 |
replaceafill | i agree with yvl on us porting views | 16:39 |
aelkner | +1 | 16:39 |
replaceafill | to give him feedback | 16:39 |
th1a | OK. SEttled. | 16:39 |
th1a | yvl: What did you do today? | 16:40 |
yvl | It was a slow day actually | 16:40 |
yvl | started working on splitting person add forms to multiple fieldsets | 16:40 |
yvl | ended up realizing that it's a good time to do some base classes now | 16:40 |
yvl | keeping in mind forms that we all wrote | 16:41 |
aelkner | didn't i do the person forms already | 16:41 |
aelkner | with multiple fieldsets and all | 16:41 |
th1a | I was going to mention that they don't seem to be in trunk. | 16:41 |
th1a | We can't be sitting on code. | 16:41 |
replaceafill | i thought aelkner made a fieldset only for demographics | 16:42 |
replaceafill | in trunk | 16:42 |
th1a | Oh, right. | 16:42 |
th1a | The view, not the form. | 16:42 |
yvl | right | 16:42 |
th1a | Oh, right. | 16:42 |
th1a | I see. | 16:42 |
aelkner | what view/form? | 16:42 |
yvl | aelkner - we need 4-5 fieldsets in say "Add Teacher" view | 16:43 |
th1a | Yes. | 16:43 |
th1a | Organizing it more as we discussed yesterday. | 16:44 |
yvl | and I remember Alan wanting form.py for a while now | 16:44 |
yvl | and our current forms that have "subforms" are not that consistent in the old skin | 16:45 |
yvl | and probably they could be | 16:45 |
yvl | also we tend to skimp on error validation | 16:45 |
th1a | Well... | 16:45 |
th1a | yvl, we really have to be careful right now about diving into plumbing. | 16:45 |
yvl | my plan is to marinate it over the weekend | 16:46 |
th1a | OK. | 16:46 |
yvl | if I arrive at something - do a simple implementation on Monday | 16:46 |
yvl | if not, just port the views bluntly | 16:46 |
th1a | We have about 40 work days between now and feature freeze and probably around twice that many views. | 16:46 |
th1a | So we need to get cranking through several a day. | 16:47 |
yvl | good point | 16:48 |
th1a | Some of those are complicated (manage...) | 16:48 |
th1a | And some are just hairy (term calendar). | 16:48 |
yvl | true | 16:49 |
th1a | OK. | 16:50 |
th1a | We've still got things from yesterday's list. | 16:50 |
th1a | If we get that far I'll have aelkner work on the add forms because. | 16:51 |
th1a | I'd like to wrap this part up if possible (probably not) | 16:51 |
yvl | ok | 16:51 |
*** jelkner has joined #schooltool | 16:52 | |
th1a | So starting next week should we focus on easier management views first? | 16:52 |
th1a | Groups, courses, sections? | 16:52 |
th1a | Before tackling years and terms? | 16:52 |
yvl | hmm | 16:53 |
th1a | Probably would be good to get a little momentum. | 16:53 |
yvl | you know, that might be a very good idea | 16:53 |
yvl | since we want to represent groups and courses without necessarily traversing through schoolyear | 16:54 |
th1a | Oh... yes, that is an issue I guess. | 16:54 |
th1a | You can't do groups without a year. | 16:54 |
yvl | but it's a good exercise | 16:55 |
th1a | Hm... | 16:55 |
yvl | say, we have no year - how will our interface look? | 16:55 |
yvl | say, we have one year - how will our interface look? | 16:55 |
yvl | say we have two or more years - <...> | 16:55 |
aelkner | back in 5 min | 16:55 |
th1a | We really could primarily switch to filtering by current year by default. | 16:56 |
yvl | we can fill the Data.fs from a trunk instance | 16:56 |
th1a | And hide the navigational aspect. | 16:56 |
yvl | but the system should be very operational without schoolyear add/index and so on views | 16:56 |
yvl | having no index.html for schoolyear can make this easier to design | 16:57 |
yvl | maybe | 16:57 |
th1a | Well, the real issue is just that groups and other things have to be contained in the year, right? | 16:58 |
th1a | It is a matter of where things go in the database. | 16:58 |
th1a | ? | 16:58 |
yvl | it's built that way now, yes | 16:59 |
aelkner | i'm back | 16:59 |
th1a | OK. We're not changing that now. ;-) | 16:59 |
th1a | I'd rather just make it clear that you have to start with a new school year and leave it at that. | 16:59 |
th1a | But really, I don't even want to get into that issue now. | 17:01 |
yvl | that's probably the first thing user should see when he hits manage school on fresh instance | 17:01 |
th1a | RIght. | 17:01 |
replaceafill | "set up procedure" :) | 17:01 |
th1a | Pretty much everything else should be greyed out. | 17:01 |
th1a | Yes. | 17:01 |
th1a | So probably we need to port years first. | 17:02 |
yvl | hmm | 17:02 |
th1a | Having said that, navigationally, you shouldn't have to go through the year to add a group. | 17:02 |
th1a | The whole concept of the year tab is going away. | 17:02 |
yvl | then we can postpone porting of school years maybe? | 17:03 |
yvl | just use databases with one set up year | 17:03 |
th1a | OK, fine. | 17:03 |
menesis | the year tab is confusing | 17:03 |
th1a | It will be gone. | 17:03 |
yvl | yay! | 17:03 |
menesis | I understand it will move to School tab | 17:04 |
menesis | plus some things moved from Manage | 17:04 |
th1a | Well, we probably don't need it at all. | 17:04 |
yvl | +1 th1a | 17:04 |
menesis | make People, Courses top-level? | 17:04 |
th1a | No. | 17:05 |
yvl | "School" level? | 17:05 |
th1a | I'm not even sure what the distinction between "Application" and "School" is and who sees them. | 17:05 |
th1a | yvl? | 17:05 |
yvl | Application is the server | 17:05 |
yvl | you do have things like email support | 17:06 |
yvl | preferably | 17:06 |
yvl | also other settings | 17:06 |
yvl | even packing a database | 17:06 |
th1a | Maybe "System" ? | 17:06 |
yvl | it's a place for administrators ideally | 17:06 |
th1a | "Settings?" | 17:06 |
aelkner | Application Setig from the old manage view | 17:06 |
yvl | school is for clerks | 17:06 |
th1a | The actual model of the school. | 17:07 |
th1a | OK. | 17:07 |
yvl | yes | 17:07 |
th1a | I think we can change the term for Application. | 17:07 |
aelkner | Site Management | 17:07 |
th1a | And perhaps it should be at right, not left. | 17:07 |
th1a | So a teacher would only see Gradebook and Intervention right now, correct? | 17:08 |
yvl | and Journal | 17:08 |
th1a | Right. | 17:08 |
yvl | I was thinking to use "School" in place of "Home" for simpler users | 17:09 |
yvl | It's still your school | 17:09 |
th1a | Well, there really should be a personal home page for users that is different from the school home. | 17:09 |
th1a | Personal dashboard. | 17:10 |
yvl | of course! | 17:10 |
yvl | I'm just talking about the tab name | 17:10 |
th1a | If they do different things they should be different tabs. | 17:10 |
yvl | "Home" is ok. "School" seemed like an interesting alternative. | 17:10 |
th1a | I think they're different things. | 17:10 |
yvl | I was thinking from a different angle | 17:11 |
th1a | Right? School is an admin page. Home is a personal dashboard. | 17:11 |
yvl | Administrator sees a school in a different way than a teacher | 17:11 |
th1a | yvl: That's why we have these discussions. ;-) | 17:11 |
yvl | sure :) | 17:11 |
th1a | They might be the same person. | 17:11 |
yvl | good point | 17:12 |
th1a | OK, we'd better shift to what aelkner and replaceafill are going to do today. | 17:13 |
aelkner | I need to ask a question first | 17:14 |
aelkner | yvl, you say we should derive the new classes from the old ones as much as possible | 17:14 |
aelkner | but i'm not sure how that can work | 17:14 |
aelkner | the old classes derive from z3cform in some cases | 17:14 |
aelkner | and override the update method | 17:14 |
aelkner | the new base classes flojurish.Page, etc. | 17:15 |
aelkner | derive from z3cform also, and have an override of update | 17:15 |
aelkner | i'm not saying it can't work, i just don't know why it would | 17:15 |
yvl | you are right | 17:15 |
yvl | basically you have some of the methods that overlay each other | 17:16 |
yvl | __call__ and update | 17:16 |
yvl | templates | 17:16 |
yvl | maybe something else | 17:16 |
yvl | hmm | 17:17 |
yvl | it is a bit pesky | 17:17 |
aelkner | my question was, how can this work? | 17:17 |
yvl | take a look at person edit view | 17:17 |
yvl | and add multiple person view | 17:17 |
aelkner | class PersonEditView(form.EditForm, PersonForm): | 17:18 |
aelkner | def update(self): | 17:18 |
aelkner | super(PersonEditView, self).update() | 17:18 |
yvl | and FlourishPersonEditView | 17:18 |
aelkner | class FlourishPersonEditView(flourish.page.Page, PersonEditView): | 17:18 |
aelkner | def update(self): | 17:18 |
aelkner | PersonEditView.update(self) | 17:18 |
yvl | yes | 17:19 |
yvl | basically you have two options | 17:19 |
yvl | when inheriting | 17:19 |
yvl | make the old class methods "primary" | 17:19 |
yvl | say, like this class FlourishSomeClass(OldEditView, flourish.page.Page) | 17:20 |
yvl | then you have to manually replace __call__ and render | 17:20 |
yvl | at the very least | 17:20 |
yvl | because you want them from flourish.page.Page | 17:21 |
yvl | other option (and that happens with the FlourishMultiplePersonAddView) | 17:21 |
yvl | wait, sorry, no | 17:21 |
yvl | the first option happens with multi-person-view | 17:21 |
yvl | the second option is to do like FlourishPersonEditView | 17:22 |
yvl | but then the update and __call__ methods are overshadowed from Page | 17:22 |
yvl | so if your view has an update, or some logic in __call__ | 17:22 |
yvl | you need to copy that logic to respective FlourishPersonEditView.update and FlourishPersonEditView.render | 17:23 |
yvl | oh, and a third option | 17:23 |
yvl | do not inherit anything | 17:23 |
yvl | write from scratch | 17:23 |
aelkner | that's what i did with the viewlets | 17:23 |
aelkner | but that's not what you suggested when you said use the old classes | 17:24 |
yvl | it's a developers call actually | 17:24 |
yvl | by "where possible" I meant "where resonable" | 17:24 |
replaceafill | i see a lot of duplication between GroupsViewlet and FlourishGroupsViewlet | 17:25 |
aelkner | right, that's my point | 17:25 |
yvl | damn, "reasonable" | 17:25 |
yvl | not reson.. | 17:25 |
aelkner | i couldn't get it to work if i simply derived from the old class | 17:26 |
th1a | We aren't going to be maintaining the old classes. | 17:26 |
th1a | There won't be a "classic" skin. | 17:26 |
aelkner | th1a, right, so is it so bad to just duplicate the code | 17:26 |
replaceafill | if we start to use them as base , we will have to | 17:26 |
aelkner | and throw away the old classes when we are done | 17:26 |
yvl | oh, so no CanDo / Cambodia support ? | 17:27 |
th1a | Well, if we use them as a base because it saves time, that's different. | 17:27 |
*** asharma has joined #schooltool | 17:27 | |
th1a | They both have time to catch up. | 17:27 |
yvl | ok | 17:28 |
aelkner | yvl, can we come up with a pattern that we can follow | 17:28 |
th1a | I mean, basically the old views are going to hang around for a few releases. | 17:28 |
aelkner | i don't care which of the options above we choose, but leaving t up to developer's discretion | 17:29 |
th1a | But as a legacy. | 17:29 |
aelkner | that seems to be more trouble than it's worth | 17:29 |
th1a | Not an ongoing option. | 17:29 |
yvl | ok, th1a | 17:29 |
yvl | you're right aelkner | 17:29 |
yvl | let me think about that a bit over the weekend | 17:29 |
aelkner | can we look at class FlourishPersonEditView a second? | 17:30 |
aelkner | is it just as simple as using that base class order | 17:30 |
aelkner | and calling the update method from the old class? | 17:30 |
aelkner | and perhaps the __call__ method when needed | 17:30 |
aelkner | if so, that pattern seems like an efficient one | 17:31 |
yvl | for z3c forms, yes, I think | 17:31 |
yvl | aelkner, you just gave me an idea | 17:32 |
yvl | yes, have a similar simple pattern | 17:32 |
aelkner | keep it simple you know who :) | 17:33 |
yvl | thank you :) | 17:33 |
yvl | ok, I'll have something more on the topic on Monday | 17:33 |
aelkner | ok, in the meantime, if that pattern works | 17:33 |
aelkner | then i'd feel comfortable doing add/edit forms for now | 17:34 |
aelkner | and await your analysis on monday | 17:34 |
yvl | sure | 17:34 |
th1a | OK. | 17:34 |
th1a | Have a good weekend yvl and menesis. | 17:34 |
yvl | if anything, you can always add import pdb; ... | 17:34 |
yvl | in the new view | 17:34 |
yvl | I mean, just | 17:35 |
yvl | def update(self): | 17:35 |
replaceafill | i have a quick question related to pdb :) | 17:35 |
yvl | import pdb; pdb.set_trace() | 17:35 |
yvl | super(TheNewView, self).update() | 17:35 |
replaceafill | when are we going to start caring about tests again? :) | 17:35 |
yvl | do same for render and __call__, and you'll see if it takes you where you want | 17:35 |
aelkner | well, that's what i did | 17:36 |
* yvl looks at the sky... | 17:36 | |
yvl | in two weeks? | 17:36 |
aelkner | and that's why i found the difficulty | 17:36 |
replaceafill | ¬¬ | 17:36 |
yvl | in one week? | 17:36 |
replaceafill | ok | 17:36 |
th1a | One week. | 17:36 |
yvl | I'd say, when we kind of settle on on what goes where | 17:36 |
yvl | aelkner, bascially what you want to see is | 17:37 |
yvl | __call__ methods leading to flourish.page.Page | 17:37 |
yvl | update methods leading to your view | 17:38 |
yvl | redner methods - also to your view | 17:38 |
yvl | if the base class had some logic in __call__, you need to put that logic in your own render | 17:38 |
aelkner | why not call the base class __call_? | 17:39 |
aelkner | like FlourishPersonEditView does with update | 17:39 |
aelkner | well, maybe call is different | 17:39 |
yvl | hmm it just looked weird to me | 17:39 |
aelkner | because it involves loading the template | 17:39 |
yvl | but you totally can | 17:39 |
aelkner | ok, well i can play around with these things as they come up | 17:40 |
aelkner | but definitely a general pattern that is efficient would be better than playing around each time | 17:40 |
yvl | well, the rule of the thumb is "if it's too difficult - it's either broken or not worth it" | 17:40 |
* yvl thought to wait for the pattern to emerge :) | 17:41 | |
yvl | maybe it's time | 17:41 |
yvl | allright... | 17:41 |
yvl | any more questions? | 17:41 |
yvl | remarks? | 17:41 |
yvl | insights? ;) | 17:41 |
aelkner | we'll have code changes for you to look at over the weekend | 17:42 |
yvl | thank you | 17:42 |
aelkner | so perhaps that will help you come up with a pattern | 17:42 |
yvl | I'll do that late Sunday | 17:42 |
yvl | or even early Monday | 17:42 |
* th1a drops the bag of gravel. | 17:42 | |
aelkner | sounds like a plan | 17:42 |
yvl | ok | 17:42 |
th1a | aelkner & replaceafill: We just need a plan for today. | 17:42 |
yvl | good luck, guys! | 17:43 |
aelkner | great weekend yvl! | 17:43 |
th1a | We need: | 17:43 |
th1a | preference dialog (and link) | 17:43 |
th1a | edit views for advisors, advisees, groups | 17:43 |
th1a | "add another" buttons for the person add forms | 17:44 |
aelkner | relationship views are more complex than simple add/edit view, so... | 17:44 |
th1a | reorganized person add forms | 17:44 |
th1a | replaceafill, Could you start with the person sidebar | 17:44 |
replaceafill | ok | 17:45 |
aelkner | yay, we need some action buttons to call up these views | 17:45 |
th1a | NOT ACTION BUTTONS. | 17:45 |
aelkner | sidebar buttons? | 17:45 |
th1a | Also, replaceafill, could you fix the hover color for the buttons. | 17:45 |
th1a | NOT BUTTONS. | 17:46 |
th1a | Links. | 17:46 |
aelkner | ok, links, that's what i meant | 17:46 |
th1a | ;-) | 17:46 |
replaceafill | th1a do you want background color on hover for the action links? | 17:47 |
aelkner | did you just call them action links?! | 17:47 |
th1a | That's semi-acceptable. | 17:47 |
th1a | Background color on hover? | 17:47 |
th1a | Like, the whole background? | 17:47 |
replaceafill | we're talking action links on left sidebar, correct? (just confirming) | 17:48 |
th1a | I'm ok with them the way the are now. At this point. | 17:48 |
th1a | Error messages look ok on the forms, btw. | 17:48 |
th1a | I don't know about "There were some errors." though. | 17:49 |
replaceafill | yes | 17:49 |
th1a | But but I need to shower and go to the grocery store or my children will have no lunch. | 17:49 |
* th1a goes to take a shower... | 17:49 | |
replaceafill | :D | 17:49 |
replaceafill | th1a can i work on the accordions? | 17:49 |
replaceafill | to display them all? | 17:49 |
aelkner | replaceafill, sounds like a good idea | 17:59 |
aelkner | i'm going to work on the preferences form, the first modal form in the flourish skin | 18:00 |
replaceafill | th1a http://69.164.203.135:6660/persons/alvaro | 18:09 |
replaceafill | all accordions open | 18:09 |
th1a | They do? | 18:12 |
replaceafill | they dont? | 18:12 |
replaceafill | refresh? | 18:12 |
th1a | btw, we need some border on the inactive accordion sections. Probably just matching the background. | 18:12 |
th1a | tbh, I'm a little dubious. | 18:13 |
th1a | What do you think? | 18:13 |
th1a | I like that it keeps the page size under control. | 18:13 |
replaceafill | i'd like a button somere "expand all" | 18:13 |
replaceafill | somewhere | 18:14 |
replaceafill | like launchpad branches | 18:14 |
replaceafill | like in | 18:14 |
th1a | True. | 18:14 |
replaceafill | and yes, the whole point of using accordions was to make the page smaller | 18:14 |
th1a | Lets leave it as it was for now. | 18:15 |
replaceafill | ok | 18:15 |
th1a | It is something we can come back to when we get more feedback. | 18:15 |
replaceafill | inactive accordions have a different background | 18:15 |
replaceafill | maybe we need more contrast? | 18:15 |
th1a | They just have no border. | 18:15 |
replaceafill | hold on, let me revert this change first | 18:16 |
th1a | Now. A border shouldn't appear from nowhere when you hover. | 18:16 |
replaceafill | change reverted | 18:16 |
* th1a goes to the grocery store. | 18:17 | |
replaceafill | so you want the border to always appear and change color when they hover on the innactive accordions? | 18:17 |
replaceafill | ok, i'll be here | 18:17 |
th1a | replaceafill: Yes. | 18:40 |
replaceafill | th1a refresh | 18:41 |
th1a | Good. | 18:42 |
th1a | Can you move the Value over to 1/3rd right instead of 2/3rds? | 18:42 |
replaceafill | ah ok | 18:42 |
replaceafill | th1a done, 33%, 66% | 18:50 |
replaceafill | widths | 18:50 |
th1a | Better. | 18:50 |
replaceafill | for general information and attributes | 18:50 |
th1a | Yes. | 18:59 |
replaceafill | th1a what action links do you want in the person view? | 19:00 |
th1a | Need a section in the sidebar for $USERNAME's ...16:51 | 19:01 |
th1a | th1aThat will have:16:51 | 19:01 |
th1a | th1a- Intervention center16:51 | 19:01 |
th1a | th1a- Reports16:51 | 19:01 |
th1a | th1aI'm not sure what the header is in whatever section Preferences goes in.16:52 | 19:01 |
th1a | th1aMisc. | 19:01 |
replaceafill | ah! :) | 19:01 |
aelkner | replaceafill, i get 5 conflicts while merging from trunk | 19:07 |
aelkner | all having to to with: | 19:07 |
aelkner | onflict: can't delete src/schooltool/app/help because it is not empty. Not deleting. | 19:07 |
aelkner | Conflict | 19:07 |
replaceafill | no idea e | 19:08 |
replaceafill | havent seen it | 19:08 |
aelkner | have you merged your branch with trunk? | 19:08 |
replaceafill | no | 19:08 |
*** fsufitch has quit IRC | 19:09 | |
*** asharma has quit IRC | 19:10 | |
replaceafill | aelkner when was the last time you merged trunk to your branch? | 19:10 |
replaceafill | ah, menesis made some changes | 19:10 |
replaceafill | 2899-2901 | 19:11 |
aelkner | yes, he removed the help directories | 19:11 |
aelkner | i don't understand the conflict | 19:11 |
aelkner | why can't bzr just remove them while merging? | 19:11 |
aelkner | and not complain about it? | 19:11 |
menesis | aelkner: can't remove them because they contain *.pyc files | 19:11 |
menesis | rm -r src/schooltool/app/help | 19:12 |
menesis | bzr resolved src/schooltool/app/help | 19:12 |
th1a | That wounds like a good idea until it deletes something you want without telling you. | 19:12 |
aelkner | menesis, thanks | 19:12 |
aelkner | th1a, yeah, bzr shouldn't do TOO much, i didn't think about the pyc files | 19:13 |
*** fsufitch has joined #schooltool | 19:13 | |
replaceafill | oh oh, server error in cambodia | 19:17 |
replaceafill | awesome! videos instead of screenshots!!! | 19:17 |
th1a | Yeah, funny. | 19:19 |
replaceafill | made a mistake in one adapter registration :( | 19:19 |
aelkner | menesis, a question | 19:19 |
replaceafill | th1a can i work on cambodia until we finish paiting today? | 19:19 |
replaceafill | it's weekend for them anyway :P | 19:19 |
th1a | Paiting? | 19:20 |
th1a | Painting? | 19:20 |
replaceafill | :D | 19:20 |
replaceafill | yes, css work | 19:20 |
replaceafill | http://69.164.203.135:6660/persons/alvaro | 19:20 |
th1a | Which do you want to do first? | 19:20 |
replaceafill | i'm on the sidebar links | 19:21 |
replaceafill | see the ###? ;) | 19:21 |
replaceafill | we need a title | 19:21 |
menesis | aelkner? | 19:21 |
th1a | $USERNAME | 19:21 |
replaceafill | ah! ok | 19:21 |
th1a | (in bash) | 19:21 |
th1a | Right? | 19:21 |
aelkner | menesis, nevermind, i figured it out | 19:21 |
replaceafill | :D | 19:22 |
th1a | It is a little redundant, but makes the point. | 19:22 |
replaceafill | hhmm should we use: | 19:25 |
replaceafill | User: alvaro | 19:25 |
replaceafill | instead of just "alvaro" | 19:25 |
th1a | Oh, I forgot the "'s" | 19:26 |
th1a | Alvaro Alvarez's... | 19:26 |
replaceafill | you mean for the title of the page? | 19:27 |
th1a | The header for the section of links? | 19:27 |
th1a | Isn't that what we're talking about? | 19:27 |
replaceafill | $USERNAME = user.title? | 19:27 |
replaceafill | i thouth $USERNAME = user.username :( | 19:27 |
th1a | No, title. | 19:28 |
replaceafill | ok | 19:28 |
th1a | I guess I should speak Python. | 19:28 |
replaceafill | :)) | 19:28 |
replaceafill | ah, title is better :) | 19:28 |
replaceafill | 3 titles near each other though | 19:29 |
replaceafill | wait, weren't we supposed to use "last name, first name" everywhere? | 19:29 |
th1a | That's the only problem but you kind of need it here for clarity. | 19:29 |
th1a | No... not doing that. | 19:29 |
th1a | Except in tables. | 19:29 |
replaceafill | ah ok | 19:29 |
th1a | In the accordion it is full name. | 19:30 |
th1a | Or should be. | 19:30 |
th1a | You need the 's | 19:30 |
replaceafill | because person.title gives you "last name, first name" | 19:30 |
th1a | Oh, switch that. | 19:30 |
replaceafill | ok | 19:30 |
replaceafill | and about the 's, i think it has translation issues | 19:31 |
replaceafill | you see the extracted string as ${person_full_name}'s | 19:31 |
th1a | Yes. | 19:31 |
th1a | Well, we'll do it my way for English. | 19:32 |
replaceafill | ok | 19:32 |
th1a | If it doesn't work in other languages, there is no reason to make it not work in English. | 19:32 |
th1a | When we have a minute I have some small footer changes (again). | 19:33 |
th1a | I can't seem to pay attention to more than one footer bug at a time. | 19:33 |
replaceafill | refresh | 19:34 |
replaceafill | where is the "Reports" link supposed to redirect? | 19:34 |
th1a | Where it does now. | 19:34 |
replaceafill | :| | 19:34 |
th1a | I think just ./reports ? | 19:34 |
th1a | reports.html? | 19:34 |
* replaceafill looks | 19:35 | |
replaceafill | i forgot we had a Reports button... | 19:35 |
* th1a checks to see if Center should be capitalized. | 19:35 | |
th1a | I guess yes. | 19:36 |
* aelkner goes to take a shower | 19:37 | |
replaceafill | th1a reports link done | 19:41 |
th1a | tbh, we can just put preferences in there too. | 19:42 |
th1a | Now... these links do need to show up or not based on permissions. | 19:43 |
th1a | Right? | 19:43 |
th1a | Hm... | 19:43 |
replaceafill | they are | 19:43 |
replaceafill | intervention center, schooltool.view | 19:43 |
th1a | OK. | 19:43 |
th1a | Good. | 19:43 |
replaceafill | reports, schooltool.edit | 19:43 |
th1a | I have to run to the bank. | 19:45 |
replaceafill | ok | 19:45 |
replaceafill | th1a change password? | 19:45 |
replaceafill | i mean, for links? | 19:45 |
th1a | Hm. | 19:46 |
th1a | Maybe we should just have a second section. | 19:46 |
th1a | Settings... | 19:46 |
th1a | Preferences | 19:46 |
replaceafill | ah | 19:46 |
th1a | Password | 19:46 |
replaceafill | good idea | 19:46 |
th1a | OK, brb. | 19:46 |
replaceafill | k | 19:46 |
replaceafill | yvl, i love viewlet recursion and "positioning" (not sorting) | 20:00 |
replaceafill | excellent | 20:00 |
replaceafill | th1a according to core trunk, we're missing: [Export] [View Calendar] [Contacts] | 20:03 |
th1a | OK, Calendar just goes first under $USERNAME | 20:09 |
replaceafill | ok | 20:10 |
th1a | What do you think about exports becoming reports? | 20:10 |
th1a | And we need an accordion for contacts. | 20:11 |
replaceafill | export doesnt sound like a report, at least to me | 20:12 |
replaceafill | do people really use that option? | 20:12 |
replaceafill | i mean, on a single person | 20:12 |
th1a | Oh... what does it even export? | 20:13 |
th1a | :-D | 20:13 |
replaceafill | xml i think | 20:13 |
replaceafill | person_export.xml | 20:13 |
th1a | It is probably an historical artifact. | 20:13 |
th1a | Let's call it a report. | 20:13 |
replaceafill | an it doesn't export much anyway... | 20:14 |
replaceafill | baseball alvaro Álvaro Álvarez | 20:14 |
th1a | We should probably do the reports view very soon. | 20:14 |
th1a | We don't need to kill it. | 20:14 |
th1a | Would you like to work on the contacts viewlet? | 20:16 |
th1a | replaceafill? | 20:16 |
replaceafill | sorry, i was changing the viewlets | 20:16 |
replaceafill | sure | 20:16 |
replaceafill | oops, wrong viewlet manager :D | 20:17 |
replaceafill | ok, contacts accordion | 20:18 |
replaceafill | Contacts for the accordion header | 20:18 |
th1a | Yes. | 20:18 |
replaceafill | title for the accordion content | 20:18 |
replaceafill | ? | 20:18 |
th1a | Are you looking at one? | 20:18 |
replaceafill | yes | 20:18 |
th1a | I don't know why that "view details" was ever in there. | 20:19 |
th1a | Anyhow... | 20:19 |
*** menesis has quit IRC | 20:19 | |
replaceafill | hhmm remeber we also have "self contact info" | 20:19 |
replaceafill | person email, etc | 20:19 |
*** ignas has quit IRC | 20:20 | |
th1a | Switch to Name, relationship | 20:20 |
th1a | then just a table for the rest should be fine. | 20:20 |
th1a | We just have to deal with multiple phones? | 20:20 |
th1a | Or is that hard coded to three options. | 20:21 |
replaceafill | home, work, mobile | 20:21 |
replaceafill | yes | 20:21 |
* replaceafill goes look | 20:21 | |
th1a | OK, that part should be straightforward. | 20:21 |
replaceafill | class IPhones(Interface): | 20:21 |
replaceafill | home_phone = TextLine(title=_(u"Home phone"), required=False) | 20:21 |
replaceafill | work_phone = TextLine(title=_(u"Work phone"), required=False) | 20:21 |
replaceafill | mobile_phone = TextLine(title=_(u"Mobile phone"), required=False) | 20:21 |
replaceafill | hold on, explain this sentence please: Switch to Name, relationship | 20:22 |
th1a | Instead of what it has now, Relationship, name. | 20:22 |
replaceafill | ah, got it | 20:22 |
th1a | The only problem is we need a separate edit link to manage all contacts for this person. | 20:23 |
th1a | I'd say just a "Manage contacts" link below the tables. | 20:23 |
th1a | Do we need headers on these tables that are just "Label | Value" ? | 20:24 |
th1a | Try them without. | 20:24 |
replaceafill | ok | 20:24 |
replaceafill | want me to try that first on the other two accordions? | 20:24 |
replaceafill | (removing the header) | 20:25 |
th1a | Yes. | 20:25 |
th1a | OK, try that and get started on the contacts. | 20:25 |
* th1a goes to make lunch. | 20:25 | |
th1a | (or go have lunch, replaceafill_ | 20:25 |
th1a | ) | 20:25 |
replaceafill | :) | 20:25 |
replaceafill | ok | 20:25 |
replaceafill | i like tables with header better | 20:28 |
replaceafill | i removed the header in general information so you can compare | 20:28 |
* th1a back. | 20:40 | |
replaceafill | :| | 20:40 |
replaceafill | th1a only had a cookie for lunch :P | 20:40 |
th1a | typing one handed | 20:40 |
replaceafill | :D | 20:40 |
th1a | i guess keep the header for now. | 20:41 |
replaceafill | ok | 20:41 |
*** ignas has joined #schooltool | 21:17 | |
replaceafill | th1a http://69.164.203.135:6660/persons/alvaro | 21:24 |
replaceafill | do we need empty values in these accordions? | 21:25 |
replaceafill | oops forgot the language :P | 21:26 |
th1a | That seems like a lot of space between the two groups in the sidebar. | 21:28 |
th1a | Make contacts second. | 21:28 |
replaceafill | 32px | 21:28 |
replaceafill | make it 16px? | 21:29 |
th1a | Well, there is the margin above for the heading. | 21:29 |
th1a | Margin below for the previous line. | 21:29 |
th1a | Plus what? | 21:29 |
th1a | Just need the manage link at bottom. | 21:31 |
th1a | Overall, I don't think it needs much tweaking, which is a very good sign! | 21:31 |
replaceafill | hhmm messed up the order... | 21:31 |
replaceafill | i'll start over, before... after... | 21:31 |
replaceafill | :) | 21:32 |
replaceafill | there, contacts second | 21:33 |
replaceafill | isn't attributes too tech? | 21:33 |
* replaceafill leaves wording to th1a ;) | 21:33 | |
replaceafill | ok, manage link below | 21:34 |
th1a | We need to let that soak a bit. | 21:34 |
replaceafill | hhmm below...? | 21:35 |
replaceafill | why not floated above to the right? | 21:35 |
replaceafill | nah, i'll put it below | 21:35 |
th1a | Could be. | 21:35 |
replaceafill | let's see | 21:35 |
th1a | Set collapsible to true on the accordion. | 21:41 |
th1a | replaceafill, I think I'll just put a TODO.txt in the flouish source. | 21:46 |
th1a | Is the root directory ok for that? | 21:46 |
replaceafill | sure | 21:47 |
replaceafill | what does "collapsible" do? | 21:47 |
replaceafill | i dont understand the docs | 21:47 |
replaceafill | "close all sections at once"..? | 21:47 |
th1a | Right now one has to stay open. | 21:48 |
replaceafill | ah | 21:48 |
replaceafill | got it | 21:48 |
replaceafill | i can close them all :) | 21:48 |
th1a | Considering the potential length of some of these, that might be less good. | 21:48 |
replaceafill | ok, put the Manage Contacts link | 21:49 |
replaceafill | check it out | 21:49 |
replaceafill | it doesnt look so bad | 21:49 |
replaceafill | http://69.164.203.135:6660/persons/alvaro | 21:49 |
replaceafill | with contacts | 21:49 |
replaceafill | http://69.164.203.135:6660/persons/menesis | 21:49 |
replaceafill | with no contacts | 21:49 |
th1a | I would do an h3 "This person has no contacts." if there are none. | 21:50 |
replaceafill | ok | 21:50 |
replaceafill | http://69.164.203.135:6660/persons/menesis | 21:53 |
replaceafill | no contacts message | 21:53 |
th1a | OK. Cool. | 21:53 |
th1a | I'd reduce the space between sections in the sidebar. | 21:53 |
replaceafill | reduced to 16px | 21:54 |
replaceafill | it was 32px | 21:55 |
th1a | Better. | 21:55 |
th1a | OK, can we do a little footer love for a minute? | 21:55 |
replaceafill | sure | 21:55 |
replaceafill | footer love, lol | 21:55 |
th1a | Hm... | 21:56 |
th1a | Make "server running" lowercase. | 21:56 |
th1a | and "Trademark" | 21:56 |
*** menesis has joined #schooltool | 21:56 | |
th1a | And TSF has a new subtitle: "We support exceptional people to change the world in extraordinary ways." | 21:57 |
th1a | So I would say... | 21:57 |
replaceafill | :| | 21:57 |
replaceafill | serve running lowercased | 21:58 |
replaceafill | what do you want me to do with Trademark? | 21:58 |
replaceafill | is a trademark? | 21:58 |
th1a | lower case. | 21:58 |
replaceafill | done | 21:58 |
replaceafill | change to the new TSF slogan? | 21:59 |
th1a | I'm thinking maybe put the copyright and trademark on line 2. | 21:59 |
th1a | And on line 3 the link and new TSF slogan. | 21:59 |
th1a | Or maybe reverse two and three. | 21:59 |
ignas | yvl, ayt? | 21:59 |
th1a | ignas: It is friday night in Lithuania. | 22:00 |
*** klausade has joined #schooltool | 22:00 | |
ignas | yeah :) like 10 pm or so | 22:00 |
ignas | so yeah, he probably is not there :) | 22:00 |
*** menesis has quit IRC | 22:01 | |
replaceafill | th1a refresh | 22:02 |
replaceafill | reverse 2 and 3? | 22:02 |
th1a | No... line 2 should be copyright + trademark. | 22:03 |
replaceafill | ah ok | 22:03 |
th1a | And only the last one should be a link. | 22:03 |
ignas | th1a, how's redesign going? | 22:03 |
th1a | ignas, http://69.164.203.135:6660/persons/ | 22:04 |
th1a | log in as default manager. | 22:04 |
th1a | It is a lot easier if you start with a good set of guidelines. | 22:04 |
th1a | And have been looking at the problems for years... | 22:04 |
ignas | gmm | 22:04 |
ignas | very flaky | 22:04 |
th1a | ? | 22:04 |
ignas | connection is dropping a lot | 22:05 |
replaceafill | th1a refresh | 22:05 |
th1a | Uh... | 22:05 |
th1a | Sometimes this doesn't work remotely. | 22:05 |
replaceafill | sorry :( | 22:06 |
th1a | Line 2: "© the Shuttleworth Foundation 2003 - 2011; SchoolTool™ is a trademark of the Shuttleworth Foundation. | 22:06 |
th1a | " | 22:06 |
replaceafill | that's better ;) | 22:06 |
th1a | Line 3: the Shuttleworth Foundation 2003 - 2011: We support exceptional people to change the world in extraordinary ways. | 22:06 |
th1a | Er | 22:06 |
th1a | no | 22:06 |
replaceafill | yeah sometimes doesnt work :P | 22:07 |
th1a | Line 3: The Shuttleworth Foundation: We support exceptional people to change the world in extraordinary ways. | 22:07 |
th1a | And make the TSF link in line 3 the only link in the footer. | 22:07 |
replaceafill | 3 TSF... | 22:11 |
replaceafill | th1a refresh | 22:11 |
ignas | th1a, I think we did 3 redesigns of our product in 2 years :) | 22:12 |
th1a | You know... I think you can just add line 2 to the end of line 1 with a couple spaces between. | 22:12 |
th1a | And we'll be done. | 22:12 |
replaceafill | refresh | 22:13 |
replaceafill | more space? | 22:13 |
th1a | OK... let's leave this for a while... | 22:14 |
replaceafill | i used the infamous for the moment ;) | 22:14 |
replaceafill | ok | 22:14 |
th1a | Now... | 22:14 |
th1a | The tables have a dotted divider above the first row. | 22:15 |
th1a | Can we control that? | 22:15 |
th1a | I'm thinking we can tweak that a little to make a headerless table acceptable. | 22:15 |
replaceafill | th1a refrsh | 22:16 |
th1a | What if we have a 2px gray line at top -- particular for headerless tables? | 22:17 |
replaceafill | th1a like that? | 22:20 |
replaceafill | hhmm th1a said "at top" | 22:20 |
th1a | The same gray as the dotted line, and without the label/value. | 22:20 |
th1a | The words, that is. | 22:21 |
replaceafill | these changes should apply only to tables inside accordions, correct? | 22:22 |
th1a | Uh... | 22:23 |
th1a | Not necessarily. | 22:24 |
replaceafill | hhmm | 22:24 |
th1a | I only really want it to show up if there is no header. | 22:24 |
th1a | BUT, | 22:24 |
th1a | you can probably blend it into the header where there is one. | 22:24 |
replaceafill | ah ok | 22:24 |
th1a | It can be the same gray. | 22:24 |
replaceafill | th1a refresh | 22:28 |
replaceafill | something like that? | 22:28 |
th1a | Yeah. | 22:29 |
replaceafill | i removed the headers from general information | 22:29 |
replaceafill | contacts | 22:29 |
th1a | 1px might be fine. | 22:29 |
replaceafill | and attributs | 22:29 |
replaceafill | changed to 1px | 22:29 |
th1a | That's fine, I think. | 22:29 |
replaceafill | and http://69.164.203.135:6660/persons still looks fine :) | 22:30 |
th1a | Although we blew our column spacing again. | 22:30 |
replaceafill | ah true | 22:30 |
th1a | That's definitely better. | 22:30 |
th1a | OK, footer line 1 is the server info. | 22:31 |
th1a | Line 2: © 2003 - 2011 the Shuttleworth Foundation: We support exceptional people to change the world in extraordinary ways. | 22:32 |
th1a | We don't need the trademark on every page. | 22:32 |
th1a | Or at least Launchpad doesn't think so. | 22:32 |
replaceafill | fixed the widths again | 22:32 |
th1a | Nice to have plenty of related projects you know someone else has vetted. | 22:32 |
th1a | Good. | 22:32 |
replaceafill | changing the footer | 22:33 |
replaceafill | changed | 22:34 |
th1a | PERFECT. | 22:35 |
th1a | (almost) | 22:35 |
replaceafill | :D | 22:35 |
th1a | I don't know if "We" should be capitalized. | 22:35 |
replaceafill | lowercased | 22:35 |
th1a | Upper. | 22:36 |
th1a | :-D | 22:36 |
replaceafill | changed | 22:36 |
th1a | Do you want to take a first cut at a relationships view? | 22:38 |
replaceafill | sure | 22:38 |
replaceafill | but | 22:38 |
replaceafill | can i havve like 30 mins to get lunch | 22:39 |
th1a | y | 22:39 |
replaceafill | will you be around after that? | 22:39 |
th1a | We're just having sandwiches for supper. | 22:39 |
replaceafill | :D | 22:39 |
th1a | So yes, for a while. | 22:39 |
replaceafill | k, bb in 30 | 22:39 |
aelkner | th1a, i'm still working on the modal dialog for person preferences | 22:41 |
aelkner | it's a bit tricky because the new flourish view macros don't work the same as the old | 22:41 |
aelkner | i think i'm going to have to recode the view from scratch because the old is not z3c | 22:42 |
aelkner | but i'll figure it out | 22:42 |
th1a | Probably you should just re-write it. | 22:43 |
aelkner | yeah, that's what i'm going to do | 22:43 |
replaceafill | didnt we have that already? | 22:43 |
replaceafill | person preferences as z3c form? | 22:43 |
th1a | This does sound familiar. | 22:44 |
aelkner | true, and i cheked | 22:44 |
aelkner | but modal_test is the branch that i worked on with replaceafill | 22:44 |
* replaceafill remembers saying "this is not a good example" | 22:44 | |
aelkner | and it isn't there | 22:44 |
replaceafill | well | 22:44 |
replaceafill | lunch time :P | 22:44 |
aelkner | it subclasses the other view | 22:44 |
aelkner | and that's based on BrowserView | 22:45 |
aelkner | not a z3c form | 22:45 |
aelkner | however, it uses the form macro | 22:45 |
aelkner | so i'm still working out what's going on in the modal_test branch | 22:45 |
*** jelkner has quit IRC | 22:45 | |
aelkner | ok, wait, correction | 22:46 |
aelkner | it is z3c | 22:46 |
aelkner | i've been looking at so many views, i'm getting them mixed up :) | 22:47 |
replaceafill | :D | 22:47 |
replaceafill | i know the feeeling | 22:47 |
aelkner | i was looking at the flourish branch where it failed to have replaceafill's change | 22:47 |
aelkner | yeah, i need to port your z3c version while i'm at it | 22:48 |
th1a | aelkner, Do reports have description properties? | 22:51 |
th1a | Yes they do. | 22:51 |
th1a | The biggest problem with this process is how awful the old version looks in comparison. | 22:55 |
replaceafill | :)) | 23:05 |
replaceafill | i was sad last night working in cambodia because of that :D | 23:05 |
replaceafill | ok, back | 23:06 |
th1a | OK. | 23:19 |
th1a | The contacts one is more complicated so let's do group. | 23:19 |
th1a | So what do we have here? | 23:19 |
th1a | A table | 23:20 |
th1a | of current groups. | 23:20 |
replaceafill | th1a a sec | 23:20 |
replaceafill | im resolving conflicts | 23:20 |
replaceafill | to push to trunk | 23:20 |
th1a | OK, so here I'd feel ok with having remove buttons per row. | 23:20 |
th1a | And for that matter, add buttons per row below. | 23:22 |
replaceafill | aelkner you may want to sync WITH trunk, "Added action links and contacts accordion for persons. Changed footer and made other css fixes" | 23:25 |
replaceafill | th1a i get the remove buttons part | 23:26 |
replaceafill | but "add buttons per row below" | 23:26 |
replaceafill | Baseball (remove) | 23:27 |
replaceafill | Soccer (remove) | 23:27 |
replaceafill | and below | 23:27 |
replaceafill | Chess (add) | 23:27 |
replaceafill | and so on? | 23:27 |
replaceafill | th1a never mind | 23:27 |
replaceafill | makes sense now :) | 23:27 |
th1a | Oh, missed that. | 23:28 |
replaceafill | th1a what about the search functionality? | 23:28 |
th1a | Yes, like we have in the persons view. | 23:28 |
aelkner | replaceafill, did you add a link for preferences? | 23:28 |
replaceafill | aelkner yes | 23:28 |
aelkner | cool, thanks | 23:28 |
replaceafill | th1a this is intended to be a single page at the beginning correct? | 23:29 |
replaceafill | i mean, no intention yet to make it dialog | 23:29 |
* replaceafill thinks about the filter widget (search form) | 23:30 | |
* aelkner goes to make dinner | 23:34 | |
th1a | replaceafill: Yes. | 23:36 |
th1a | That is, correct. | 23:36 |
th1a | Just improving the page. | 23:36 |
replaceafill | k | 23:36 |
th1a | I'd kinda like a choice to list groups from all years or just the current year. | 23:40 |
th1a | Er. | 23:40 |
th1a | No. | 23:40 |
th1a | Not. | 23:40 |
th1a | Forget that. | 23:40 |
replaceafill | :D | 23:40 |
replaceafill | just current year | 23:40 |
th1a | You can already do that. | 23:40 |
replaceafill | ah | 23:40 |
replaceafill | really? | 23:41 |
th1a | The accordion view should give all years, right? | 23:41 |
th1a | Or is that School Year column just for show. ;-) | 23:41 |
th1a | Yes, it will. | 23:41 |
th1a | OK. | 23:41 |
replaceafill | :D | 23:41 |
replaceafill | th1a the current groups view doesnt give me next years groups, unless the user is already a member of one | 23:44 |
replaceafill | 2012 groups are not shown in the "available groups" | 23:44 |
th1a | Ah. | 23:45 |
th1a | OK, that's a separate issue. | 23:45 |
replaceafill | ok | 23:45 |
th1a | But a bug! | 23:45 |
replaceafill | :D | 23:46 |
th1a | We do need a year column, to be sure. | 23:46 |
replaceafill | confirmed: | 23:47 |
replaceafill | @adapter(ISchoolToolApplication) | 23:47 |
replaceafill | @implementer(interfaces.IGroupContainer) | 23:47 |
replaceafill | that adapters looks for the active school year only | 23:47 |
th1a | Let's fix the widget first. | 23:48 |
replaceafill | k | 23:48 |
th1a | I mean, get the style/design/layout. | 23:48 |
replaceafill | yes | 23:48 |
th1a | I think this is fairly straightforward. | 23:48 |
replaceafill | i think we only need to change the template | 23:49 |
th1a | btw, last, fist snuck back into the person sidebar. | 23:49 |
replaceafill | it was always like that :P | 23:50 |
replaceafill | probably Alvaro Alvarez was not the best person to test this :D | 23:51 |
replaceafill | changing it to "full name" | 23:51 |
th1a | lol | 23:52 |
th1a | Wait, full name? | 23:52 |
th1a | Is that all the parts? | 23:52 |
replaceafill | first name last name | 23:52 |
replaceafill | ah sorry, no | 23:52 |
replaceafill | just those two attributes | 23:52 |
th1a | kk | 23:53 |
th1a | I'm already getting worried about length there... | 23:53 |
th1a | Gediminas's name barely fits. | 23:54 |
replaceafill | we have lots of space on the right ;) | 23:54 |
th1a | Yeah, we can just continue the name at right. | 23:54 |
replaceafill | menesis name is shown with two lines in my browser | 23:54 |
replaceafill | probably because i dont have the ubuntu fon | 23:55 |
replaceafill | t | 23:55 |
th1a | Oh, fine. | 23:55 |
th1a | As long as it doesn't run into the content area or break in some other horrible way. | 23:55 |
th1a | Sometimes I just assume the worst will happen. | 23:55 |
replaceafill | http://img651.imageshack.us/img651/1136/pantallazojs.png | 23:55 |
replaceafill | sorry i used a screenshot instead of a video ;) | 23:56 |
replaceafill | it's your "manager" nature ;) | 23:56 |
th1a | OK. It works. | 23:56 |
th1a | btw: http://font.ubuntu.com/web/ | 23:57 |
th1a | Add that. | 23:57 |
replaceafill | ah!?!? | 23:58 |
replaceafill | web fonts? | 23:58 |
replaceafill | changed to "first name last name" | 23:58 |
th1a | See if that works. | 23:59 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!