*** yvl has joined #schooltool | 10:22 | |
*** khildin has joined #schooltool | 10:38 | |
*** replaceafill has joined #schooltool | 15:48 | |
*** th1a has joined #schooltool | 16:20 | |
th1a | hi aelkner, yvl, replaceafill. | 16:30 |
---|---|---|
aelkner | mornign | 16:30 |
yvl | good morning | 16:30 |
replaceafill | good morning/afternoon | 16:30 |
th1a | aelkner: What's your condition? | 16:31 |
aelkner | i'm much better thanks | 16:31 |
aelkner | yvl, thanks for the email, it worked to rebranch everythin | 16:32 |
yvl | great | 16:32 |
aelkner | after that worked, i fixed the problem in my main inbox simply by rebranching your branch | 16:32 |
aelkner | that's annoying because i had know way to know that would have been necessary | 16:32 |
aelkner | i guess my original suspicion was correct about a networking problem while running bin/buildout | 16:33 |
aelkner | i think in the future, the first thing to try when weird things like that happen is make realclean | 16:33 |
aelkner | it just didn't occur to me that i would need to do that | 16:34 |
aelkner | bin/buildout throws a lot errors even when evrything is ok | 16:34 |
aelkner | messages like 'Skipping' , for instance | 16:34 |
aelkner | anyway, lesson leaned, but i appreciate you taking the time to provide a working scenario | 16:35 |
yvl | no problem | 16:36 |
yvl | glad it worked | 16:36 |
aelkner | th1a, i should have a resource report to show you this afternoon | 16:36 |
aelkner | and now i can do any other report like the attendance report you suggested | 16:36 |
aelkner | replaceafill, when i run the section roster report the terminal output has two errors even though the report works | 16:37 |
aelkner | Directive 'pto_header' could not be processed and was ignored. (file section_roster_art_a_1211190929.pdf, line 144) | 16:37 |
aelkner | same for the trailer | 16:37 |
aelkner | do you get that? | 16:37 |
replaceafill | aelkner, no, i haven't used that report in some time now | 16:37 |
aelkner | could you try that real quick right now so i can compare? | 16:38 |
replaceafill | what's the branch again? | 16:38 |
aelkner | oh, you don't have a reports branch at the moment? | 16:38 |
replaceafill | nope | 16:38 |
yvl | yeah, aelkner | 16:38 |
aelkner | that's ok, never mind | 16:38 |
yvl | it throws that error | 16:39 |
yvl | haven't looked at that yet | 16:39 |
aelkner | i won't worry about it if the report works, i was just curious | 16:39 |
yvl | weird thing is that is not ignored :) | 16:39 |
yvl | pto directive is used when you want to add "continued on next page" messages | 16:40 |
yvl | also - repeat titles above tables and such | 16:40 |
yvl | please continue | 16:41 |
aelkner | ok, i'll let everyone know if i think a failure of a report to work might be related | 16:41 |
aelkner | otherwise, i won't worry about it | 16:41 |
aelkner | so that's it for me, just one thing though | 16:41 |
aelkner | th1a, you never asked for out October invoices | 16:42 |
th1a | That's because I'm not paying anyone this month. | 16:42 |
th1a | Sorry I forgot to mention that. | 16:42 |
aelkner | :) | 16:42 |
th1a | I'm sure you all have plenty of money in the bank. | 16:43 |
yvl | :D | 16:43 |
aelkner | well, now that we one the election, there was that million dollar deposit i noticed | 16:43 |
th1a | OK, so moving on. | 16:43 |
th1a | Thanks aelkner. | 16:43 |
aelkner | i'll look for you this afternoon | 16:43 |
th1a | Lets hear from everyone and then get to some general report issues. | 16:44 |
th1a | so... yvl? | 16:44 |
yvl | I'm slowly working towards finishing the remade roster report | 16:44 |
yvl | and have added some plumbing on template slots | 16:45 |
yvl | I think I'll try adding some demoish personal info report | 16:46 |
yvl | that's it | 16:47 |
yvl | also - I'd like to book plane tickets at some point | 16:47 |
* yvl done | 16:48 | |
th1a | Yes, we'll discuss that last. | 16:48 |
th1a | Thanks yvl. | 16:48 |
th1a | replaceafill? | 16:48 |
replaceafill | ok | 16:48 |
replaceafill | i've been working on the labels + titles sorting | 16:49 |
replaceafill | for skills | 16:49 |
replaceafill | and skillsets, nodes, documents | 16:49 |
replaceafill | there were 11 views listing labels + titles somehow | 16:49 |
replaceafill | i've changed 9 to use table formatters with sorting ability | 16:50 |
replaceafill | i finally understood what the subsort parameter does for columns :) | 16:50 |
replaceafill | i also realized that we need some kind of subscriber, so the section skills stays in sync with the course skill | 16:50 |
replaceafill | at least for labels + titles | 16:51 |
replaceafill | not sure about other attributes, like required and such | 16:51 |
replaceafill | i also asked glenda for the new verso skills xls | 16:52 |
replaceafill | apparently sites in the pilot are still not using it | 16:52 |
replaceafill | oh | 16:52 |
replaceafill | and today i confirmed this bug: | 16:52 |
replaceafill | https://bugs.launchpad.net/schooltool/+bug/1080645 | 16:52 |
replaceafill | i know how to fix it (similar to http://bazaar.launchpad.net/~schooltool-owners/schooltool/flourish/revision/3375) | 16:53 |
replaceafill | parameters need to be encoded before passed to redirect | 16:53 |
yvl | yep :/ | 16:53 |
replaceafill | so i'll fix that and write a similar stest | 16:54 |
aelkner | can we get this stuff into trunk at some point soon? | 16:54 |
replaceafill | i have one question for yvl | 16:54 |
aelkner | it helps to be able to see the changes come in | 16:54 |
yvl | listening | 16:55 |
replaceafill | is it possible to override a view without using a skin? | 16:55 |
replaceafill | here's the scenario: | 16:55 |
replaceafill | jelkner wants some customization in the mygrades view for cando | 16:55 |
replaceafill | he wants me to insert some columns with schooltool.quiz information | 16:55 |
replaceafill | but afaik that's not possible without creating a new skin, right? | 16:56 |
yvl | well, it is possible with includeOverrides | 16:56 |
replaceafill | from one plugin to another plugin? | 16:56 |
yvl | could work | 16:57 |
replaceafill | ah ok | 16:57 |
yvl | or you could put it in a zcml slug | 16:57 |
replaceafill | i'll try that | 16:57 |
yvl | it could add a bit of maintenance though ;) | 16:57 |
replaceafill | zcml slug? | 16:58 |
yvl | /etc/schooltool/standard/plugins | 16:59 |
replaceafill | ah | 16:59 |
yvl | add override_this.zcml | 16:59 |
replaceafill | like we used to do with the gradebook | 16:59 |
yvl | that has includeOverrides | 16:59 |
yvl | yes | 16:59 |
replaceafill | ah got it | 16:59 |
replaceafill | thanks i'll try that! | 16:59 |
yvl | but it should also work from plugin.zcml | 16:59 |
yvl | in the package | 16:59 |
replaceafill | right | 16:59 |
yvl | (if it uses z3c.autoinclude of course) | 17:00 |
replaceafill | i've been using configure.zcml | 17:00 |
replaceafill | maybe that's why i get configuration errors | 17:00 |
yvl | you did try with includeOverrides though, right? | 17:00 |
aelkner | ah, that might explain the problem i was having a while back wth schooltool.courseinfo | 17:00 |
replaceafill | yvl, yes | 17:00 |
aelkner | i got configuration errors, too, when i tried to includeOverrides | 17:01 |
replaceafill | ok, that's it from me, thanks | 17:01 |
yvl | mm | 17:02 |
yvl | you know | 17:02 |
aelkner | so, noone answered my question about trunk, when will the reports stuff get in there? | 17:02 |
yvl | maybe we should just add overrides.zcml to all our plugins | 17:02 |
replaceafill | ah | 17:02 |
replaceafill | a standard file everywhere | 17:02 |
replaceafill | to do this kind of stuff | 17:02 |
aelkner | that's a good idea | 17:02 |
yvl | and make those included from z3c.autoinclude | 17:03 |
yvl | after everything else is in | 17:03 |
th1a | aelkner: Not this week. | 17:03 |
aelkner | th1a, ok, np | 17:03 |
replaceafill | yvl, so, order really matters in the inclusions, right? | 17:03 |
yvl | I think so | 17:03 |
replaceafill | good to know :) | 17:03 |
aelkner | also, the z3c.autoinclude thing, right? | 17:03 |
replaceafill | i'll try that, schooltool.quiz setup is similar to cando's, gradebook's, etc | 17:04 |
yvl | well, z3c.autoinclude gets processed at one point | 17:05 |
yvl | see | 17:05 |
yvl | flourish/skin/instance/configure.zcml | 17:05 |
yvl | includePlugins | 17:05 |
aelkner | ok, i'll definitely bookmark today's log for when i have to look at schooltool.courseinfo again | 17:06 |
th1a | anything else replaceafill? | 17:09 |
replaceafill | th1a, no that's it | 17:09 |
replaceafill | will be done with these views today | 17:09 |
th1a | OK. | 17:10 |
th1a | That's another one of those changes that ended up being more complicated than it looked. | 17:10 |
th1a | Thanks replaceafill. | 17:10 |
th1a | OK, so one big reports issue is grids. | 17:11 |
th1a | Both grids in general and grids with diagonal headers. | 17:11 |
th1a | Where are we with either yvl? | 17:12 |
yvl | not started on those yet | 17:12 |
yvl | well, we do have few styles | 17:12 |
yvl | covering most of "tables" and "lists" part of the style guide | 17:12 |
yvl | but nothing for gradebookish grids yet | 17:13 |
yvl | they're on my todo list though :) | 17:13 |
th1a | Should we work on reports without grids then, I presume. | 17:13 |
th1a | A lot of them end up having grids of one kind or another. | 17:14 |
yvl | it would be good to know types of grids | 17:15 |
yvl | but we can easily add a very simple table grid, and work from there | 17:15 |
th1a | I don't have anything too fancy in mind. | 17:16 |
th1a | A grid, and a grid with diagonal headers. | 17:16 |
th1a | I just don't want to do a bunch in what will turn out to be the wrong way. | 17:16 |
yvl | translation: a grid, and a fancy grid :) | 17:16 |
th1a | Running off the page is a big issue. | 17:17 |
yvl | true | 17:17 |
yvl | so | 17:17 |
yvl | we do have to specify column widths | 17:17 |
th1a | In fact, we need to make a point of testing that for each of these as we write them. | 17:17 |
yvl | thus we can calculate how many columns fit, and when we should split a table into two tables | 17:18 |
yvl | I meant: we must | 17:18 |
th1a | Yes, splitting into two will be the right choice sometimes. | 17:18 |
yvl | there's one catch though | 17:19 |
yvl | assume the table T runs out both horizontally and vertically | 17:19 |
yvl | we split it vertically into two: T-left and T-right | 17:19 |
yvl | and automatics will handle the horizontal split | 17:20 |
yvl | so we'll get | 17:20 |
yvl | page 1: T-left | 17:20 |
yvl | page 2: T-left continued | 17:20 |
yvl | page 3: T-right | 17:20 |
yvl | page 4: T-right continued | 17:20 |
yvl | I hope it's ok, because this is how it works | 17:20 |
th1a | It is either that or just not allow the too-wide table. | 17:21 |
yvl | yes | 17:21 |
yvl | in some cases we won't be able to limit ourselves probably | 17:22 |
th1a | Or just shrink them. | 17:22 |
yvl | also an option | 17:22 |
th1a | How are we dealing with page size at this point? | 17:23 |
th1a | Does that have to be hard-wired? | 17:23 |
yvl | no | 17:23 |
yvl | but we assume it is | 17:23 |
yvl | A4 | 17:24 |
yvl | we can make it flexible of course | 17:24 |
th1a | Well, we don't use A4 paper here... | 17:24 |
th1a | Also, in particular allowing landscape is useful. | 17:24 |
th1a | So what kind of overhead are we looking for to support different sizes/alignments? | 17:25 |
th1a | Orientation? | 17:25 |
yvl | ? | 17:27 |
yvl | depends? | 17:27 |
th1a | I mean, do we need to bake that into our infrastructure here? | 17:28 |
yvl | as we're just starting, putting an extra app preference for paper size is not that hard | 17:28 |
yvl | well, we do need to start handling | 17:28 |
yvl | it | 17:28 |
yvl | that means - not assume margins and such | 17:29 |
replaceafill | what about a report options dialog? | 17:29 |
yvl | sure | 17:29 |
yvl | and store it in app prefs | 17:29 |
yvl | we can even call it Print options | 17:29 |
yvl | or something | 17:29 |
yvl | it will probably be mostly ok (as in - we won't need to calculate much) | 17:30 |
yvl | except for some corner cases | 17:31 |
yvl | like | 17:31 |
th1a | Well, that gets right to the other issue I have jotted down here which is reports which require an intermediate dialog. | 17:31 |
yvl | how many columns fit horizontally and the text is still readable | 17:31 |
yvl | oh, report options dialog - yes :) | 17:32 |
replaceafill | :) | 17:32 |
th1a | I would say the main thing about those corner cases is that we need to allow the user to print one out and if it doesn't work, have some way to fix it. | 17:32 |
th1a | If you can say "oh, too many columns, but I can select which columns will print and fix it" | 17:33 |
th1a | Then you're ok. | 17:33 |
yvl | right | 17:33 |
th1a | You don't necessarily need to automagically guess right every time. | 17:33 |
yvl | we just need to keep those cases in mind when doing new reports | 17:33 |
th1a | I'm thinking the only tables that have to split horizontally are big grids that you might want to hang on the wall. | 17:34 |
th1a | Like a big master schedule. | 17:34 |
th1a | But otherwise, I think people will just say WTF if we do that automatically. | 17:34 |
yvl | you're probably right | 17:35 |
th1a | OK... so. | 17:38 |
th1a | Is there anything in particular we should do plumbing wise to deal with dialogs for reports that have options, including page orientation/size? | 17:38 |
yvl | user-defined page orientation... need to test, don't know | 17:39 |
yvl | page size... I think replaceafill used page_size and margins in all calculations | 17:40 |
yvl | so just need to check | 17:40 |
yvl | oh, also for reports that have options... | 17:42 |
yvl | if we want to set school-wide defaults, we need to write a view | 17:43 |
yvl | and if we want to allow overriding these defaults for each report - we'll need to update all report dialogs | 17:43 |
yvl | but that is it | 17:43 |
th1a | What about the dialog itself. | 17:44 |
th1a | Do we want some kind of standardizing widgetry? | 17:44 |
yvl | widgetry - no | 17:46 |
yvl | but I guess we'll do a default want to download the pdf dialog form | 17:47 |
yvl | others will need to extend it | 17:47 |
th1a | OK... | 17:48 |
th1a | So... these are things for yvl's to do. | 17:49 |
th1a | List. | 17:49 |
yvl | ok | 17:50 |
yvl | just reiterating: | 17:50 |
th1a | Now... I'm gathering that the immediate takeaway for aelkner is to use pages_size and margins and whatever else in his templates so they do size dynamically? | 17:50 |
yvl | (to figure out priorities) | 17:50 |
yvl | yes, th1a | 17:50 |
yvl | - dialog to configure the page sizes and margins | 17:51 |
yvl | -- some default dropdown of page sizes | 17:51 |
yvl | - school-wide page size options | 17:51 |
yvl | other things I could/want to do | 17:52 |
yvl | - finish tweaking default page template, add school logo | 17:52 |
yvl | - write a test report that includes different sections (person info seems about right) | 17:53 |
yvl | - write a grid that has slanted column titles | 17:53 |
yvl | that's it for now | 17:54 |
yvl | the "I want to do" is made of stuff that has some unanswered questions | 17:55 |
yvl | for example | 17:55 |
yvl | if we add multiple sections to the report | 17:55 |
th1a | OK, so if we can deal with the page size thing by writing the templates carefully, we can hold off on the choice machinery. | 17:55 |
yvl | how will we specify title on top of the page? | 17:56 |
yvl | it's baked into page template | 17:56 |
th1a | I would say 3,4,5,1,2 above. | 17:56 |
yvl | ok | 17:56 |
th1a | Which page template? | 17:56 |
yvl | RML page template | 17:56 |
yvl | it's the format thing | 17:57 |
yvl | we need to have convenient machinery that allows plugging in different parts into the story | 17:57 |
yvl | (and we do have it) | 17:57 |
yvl | like... | 17:57 |
yvl | School tab in web | 17:57 |
yvl | or Person home | 17:57 |
th1a | I don't think title has the same role in a printed report. | 17:58 |
yvl | but we also probably need different page templates, that are almost the same, but have different title and header text(s) | 17:58 |
yvl | I'm not sure we're on the same page here, th1a | 17:59 |
th1a | I don 't think so. | 17:59 |
yvl | I was talking about the top "band" in headlines | 17:59 |
yvl | that says... "STUDENT PROFILE" | 18:00 |
yvl | or "REPORT CARD" | 18:00 |
yvl | I assume at some point we want to be able to request aggregate reports | 18:00 |
yvl | that add all report cards after student profile | 18:00 |
th1a | Hm. | 18:01 |
th1a | I don't think so. | 18:02 |
th1a | Or, we're thinking of different things. | 18:02 |
th1a | But also, I don't think we really want any boilerplate like all reports have a H1 title at top. | 18:02 |
yvl | so... | 18:03 |
yvl | what kinds of boilerplate do we want? | 18:03 |
yvl | we now have the one from guidelines | 18:04 |
th1a | Essentially optional letterhead type stuff. | 18:04 |
yvl | the one that's always the same | 18:04 |
th1a | About the school. | 18:04 |
yvl | H1 | 18:04 |
yvl | 4 lines subtitles at left | 18:04 |
yvl | 6 lines at right | 18:04 |
* th1a should probably look at the guidelines. ;-) | 18:04 | |
th1a | Oh, that. | 18:05 |
yvl | yes | 18:06 |
yvl | so I don't think we want to enforce it | 18:06 |
th1a | Well, yes, I see. | 18:06 |
yvl | but we probably want to bake it into our "simple letterhead" | 18:06 |
th1a | No, actually, sorry, it is fine the way Vinny has it. | 18:06 |
yvl | kk | 18:07 |
th1a | If we could decide where a school logo should go... | 18:07 |
yvl | or Vinny could decide where "page 1 of 4" should go... :P | 18:08 |
th1a | You guys have to remember that if you don't tell me what to look at I'll just use my imagination. | 18:08 |
yvl | ok | 18:08 |
th1a | I'd say the logo could go to the left of the name/address. | 18:09 |
th1a | We just need to try it a few places. | 18:09 |
th1a | (not the schooltool logo, only the school logo) | 18:09 |
yvl | sure | 18:09 |
yvl | it could also be text + logo | 18:09 |
yvl | school name + logo :) | 18:10 |
yvl | or not | 18:10 |
yvl | logos tend to include name | 18:10 |
th1a | We can't count on that. | 18:10 |
th1a | Otherwise, we can just try some things. | 18:10 |
th1a | OK, aelkner, have we confused you? | 18:11 |
yvl | btw: aelkner, replaceafill, please pull my reports branch before continuing on reports | 18:12 |
replaceafill | yvl, kk | 18:12 |
th1a | Or perhaps we put him to sleep. | 18:13 |
th1a | OK, thanks yvl. | 18:13 |
yvl | :D | 18:13 |
yvl | random feature | 18:13 |
replaceafill | :D | 18:13 |
aelkner | th1a, ok, it would help perhaps to conclude some things | 18:13 |
aelkner | i mean, short term | 18:13 |
yvl | we could... add option to select a language when requesting the reports | 18:14 |
aelkner | you said something about limiting reports | 18:14 |
aelkner | to not need the selector of page size | 18:14 |
aelkner | that's a good short term way to allow reports to be written | 18:14 |
aelkner | i noticed that the section roster didn't have anything about it, so my resource report doesn't either | 18:15 |
aelkner | the story tag has the ptoheader and trailer | 18:15 |
aelkner | i'm not sure how they work and there are the warning messages that we discussed | 18:15 |
aelkner | but otherwise i don't see anything about page size, so point is | 18:15 |
th1a | Selector of page size? | 18:16 |
aelkner | it would be fine to not consider that issue | 18:16 |
aelkner | by that i mean no keywords | 18:16 |
aelkner | in the template, no page_size= pr whatever | 18:16 |
yvl | btw, aelkner, what report are you working on now? | 18:16 |
aelkner | so i'm assuming that is working off of defaults | 18:16 |
aelkner | it just lists the contents of the resource container | 18:17 |
yvl | ah | 18:17 |
aelkner | btw, let me look at something a moment, i wanted to comment | 18:17 |
yvl | yeah, you can get away with just specifying percentiles there | 18:17 |
aelkner | i need to call up the resource report again | 18:17 |
replaceafill | yvl, are table formatters still in your plans for reports plumbing? | 18:18 |
yvl | yes and no | 18:19 |
replaceafill | ah :( | 18:19 |
yvl | table formatters are to cumbersome to use as a whole | 18:19 |
yvl | then again, | 18:19 |
yvl | using a simple one with columns... that's another story | 18:19 |
yvl | get free sorting and such | 18:20 |
aelkner | guys, i sent an email to the developer list, it has the resource report attached | 18:20 |
aelkner | it shows how pto_header, which container the (continued message), works, quite nicely | 18:20 |
aelkner | contains, not container, sloppy typist :( | 18:21 |
aelkner | that's from the small sample data import, so the resources are all of type, Resource | 18:22 |
yvl | right | 18:22 |
th1a | I guess we could have aelkner add school address to the system. | 18:23 |
yvl | btw, after pulling, see flourish/skin/report.py IPlainPDFPage | 18:23 |
yvl | (and make your report inherit PlainPDFPage) | 18:23 |
yvl | a short comment on my changes: | 18:24 |
yvl | there is also IPlainTemplateSlots | 18:24 |
yvl | that specify what data could be put into page template when it's rendered in the report | 18:24 |
yvl | slots like top_center, top_left, title, etc. | 18:25 |
yvl | (some are missing ATM) | 18:25 |
th1a | Can you use subheaders to sort by type and add a description column? | 18:25 |
yvl | a class PlainPageTemplateSlots is (by default) used to extract the data from view to the pdf page template | 18:26 |
yvl | what it gives now, is that you pdf templates and views are decoupled | 18:27 |
yvl | and for you it means, you can add, for example, subtitles_left property in the view and it will be rendered | 18:28 |
* yvl done interrupting | 18:28 | |
th1a | "Resource Report" needs to go into the gray bar at top. | 18:30 |
th1a | Along with the year. | 18:30 |
th1a | Or maybe that's what aelkner was planning on doing this afternoon. | 18:31 |
aelkner | no, actually, what i'm showing now is what i planned on for this afternoon | 18:31 |
aelkner | i was able to do it while you discussed reports in general | 18:32 |
th1a | OK, do you need to ask yvl anything to do what I suggested? | 18:32 |
aelkner | well, perhaps, but i don't know what to ask yet | 18:32 |
yvl | please don't forget to inherit from flourish.report.PlainPDFPage | 18:32 |
aelkner | i need to grok the new changes yvl pushed just in case they impact things | 18:33 |
th1a | OK. | 18:33 |
yvl | my change will probably break your report now, inheriting will fix | 18:33 |
th1a | Let's wrap this up then. | 18:33 |
aelkner | and what about the seciton roster, was that ever ok th1a? | 18:33 |
aelkner | i was working off of that, so it that's wrong, working off of it is not a good plan :) | 18:33 |
th1a | Actually that has the same problem. | 18:33 |
yvl | and in your view, aelkner, you can add attributes/properties: name, scope, title | 18:33 |
yvl | and section roster is updated :) | 18:33 |
yvl | lemme send it | 18:33 |
th1a | aelkner: You need to look at Vinny's doc. | 18:34 |
aelkner | i can fix the section roster as i fix the resource report | 18:34 |
aelkner | yeah, i was looking, they don't subheaders btw | 18:34 |
aelkner | unless you mean the bottom of the page header | 18:34 |
aelkner | that's where we have Resource Report (or Section Roster) now | 18:34 |
th1a | No, they don't have subheads. | 18:35 |
aelkner | the guidelines have Courses (continued) in one case | 18:35 |
aelkner | Basic Info in another | 18:35 |
aelkner | anyway, what should we do about subheaders? | 18:35 |
aelkner | do we have a tag? | 18:36 |
yvl | sent | 18:36 |
aelkner | yvl, what have you sent? | 18:36 |
yvl | updated section rosters pdf | 18:36 |
aelkner | an email or a push? | 18:36 |
aelkner | ah, got it | 18:37 |
th1a | We don't want the second Section Roster there, ofc. | 18:37 |
yvl | of course | 18:38 |
aelkner | yeah, well, isn't that the place for the subheader | 18:38 |
aelkner | i mean, if we are having subheaders for each resource type | 18:38 |
aelkner | then as a particular resource type continues potentially over many pages | 18:38 |
yvl | umm, no | 18:38 |
aelkner | we would want to repeat that subheading, so to speak, no? | 18:38 |
yvl | subheaders are the little text lines below title | 18:38 |
yvl | Math --- title | 18:39 |
yvl | Instructors: John Peter -- subtitle (left) | 18:39 |
aelkner | th1a, is that what you meant? | 18:39 |
yvl | I added the second section roster for testing purposes actually | 18:39 |
yvl | (because such form is used sometimes -- for General Info, Courses and such) | 18:40 |
th1a | I meant subheads in the table (as well). | 18:40 |
aelkner | th1a, specifically, what are you thinking? continue them? | 18:40 |
aelkner | or do they appear only at the beginning of the table change? | 18:40 |
aelkner | so, for instance: | 18:41 |
aelkner | we have, say three groups of resources | 18:41 |
aelkner | 5 rooms (location) | 18:41 |
aelkner | 7 projectors (equipment) | 18:41 |
aelkner | 40 whatevers, that third type we haven't really defined well | 18:42 |
aelkner | anyway, the first page has two tables (because there is room) | 18:42 |
aelkner | and before each table is a heading (like the h2, or is it h3?) before our tables in html | 18:42 |
aelkner | and the third table also starts on page 1, but is so long that it continues to the next page | 18:43 |
aelkner | but on page 2, no mention of the subheading | 18:43 |
th1a | We have subheaders in our regular tables. | 18:43 |
aelkner | regular, read: html? | 18:44 |
th1a | yes. | 18:44 |
aelkner | the answer is yes | 18:44 |
aelkner | but html pages are always single pages | 18:44 |
aelkner | there is no concept or need to worry about continue to next page | 18:44 |
th1a | Put the header and the sub-header at the top on each new page. | 18:45 |
aelkner | just the batching that appears below the table subheader, but that's differetnt | 18:45 |
aelkner | there you go, that's what i was looking for | 18:45 |
aelkner | yvl, you see my point? | 18:45 |
yvl | yes | 18:45 |
yvl | if you have a single subheader though, it's easy to do | 18:45 |
yvl | since you can specify how many top rows to repeat | 18:46 |
th1a | I don't know why you'd do it differently... | 18:46 |
yvl | but if you have, say... | 18:46 |
yvl | row 0: Title | Description | 18:46 |
yvl | row 1: Projectors | 18:46 |
yvl | ... | 18:46 |
yvl | row 7: projector7 | very good one | 18:46 |
yvl | row 8: Locations | 18:46 |
yvl | row 9: Ball room | the big one | 18:47 |
yvl | and you want on second page repeated: | 18:47 |
yvl | row 0 | 18:47 |
yvl | row 8 | 18:47 |
yvl | I don't know how to do that at the moment | 18:47 |
aelkner | yeah, i would think that we need to solve this grouping design up front | 18:48 |
aelkner | it's a common report function as it is a common sql query | 18:48 |
aelkner | and we should have consistent look and feel for grouped reports | 18:48 |
aelkner | th1a, sounds like you favored putting the subheadings at the top | 18:49 |
aelkner | and not mixing them in with the rows as yvl just suggested | 18:49 |
aelkner | but you may change your mind, ofc | 18:49 |
th1a | When you go to the next page, I'd think you'd want the header and subheader (continued). | 18:49 |
aelkner | i think that makes sense | 18:50 |
th1a | Unless anyone thinks the user should just remember the state themselves. | 18:50 |
aelkner | when you have a 300 page printed report | 18:50 |
aelkner | strike that, we all know that the subheading needs to continue, never mind | 18:50 |
aelkner | it's just a matter of how and where | 18:51 |
yvl | ok, so th1a was not talking about table subheaders as in "a table row shaded in gray" | 18:51 |
aelkner | he didn't say so specifically | 18:51 |
aelkner | there's no point in trying to guess about something like that :) | 18:52 |
th1a | I'm talking about "sub-section title" in the guidelines. | 18:52 |
aelkner | what page number? | 18:52 |
th1a | (which may need some tweaking to look less like the regular header. | 18:52 |
th1a | Page 4 | 18:52 |
aelkner | there you have more than one table on the same page, and the tables are not even the same dimensions | 18:53 |
aelkner | the column headings are all you have there | 18:54 |
aelkner | they don't have a h2 or h3 -like thing at the start of each table | 18:54 |
yvl | oh, repeating subsection title and stuff... ok, thats what <pto> is for | 18:54 |
th1a | The SUB-SECTION TITLE | 18:55 |
yvl | whoops | 18:55 |
yvl | ok | 18:55 |
aelkner | yeah, the column headings are the same regardless of resource type | 18:55 |
yvl | now I see | 18:55 |
yvl | so no | 18:55 |
th1a | Yes. | 18:55 |
yvl | I don't know how to do that | 18:55 |
aelkner | the pto, as you said | 18:55 |
yvl | maybe | 18:56 |
th1a | OK, so this is not just baked into RML? | 18:56 |
yvl | nope | 18:56 |
yvl | something similar is baked in | 18:56 |
yvl | you can repeat a number of top table rows on each page split | 18:56 |
yvl | that's how we get repeated Full Name | ID header rows each page | 18:57 |
aelkner | yvl, can you explain why the continued thing works? | 18:57 |
aelkner | i see that it works nicely, but i can't see why yet | 18:58 |
yvl | but we could probably work around that by splitting a table into many tables | 18:58 |
aelkner | the resource report, like the section roster, has the pto section | 18:58 |
aelkner | wherein the continued message is there | 18:58 |
aelkner | but the first page has just the Section Roster message, | 18:59 |
aelkner | how is it that it doesn't get rendered each time? | 18:59 |
yvl | because of pto_header and pto_footer | 18:59 |
aelkner | it's not inside the pto tags, so it can't be tat | 18:59 |
yvl | but I don't think you can do that *inside* of a table | 18:59 |
aelkner | so it's a bit if magic, yes? | 18:59 |
yvl | oh, the section roster | 19:00 |
yvl | it's in the pdf template | 19:00 |
aelkner | yeah, i'm speaking of section_roster.pt | 19:00 |
yvl | along with the page header and the page footer | 19:00 |
aelkner | you see, pto contains pto_header and pto_trailer | 19:01 |
yvl | you could look at skin/flourish/rml/pdf_plain_page_template.pt | 19:01 |
yvl | and notice drawStrings and such | 19:01 |
yvl | well, it's getting late | 19:04 |
th1a | OK, yes. | 19:04 |
yvl | can we arrive at some resolution? ;) | 19:04 |
aelkner | are we meeting tomorrow same time | 19:04 |
yvl | and I think we should do a hangout some time | 19:04 |
th1a | Well, I can't meet tomorrow, I have a dentist appointment. | 19:04 |
th1a | But you guys probably should meet. | 19:04 |
th1a | Check in at least. | 19:04 |
aelkner | yes, a hangout with screenshare would help | 19:04 |
th1a | Or just send an email aelkner. | 19:04 |
aelkner | about what? | 19:05 |
th1a | Whatever problem you need to discuss. | 19:05 |
th1a | In the meantime... | 19:05 |
th1a | Thanks guys. | 19:05 |
* th1a drops the bag of gravel. | 19:05 | |
replaceafill | thanks everybody | 19:05 |
yvl | thanks guys | 19:06 |
aelkner | ok, thanks guys, cya wed? | 19:06 |
th1a | So... replaceafill, yvl - sprint Jan 28-Feb 1? | 19:06 |
th1a | Wednesday, definitely. Tuesday if necessary for you. | 19:06 |
yvl | sounds good th1a | 19:06 |
replaceafill | th1a, ok | 19:06 |
yvl | hmm | 19:07 |
yvl | nevermind | 19:07 |
th1a | That would be arriving Saturday. | 19:07 |
yvl | sure | 19:07 |
th1a | Warm up Sunday. | 19:07 |
replaceafill | arrive saturday, leave next saturday, right? | 19:08 |
replaceafill | s/next/following :) | 19:08 |
yvl | I think so :) | 19:09 |
yvl | ok | 19:09 |
yvl | see you guys soon | 19:09 |
*** yvl has quit IRC | 19:09 | |
*** magespawn has quit IRC | 19:30 | |
*** magespawn has joined #schooltool | 19:31 | |
veloutin | hey, so you guys have been playing with ZODB a lot... what's your opinion on it now? | 20:05 |
*** replaceafill has quit IRC | 20:34 | |
th1a | veloutin: ayt? | 20:43 |
*** replaceafill has joined #schooltool | 20:46 | |
*** replaceafill has joined #schooltool | 20:46 | |
*** replaceafill has left #schooltool | 21:47 | |
*** replaceafill has joined #schooltool | 21:47 | |
*** replaceafill has joined #schooltool | 21:47 | |
*** khildin has quit IRC | 23:48 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!