| *** ccarey has joined #schooltool | 00:16 | |
| ignas | ccarey: hi | 00:17 |
|---|---|---|
| ccarey | hi ignas | 00:17 |
| ignas | how's the day? | 00:17 |
| ccarey | it's been fine; just got home | 00:17 |
| ignas | i see, should we start now, or should I wait for you to do whatever you usually do when you come home ? ;) | 00:18 |
| ccarey | i'm ready now | 00:19 |
| ignas | so how is your weekly calendar view work going? | 00:19 |
| ignas | or do you want to concentrate on CanDo buildout things at the moment? | 00:19 |
| ccarey | i just wanted to ask something about the weekly calendar view | 00:20 |
| ignas | ok | 00:20 |
| ccarey | i'm creating dummy events in getCurrentWeek() to fill the spaces for now | 00:20 |
| ignas | I see | 00:20 |
| ccarey | is this okay, or should the page template be the one who fills in the spaces | 00:20 |
| ignas | hmm, not sure I can say without seeing the code | 00:21 |
| ignas | I would not use the actual event class to fill spaces i guess | 00:21 |
| ccarey | it's been a little difficult trying to get the events in a table because | 00:22 |
| ccarey | in a table, you can only add by rows | 00:22 |
| ccarey | but the list has events for each day; so it's by column instead | 00:23 |
| ignas | hmm | 00:23 |
| ignas | you are working on WeeklyCalendarView, yes? | 00:24 |
| ccarey | yes | 00:24 |
| ccarey | i'm thinking maybe the view needs a function that will return the week events by the period, rather than the day | 00:25 |
| ignas | you could do that | 00:25 |
| ignas | i mean - you can make the getCurrentWeek function do that as well | 00:26 |
| *** jelkner has joined #schooltool | 00:26 | |
| ccarey | ok, i can try that then | 00:26 |
| *** jelkner has quit IRC | 00:26 | |
| *** jelkner has joined #schooltool | 00:27 | |
| ignas | you might even alternate between two templates depending on whether there is a default timetable schema set, or not | 00:27 |
| ignas | if that would make it more convenient to you | 00:27 |
| ignas | you'd have to set templates in the class itself and override __call__ method for that I think | 00:28 |
| ccarey | the __call__ method for WeeklyCalendarView? | 00:29 |
| ignas | template="templates/cal_weekly.pt" | 00:30 |
| ignas | in zcml | 00:30 |
| ignas | Zope3 creates index() method on your view that get's called from __call__ of the BrowserView class | 00:30 |
| ignas | from what I can recall | 00:30 |
| ignas | so if you will not set the template in zcml | 00:31 |
| ignas | and have 2 attributes | 00:31 |
| ignas | like simple_template = ViewPageFileTemplate("foo/bar.pt") | 00:31 |
| ignas | and tt_schema_template = ViewPageFileTemplate("bar/foo.pt") | 00:31 |
| ignas | you can dispatch among them in the __call__ of the view | 00:32 |
| ignas | so you would not have to do complex conditionals in the template itself | 00:32 |
| ccarey | alright | 00:33 |
| ignas | you might be able to find examples of this pattern in some places in schooltool | 00:33 |
| ignas | schooltool.app.browser.cal.EventDeleteView | 00:34 |
| ignas | for example | 00:34 |
| ccarey | yes, i was just taking a look at that | 00:34 |
| ccarey | ok, i think i have a good idea of what to do next | 00:35 |
| ignas | good :) | 00:36 |
| ccarey | so will we start taking a look at the CanDo buildout? | 00:37 |
| ignas | did you take a look at the projects i pointed to you | 00:38 |
| ccarey | a quick look, but not in detail yet | 00:39 |
| ignas | well - anyway, we have to set you up for some buildout usage | 00:39 |
| ignas | look at http://paste.lisp.org/display/55080 | 00:40 |
| ignas | and put something simmilar to that in your ~/.buildout/default.cfg | 00:40 |
| ignas | so that you would not have to download same eggs over and over again | 00:40 |
| ignas | tell me when you're done | 00:41 |
| ccarey | ok, i'm done | 00:43 |
| ignas | do you have bzr installed on your machine? | 00:43 |
| ccarey | no, i haven't got it properly working | 00:44 |
| ccarey | hold on, one sec | 00:44 |
| ccarey | i'm missing bzrlib.breakin | 00:45 |
| ignas | hmm, strange | 00:45 |
| ignas | what does "which bzr" say? | 00:46 |
| ccarey | ooh, /home/chris/bin/bzr | 00:46 |
| ignas | try /usr/bin/bzr | 00:46 |
| ignas | or just rename your personal bzr | 00:47 |
| ccarey | what should i do to rename it? | 00:48 |
| ignas | mv /home/chris/bin/bzr /home/chris/bin/bzr.bak | 00:48 |
| ignas | for example | 00:49 |
| th1a | ignas: everything seems have to completed without "section_events." | 00:49 |
| ignas | good :) now just log in as teacher023 or teacher042 ;) | 00:49 |
| ignas | or whichever integer you like | 00:49 |
| ignas | and try looking around | 00:49 |
| ignas | and taking a lot of notes | 00:50 |
| ignas | ccarey: when you will have bzr working do: bzr co --lightweight lp:~ignas/schooltool/schooltool.lyceum.journal/ in some place you want to check out the repository | 00:51 |
| * th1a is making dinner now... | 00:51 | |
| ccarey | ignas: both folders with bzr are misbehaving - bzrlib version doesn't match bzr version | 00:52 |
| ignas | hmm | 00:52 |
| ignas | echo $PYTHONPATH | 00:52 |
| ccarey | /home/chris/lib/python | 00:52 |
| ccarey | actually, it's still looking for /home/chris/bin/bzr | 00:53 |
| ignas | restart your terminal | 00:53 |
| ccarey | but which bzr is giving me /usr/bin/bzr | 00:53 |
| ignas | bash caches this information | 00:53 |
| ccarey | ugh, still the bzrlib version error | 00:54 |
| ignas | export PYTHONPATH= | 00:54 |
| ignas | and try again | 00:54 |
| ccarey | no luck, i'm trying reinstalling | 00:55 |
| ccarey | it must have been an installation problem | 00:56 |
| ignas | maybe it was | 00:56 |
| ccarey | ok it's checking out | 00:57 |
| ccarey | i have schooltool.lyceum.journal now | 00:57 |
| ignas | good | 00:58 |
| ignas | now look at the files that are in the top level directory | 00:58 |
| ignas | the files that you care about are buildout.cfg and Makefile | 00:58 |
| *** jelkner has quit IRC | 00:59 | |
| ignas | Makefile because it is doing the build and test steps quite differently from the old style one that is in CanDo at the moment | 00:59 |
| ignas | and buildout.cfg is the core of the new build system | 00:59 |
| *** wbrady has joined #schooltool | 00:59 | |
| ignas | the [buildout] section lists all the "parts" that will get built | 01:00 |
| ignas | when you run bin/buildout | 01:00 |
| ignas | other sections describe each part | 01:00 |
| ignas | most parts have recipes | 01:01 |
| ignas | that describe the way that will be used to build the part | 01:01 |
| ignas | zc.recipe.egg is for setting up eggs | 01:01 |
| ignas | zc.recipe.testrunner creates a script that will run tests (named the same way the part is named) | 01:02 |
| ignas | if you would type "make" | 01:02 |
| ignas | which you probably should do ;) | 01:02 |
| ignas | it will bootstrap buildout | 01:03 |
| ignas | and use the buildout to install the rest of the stuff | 01:03 |
| ignas | tell me when buildout will have finished | 01:04 |
| ccarey | am i supposed to have a bin/buildout folder here? | 01:04 |
| ignas | no, not at the moment | 01:05 |
| ignas | the file will be created | 01:05 |
| ignas | after you run "make" | 01:06 |
| ignas | meanwhile you might want to check out svn+ssh://source.schooltool.org/svn/cando/branches/cando-buildout-integration branch | 01:08 |
| ignas | if you haven't done so already | 01:08 |
| ccarey | ok | 01:09 |
| ccarey | buildout stopped -- couldn't install lxml 1.3.6 | 01:10 |
| ignas | sudo apt-get build-deb python-lxml | 01:11 |
| ignas | build-dep | 01:11 |
| ignas | not build-deb | 01:11 |
| ccarey | ok buildout is still running | 01:16 |
| ccarey | but i'm getting Permission denied (publickey) when i try to do a checkout | 01:16 |
| ignas | hmm | 01:17 |
| ccarey | of the cando-buildout-integration branch | 01:17 |
| ignas | could you post svn info url in your cano checkout | 01:17 |
| ignas | because we might be using different ways of checking out cando | 01:17 |
| ccarey | how do i do that? | 01:18 |
| ignas | go to your cando | 01:18 |
| ignas | and type "svn info" | 01:18 |
| ignas | you will see the url of your checkout in there somewhere | 01:18 |
| ccarey | https://svn.schooltool.org/cando/trunk | 01:19 |
| ignas | so you shoud do "svn co https://svn.schooltool.org/cando/branches/cando-buildout-integration" | 01:20 |
| ignas | instead of the svn+ssh one | 01:20 |
| ignas | because you are using https to access svn repository | 01:20 |
| ccarey | right | 01:21 |
| ccarey | ok i made a checkout | 01:21 |
| ignas | good | 01:21 |
| ignas | we will be working with that checkout | 01:21 |
| ignas | so we'd not break anything ;) | 01:22 |
| ignas | oh, nearly forgot - the buildout.cfg [buildout] section | 01:22 |
| ignas | contained one more important line | 01:22 |
| ignas | "develop = ." | 01:22 |
| ignas | you see - buildout can be used to deploy egg based applications, without any sources available, it will download everything from the internet ... | 01:23 |
| ignas | but when you want buildout to use "cando" or "schooltool" checkout instead of the egg from the internet | 01:23 |
| ignas | you check it out somewhere and add it to the develop line | 01:24 |
| ignas | for example - if you have schooltool.lyceum.journal buildout | 01:24 |
| ignas | and want to work on schooltool at the same time in the same buildout you can either | 01:24 |
| ignas | make a schooltool checkout inside of your buildout | 01:24 |
| ignas | and add "develop = . schooltool" | 01:24 |
| ignas | which means - there are 2 development eggs - one in the directory "schooltool" and another one in the directory "." | 01:25 |
| ignas | the one in "." is schooltool.lyceum.journal in this case | 01:25 |
| ignas | i sometimes use "../schooltool" if i want to use development version of schooltool while not having it in the same directory | 01:26 |
| ignas | anyway - has your buildout finished yet? | 01:26 |
| ignas | ;) | 01:26 |
| ccarey | yes it finished | 01:26 |
| ignas | cool | 01:26 |
| ignas | now if you would look at bin directory in your buildout | 01:26 |
| ignas | it has scripts like "test" "buildout" "i18nextract" and a couple more from what i can recall | 01:27 |
| ignas | so test is pretty obvious - it runs tests | 01:27 |
| ignas | you can try running "bin/test" from your buildout | 01:27 |
| ignas | to check if they pass | 01:27 |
| ignas | bin/buildout is used when you modify your buildout.cfg | 01:28 |
| ignas | by adding new parts or changing existing ones | 01:28 |
| ignas | or when you want to update your sandbox with new eggs | 01:28 |
| ignas | usually buildout downloads newest eggs by default | 01:28 |
| ignas | but it's slow | 01:28 |
| ignas | so i have the line in buildout.cfg | 01:28 |
| ignas | that says "newest = false" | 01:29 |
| ignas | so if I want new eggs i do "bin/buildout -n" | 01:29 |
| ignas | i think aelkner added a "make update" rule to the makefile to do svn up + bin/buildout -n | 01:29 |
| ccarey | it's there | 01:30 |
| ignas | cool :) | 01:30 |
| ignas | it even says svn up | 01:30 |
| ignas | though it's a bzr checkout | 01:30 |
| ignas | our goal is to make cando use the same infrastructure | 01:31 |
| ignas | so you probably can just copy and paste the make file and bootstrap.py | 01:31 |
| ignas | to your cando checkout | 01:31 |
| ignas | and buildout.cfg | 01:31 |
| ignas | and version.txt.in | 01:31 |
| ignas | and MANIFEST.in | 01:32 |
| ignas | and fix buildout.cfg to point to cando rather than schooltool.lyceum.journal | 01:32 |
| ignas | same for Makefile | 01:32 |
| ccarey | ok =) | 01:32 |
| ignas | oh and replace the bzr revno line with "svnversion >> version.txt" | 01:34 |
| ccarey | this is all with cando-buildout-integration right? not the current cando? | 01:37 |
| ignas | yes | 01:38 |
| ignas | we don't want to break sandbox for everyone just yet ;)_ | 01:38 |
| ccarey | right =) | 01:38 |
| ccarey | ok i made the changes | 01:40 |
| ignas | good | 01:42 |
| ignas | try "make" | 01:42 |
| ccarey | Couldn't find index page for 'cando-buildout-integration' | 01:46 |
| ccarey | also couldn't find distribution | 01:46 |
| ignas | the egg for "eggs = " | 01:46 |
| ignas | is cando | 01:46 |
| ignas | not cando-buildout-distribution | 01:47 |
| ccarey | oops | 01:47 |
| ccarey | ok, make finished | 01:48 |
| ignas | wow :) | 01:49 |
| ignas | bin/make-schooltool-instance instance/ | 01:50 |
| ignas | if that works | 01:51 |
| ignas | bin/start-schooltool-instance instance/ | 01:51 |
| ignas | and look whether it's cando ;) | 01:51 |
| ccarey | its missing a schooltool.gradebook egg | 01:54 |
| ccarey | wait, its there | 01:55 |
| ignas | lisppaste5: url | 01:56 |
| lisppaste5 | To use the lisppaste bot, visit http://paste.lisp.org/new/schooltool and enter your paste. | 01:56 |
| ignas | full error message including commands you executed | 01:56 |
| ignas | please ;) | 01:56 |
| lisppaste5 | cpcarey pasted "cando buildout make error" at http://paste.lisp.org/display/55099 | 01:58 |
| ccarey | configure.zcml is missing from the egg | 01:59 |
| ignas | nope | 01:59 |
| ignas | cando still depends on schooltool release | 01:59 |
| ignas | and these are nightlies | 02:00 |
| ignas | so you should include schooltool/common/configure.zcml | 02:00 |
| ignas | in the zcml | 02:00 |
| ignas | pcakage="schooltool.common" | 02:00 |
| ignas | fix cando/cando2007/configure.zcml | 02:00 |
| ignas | and try running it again | 02:00 |
| ccarey | i included the package and i'm getting the same error | 02:05 |
| ignas | you should remove the <include package="schooltool" /> | 02:06 |
| ignas | and place the common include in there | 02:06 |
| ccarey | ok that worked, i'm at a second error, let me go ahead and post that | 02:09 |
| lisppaste5 | cpcarey pasted "cando buildout make error 2" at http://paste.lisp.org/display/55100 | 02:11 |
| ignas | let me guess | 02:13 |
| ignas | aelkner removed IStatistics | 02:13 |
| ignas | from the trunk | 02:14 |
| ignas | and Cando is still using it | 02:14 |
| ignas | I guess we'll have to postpone this one | 02:14 |
| ignas | because its quite late in here, sorry | 02:14 |
| ccarey | no i understand | 02:14 |
| ignas | you should talk to aelkner and find out what happened to IStatistics interface | 02:14 |
| ignas | or just look at svn commit logs | 02:14 |
| ccarey | ok | 02:14 |
| ignas | and see what, who and when did something to the interface | 02:14 |
| ignas | Author: aelkner | 02:15 |
| ignas | Date: 2007-12-15 01:08:07 -0500 (Sat, 15 Dec 2007) | 02:15 |
| ignas | removed unused statistics adapter | 02:15 |
| ignas | :D | 02:15 |
| ccarey | did you want to set a cut off time so you don't have to stay up too late? | 02:15 |
| ccarey | =) | 02:15 |
| ignas | nah, it mostly depends on how sleepy I am | 02:15 |
| ignas | and I am quite sleepy ;) | 02:15 |
| ignas | so - yell at aelkner for breaking cando | 02:16 |
| ccarey | ok, so i'll look into that | 02:16 |
| aelkner | my ears are burning here | 02:16 |
| ignas | by breaking schooltool.gradebook public interface | 02:16 |
| aelkner | what did i break? | 02:16 |
| ignas | cando | 02:16 |
| ignas | still uses IStatistics | 02:16 |
| aelkner | where? | 02:17 |
| ignas | and you have removed it from schooltool.gradebook | 02:17 |
| aelkner | ooh | 02:17 |
| ignas | src/cando/virginia/browser/virginia.py | 02:17 |
| aelkner | we don't need it in cando | 02:17 |
| ignas | so - either fix cando or fix schooltool.gradebook | 02:17 |
| * ignas goes to sleep | 02:17 | |
| ignas | see you all tomorrow | 02:17 |
| aelkner | i'll fix cando | 02:17 |
| ccarey | thanks ignas | 02:17 |
| ignas | aelkner: backport your fix to cando-buildout-integration branch please | 02:18 |
| ignas | bye | 02:18 |
| *** ignas has quit IRC | 02:18 | |
| aelkner | ccarey what's up? | 02:19 |
| ccarey | we were working on starting a schooltool instance with the cando-buildout | 02:20 |
| ccarey | and IStatistics was missing | 02:20 |
| aelkner | ccarey: i'm wondering why cando works at all if the statistics package is really gone | 02:23 |
| aelkner | i mean, once it got to that import, it would crash | 02:23 |
| aelkner | and people are using cando in the field with no crashes | 02:24 |
| ccarey | hmmm | 02:24 |
| aelkner | ah | 02:24 |
| aelkner | the answer is that cando is using a schooltool egg | 02:25 |
| aelkner | and that people haven't tried to update it | 02:25 |
| aelkner | so it still has the statistics package | 02:25 |
| aelkner | and the last time i tested cando, i.e., before my last commit | 02:26 |
| aelkner | there was still a statistics package in schooltool | 02:26 |
| ccarey | i see | 02:26 |
| aelkner | so you're working in a brach of cando? | 02:27 |
| ccarey | well we working with cando-buildout-integration which gets its eggs from cando | 02:28 |
| aelkner | ccarey: what happens if you just get rid of the import in the file ignas mentioned above? | 02:29 |
| *** alga has joined #SchoolTool | 02:30 | |
| ccarey | i can see what happens | 02:30 |
| aelkner | line 52 of virginia/browser/virginia.py should get the axe | 02:31 |
| aelkner | that's an import that it doesn't even use | 02:31 |
| ccarey | it didn't seem to have problems with removing the import | 02:32 |
| aelkner | did it fix your problems? | 02:32 |
| ccarey | i think so, it just continued on to another problem here | 02:33 |
| ccarey | SchoolToolMessage import in cando/newskin/global.py | 02:33 |
| aelkner | you could probably blame ignas for that one. i didn't change schooltool to no longer have SchooltoolMessage | 02:36 |
| ccarey | i changed line 52 of global.py to | 02:37 |
| ccarey | from schooltool.common import SchoolToolMessage as _ | 02:37 |
| ccarey | and it's running fine now | 02:37 |
| aelkner | ah, so you found out where he moved it? good work | 02:39 |
| ccarey | i think that's it for now | 02:39 |
| ccarey | i got it running and that's where ignas wanted to stop | 02:39 |
| aelkner | cool | 02:40 |
| ccarey | aelkner: i'm signing off for today | 02:41 |
| aelkner | ok, cya | 02:41 |
| ccarey | bye | 02:41 |
| *** ccarey has quit IRC | 02:42 | |
| *** wbrady has quit IRC | 04:38 | |
| *** th1a has quit IRC | 04:54 | |
| *** alga has quit IRC | 07:15 | |
| *** ignas has joined #schooltool | 09:59 | |
| *** pcardune has joined #schooltool | 12:08 | |
| *** pcardune_ has joined #schooltool | 12:36 | |
| *** pcardune has quit IRC | 12:56 | |
| *** ignas has quit IRC | 14:21 | |
| *** ignas has joined #schooltool | 14:30 | |
| *** SteveA_ is now known as SteveA | 14:42 | |
| pcardune_ | if anyone is interested, i'm writing a zope tutorial here: http://blog.carduner.net/2008/01/31/z3c-tutorial-continued/ | 14:43 |
| *** pcardune_ has quit IRC | 14:55 | |
| *** aelkner has quit IRC | 14:56 | |
| *** alga has joined #SchoolTool | 14:57 | |
| *** wbrady has joined #schooltool | 15:06 | |
| *** th1a_ is now known as th1a | 16:05 | |
| th1a | ignas: In case you're wondering, the buildout works on Fedora. | 16:05 |
| * th1a has his desktop running Fedora for OLPC hacking. | 16:05 | |
| ignas | cool | 16:06 |
| ignas | i think the version that depended on libxml2 had some problems with fedora | 16:06 |
| th1a | It is a good thing. | 16:12 |
| th1a | Well, as far as I can tell I can't get a python2.4 rpm for Fedora 8 though. So I compiled that. | 16:13 |
| th1a | So that's one hitch. | 16:13 |
| *** aelkner_ has joined #schooltool | 16:20 | |
| aelkner_ | ignas: ayt? | 16:20 |
| *** mgedmin has joined #schooltool | 16:23 | |
| ignas | yes | 16:24 |
| ignas | th1a: interesting, what are they using ? python2.5 ? | 16:24 |
| ignas | aelkner_: yes | 16:25 |
| aelkner_ | After you ledt last night, I helped ccarey get his build to work | 16:25 |
| ignas | i saw that | 16:26 |
| aelkner_ | that involved removing the unused import of IStatistics | 16:26 |
| th1a | ignas: Yes, 2.5. | 16:26 |
| aelkner_ | but also reacting to your movement of SchooltoolMessage to schooltool.common | 16:26 |
| aelkner_ | I have a problem with cando now as a result | 16:26 |
| aelkner_ | Cando itself is tied to schooltool release | 16:26 |
| aelkner_ | so now cando won't work as your move to common is not there | 16:27 |
| aelkner_ | i could wait to change that one import | 16:27 |
| aelkner_ | until we go with a newer schooltool egg | 16:27 |
| ignas | well - you should | 16:27 |
| ignas | that's why i have a branch | 16:27 |
| ignas | for the buildout-integration work | 16:27 |
| ignas | because the branch also pulls cando to depend on the upcomming schooltool release | 16:28 |
| aelkner_ | but when you back-port it to cando, it will break | 16:28 |
| ignas | instead of the old one | 16:28 |
| aelkner_ | unless schooltoll release is more up to date | 16:28 |
| ignas | or someone changes the find-links and setup.py | 16:28 |
| ignas | old cando will have to be cleaned up anyway | 16:29 |
| ignas | because they will be using buildout | 16:29 |
| ignas | "old cando sandboxes" | 16:29 |
| aelkner_ | what will cando-buildout use for schooltool? release? | 16:30 |
| ignas | nightlies at least until the new release comes out | 16:30 |
| ignas | because well - if we are going to release cando and schooltool together | 16:30 |
| ignas | they will have to be tested to work together | 16:31 |
| th1a | ignas: Let me just note that I don't consider getting a CanDo release together to be a requirement for Hardy. | 16:33 |
| ignas | i know, it does not add more work for me ;) | 16:33 |
| *** wjohnsto has joined #schooltool | 16:35 | |
| wjohnsto | ignas: ayt? | 16:35 |
| ignas | ye | 16:37 |
| wjohnsto | actually, I have to go, class is ending | 16:37 |
| wjohnsto | I'll email you | 16:37 |
| ignas | ok | 16:38 |
| aelkner_ | ignas: the thing about cando now is that it depends on a stable schooltool so that if schooltool temprarly breaks, cando is not efeected | 16:40 |
| aelkner_ | if we change it to depend on nightlies, we loose that safety | 16:40 |
| ignas | well - if 2 projects are to go together | 16:41 |
| ignas | they will have to have the same release cycle | 16:41 |
| ignas | so - cando users will have to use stable cando + stable schooltool | 16:41 |
| ignas | while unstable cando will be developed in parallel with unstable schooltool | 16:41 |
| aelkner_ | that's fine | 16:41 |
| ignas | or else we won't be able to release together | 16:41 |
| aelkner_ | as long as cando users are not using unstable cando, there will be no problem | 16:42 |
| aelkner_ | but we can't back-port your branch into cando stable | 16:42 |
| th1a | If CanDo users are tracking unstable, that's a problem, period. | 16:42 |
| ignas | yep trunk is by definition - unstable | 16:43 |
| ignas | it is not a "release" | 16:43 |
| ignas | releases live in branches | 16:43 |
| ignas | and are tagged | 16:43 |
| *** wjohnsto has quit IRC | 16:49 | |
| ignas | aelkner_: no more Wild West Development practices for Cando ;) | 16:49 |
| aelkner_ | how do you mean? | 16:50 |
| ignas | from what i understand release process for cando is: | 16:50 |
| ignas | back up data.fs | 16:50 |
| ignas | svn up | 16:51 |
| ignas | make run | 16:51 |
| ignas | which works for 1 place | 16:51 |
| ignas | but if you are going to release something, at least tagging releases | 16:51 |
| ignas | setting version numbers | 16:51 |
| ignas | packaging them | 16:52 |
| ignas | and then deploying packages | 16:52 |
| ignas | is a bit more reliable | 16:52 |
| ignas | especially if more than one instance is deployed | 16:52 |
| aelkner_ | we can discuss our release plans at pycon | 16:58 |
| aelkner_ | until then, we don't have to use the buildout in the field | 16:58 |
| aelkner_ | we only have two deplyments | 16:59 |
| aelkner_ | and that will still be tru until the summer | 16:59 |
| aelkner_ | so we can stay with using cando trunk which depends on stable schooltool | 16:59 |
| ignas | so if I understand correctly - you want me to take care of cando and schooltool integration on the code and project level, especially when it comes to releasing, while not changing anything in your setups or development/deployment practices? | 17:02 |
| aelkner_ | i'm not saying that. | 17:04 |
| aelkner_ | the whole cando-buildout thing got started when jelkner wanted to tie cando release with schooltool | 17:05 |
| ignas | yes | 17:05 |
| aelkner_ | that's a publicity thing, not a practical one | 17:05 |
| ignas | oh | 17:05 |
| aelkner_ | practically speaking, we have cando in the field, and it needs to be stable | 17:06 |
| aelkner_ | that's my only concern | 17:06 |
| ignas | not the only one | 17:06 |
| ignas | you want to be able to change it whenever you want | 17:06 |
| ignas | as in - check in some code into trunk | 17:06 |
| ignas | svn up | 17:06 |
| aelkner_ | we can do that now | 17:06 |
| ignas | and it's deployed | 17:06 |
| aelkner_ | right | 17:06 |
| ignas | yes, and it seems that this concern is also very important to you | 17:06 |
| aelkner_ | so we're ok if we continue to depnd on the stable schooltool | 17:07 |
| ignas | not on the stable | 17:07 |
| ignas | on the "schooltool release -1" | 17:07 |
| aelkner_ | that's fine | 17:07 |
| aelkner_ | that's what i mean by stable | 17:07 |
| aelkner_ | the latest release | 17:07 |
| aelkner_ | rather than what cando-buildout depends upon | 17:07 |
| ignas | no not the last release, but the second last | 17:07 |
| ignas | because you see - schooltool will release schooltool.stapp2008spring | 17:08 |
| aelkner_ | is that what cando is depending on in trunk now? | 17:08 |
| ignas | cando will still be using schooltool.stapp2007 | 17:08 |
| ignas | aelkner_: no cando depends on schooltool2007 release | 17:08 |
| aelkner_ | is that what you mean by release -1? | 17:08 |
| ignas | yes | 17:09 |
| aelkner_ | so -1 mean 'one year ago'? | 17:09 |
| ignas | more like 6 months | 17:09 |
| aelkner_ | right | 17:09 |
| ignas | you see - if you will not have unstable cando branch that is tracking schooltool nightlies | 17:09 |
| ignas | you won't be able to release with the new schooltool | 17:09 |
| ignas | it's like using Zope3.3 | 17:09 |
| ignas | and then trying to get your package into debian at the same time Zope3.4 is release | 17:10 |
| ignas | d | 17:10 |
| ignas | schooltool is using Zope3.4 because we will release depending on Zope3.4 | 17:11 |
| aelkner_ | when the summer comes we can get cando to depend on schooltool.stapp2008spring i suppose | 17:11 |
| ignas | if cando is using schooltool2007 and has no branch tracking schooltool2008 - you will only release with schooltool2007 | 17:11 |
| ignas | yes you can, but it will very seriously hamper the ability of schooltool project to change things | 17:11 |
| ignas | schooltool is planning 6 monthly releases | 17:12 |
| ignas | so either we include both releases in ubuntu | 17:12 |
| ignas | or we make them always backwards compatible | 17:12 |
| ignas | so it's in theory "integrated" and in practice - cando is living it's life as far from schooltool as possible | 17:13 |
| ignas | as in - farther away than schooltool is from Zope3 | 17:13 |
| aelkner_ | once again, things to solve this summer | 17:15 |
| aelkner_ | i'm not going to fill my head with these issues when we don't have a need to deploy the new buildout | 17:15 |
| aelkner_ | ignas: i'd like to ask an unrelated question | 17:17 |
| aelkner_ | how does the bin/start-instance end up finding the site,.zcml root? | 17:18 |
| aelkner_ | i found school.zcml in the instance dir | 17:19 |
| aelkner_ | who looks for that? | 17:19 |
| ignas | schooltoo.conf | 17:20 |
| ignas | so from what I understand - there will be no Hary Cando release | 17:21 |
| ignas | Hardy | 17:21 |
| aelkner_ | i wouldn't say that | 17:22 |
| ignas | and all the jelkners cando/schooltool/buildout integration plans will be implemented after the summer | 17:22 |
| aelkner_ | hardy is in august, right? | 17:22 |
| ignas | april i think | 17:22 |
| aelkner_ | so we'll release the hardy cando after the summer | 17:22 |
| aelkner_ | or during the summer i should say | 17:22 |
| aelkner_ | after we've worked out the kinks | 17:23 |
| ignas | oh, so you are not planning on being in ubuntu | 17:23 |
| aelkner_ | oh, maybe we will, but it won't be me that works on that | 17:23 |
| aelkner_ | that will have to be for the cando team | 17:23 |
| aelkner_ | i'm not really part of that now as there isn't the funding | 17:24 |
| aelkner_ | and i'm full-time on the sla work | 17:24 |
| aelkner_ | but if jason and the interns can get that going, then fine | 17:24 |
| * th1a returns from his shower. | 17:24 | |
| ignas | to quote jelkner: "When SchoolTool gets integrated in into the core Ubuntu distro, CanDo gets integrated with it." | 17:25 |
| aelkner_ | th1a: could you make jeff understand that i can't spend all this time dealing with cando release | 17:25 |
| th1a | I'm trying to understand all the moving parts here. | 17:25 |
| th1a | We need to be able to: | 17:26 |
| th1a | a) bugfix the current CanDo. | 17:26 |
| th1a | b) have a process for whatever CanDo is being used next fall. | 17:26 |
| th1a | For a) we need to continue doing whatever crazy-assed thing CanDo has been doing. | 17:27 |
| aelkner_ | crazy-assed? i take exception :) | 17:28 |
| th1a | For b) there is no big rush. We've got until summer to come up with some packages that work as proper extensions to SchoolTool. | 17:28 |
| aelkner_ | ignas seemed to think we needed it for april | 17:28 |
| aelkner_ | but i think the summer is fine | 17:28 |
| ignas | ok, so why was jelkner planning for ccarey to work on it during pycon? | 17:29 |
| th1a | Well, the upshot is that any feature enhancements won't be released until six months out. | 17:29 |
| th1a | It seems like getting the ball rolling now makes sense. | 17:29 |
| th1a | Unstable CanDo needs to track unstable SchoolTool. | 17:30 |
| th1a | Right? | 17:30 |
| ignas | th1a: there is no such thing as stable cando | 17:30 |
| aelkner_ | yes there is | 17:30 |
| aelkner_ | trunk | 17:30 |
| aelkner_ | which depends on schooltool2007 | 17:30 |
| th1a | Well, deployed-unstable and undeployed-unstable. | 17:30 |
| ignas | look at buildbot | 17:31 |
| aelkner_ | which one? | 17:31 |
| th1a | Which what? | 17:31 |
| ignas | it's green at the moment | 17:32 |
| ignas | but i have seen a lot of buildbot failures | 17:32 |
| ignas | in my mail | 17:32 |
| ignas | in cando-checkins | 17:32 |
| aelkner_ | that was because cando buildbot needed to fix an eggs prblem | 17:32 |
| ignas | i see | 17:33 |
| aelkner_ | jason just needed to rm -rf the eggs dir to get cando builtbot to work | 17:33 |
| ignas | we seem to be disagreeing on what "stable" means though | 17:33 |
| ignas | and on whether cando needs milestones for deployment or not | 17:33 |
| aelkner_ | cando users want to be able to get fixes right away | 17:34 |
| aelkner_ | that may have to change after the summer | 17:34 |
| aelkner_ | as we bring in more users | 17:34 |
| aelkner_ | but for now | 17:34 |
| ignas | or may not have to change, as long as you have two branches | 17:34 |
| ignas | release one | 17:34 |
| aelkner_ | we just change the trunk and have them svn up | 17:34 |
| ignas | and trunk | 17:34 |
| th1a | CanDo will have to switch to a proper release model. | 17:34 |
| ignas | which would yield to users using release branch, developers working on trunk | 17:34 |
| ignas | and backporting fixes to the release | 17:35 |
| th1a | Updates will have to come through apt-get. | 17:35 |
| ignas | not necessary, just proper svn release tagging would do | 17:35 |
| aelkner_ | th1a's point is well taken | 17:35 |
| th1a | Well, *eventually* via apt-get. | 17:35 |
| aelkner_ | jelkner would prefer the apt-get approach | 17:35 |
| aelkner_ | starting next fall i figure | 17:36 |
| aelkner_ | once again, things to work out this summer in my opinion | 17:36 |
| ignas | then we don't do any buildout stuff until summer | 17:36 |
| aelkner_ | i could be involved more then as sla will slow down some at that point | 17:36 |
| aelkner_ | right, th1a? | 17:37 |
| ignas | there is no point in doing it if it will be abandoned for 4 months after being completed | 17:37 |
| th1a | I guess the question in my mind is whether there is anything to be gained by starting now. | 17:37 |
| ignas | well - if i will fix the integration branch now, and it will have to be merged into trunk in 4 months after being finished | 17:38 |
| ignas | we will get more conflicts | 17:38 |
| ignas | and no one will be using the branch for anything anyway | 17:38 |
| aelkner_ | ignas: are you going to be able to attend the cando meeting sat noon our time? | 17:38 |
| th1a | I don't like these Saturday meetings. | 17:39 |
| aelkner_ | i don't either | 17:39 |
| ignas | maybe, it's 7pm Saturday for me | 17:39 |
| aelkner_ | yes | 17:39 |
| ignas | so i can't guarantee i won't be watching a movie, or eating out during that time | 17:39 |
| ignas | i mean - it's Saturday evening | 17:39 |
| th1a | I guess whether "no one will be using the branch anyway" is the question. | 17:39 |
| aelkner_ | jelkner will have to reconsider the meeting time | 17:40 |
| th1a | Is there an advantage to having it around for ongoing development, or is it only relevant to packaging and deployment? | 17:40 |
| aelkner_ | ignas: if you're there, we can discuss this; otherwise, it can wait | 17:40 |
| ignas | th1a: i think there is | 17:40 |
| ignas | th1a: but it adds more work for cando deployment and development | 17:40 |
| aelkner_ | jelkner's right at least for getting us to think about this sooner rather than later | 17:41 |
| aelkner_ | but we may need to decide to hold off on solving it | 17:41 |
| aelkner_ | until the summer? | 17:41 |
| aelkner_ | i mean, there is no user story for having the hardy release ready for april | 17:41 |
| aelkner_ | just a wich on jelkner's part | 17:42 |
| ignas | i'd still go with "start using proper development practices even though it's more work" approach | 17:42 |
| ignas | but yes - it's not me who will be doing that work | 17:42 |
| aelkner_ | me neither | 17:42 |
| ignas | as in - I don't develop Cando features not do bugfixes | 17:43 |
| ignas | so it will add work for people who do these tasks | 17:43 |
| ignas | s/not/nor/ | 17:43 |
| th1a | I don't think changing their release practices for what's deployed now is something to worry about. | 17:43 |
| aelkner_ | jelkner's hope is to get the interns ready to handle these issues | 17:44 |
| aelkner_ | so to that end ccarey has been working with ignas | 17:44 |
| aelkner_ | but ccarey will be expected to handle this in the long run | 17:45 |
| aelkner_ | not ignas or aelkner | 17:45 |
| aelkner_ | i'd say we continue with what ccarey is doing | 17:45 |
| aelkner_ | and at pycon, we could discuss a more formal practice for going forward | 17:46 |
| aelkner_ | does that make sense? | 17:46 |
| th1a | I'm not sure what makes sense. | 17:47 |
| aelkner_ | pycon will find all interested parties in the same place drinking the same beer | 17:47 |
| aelkner_ | at that point, i'm sure we can work out what makes sense | 17:47 |
| aelkner_ | at least to a drunk | 17:47 |
| aelkner_ | but for now we can still benefit from ccarey's work | 17:48 |
| aelkner_ | we're not going to be changing cando that much that we would have serious conflicts | 17:49 |
| aelkner_ | when we try to get the buildout released | 17:49 |
| ignas | aelkner_: what ccarey is doing is what you initially were against - ccarey was working on cando integration with unstable schooltool. So you think we should continue even if it might turnout that all the work performed was just an elaborate training exercise? | 17:49 |
| aelkner_ | the training exercise is benefitial in itself, but | 17:50 |
| aelkner_ | it won't be only an exercise | 17:50 |
| aelkner_ | we've got a buildout now | 17:50 |
| aelkner_ | and at pycon it will only be a small matter to get it solid for release | 17:50 |
| th1a | I don't understand the scenario by which it is only a training exercise. | 17:51 |
| aelkner_ | that's my point | 17:52 |
| ignas | well - we do all the work, and in pycon we decide that cando is only going to start using "current" schooltool in summer | 17:52 |
| th1a | OK -- that's quite likely, right? | 17:53 |
| aelkner_ | no prob | 17:53 |
| aelkner_ | we decide it so at pycon | 17:53 |
| aelkner_ | and we keep on top of it until the summer | 17:53 |
| aelkner_ | we could have a buildbot for it and everything | 17:53 |
| th1a | Is anyone going to be writing new features for CanDo in the next 4 months? | 17:53 |
| aelkner_ | then, in the summer, we make sure it's ready for deployment to the new Virginia sites | 17:54 |
| aelkner_ | mostly bugg fixes at first | 17:54 |
| aelkner_ | i figure summer sprints will be where new features come in | 17:54 |
| aelkner_ | but front-loading the process with having ccarey working on buildout is a good idea | 17:55 |
| aelkner_ | so we'll be ready in the summer to integrate everything | 17:55 |
| ignas | "integrate everything"? | 17:56 |
| aelkner_ | get everyone using the buildout including the present cando sites | 17:57 |
| th1a | Well... again, the goal should really be having a real release ready. | 17:58 |
| ignas | aelkner_: so you disagree with jelkner on the point that it must "happen now" | 17:58 |
| th1a | Not switching people to buildout. | 17:58 |
| aelkner_ | sounds like an unfunded mandate to me :) | 17:59 |
| th1a | I think jelkner is just going on the intuitive feel that sooner is better than later. | 17:59 |
| th1a | It is generally a good assumption, if there is a risk things are going to diverge further. | 17:59 |
| ignas | th1a: I kind of agree with him on this point, as in - I think that having cando with the same process as SLA and lyceum is a good idea | 18:00 |
| ignas | even if that process might not be as lightweight :/ | 18:00 |
| aelkner_ | jelkner definitely wants cando to work like lyceum and sla | 18:00 |
| th1a | I think that's the point. | 18:01 |
| ignas | having cando interns work with the old schooltool while working on cando bugfixes | 18:01 |
| ignas | does nothing to integrate them | 18:01 |
| ignas | into working on schooltool | 18:01 |
| ignas | because they can't change the schooltool code | 18:01 |
| th1a | Well, they'll have to port the bugfixes. | 18:01 |
| ignas | th1a: you mean we would declare the buildout-integration branch the "new trunk" and have them work on it | 18:02 |
| ignas | while backporting fixes to trunk? | 18:02 |
| th1a | I guess that's more logical. | 18:02 |
| ignas | i mean, but swapping that and having it the sane way would take like 2 svn switch commands in the deployed sites | 18:03 |
| ignas | you'd just say that the current cando trunk is "release 0.1" | 18:03 |
| ignas | branch it, tag it | 18:03 |
| ignas | and make instances svn switch to the release branch | 18:03 |
| ignas | they'll still be able to do "svn up" stuff | 18:03 |
| ignas | while interns will be working on "cando 0.2dev" | 18:03 |
| ignas | and backporting bugfixes to the release branch | 18:04 |
| th1a | So is that the answer then? | 18:04 |
| ignas | like proper grown up developers | 18:04 |
| aelkner_ | i'm not sure what you mean by that | 18:05 |
| aelkner_ | sorry, confused on the branch it tag it statement | 18:05 |
| aelkner_ | sounds complicated | 18:05 |
| ignas | the main disagreement seemed to be (if I understood correctly) whether new cando development should proceed using schooltool release, or development schooltool version | 18:05 |
| aelkner_ | that's a good question | 18:06 |
| ignas | aelkner_: but it's industry standard practice i think | 18:06 |
| ignas | the tag release, work on trunk, backport fixes | 18:06 |
| ignas | part | 18:06 |
| aelkner_ | i'll take your word on that. it's just that i can't visualize the whole process just yet | 18:07 |
| aelkner_ | i'd like to see this on a whiteboard | 18:07 |
| aelkner_ | this can wait for pycon, right? | 18:07 |
| aelkner_ | in the meantime, ccarey works on the branch | 18:08 |
| aelkner_ | and bur-fixes are done in turnk | 18:08 |
| aelkner_ | to be release immediately | 18:08 |
| ignas | yes the backport to trunk can wait | 18:08 |
| aelkner_ | good | 18:08 |
| ignas | it would be nice if you would "svn merge" the fixes you do on trunk | 18:08 |
| ignas | to the branch | 18:08 |
| ignas | it would save work later | 18:08 |
| aelkner_ | that should be no problem | 18:09 |
| aelkner_ | though we don't need to merge every time we fix a bug | 18:09 |
| aelkner_ | we could do the merge at pycon | 18:09 |
| aelkner_ | or sooner if there seems to be a lot of bug fixes | 18:09 |
| aelkner_ | there might not be so many | 18:09 |
| aelkner_ | in the short term | 18:10 |
| aelkner_ | and pycon's not too far away | 18:10 |
| th1a | So I think ignas has this figured out. | 18:12 |
| ignas | by the way - who is responsible for the deployed cando instances? | 18:13 |
| th1a | Lumiere? | 18:13 |
| aelkner_ | for one, yes | 18:14 |
| aelkner_ | jelkner has the other | 18:14 |
| aelkner_ | and wbrady or mgallagher handle that one | 18:15 |
| aelkner_ | i gave them the procedure | 18:15 |
| aelkner_ | which involves svn up on the cando trunk | 18:15 |
| aelkner_ | before restarting the server | 18:15 |
| aelkner_ | they always backup Data.fs to be safe | 18:16 |
| ignas | I see, so if I will want to change the release procedure, or have them change the sandboxes a bit, I should talk to them | 18:19 |
| aelkner_ | ignas: i have some questions about lyceum versus sla | 18:20 |
| aelkner_ | i created sla and sla-buildout by cloning jelkner2007 and jelkner-buildout | 18:20 |
| aelkner_ | but lyceum seems quite different | 18:20 |
| aelkner_ | for instance, you don't have the lyceum package under schooltool | 18:20 |
| ignas | well - yes, because lyceum started out with it's own namespace | 18:21 |
| ignas | back then schooltool was not a namespace package | 18:21 |
| ignas | so you could not have schooltool.something | 18:21 |
| ignas | without having it in the same repository | 18:22 |
| aelkner_ | sla IS in the same repo | 18:22 |
| ignas | same checkout | 18:22 |
| aelkner_ | sla and sla-buildout are in trunk | 18:22 |
| aelkner_ | alongside schooltool | 18:23 |
| ignas | alongside | 18:23 |
| ignas | not *in* | 18:23 |
| ignas | which is the key difference | 18:23 |
| ignas | without schooltool being a namespace package | 18:23 |
| ignas | and schooltool was not a namespace package in the 2007 release | 18:23 |
| ignas | you can't have other eggs using "schooltool" | 18:23 |
| ignas | in their package hierarchy | 18:23 |
| aelkner_ | sla and sla-buildout are not eggs | 18:24 |
| aelkner_ | i just check out sla-buildout | 18:24 |
| ignas | sla-buildout is not | 18:24 |
| ignas | sla is an egg | 18:24 |
| ignas | you are not releasing it as an egg | 18:24 |
| aelkner_ | and it in turn checks out schooltool and sla as sibblings | 18:24 |
| ignas | but it still can be packaged as an egg | 18:25 |
| ignas | and even deployed as an egg | 18:25 |
| aelkner_ | and sla include stapp2007 | 18:25 |
| aelkner_ | but i don't need that | 18:25 |
| aelkner_ | i just need to be able to svn up it | 18:25 |
| ignas | having sla as an egg | 18:26 |
| ignas | makes it easier for you to pull in additional dependencies | 18:26 |
| ignas | makes it possible for me or someone else to refactor and package useful components of sla into separate eggs | 18:26 |
| ignas | and is a good thing to have | 18:26 |
| ignas | schooltool is an egg too, and cando is an egg actually | 18:27 |
| *** pcardune has joined #schooltool | 18:27 | |
| ignas | even though it hasn't got it's packaging procedure straightened out | 18:27 |
| aelkner_ | but i don't need to repackage sla components into anything for the next 6 months | 18:28 |
| ignas | oh and you could not have schooltool/sla if it was not an egg | 18:28 |
| aelkner_ | it isn't an egg | 18:28 |
| aelkner_ | and i do have schooltool/sal | 18:28 |
| aelkner_ | sla | 18:28 |
| ignas | it is an egg just like jelkner2007 and lyceum and tizard | 18:29 |
| aelkner_ | if you look in trunk, that's the way it is now | 18:29 |
| ignas | if you only see it in development mode | 18:29 |
| ignas | does not make it "not an egg" | 18:29 |
| aelkner_ | fair enough | 18:30 |
| aelkner_ | i don't want to think about it as an egg for now | 18:30 |
| aelkner_ | i just want to develop it | 18:30 |
| ignas | you are welcome | 18:30 |
| aelkner_ | too many things to consider | 18:31 |
| aelkner_ | i just want to develop and deploy here | 18:31 |
| ignas | well - yes, developing applications is difficult, especially if you are trying to do it in a future proof manner | 18:31 |
| ignas | well - it's what you are doing | 18:32 |
| aelkner_ | i prefer not to future proof when the future is not even certain | 18:32 |
| aelkner_ | XP practice and all | 18:32 |
| aelkner_ | XP dictates delvelop, release quickly | 18:33 |
| ignas | XP works well, unless you use ZODB | 18:33 |
| aelkner_ | get user feedback sooner rather than later | 18:33 |
| aelkner_ | hugh? | 18:33 |
| th1a | ignas: lol | 18:33 |
| aelkner_ | hw does ZODB impact XP? | 18:34 |
| ignas | like any database, it makes it difficult to perform certain kinds of refactoring | 18:34 |
| ignas | it makes it difficult if not impossible to have "no releases" | 18:34 |
| ignas | and work with a flowing trunk | 18:34 |
| * pcardune watches a losing battle for someone... | 18:34 | |
| ignas | is pcardune a zopeproject convert already or should he get baptized too? | 18:35 |
| ignas | ;) | 18:35 |
| aelkner_ | i don't see the difficulty with the flowing trunk | 18:35 |
| ignas | you never had the task "make this 6 month old database work" | 18:36 |
| pcardune | ignas: it makes it easier to write a tutorial... | 18:36 |
| pcardune | ignas: I was actually going to write a customization of zopeproject to better suit the tutorial... one without formlib | 18:36 |
| ignas | aelkner_: when you try to give your software to 100 people rather than deploy it on 2 servers some things become more difficult than others | 18:37 |
| ignas | as for - no extraction for the next 6 months | 18:38 |
| ignas | well - that's what I thought about lyceum.person and lyceum.journal | 18:38 |
| ignas | now I know how to move classes from one place to another using evolution scripts | 18:38 |
| ignas | and know how the process of removing BBB classes works | 18:39 |
| aelkner_ | what are BBB classes? | 18:42 |
| ignas | classes that are still in there to keep database backwards compatibility | 18:43 |
| ignas | you see - XP is easy to do when you can refactor anything | 18:43 |
| ignas | how can you do proper XP if you can't remove a module, because it has the schoolbell.person.Person class in it for backwards compatibility? | 18:44 |
| ignas | apparently - you can, but only if - you have public proper releases every month or six months or so, or you control all the places your application is deployed | 18:45 |
| aelkner_ | what's the acronym for BBB? | 18:45 |
| ignas | it's a comment tag | 18:45 |
| ignas | XXX - for bad things | 18:45 |
| ignas | TODO - for things to do | 18:45 |
| ignas | BBB - to note that this specific place if in there due to backwards compatibility | 18:46 |
| ignas | and should not be removed even if it looks useless | 18:46 |
| aelkner_ | oh | 18:47 |
| *** wbrady has quit IRC | 18:48 | |
| ignas | and yes - if you would look at schooltool | 18:48 |
| ignas | it still has a module named schoolbell | 18:48 |
| ignas | you would still have to have a module called "journal" in cando, if you had released cando in gutsy | 18:49 |
| th1a | ignas: OK, first question... why do I see so many sections in my list of calendars when I log in as a teacher? | 19:18 |
| th1a | Is that all the sections I've ever taught? | 19:18 |
| ignas | yes | 19:18 |
| ignas | you don't like it too, yes? | 19:19 |
| th1a | So that really should be sections from the current term? | 19:19 |
| th1a | It is pretty obviously bad. | 19:19 |
| th1a | I mean, I want to *see* those on my calendar, | 19:19 |
| ignas | could you file a bug so we'd have a permanent place for discussion | 19:19 |
| th1a | but I don't need to see them on that list, and I don't need to turn them on and off individually. | 19:19 |
| th1a | OKee. | 19:20 |
| ignas | i know, just that i don't know the proper solution yet | 19:20 |
| ignas | because if you would look at your calendar a year back | 19:20 |
| ignas | the overlay legend would show nonsense | 19:20 |
| ignas | as in - it would show colors for this term | 19:21 |
| ignas | with events from the last term | 19:21 |
| th1a | Ah. | 19:21 |
| th1a | Hm. | 19:22 |
| th1a | OK. Discussion needed. | 19:22 |
| th1a | One solution would be to only show items in the legend that have events on that day/week/month. | 19:24 |
| ignas | seems good | 19:25 |
| ignas | any Ideas for yearly view? | 19:25 |
| ignas | it might span 2 terms or even 3 terms in some schools | 19:26 |
| th1a | In terms of the legend? It isn't really a big deal if the yearly view has a hairy legend. | 19:27 |
| ignas | i guess yes | 19:27 |
| th1a | All you're going to do with that is jump to a date, I'd think. | 19:29 |
| ignas | i think so too | 19:30 |
| ignas | i'd like to have timetable events "blue or green" independent from section and a legend "timetable events" for the yearly view | 19:30 |
| ignas | but it's not necessary | 19:31 |
| ignas | and is more of a wishlist | 19:31 |
| th1a | ignas: What about this https://bugs.edge.launchpad.net/schooltool/+bug/79884 | 19:56 |
| ignas | hmm, you should try it | 19:57 |
| ignas | i think it will work in most cases now | 19:57 |
| ignas | thanks to ccarey fixing event links ;) | 19:57 |
| ignas | now when you click on an event - you ho to the edit view | 19:57 |
| ignas | and the referer will point you back to the calendar you came from | 19:57 |
| ignas | while before you were crossing the event view view | 19:57 |
| ignas | and the view view was the referer of the edit view | 19:58 |
| ignas | if it is still active | 19:58 |
| ignas | it is fixable at least | 19:58 |
| ignas | if you'd check it on the current schooltool | 19:58 |
| ignas | i'd be very glad to either close the bug | 19:58 |
| ignas | or give it to one of the interns that is looking for a task | 19:58 |
| *** th1a has left #schooltool | 20:04 | |
| *** th1a has joined #schooltool | 20:04 | |
| th1a | Well, the bug is still there if you're editing a section event. | 20:04 |
| th1a | ignas: Why don't you point an intern at it. Have them test all the cases and fix 'em. | 20:06 |
| * pcardune is glad that interns are being put to good use | 20:09 | |
| th1a | Well, we're trying. | 20:10 |
| th1a | It is hard. | 20:10 |
| ignas | not too hard | 20:11 |
| th1a | Hard to keep the interns going? | 20:11 |
| ignas | ccarey is doing quite well on the tasks that i am giving him | 20:11 |
| th1a | Good. | 20:12 |
| pcardune | th1a: you should just make all of them keep twitter accounts that they have to update every hour | 20:13 |
| ignas | :) | 20:13 |
| th1a | Or, make them log on to IRC. | 20:14 |
| pcardune | fsufitch ping | 20:14 |
| th1a | ignas: Are you getting bug emails from LP? | 20:15 |
| ignas | yes | 20:15 |
| th1a | ignas: Do you want more? | 20:32 |
| ignas | th1a: the ui for enter and tab is a bit different | 20:36 |
| ignas | when you select a row or a column | 20:36 |
| ignas | enter transfers you to the next cell in the selected area | 20:36 |
| ignas | so you could easily fill in grades for one person or one date | 20:37 |
| ignas | just hitting "grade" + <enter> + "grade" + <enter> | 20:37 |
| th1a | Ah... | 20:38 |
| ignas | it was something teachers asked me to do | 20:38 |
| ignas | and they seem to be fine with the concept | 20:39 |
| th1a | Well, it is a little less standard than doing like Excel. | 20:39 |
| ignas | it is, yes | 20:39 |
| ignas | i'll talk to them about it | 20:39 |
| th1a | Could you make tab go along a row at least? | 20:39 |
| ignas | i didn't know that excel did it this way ;) | 20:39 |
| ignas | what tab does now? | 20:39 |
| ignas | if you have a row/column selected | 20:40 |
| th1a | Return does that now? | 20:41 |
| th1a | Enter. | 20:41 |
| th1a | I still think I'm using a Commodore 64. | 20:41 |
| ignas | i'll make tab go "left" by default if there is a cell selected then | 20:42 |
| th1a | "left?" not right? | 20:42 |
| ignas | "right" | 20:42 |
| ignas | not "left" | 20:42 |
| ignas | I'll try and list you all the other missing things that lyceum people would like to see | 20:42 |
| ignas | so we could prioritize appropriately | 20:43 |
| ignas | for the upcoming release | 20:43 |
| ignas | i have a menu for lyceum that shows all the sections for a teacher | 20:43 |
| ignas | linking directly to the journal | 20:43 |
| ignas | so teacher can always easily access his sections | 20:44 |
| ignas | like " > navigation" " > actions" " > my sections" | 20:44 |
| ignas | i'll backport it to schooltool.lyceum.journal | 20:44 |
| ignas | because it seems like a good idea (for me at least) | 20:45 |
| th1a | Seems practical. | 20:46 |
| ignas | lyceum liked it better than the dashboard approach | 20:46 |
| ignas | ok, thanks for the comments, i have to go now | 20:46 |
| th1a | Good night! | 20:46 |
| ignas | but if you'll see some more things you don't want to have in the release | 20:46 |
| ignas | just file a bug, or write an email | 20:47 |
| th1a | OK. | 20:47 |
| ignas | bye | 20:47 |
| *** ignas has quit IRC | 20:47 | |
| *** pcardune has quit IRC | 21:14 | |
| *** mgedmin has quit IRC | 21:29 | |
| *** alga has quit IRC | 23:32 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!