| ---Disconnected (Connection reset by peer). | 11:57 | |
| **** ENDING LOGGING AT Wed Aug 25 11:57:02 2004 | ||
| **** BEGIN LOGGING AT Wed Aug 25 11:57:19 2004 | ||
| -->You are now talking on #schooltool | 11:57 | |
| ---Topic for #schooltool is www.schooltool.org || IRC logs at http://stone.tuttlesvc.org:880/logbot/ | 11:57 | |
| ---Topic for #schooltool set by mgedmin at Fri Jul 16 18:15:52 2004 | 11:57 | |
| -TomLogging-This channel is logged - http://stone.tuttlesvc.org:880/logbot/ | 11:57 | |
| -->Aiste (~aiste@office.pov.lt) has joined #schooltool | 11:59 | |
| -->SteveA (~steve@host217-37-231-28.in-addr.btopenworld.com) has joined #schooltool | 12:44 | |
| -->thisfred (~thisfred@a213-84-57-72.adsl.xs4all.nl) has joined #schooltool | 13:31 | |
| <--Aiste has quit (Read error: 110 (Connection timed out)) | 17:42 | |
| -->th1a (~hoffman@68-233-81-160.pittpa.adelphia.net) has joined #schooltool | 17:53 | |
| th1a | mgedmin: you around? | 18:38 |
|---|---|---|
| mgedmin | yes | 18:38 |
| th1a | I think there is still a problem with the timetable schema generation. Let me explain what I'm trying to do. | 18:43 |
| th1a | I have a two-day cycle. Each day has four periods. | 18:43 |
| th1a | So I set up Day 1 with periods A, B, C, D | 18:44 |
| th1a | And Day 2 with E, F, G, H. | 18:44 |
| th1a | The problem is when I go down to step 3, each day has eight time slots -- A through H. | 18:45 |
| th1a | Whereas there are actually only four periods in each day. | 18:46 |
| th1a | Does that make sense? | 18:46 |
| mgedmin | yes | 18:55 |
| mgedmin | but I do not see the problem | 18:55 |
| mgedmin | not all slots need to be defined | 18:56 |
| th1a | I don't know what to do though, because in this case the periods don't correspond to days. | 18:57 |
| th1a | So I can't say "period A is at 9:00 on Monday" because period A is at 9:00 on alternating days. | 18:58 |
| mgedmin | I still do not see the problem | 18:58 |
| mgedmin | if period A is always at 9:00, you can say so explicitly | 18:58 |
| mgedmin | if Tuesday defines a period A at 9:00 | 18:58 |
| mgedmin | but it so happens that this particular tuesday is Day 2 in our schedule | 18:58 |
| mgedmin | and therefore does not actually have a period A | 18:59 |
| mgedmin | then it is not a problem -- the timetable skips period A for this day | 18:59 |
| th1a | Oh. I see. So essentially "if there is a period A on Monday, it will be at this time" | 18:59 |
| mgedmin | yes | 18:59 |
| th1a | OK. | 18:59 |
| mgedmin | it is possible that the system is too flexible and therefore confusing | 19:00 |
| mgedmin | examples should help | 19:00 |
| th1a | By default, if you're doing a repeating cycle, it should assume that every day of the week has the same time schedule. It would be better if the days of the week grid only appeared when it is necessary. | 19:03 |
| th1a | Although it is hard to guess how common a case it is. | 19:03 |
| th1a | Normally, it would be fine to just enter the start and end times in step one, when you're defining the days and the periods. | 19:08 |
| th1a | So perhaps the days of the week grid could just override the times set in the main days/periods grid when necessary. | 19:34 |
| mgedmin | what about the following solution: | 19:37 |
| mgedmin | (*) period times are the same for all days | 19:37 |
| mgedmin | ( ) period times depend upon the day of week | 19:38 |
| mgedmin | and then if the first one is selected, we only show one column | 19:38 |
| mgedmin | I do not think it is possible to add times to the main grid | 19:39 |
| th1a | OK. | 19:39 |
| th1a | That works, too. | 19:39 |
| th1a | Whatever is easier. | 19:40 |
| th1a | OK. I gotta run. Thanks! | 19:41 |
| <--th1a has quit () | 19:41 | |
| <--SteveA has quit ("Leaving") | 20:55 | |
| <--thisfred has quit ("Farewell, cruel channel...") | 21:24 | |
| **** ENDING LOGGING AT Wed Aug 25 21:46:49 2004 | ||
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!