| *** ignas has quit IRC | 00:01 | |
| *** ignas has joined #schooltool | 00:06 | |
| *** strichter is now known as srichter | 00:41 | |
| *** ignas has quit IRC | 01:17 | |
| *** alga has quit IRC | 02:43 | |
| *** tiredbones has joined #schooltool | 02:59 | |
| *** wrobel` has joined #schooltool | 03:19 | |
| *** wrobel has quit IRC | 03:27 | |
| *** alga has joined #SchoolTool | 05:05 | |
| *** vidasp has joined #schooltool | 06:33 | |
| *** ashik has joined #schooltool | 08:34 | |
| *** alga has quit IRC | 08:34 | |
| ashik | Can any body help me regarding localization? | 08:34 |
|---|---|---|
| ashik | Is any one here? | 08:46 |
| *** ashik has left #schooltool | 09:41 | |
| *** jfroche has joined #schooltool | 10:49 | |
| *** vidasp has quit IRC | 11:47 | |
| *** vidasp has joined #schooltool | 12:42 | |
| *** ignas has joined #schooltool | 12:53 | |
| ignas | jfroche: hi | 12:57 |
| jfroche | hello hello | 12:57 |
| ignas | anything new on your side ? | 12:57 |
| jfroche | working on a z3 product to export roundup issues to launchpad | 12:58 |
| jfroche | do you think i can commit this to schooltool repos ? | 12:58 |
| ignas | why z3 ? | 12:59 |
| ignas | and why product ? | 12:59 |
| ignas | i think roundup is written in python | 12:59 |
| jfroche | it is right | 12:59 |
| ignas | and doing an export on roundups side would be much easier | 12:59 |
| jfroche | i need practicing on z3 | 12:59 |
| jfroche | will need to work with Tom on which issue to keep | 13:00 |
| jfroche | need to export each issue to malone xml | 13:00 |
| jfroche | need to be able to select which issue to export | 13:00 |
| ignas | but still it seems like a lot of extra work | 13:00 |
| jfroche | you think i should stop ? | 13:01 |
| vidasp | jfroche: hi | 13:02 |
| jfroche | hello | 13:02 |
| ignas | i just think that there is an easier way of doing that | 13:02 |
| vidasp | how are you going to connect roundup to your z3 product? | 13:02 |
| jfroche | working with the instance | 13:03 |
| vidasp | roundup has pretty flexible web publishing framework itself | 13:03 |
| jfroche | right but i prefer to learn z3 than roundup | 13:04 |
| ignas | just, wouldn't it be wiser to do learning z3 and export issues from roundup as separate activities | 13:06 |
| ignas | because well, it's like using haskel to export roundup issues, it is possible, but probably not very convenient | 13:07 |
| ignas | as for the svn repository, I think going with bzr and publishing it on schooltool website would be better, as schooltools repository already contains more than schooltool (which makes export to bzr more complicated) | 13:09 |
| jfroche | thought you postpone the export ? | 13:10 |
| ignas | probably, depends on the state of tools at the moment | 13:11 |
| ignas | i am looking at bzr-svn now | 13:12 |
| ignas | as it should be capable of doing the export | 13:12 |
| ignas | just that keeping such tools in separate repositories is IMHO better | 13:13 |
| jfroche | which tools you mean ? | 13:14 |
| jfroche | i see that there is 1 branch for the moment in bzr | 13:16 |
| ignas | that is the problem, at the moment there is only trunk of schooltool in bzr (and it was imported automatically by launchpad i think) | 13:17 |
| ignas | but to fully migrate from svn to bzr | 13:17 |
| ignas | we have to migrate the full repository with all the branches, subproducts, and a whole lot of history | 13:17 |
| ignas | (schoolbell schooltool merge for example) | 13:17 |
| ignas | and make sure it is usable by developers after migration | 13:18 |
| jfroche | does bzr-svn can do such things ? | 13:19 |
| ignas | probably, will need some hacking | 13:19 |
| ignas | that's why it would take some time to do it properly | 13:19 |
| ignas | having products that do not share any code with schooltool in the same svn repository makes migration a bit more difficult | 13:20 |
| ignas | as such things should probably have their own bzr repositories | 13:21 |
| ignas | and not share one with schooltool | 13:21 |
| ignas | so having a z3 product that was written to learn z3 in a bzr repository is safer, yet allows one to learn bzr as well | 13:22 |
| jfroche | right | 13:30 |
| jfroche | will look at bzr yet then | 13:30 |
| ignas | do you mean "will look at bzr then" or "will not look at bzr yet then"? | 13:31 |
| jfroche | ignas: you think i should stop doing z3 now and throw what i did ? | 13:31 |
| jfroche | mean i am reading bzr doc ;) | 13:31 |
| ignas | i mean that you should spend at least 30 minutes - 1 hour looking at roundup+docs to see whether your problem can be solved in an easier way | 13:32 |
| ignas | unless you will be done with the migration real soon | 13:32 |
| jfroche | ok ll commit the product in bzr but will go into roundup then | 13:36 |
| ignas | maybe you know whether the roundup instance in schooltool server or on POV one ? | 13:36 |
| jinty | it's in the schooltool server;) | 13:37 |
| ignas | i see, can't help you much then :/ | 13:37 |
| ignas | haven't touched the custom product based on roundup a few months so my memory is flaky | 13:38 |
| jfroche | is there a custom product there ? | 13:38 |
| ignas | no, e in POV did one for our clients | 13:40 |
| ignas | but i can't really recall any places that have to be touched to add a view for issue list | 13:40 |
| ignas | without looking at a running roundup instance | 13:40 |
| ignas | jinty: what db is schooltool issue tracker using there? | 13:43 |
| ignas | jinty: if it's sqlite maybe I could get a nice tarball to try export views on, as it would take less time for me to do the export | 13:44 |
| jfroche | ignas: i have a tarball with the schooltool roundup instance | 13:45 |
| jfroche | want it ? | 13:45 |
| ignas | would be nice | 13:45 |
| ignas | it has the database with it? | 13:45 |
| jinty | I'm reasonably sure yes | 13:47 |
| jinty | I'm popping out now, but will be around later | 13:47 |
| jfroche | right instance use anydbm , data are in it | 13:48 |
| ignas | cool | 13:48 |
| ignas | is it of an emailable size | 13:49 |
| ignas | or can you just give me a link? | 13:49 |
| jfroche | 4.2 | 13:49 |
| jfroche | Mb | 13:49 |
| vidasp | jfroche: vidas@pov.lt | 13:50 |
| jfroche | i am sending it to ignas | 13:50 |
| jfroche | you want it too ? | 13:50 |
| ignas | send it to vidas | 13:50 |
| ignas | we are at the same office | 13:50 |
| jfroche | ok | 13:50 |
| ignas | and he is the one who knows roundup better than I do | 13:50 |
| jfroche | okok | 13:51 |
| ignas | what data is needed for the export xml ? | 13:54 |
| ignas | like attributes of an issue + comments | 13:54 |
| ignas | or anything more | 13:54 |
| jfroche | that's what i am waiting for | 13:55 |
| jfroche | Steve point me the guy who knows about the XML doc | 13:56 |
| jfroche | but no news from him | 13:56 |
| jfroche | to I asked Steve | 13:56 |
| jfroche | waiting for an answer | 13:56 |
| jfroche | but as soon as i have it i ll do it | 13:57 |
| jfroche | vidasp: ignas mail sent | 14:02 |
| jfroche | ignas: should i publish my branch containing the little z3 product ? | 15:32 |
| ignas | you can, though what exactly is it doing ? | 15:33 |
| *** thisfred has joined #schooltool | 15:33 | |
| jfroche | for the moment you can create a container and import roundup issues | 15:34 |
| ignas | through the web or directly from the database ? | 15:35 |
| jfroche | taking the issue directly from the roundup instance | 15:35 |
| jfroche | creating one contained object for each issue | 15:36 |
| ignas | and comments ? | 15:36 |
| jfroche | that was the next step | 15:36 |
| jfroche | but don't i ll go further | 15:36 |
| jfroche | cause i ll need to export users too | 15:36 |
| jfroche | eventhought i don't know if launchpad can create users from xml | 15:37 |
| vidasp | what do you mean saying "directly from the roundup..."? | 15:38 |
| ignas | i think users will have to register themselves | 15:38 |
| jfroche | vidasp: tracker = instance.open(self._location) | 15:39 |
| jfroche | db = tracker.open('admin') | 15:39 |
| jfroche | for roundupIssueId in db.issue.list(): | 15:40 |
| jfroche | ... | 15:40 |
| jfroche | code is there http://svn.jfroche.be/trunk/trackerexport/ | 15:55 |
| ignas | jfroche: err do you really need to add factory directives to all classes instead of just creating objects ? | 16:00 |
| jfroche | whats the best way to do ? | 16:00 |
| ignas | i'd say the shortest one | 16:00 |
| ignas | from foo.bar import Baz and Baz() | 16:01 |
| ignas | and instead of "setitem(self, self.__setitem__, roundupIssueId, issue)" self[roundupIssueId] = issue might be enough | 16:03 |
| *** jfroche has quit IRC | 16:03 | |
| *** jfroche has joined #schooltool | 16:04 | |
| ignas | jfroche: what was the last message you saw ? | 16:05 |
| jfroche | from foo.bar import Baz and Baz() | 16:05 |
| jfroche | sorry | 16:05 |
| jfroche | dummy dynamic ip address | 16:05 |
| ignas | and instead of "setitem(self, self.__setitem__, roundupIssueId, issue)" self[roundupIssueId] = issue might be enough | 16:06 |
| ignas | can't tell for sure but unit tests should catch such things | 16:07 |
| ignas | zapi.createObject is difficult to test too | 16:07 |
| ignas | unless one relies only on functional tests | 16:07 |
| jfroche | i see | 16:08 |
| jfroche | my idea was to create a MaloneIssueAdapter adapter for the IRoundupIssue which would take the attribute to Malone name | 16:09 |
| jfroche | s/name/fieldname | 16:10 |
| ignas | container.constraints.contains(ISomeInterface) and container.constraints.containers(ISomeInterface) | 16:10 |
| jfroche | wanted to be clean but its right it might be too much work for not much | 16:10 |
| ignas | are better than Field constraints | 16:10 |
| ignas | it's not clean | 16:10 |
| ignas | it's over complicated for the task | 16:11 |
| ignas | where did you find the idea of using zapi.createObject ? | 16:12 |
| ignas | i don't think it is in Zope3 tutorial | 16:12 |
| jfroche | Philikon's book | 16:13 |
| ignas | it's not publicly available :/ | 16:16 |
| jfroche | right but i think it's a good one | 16:17 |
| jfroche | ignas: does the ObjectAdded event get trigered when you do self[roundupIssueId] = issue ? | 16:24 |
| ignas | as you are inheriting from OrderedContainer and OrderedContainer is doing setitem(self, self._data.__setitem__, key, object) for you | 16:25 |
| ignas | the code you wrote might be wrong too, as you are working around all the magic of OrderedContainer | 16:26 |
| jfroche | right ok | 16:27 |
| jfroche | thanks | 16:27 |
| ignas | as for interfaces in schooltool we're doing IGroupContained(IGroup, IContained) | 16:29 |
| ignas | so one verifyObject is enough and one implements is enough | 16:29 |
| jfroche | ok | 16:30 |
| *** alga has joined #SchoolTool | 16:32 | |
| *** vidasp has quit IRC | 17:25 | |
| *** ignas has quit IRC | 17:42 | |
| *** wrobel` has quit IRC | 17:59 | |
| *** jinty has quit IRC | 18:46 | |
| *** jinty has joined #schooltool | 19:02 | |
| *** jfroche has quit IRC | 19:16 | |
| *** thisfred has quit IRC | 22:19 | |
| *** tiredbones_ has joined #schooltool | 23:13 | |
| *** tiredbones has quit IRC | 23:28 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!