| *** aitch100s76 has joined #schooltool | 00:00 | |
| jstraw | ignas: in term creation, we need to fix the date fields | 00:01 |
|---|---|---|
| jstraw | to be like all the others | 00:01 |
| jstraw | should be 2008-12-12 | 00:02 |
| aitch100s76 | as in YYYY-MM-DD? | 00:02 |
| jstraw | yea | 00:02 |
| jstraw | right now it seems to be a couple choices | 00:02 |
| aitch100s76 | Depends where you are and you "locale" setting | 00:03 |
| jstraw | ignas: also, terms should overlap... Fall, Spring, Year-Long | 00:03 |
| jstraw | aitch100s76: I know | 00:03 |
| ignas | jstraw: i have fixed it already | 00:04 |
| ignas | jstraw: now it's locale specific in both views | 00:04 |
| ignas | jstraw: no, terms do not overlap | 00:04 |
| ignas | jstraw: ever | 00:04 |
| jstraw | uh | 00:05 |
| jstraw | ok, can one course be in 2 terms? | 00:05 |
| aitch100s76 | Ignas: what about at a college when a "incomplete" is in play due to an unexpected medical proble for a student? | 00:06 |
| jstraw | aitch100s76: they're still on the last term | 00:06 |
| ignas | jstraw: Courses are in school years | 00:06 |
| jstraw | the question I have is about classes that span an entire yera | 00:06 |
| ignas | sections are in terms | 00:06 |
| jstraw | ok, a section that spans 2 terms | 00:06 |
| jstraw | or 4 terms | 00:06 |
| ignas | sections will be connected if users will want between terms | 00:06 |
| ignas | so it will be 4 different section objects | 00:07 |
| ignas | that are referring each other | 00:07 |
| jstraw | ok | 00:07 |
| ignas | jstraw: overlapping terms are too difficult to manage code wise (you can't map dates to terms, you suddenly can have conflicting/overlapping timetables, and you must have some terms "more important" than others...), sections spanning multiple terms just add to that confusion, because you suddenly can't map section to term, moving sections between terms becomes just an issue of scheduling, and having some sections "term" based and some "mul | 00:11 |
| ignas | ti term based" is too complicated... | 00:11 |
| jstraw | k | 00:12 |
| ignas | as for dated - I am open to suggestions, as the current situations is a *mess* | 00:12 |
| ignas | i mean - we are formatting dates by locale | 00:13 |
| ignas | having locale specific entry | 00:13 |
| ignas | means - you can copy paste dates in the system | 00:13 |
| ignas | though - we only have data pickers for ISO date format YYYY-MM-DD | 00:13 |
| aitch100s76 | Ignas: Suggestion for the date problem... Why not have a "hint" that displays next to the data entry box that shows what format that box expects the data in? | 00:14 |
| ignas | aitch100s76: well - there is such a field "description" that is displayed next to the input | 00:15 |
| ignas | trouble is | 00:15 |
| ignas | it's pretty tricky making it locale specific too | 00:15 |
| ignas | because you want it not translated | 00:15 |
| ignas | which is easy | 00:15 |
| ignas | but rather localized, so you want to have a printable date format representation, or an example date in a description | 00:16 |
| ignas | which Zope3 does not really make easy to do | 00:16 |
| ignas | so choices are | 00:17 |
| jstraw | I suggest killing off locale specific dates | 00:17 |
| ignas | ISO date formatting when date format is set to "short" and ISO date entry everywhere | 00:17 |
| ignas | + picker | 00:17 |
| aitch100s76 | ok it was an idea, having not explored Zope3 that much I was not aware of the difficulties | 00:17 |
| ignas | or working on locale specific pickers | 00:18 |
| jstraw | and force YYYY-MM-DD | 00:18 |
| ignas | we must keep locale specific medium and long formatters | 00:18 |
| ignas | as they include month / weekday names | 00:18 |
| jstraw | yea... | 00:18 |
| ignas | th1a, jstraw: i guess we could think of a solution during our Monday meeting or after it | 00:21 |
| jstraw | k | 00:21 |
| aitch100s76 | I can live with YYYY-MM-DD system wide | 00:24 |
| aitch100s76 | otyher d | 00:24 |
| jstraw | ignas: I think bringing things in in multiple formats is ok, but we should store it all as YYYY-MM-DD | 00:24 |
| jstraw | and then re-display as that | 00:24 |
| ignas | jstraw: we are not storing strings anywhere | 00:24 |
| jstraw | k | 00:25 |
| ignas | we are storing dates ;) | 00:25 |
| aitch100s76 | other data bases that i work with are YYYY-MM-DD-HH-mm-ss | 00:25 |
| jstraw | ignas: yea | 00:25 |
| *** jstraw has quit IRC | 00:29 | |
| *** aitch100s76 has left #schooltool | 00:38 | |
| *** ignas has quit IRC | 02:11 | |
| *** replaceafill has quit IRC | 02:52 | |
| *** th1a has quit IRC | 05:07 | |
| *** alga has quit IRC | 07:09 | |
| *** alga has joined #SchoolTool | 13:27 | |
| *** jelkner has joined #schooltool | 20:36 | |
| *** jelkner has quit IRC | 20:46 | |
| *** jelkner has joined #schooltool | 20:47 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!