| *** ignas has joined #schooltool | 00:06 | |
| *** hoffman has quit IRC | 00:31 | |
| *** ignas has quit IRC | 00:45 | |
| *** menesis has quit IRC | 01:32 | |
| *** issyl0 has quit IRC | 02:35 | |
| *** issyl0 has joined #schooltool | 02:35 | |
| *** issyl0 has quit IRC | 02:35 | |
| *** issyl0 has joined #schooltool | 02:35 | |
| *** aks has joined #schooltool | 06:25 | |
| *** aks has joined #schooltool | 06:26 | |
| *** aks has joined #schooltool | 06:26 | |
| *** aks has joined #schooltool | 06:26 | |
| *** aks has quit IRC | 08:44 | |
| *** aks has joined #schooltool | 10:20 | |
| *** menesis has joined #schooltool | 10:27 | |
| *** aks has quit IRC | 10:40 | |
| *** aks has joined #schooltool | 10:49 | |
| *** aks has joined #schooltool | 10:49 | |
| *** menesis has quit IRC | 13:03 | |
| *** aks has quit IRC | 14:14 | |
| *** menesis has joined #schooltool | 14:28 | |
| *** ignas has joined #schooltool | 16:33 | |
| *** replaceafill has joined #schooltool | 17:44 | |
| aelkner | replaceafill, hey | 17:59 |
|---|---|---|
| replaceafill | hey aelkner | 18:00 |
| aelkner | how; it going? | 18:01 |
| replaceafill | good, i'm working on /email | 18:01 |
| replaceafill | you? | 18:01 |
| aelkner | i worked on the schoolyear add view, copying the old skin template to create a flourish version | 18:02 |
| aelkner | and i registered the datepicker widget stuff for flourish | 18:02 |
| aelkner | so it renders the button, but pushing it doesn't do anything | 18:02 |
| aelkner | could you check it out in firebug real quick? | 18:03 |
| replaceafill | what's the url? | 18:03 |
| aelkner | http://69.164.203.135:36660/schoolyears/add.html | 18:03 |
| aelkner | i pushed all my changes to trunk, too | 18:04 |
| replaceafill | you're going to remove that inline <style> right? :) | 18:06 |
| aelkner | i knew you'd say something about that :) | 18:06 |
| replaceafill | ;) | 18:06 |
| aelkner | what's the right way to move the style? | 18:06 |
| aelkner | can you point me to an example of local style? | 18:07 |
| replaceafill | we dont have local styles | 18:07 |
| aelkner | so where do i move it to? | 18:07 |
| replaceafill | leave it like that for now, put an <!-- XXX: CSS TODO --> on it please | 18:08 |
| replaceafill | we should probably just mark the table with a custom class | 18:08 |
| replaceafill | and set the right styles in table.css | 18:09 |
| aelkner | ok | 18:09 |
| replaceafill | about the [...] buttons | 18:09 |
| replaceafill | why do you expect those to open the jqueryui calendar widget? | 18:10 |
| replaceafill | they're for zc.datetimewidget | 18:10 |
| aelkner | i wasn't expecting anything different than the old skin | 18:11 |
| aelkner | are you saying we need to change that to use jqueryui? | 18:11 |
| replaceafill | ah, no, my bad, i understood you wanted the jquery-ui datepicker | 18:11 |
| replaceafill | "and i registered the datepicker widget stuff for flourish" | 18:11 |
| replaceafill | you want the zc.datetimewidget | 18:12 |
| aelkner | right, we just have this ongoing need to reregister old skin stuff for flourish | 18:12 |
| aelkner | anything new, like jqueryui, is another thing | 18:12 |
| aelkner | that would represent new functionality in the new skin | 18:13 |
| aelkner | but we hadn't discussed changing the datpickers in the new skin | 18:13 |
| aelkner | what do you think about the js at the top of the template | 18:13 |
| aelkner | the old skin version of the template | 18:14 |
| aelkner | had it fill in extrahead | 18:14 |
| aelkner | but we're not using page macros where we fill in extrahead | 18:14 |
| aelkner | instead we've been putting our js right in the body | 18:14 |
| replaceafill | yes, that's the approach yvl wants us to use | 18:15 |
| replaceafill | as long as it works... | 18:15 |
| aelkner | could there be something wrong with the syntax there? | 18:15 |
| replaceafill | let me update my trunk to get your changes | 18:15 |
| replaceafill | aelkner you know, the calendar is being rendered | 18:20 |
| replaceafill | have you noticed that? | 18:20 |
| aelkner | let me look | 18:21 |
| replaceafill | refresh the page, open firebug | 18:21 |
| replaceafill | check the footer element in firebug | 18:22 |
| replaceafill | click the [...] | 18:22 |
| replaceafill | and you'll see the calendar being inserted | 18:22 |
| replaceafill | if i set a z-index: 1 on it, it shows | 18:22 |
| replaceafill | blame .schooltool > .page having an z-index: 1 | 18:23 |
| aelkner | did you mean 'click the ...' after clicking the inspect button? | 18:23 |
| replaceafill | yes | 18:23 |
| replaceafill | the calendar div is inserted below <div class="schooltool"> | 18:24 |
| aelkner | so where's the caledar? | 18:24 |
| aelkner | :) | 18:24 |
| replaceafill | it's behind the page | 18:24 |
| replaceafill | .schooltool > .page has a z-index property | 18:24 |
| aelkner | i see it now | 18:24 |
| aelkner | go on | 18:24 |
| replaceafill | .schooltool contains: | 18:24 |
| replaceafill | .header, .page, .footer | 18:24 |
| replaceafill | because of the shadow effects, .page needs a z-index higher than .header | 18:25 |
| replaceafill | so, we set it to 1 | 18:25 |
| replaceafill | but apparently that's making the calendar not to show | 18:25 |
| replaceafill | because the calendar doenst have a z-index | 18:25 |
| replaceafill | so it's being displayed behind .page | 18:25 |
| aelkner | got it | 18:26 |
| aelkner | interesting | 18:26 |
| replaceafill | we can set its z-index to 1 or 2 | 18:26 |
| replaceafill | i our css | 18:26 |
| aelkner | is it that simple? | 18:26 |
| replaceafill | yes | 18:26 |
| replaceafill | div.calendar { z-index: 2} | 18:26 |
| aelkner | cool, o need to hack/register zc.datepicker! | 18:26 |
| replaceafill | you mean jqueryui? | 18:27 |
| aelkner | no i meant, if the zindex was set in python, maybe we wold need to subclass/register a hack to change it | 18:27 |
| aelkner | but if you can change it with css, cool | 18:27 |
| replaceafill | http://69.164.203.135:6660/schoolyears/add.html | 18:29 |
| aelkner | i haven't gotten used to the programming-like features css and selectors gives you | 18:29 |
| replaceafill | there, i set z-index to 2 for the div.calendar | 18:29 |
| aelkner | now that's a simple fix! | 18:30 |
| aelkner | me likey | 18:30 |
| replaceafill | :) | 18:30 |
| replaceafill | i'll push it to trunk | 18:30 |
| aelkner | cool, thanks | 18:31 |
| aelkner | so can you explain how the shadow effects problem/solution works? | 18:32 |
| replaceafill | fix pushed to trunk | 18:33 |
| replaceafill | "Added css fix for zc.datetimewidget calendar" | 18:33 |
| replaceafill | could you try it in your instance? | 18:33 |
| aelkner | ok | 18:33 |
| aelkner | works in my local/demo instances, thanks | 18:36 |
| replaceafill | great | 18:36 |
| aelkner | we'll need some z-index planning at some point | 18:36 |
| replaceafill | i rather staying out of z-indexes :) | 18:37 |
| aelkner | could you explain the shadow effects problem/solution | 18:37 |
| replaceafill | ah sure | 18:38 |
| replaceafill | so we have the header, the page, and the footer | 18:38 |
| replaceafill | if you check the shadows for the three | 18:39 |
| replaceafill | you notice the footer doesnt have any | 18:39 |
| replaceafill | and it seems like the header and the page share their shadow | 18:39 |
| replaceafill | but that's not possible, unless they're contained in a single element | 18:40 |
| replaceafill | however i didnt want the extra markup | 18:40 |
| replaceafill | i mean doing something like <div.wrapper><div.header><div.page> | 18:41 |
| replaceafill | just for the shadow effect | 18:41 |
| replaceafill | so, the header and the page have their own shadow | 18:41 |
| replaceafill | s | 18:41 |
| aelkner | so what's a shadow? :) | 18:41 |
| aelkner | is that the thing you see in firebug | 18:42 |
| replaceafill | you see the borders of the header and page | 18:42 |
| aelkner | when you inspect as you roll over elements? | 18:42 |
| replaceafill | and the breadcrumbs | 18:42 |
| replaceafill | and the top navbar | 18:42 |
| replaceafill | they have like a grey border | 18:42 |
| replaceafill | but it's not a "border: ..." property | 18:42 |
| replaceafill | it's a "box-shadow: ...." | 18:43 |
| replaceafill | anyway, since shadows collapse between the header and the page | 18:43 |
| aelkner | -moz-box-shadow: | 18:44 |
| replaceafill | i solved it with a hack | 18:44 |
| replaceafill | yes | 18:44 |
| aelkner | v | 18:44 |
| aelkner | -webkit-box-shadow: | 18:44 |
| replaceafill | that's for chrome to understand it | 18:44 |
| replaceafill | and safari i think | 18:44 |
| replaceafill | the page is moved like 4px up | 18:45 |
| replaceafill | so it goes 4px behind the header | 18:45 |
| replaceafill | then z-index: 2 is set on the header | 18:46 |
| replaceafill | and z-index: 1 on the page | 18:46 |
| replaceafill | meaning that the header is on top of the page | 18:46 |
| replaceafill | you need to move the page up, or you'd get a gap between the shadows... | 18:46 |
| replaceafill | it's tiny... but you can notice it :) | 18:47 |
| replaceafill | (if you look closely) | 18:47 |
| replaceafill | .schooltool > .page { | 18:47 |
| replaceafill | margin-top: -4px; /* Hack to close the */ | 18:47 |
| replaceafill | padding-top: 4px; /* gap in the shadows */ | 18:47 |
| aelkner | that's some tricky stuff | 18:48 |
| aelkner | perhaps it should be in its own file at least | 18:48 |
| aelkner | with a nice header comment explaining what you ust said here | 18:48 |
| aelkner | but anyway, thanks for the explanation! | 18:49 |
| replaceafill | i think we have to review the css closely before the release | 18:49 |
| replaceafill | to organize better, etc | 18:49 |
| aelkner | we need to budget, and by we i mean tom, time to refactor | 18:50 |
| aelkner | fix tests! | 18:50 |
| replaceafill | definitely! | 18:50 |
| aelkner | new test coverage | 18:50 |
| aelkner | css reorg for clarity ease of new use | 18:50 |
| aelkner | even view class refactor for optimal new class development | 18:51 |
| aelkner | perhaps that last one will get a big veto :) | 18:51 |
| replaceafill | :D | 18:52 |
| aelkner | i just want to make sure we have a big celebration when we get to a million lines of code :) | 18:52 |
| aelkner | anyway, thanks for the css lesson today | 18:54 |
| replaceafill | np, sorry that the z-indexes got in your way | 18:54 |
| aelkner | nah, that's ok, i knew you would be able to handle anything you broke :) | 18:54 |
| replaceafill | and dont forget to at least mark that inline <style> ;) | 18:55 |
| aelkner | i did, didn't push to trunk yet | 18:55 |
| replaceafill | thanks | 18:55 |
| *** menesis has quit IRC | 20:19 | |
| *** ignas has quit IRC | 20:28 | |
| aelkner | replaceafill, i'm having another css problem with errors on add school year | 21:31 |
| replaceafill | url? | 21:31 |
| aelkner | one sec, i have tp push | 21:32 |
| aelkner | http://69.164.203.135:36660/schoolyears/add.html | 21:35 |
| aelkner | choose dates from this month | 21:35 |
| aelkner | if you firbug the div where it says 'There were some errors" | 21:35 |
| aelkner | you see that there is a hidden div with the overlap error message | 21:35 |
| aelkner | div class="errors" | 21:36 |
| replaceafill | yes | 21:36 |
| replaceafill | the ul.errors | 21:36 |
| aelkner | display: none | 21:36 |
| aelkner | so that's on purpose :) | 21:37 |
| replaceafill | yes, th1a doesnt want errors displayed there | 21:37 |
| replaceafill | he wants them next to the widgets | 21:37 |
| replaceafill | btw | 21:37 |
| replaceafill | that's why your form should say: | 21:37 |
| replaceafill | formErrorsMessage = _('Please correct the marked fields below.') | 21:37 |
| replaceafill | all of them | 21:38 |
| replaceafill | base class!!! | 21:38 |
| replaceafill | :) | 21:38 |
| aelkner | :) | 21:38 |
| replaceafill | and | 21:38 |
| replaceafill | there's a js hack i've been using too: | 21:38 |
| replaceafill | basicperson/browser/templates/f_person_form.pt | 21:39 |
| replaceafill | see the <script> at the top | 21:39 |
| replaceafill | that's a hack to mark the error fields | 21:39 |
| replaceafill | i need to investigate how to set classes conditionally with z3c.form | 21:39 |
| replaceafill | (if that's possible) | 21:39 |
| replaceafill | for now, the hack uses jquery to mark the fields with errors | 21:40 |
| aelkner | yeah, i remember yvl scolding you for that bit of magic :) | 21:42 |
| replaceafill | yes | 21:42 |
| aelkner | i still couldn't tell you how that call works | 21:42 |
| aelkner | first sibling? | 21:42 |
| replaceafill | yes | 21:42 |
| replaceafill | it's the way z3c.form renders the widgets | 21:42 |
| aelkner | why? | 21:42 |
| replaceafill | it uses: | 21:43 |
| replaceafill | <div.row> | 21:43 |
| replaceafill | <div.label> | 21:43 |
| replaceafill | <div.widget> | 21:43 |
| replaceafill | <div.error> | 21:43 |
| replaceafill | so, if you get an error | 21:43 |
| aelkner | when you say <div.row> you mean <div class="row">? | 21:43 |
| replaceafill | you go to .prev() | 21:43 |
| replaceafill | yes | 21:43 |
| replaceafill | .prev() gets you to <div.widget> | 21:44 |
| aelkner | ah, shorthand | 21:44 |
| replaceafill | but div.widget could contain several tihngs | 21:44 |
| replaceafill | but the first is always the <input> or <textarea> or <select> | 21:44 |
| replaceafill | elements | 21:44 |
| replaceafill | so you add the class 'error' to that first element | 21:45 |
| replaceafill | stinks all over the place :) | 21:45 |
| replaceafill | but it works ;) | 21:45 |
| replaceafill | but i rather we find a nice way to set the 'error' class through z3c.form | 21:45 |
| *** hoffman has joined #schooltool | 21:46 | |
| replaceafill | once we do that, we remove those js hacks :) | 21:46 |
| replaceafill | hello hoffman! | 21:46 |
| aelkner | so addClass('error') adds the css class that causes the field to have a red outline, right? | 21:46 |
| replaceafill | yes | 21:46 |
| aelkner | hey hoffman | 21:47 |
| replaceafill | aelkner same effect when you focus the field | 21:47 |
| aelkner | the thing about the overlap error is that it is not a widget error | 21:47 |
| aelkner | it is a form error | 21:47 |
| aelkner | the message applies to the whole of the data, not one field | 21:48 |
| hoffman | Hey replaceafill & aelkner. | 21:48 |
| replaceafill | aelkner like an invariant error? | 21:48 |
| Lumiere | someone lost a letter | 21:48 |
| * Lumiere goes back to lurking | 21:48 | |
| aelkner | hoffman, status | 21:49 |
| aelkner | your last comment on the channel mided me that the schoolyear add didn't have everything the old one did | 21:49 |
| aelkner | which made me realize that i needed to make a flourish copy of the schoolyear_add template | 21:49 |
| aelkner | and then i got all the fields that are there in the old skin | 21:50 |
| aelkner | http://69.164.203.135:36660/schoolyears/add.html | 21:50 |
| aelkner | i then saw that i needed to add flourish registrationsfor the datepicker widget | 21:51 |
| aelkner | once i figured out what they were | 21:51 |
| aelkner | a side-effect of replaceafill fixing the shadow css was that the calendar was hidden | 21:51 |
| aelkner | but he was able to spot that quickly and fix it | 21:51 |
| aelkner | lately, i've been adding various registrations for content provides to flourish | 21:52 |
| aelkner | so that things like @@link or @@shortDate didn't crash | 21:52 |
| aelkner | and that has led me to where I am now where the new year overlap message | 21:52 |
| aelkner | renders but is hidden to a css rule you and replaceafill agreed on and implemented | 21:53 |
| aelkner | that hides the errors div for form errors | 21:53 |
| aelkner | we should talk about that after replaceafill has updated you, but that's my update | 21:53 |
| hoffman | I'm getting an iframe or something inside the year add form. | 21:54 |
| aelkner | ? | 21:54 |
| aelkner | replaceafill, can you follow the link to see what hoffman might be referring to? | 21:55 |
| replaceafill | ok | 21:55 |
| hoffman | It is a scroll bar inside the page. | 21:55 |
| hoffman | There is a separate scroll bar for the content area. | 21:56 |
| aelkner | are you using chrome? | 21:56 |
| hoffman | Not in this case. | 21:56 |
| replaceafill | confirmed, in chrome i get the same | 21:56 |
| aelkner | how about firefox? | 21:56 |
| aelkner | is this immediately upon calling p the link i posted or after hitting submit? | 21:57 |
| hoffman | Immediately. | 21:57 |
| replaceafill | yes | 21:57 |
| replaceafill | the second fieldset flows out of the parent div | 21:58 |
| aelkner | i'm not seeing it | 21:58 |
| *** menesis has joined #schooltool | 21:58 | |
| * replaceafill goes check the template | 21:58 | |
| replaceafill | aelkner you have a typo in the template | 21:59 |
| replaceafill | two <legend>s | 21:59 |
| replaceafill | missed the / in the second one | 21:59 |
| aelkner | fixing | 22:00 |
| aelkner | loading fix, please wait... | 22:01 |
| replaceafill | fixed in chrome | 22:01 |
| aelkner | fix, loaded | 22:01 |
| aelkner | you just tried before i said it was loaded? | 22:02 |
| replaceafill | yep | 22:02 |
| replaceafill | aelkner on the overlap error | 22:02 |
| replaceafill | we have a problem with our new "display errors next to widgets" approach and invariant validations | 22:03 |
| replaceafill | we discussed that with yvl like 2 or 3 mondays ago | 22:04 |
| replaceafill | and he told me that invariants were not designed to work like that | 22:04 |
| *** menesis has quit IRC | 22:04 | |
| replaceafill | and i should use a simple field validator instead | 22:04 |
| replaceafill | check: | 22:05 |
| replaceafill | person.browser.person.PasswordsMatchValidator | 22:05 |
| replaceafill | that one used to be an @invariant in the interface | 22:05 |
| aelkner | line number? | 22:07 |
| aelkner | i can't find it | 22:07 |
| replaceafill | have you synced with trunk? | 22:07 |
| replaceafill | that's on trunk | 22:07 |
| replaceafill | like 379 | 22:07 |
| aelkner | how long ago, i merged today | 22:07 |
| replaceafill | http://bazaar.launchpad.net/~schooltool-owners/schooltool/flourish/revision/2994 | 22:09 |
| aelkner | i see, so what is the upshot of the diff, where does the password match error get rendered? | 22:10 |
| aelkner | 'Supplied new passwords are not identical' | 22:10 |
| replaceafill | yes, but if you look closely, it looks in the request :( | 22:11 |
| replaceafill | anyway, the point is, that was an invariant check | 22:11 |
| replaceafill | that got converted to a field validator check | 22:11 |
| replaceafill | to get the error next to the widget | 22:12 |
| aelkner | widgets, you mean, because there are two password fields that are guilty of not matching | 22:12 |
| replaceafill | check the discriminator below | 22:13 |
| replaceafill | it's assigned to ['password'] only | 22:13 |
| replaceafill | i mean, the validator | 22:13 |
| replaceafill | so, you'll get the error only in that widget | 22:13 |
| aelkner | so the password match validator is called for the password field | 22:17 |
| aelkner | because it is registered to do so | 22:17 |
| replaceafill | yes | 22:17 |
| *** menesis has joined #schooltool | 22:17 | |
| aelkner | and it checks the contents of its data against that of the verify_password field | 22:17 |
| replaceafill | correct | 22:17 |
| aelkner | and raises the error if the are different | 22:17 |
| aelkner | so in addition to being a hack, it's special logic to the password problem | 22:18 |
| replaceafill | the hack is that i check the request to get the value of verify_password | 22:19 |
| replaceafill | the data hasn't been serialized yet | 22:19 |
| replaceafill | in the case of password fields that's not a problem | 22:19 |
| replaceafill | because the data manager doesnt do much on the field value | 22:19 |
| replaceafill | but if it were a Choice or something that would require more 'magic' | 22:20 |
| replaceafill | hoffman my report? | 22:21 |
| hoffman | Sure. | 22:21 |
| replaceafill | well, i cleaned /security.html | 22:21 |
| replaceafill | http://69.164.203.135:6660/security.html | 22:21 |
| replaceafill | doesnt look great, but looks better i think | 22:21 |
| replaceafill | and i finished the /email functionality | 22:22 |
| replaceafill | http://69.164.203.135:6660/email | 22:22 |
| hoffman | Security looks fine. | 22:22 |
| hoffman | email looks fine. | 22:23 |
| replaceafill | just a couple of comments: | 22:24 |
| replaceafill | http://69.164.203.135:6660/email/settings.html | 22:24 |
| replaceafill | i changed Enable from a single checkbox to two radio buttons | 22:24 |
| replaceafill | also, do we want to keep the red/green message colors for Server Status? | 22:25 |
| hoffman | We'll have a new palette. | 22:25 |
| replaceafill | ah, true | 22:25 |
| hoffman | I signed the estimate with Schwa today, btw. | 22:25 |
| hoffman | So that's happening. | 22:25 |
| replaceafill | great | 22:25 |
| * replaceafill looks lots of css changes in the horizon :) | 22:26 | |
| replaceafill | my last comment is about the functionality of the settings | 22:26 |
| replaceafill | for the password | 22:26 |
| hoffman | What is the "Done" story for these pages? | 22:26 |
| hoffman | (also, aelkner) | 22:26 |
| replaceafill | ah also that | 22:26 |
| hoffman | Basically, we should always be asking that. | 22:26 |
| replaceafill | should we add a Done button to forms that submit success to themselves? | 22:27 |
| hoffman | Well, maybe they shouldn't be doing that. | 22:27 |
| * hoffman hasn't actually tried these forms yet. | 22:27 | |
| hoffman | otoh, we don't really know exactly where "Done" is taking you in the end for these manage forms. | 22:28 |
| hoffman | We haven't settled on School | Application definitively. | 22:28 |
| hoffman | We'll nail that down next week. | 22:29 |
| hoffman | replaceafill: Do you still have enough things in your queue? | 22:30 |
| replaceafill | if you're ok with /email i was thinking of jumping to /control | 22:31 |
| hoffman | Why does email settings go to itself? | 22:32 |
| replaceafill | just to confirm your changes were saved :) | 22:32 |
| replaceafill | i though of that since it's a change in the state of the app | 22:33 |
| hoffman | Why don't we add the settings to /email then. | 22:33 |
| replaceafill | ah | 22:33 |
| hoffman | er... no, ok, I see. | 22:34 |
| hoffman | This does need some tweaking. | 22:34 |
| hoffman | What is the table on /email telling me? | 22:34 |
| replaceafill | i think /email/settings.html should go to a different place than the queued messages | 22:34 |
| replaceafill | hoffman right now, not much | 22:35 |
| hoffman | What is it supposed to be telling me? | 22:35 |
| replaceafill | it used to have almost all the fields of IEmail | 22:35 |
| replaceafill | what your queued messages are | 22:35 |
| hoffman | Is the table telling me the queued messages? | 22:36 |
| hoffman | Is there only one SMTP server per SchoolTool instance? | 22:36 |
| replaceafill | yes | 22:36 |
| hoffman | OK, so first off, that table needs to be labeled. | 22:36 |
| hoffman | And perhaps just a view of its own. | 22:36 |
| hoffman | And just make the main page the settings view. | 22:37 |
| hoffman | And an edit pencil to edit it. | 22:37 |
| hoffman | Which sends you back to the main view. | 22:37 |
| hoffman | Then you don't need a settings action. | 22:37 |
| replaceafill | nice! | 22:37 |
| replaceafill | i like it | 22:37 |
| replaceafill | :) | 22:38 |
| hoffman | But you can add a "Mail log" action & view. | 22:38 |
| replaceafill | Mail log? you mean to track all the messages sent? | 22:38 |
| hoffman | Or queue. | 22:39 |
| hoffman | That's what we've got, right? | 22:39 |
| replaceafill | we dont track successfully sent messages | 22:39 |
| hoffman | I'm NOT suggesting new functionality here, intentionally. | 22:39 |
| replaceafill | we just track stuck messages | 22:39 |
| hoffman | The problem is you didn't label that table so I'm confused! | 22:40 |
| replaceafill | :) | 22:40 |
| replaceafill | my bad | 22:40 |
| replaceafill | well, we use "Email Queue" | 22:40 |
| replaceafill | so instead of Mail log, should be "Email queue" | 22:41 |
| replaceafill | right? | 22:41 |
| hoffman | If that's what it is. | 22:42 |
| replaceafill | yes | 22:42 |
| replaceafill | what title should i use for the link | 22:42 |
| replaceafill | like Actions | 22:42 |
| replaceafill | Actions | 22:42 |
| replaceafill | - Send Test | 22:42 |
| replaceafill | XXX | 22:43 |
| replaceafill | - Email queue | 22:43 |
| replaceafill | (sorry, i meant for the link group) | 22:43 |
| hoffman | Just don't call them buttons. ;-) | 22:44 |
| replaceafill | :D | 22:44 |
| hoffman | Yeah... | 22:44 |
| hoffman | Email queue isn't really an action. | 22:44 |
| replaceafill | right | 22:44 |
| hoffman | But... stick it there for now. | 22:44 |
| replaceafill | ok | 22:44 |
| replaceafill | will work on that after lunch :) | 22:44 |
| hoffman | aelkner: You have stuff to do? | 22:46 |
| aelkner | yes, still stuff to do with schoolyears | 22:50 |
| aelkner | can i do terms after that? | 22:50 |
| aelkner | it will have similar issues with dates and overlaps and such | 22:50 |
| hoffman | OK. | 22:50 |
| hoffman | Also the organization will be a little different since they won't be contained by years anymore in terms of navigation. | 22:51 |
| aelkner | oh, how would the user create terms? | 22:51 |
| hoffman | Well, from /terms, I guess. | 22:51 |
| hoffman | you | 22:51 |
| hoffman | will have to designate the year? | 22:51 |
| hoffman | I | 22:52 |
| hoffman | am not sure. | 22:52 |
| aelkner | hm | 22:52 |
| hoffman | I've not really thought about it in detail. | 22:52 |
| hoffman | But you won't be making other things contained by years from within the year. | 22:52 |
| aelkner | with /terms /courses /groups, all the same issue with how the user communicates the year | 22:54 |
| aelkner | we could assume active year | 22:54 |
| hoffman | Well... by default perhaps, but they'll need to be able to select it. | 22:54 |
| hoffman | Probably in most cases you're setting up the NEXT year anyhow. | 22:55 |
| aelkner | i must say, i'm ot sure why we would want to change all of this | 22:55 |
| aelkner | keep in mind that a lot of work has been done with traversal adapters | 22:55 |
| aelkner | and views that work off of certain contexts | 22:55 |
| aelkner | schooyear/addTerm.html i think is an example | 22:56 |
| hoffman | Alternately, you could select the year when you initiate the add, and just end up adding from within the year. | 22:56 |
| aelkner | i suppose we could wrangle the new view to render the links we need | 22:56 |
| hoffman | Just making it more transparent to the user. | 22:56 |
| hoffman | Or, perhaps less transparent actually. | 22:56 |
| aelkner | :) | 22:57 |
| hoffman | Hrm... | 22:57 |
| aelkner | more seemless, less transparanet | 22:57 |
| hoffman | Perhaps what you see in terms is a table with subheaders per year. | 22:58 |
| aelkner | i think the user likes the idea of thinking about a schoolyear by itself | 22:58 |
| hoffman | And an edit pencil next to each year. | 22:58 |
| aelkner | ah, yes, so /terms is an accoridon view | 22:58 |
| hoffman | I'm pretty certain no other application would work that way. | 22:58 |
| aelkner | with the active year open by default | 22:58 |
| hoffman | I don't think it needs to be an accordion. | 22:58 |
| hoffman | Five years with four terms is still not a very big table. | 22:59 |
| aelkner | when you no other application, is there another application with the same type of problem? | 22:59 |
| hoffman | Every other student information system. | 22:59 |
| hoffman | Our approach tends to be informed by the ZODB structure. | 23:00 |
| aelkner | if we have a table of all the terms., historically, that could beg the question by the user: | 23:00 |
| aelkner | why do i want to see these other years? | 23:00 |
| aelkner | i don't carfe about them anymore | 23:00 |
| aelkner | and having them all come up as a default behavior could be a real head-scratcher | 23:01 |
| hoffman | OK... sort of the point here is that the old way has people navigating through year/term more than they should be anyhow. | 23:01 |
| hoffman | In particular through year. | 23:01 |
| hoffman | So basically the admin should be the only person looking at term, when he's administering terms. | 23:02 |
| hoffman | So seeing old ones isn't that weird. | 23:02 |
| hoffman | And perhaps helpful! | 23:02 |
| hoffman | Also, we'll be moving reports too so they won't be, say, going to terms to generate reports. | 23:02 |
| hoffman | This'll just be when they're working directly with terms. | 23:03 |
| hoffman | Or maybe they'll go to terms for reports as one route, but deprecating it. | 23:04 |
| hoffman | Anyhow, I'm liking table/subtable by year as the main index. | 23:05 |
| aelkner | oh, and you wanted the terms table to be descending year, so it wouldn't be that annoying | 23:05 |
| hoffman | For, say, groups we'll probably want accordions, because you can have a lot more groups per year than terms. | 23:05 |
| aelkner | so, just in case i clear the schooyears task before i can reach you, /term should be a table | 23:06 |
| aelkner | sorted in reverse timewise | 23:06 |
| aelkner | so last term is first row | 23:06 |
| aelkner | that term being either last term of current active ear | 23:06 |
| aelkner | or last term of new year that hasn't been activated yet | 23:07 |
| aelkner | sound like a good first thing to do for coding /terms? | 23:07 |
| hoffman | Yes. | 23:07 |
| aelkner | cool, sounds like a straightforward thing to start with | 23:07 |
| hoffman | kk | 23:08 |
| * hoffman goes back outside. | 23:09 | |
| *** ignas has joined #schooltool | 23:21 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!