| *** srichter has joined #zope3-dev | 00:17 | |
| projekt01 | Is somebody using ListWidget, TupleWidget or SequenceWidget? | 00:20 |
|---|---|---|
| projekt01 | srichter, Did you know that the SequenceWidget is broken! Need your suggestion for a solution! Or is anybody listen with skills to discuss this here? | 00:55 |
| *** J1m has joined #zope3-dev | 00:58 | |
| projekt01 | J1m, Ah I got someone where I can ask. ;-) Did you see that the ListWidget Is broken? | 01:00 |
| J1m | No | 01:01 |
| J1m | Are there tests failing? Or are there no tests? | 01:02 |
| projekt01 | Dman did change the constructor attributes to work with CoustomWidgetFactory at 15.1.1005 in the SequenceWidget | 01:02 |
| projekt01 | No he changed the tests too | 01:02 |
| projekt01 | Should I fix it? | 01:02 |
| J1m | That would be great. :) | 01:03 |
| projekt01 | Hes target was to use a simply constructor for working with (sel, context, request, subwidget) but it's a multi adapter | 01:03 |
| projekt01 | With (self, context, field request, subwidget) | 01:03 |
| J1m | I don't really follow that. | 01:04 |
| projekt01 | Ok, should I add a CustomSequenceWidgetFactory ? | 01:04 |
| J1m | I don't know. You may know better than I. I'd have to study the code and I don't have time now. | 01:04 |
| projekt01 | Ok, I will fix it and write a mail later to the list how we can use custom widget factory with sequence. | 01:05 |
| J1m | I haven't kept up with the custom widget work. | 01:06 |
| J1m | ok | 01:06 |
| J1m | Thanks | 01:06 |
| J1m | I've got to go. | 01:06 |
| J1m | Later. | 01:06 |
| *** J1m has quit IRC | 01:06 | |
| *** zagy has quit IRC | 01:14 | |
| *** bskahan has quit IRC | 01:20 | |
| *** mexiKON has joined #zope3-dev | 01:53 | |
| *** philiKON has quit IRC | 02:01 | |
| *** mexiKON is now known as philiKON | 02:04 | |
| *** mgedmin has quit IRC | 03:16 | |
| *** ChanServ sets mode: +o srichter | 03:18 | |
| *** mgedmin has joined #zope3-dev | 03:34 | |
| *** mgedmin has quit IRC | 03:35 | |
| *** vlado has joined #zope3-dev | 04:30 | |
| *** vlado has quit IRC | 05:22 | |
| *** projekt01 has quit IRC | 05:32 | |
| *** replaceafill has joined #zope3-dev | 06:44 | |
| *** replaceafill has quit IRC | 06:48 | |
| *** rejj has quit IRC | 08:53 | |
| *** zagy has joined #zope3-dev | 08:56 | |
| *** rejj has joined #zope3-dev | 09:26 | |
| *** zagy has quit IRC | 10:39 | |
| *** zagy has joined #zope3-dev | 10:40 | |
| *** tav has quit IRC | 11:05 | |
| *** Theuni has joined #zope3-dev | 11:07 | |
| *** tav has joined #zope3-dev | 11:20 | |
| *** ChanServ sets mode: +o tav | 11:20 | |
| *** zagy has quit IRC | 12:07 | |
| *** BjornT has quit IRC | 12:25 | |
| *** d2m has quit IRC | 12:28 | |
| *** d2m has joined #zope3-dev | 13:17 | |
| *** BjornT has joined #zope3-dev | 13:17 | |
| *** zagy has joined #zope3-dev | 15:01 | |
| rejj | is anyone alive? | 15:04 |
| philiKON | yep | 15:16 |
| rejj | too late, heh | 15:17 |
| rejj | I was trying to enter a follow-up to an issue in the collector | 15:17 |
| rejj | I've registered an account and logged in, but it still wouldn't let me | 15:18 |
| rejj | I guess that's a permissions issue | 15:18 |
| rejj | so I just mailed z3-dev instead | 15:18 |
| *** BjornT has quit IRC | 15:19 | |
| *** sashav has joined #zope3-dev | 15:33 | |
| srichter | philiKON: what was the preferred way again to call macros? | 15:40 |
| srichter | view/macroname or context/@@macroname ? | 15:41 |
| philiKON | context/@@standard_macros/macroname | 15:42 |
| srichter | thanks | 15:42 |
| rejj | Hmmm. is the zope3-dev list moderated? | 15:43 |
| philiKON | no | 15:49 |
| philiKON | but you have to be subscribed in order to be able to post | 15:49 |
| rejj | I am. | 15:49 |
| rejj | but I haven't seen my mail come back to me yet through the list | 15:49 |
| *** projekt01 has joined #zope3-dev | 15:53 | |
| rejj | aha. error on my end. heh | 16:08 |
| *** BjornT has joined #zope3-dev | 16:11 | |
| Workblia | hi | 16:14 |
| projekt01 | Do you mean, the select box misses the id attribute in the tag? | 16:43 |
| projekt01 | Do you = Workblia or somebody-else | 16:44 |
| Workblia | yup | 16:44 |
| Workblia | <select name="field.recurrence_type" size="1" > | 16:45 |
| projekt01 | In wich use case, within a Chioce Field? | 16:45 |
| Workblia | <input class="textType" id="field.title" name="field.title" size="20" type="text" value="" /> | 16:45 |
| projekt01 | Where can I see this as a example? | 16:45 |
| Workblia | a sex | 16:46 |
| Workblia | a sec | 16:46 |
| Workblia | :P | 16:46 |
| Workblia | all widgets inheriting from ItemsEditWidgetBase should miss it | 16:46 |
| projekt01 | Do you have a sample in the ZMI? | 16:47 |
| Workblia | MultiSelectWidget | 16:47 |
| Workblia | set of choices in schema | 16:48 |
| Workblia | oops | 16:48 |
| Workblia | not a set of choises | 16:48 |
| Workblia | just a Choice | 16:48 |
| Workblia | with a vocabulary | 16:48 |
| projekt01 | Do you know a sample schema which uses a choice and produce this selectbox? | 16:49 |
| projekt01 | I think there is another bug with Set field described by Jim, but that's another thing. | 16:49 |
| projekt01 | I will check it and fix it. | 16:49 |
| Workblia | projekt01, i know of that bug, i fixed it, marius commited it (at least part of that set bug) | 16:49 |
| Workblia | the part that was geting in my way | 16:50 |
| projekt01 | Is the Set field fixed? | 16:50 |
| Workblia | not exactly | 16:50 |
| Workblia | to much to fix there | 16:50 |
| Workblia | at least you can use a Set of Choises now | 16:51 |
| Workblia | and it kind of works | 16:51 |
| Workblia | as much as i tested | 16:51 |
| Workblia | s/choises/choices | 16:52 |
| projekt01 | Hm, I like to fix all widget bugs now. | 16:52 |
| projekt01 | But I have to know more about this bug. | 16:52 |
| projekt01 | What exactly can't we do with a Set field? | 16:53 |
| projekt01 | Or better what was the problem before and after marius fix? | 16:53 |
| projekt01 | And what's still missing? | 16:53 |
| projekt01 | Do you have time to explain? | 16:54 |
| Workblia | well the small fix that was made | 16:54 |
| Workblia | fixed issue - the field was expecting a set | 16:54 |
| Workblia | and was given a list | 16:54 |
| Workblia | so it would stay invalid all the time | 16:55 |
| Workblia | a small def in the right place fixed it | 16:55 |
| Workblia | yet what was noticed - | 16:55 |
| Workblia | 1 of the three multi value widgets is not used/tested anywhere at all | 16:55 |
| Workblia | no zcml for it too | 16:56 |
| Workblia | the other two are poorly tested | 16:56 |
| Workblia | they are rendered yet no one tries to pass values to them and see whether they would work in a form | 16:56 |
| Workblia | and there are 3 proposals about fixing the widgets | 16:56 |
| Workblia | so some of the tasks are described in there | 16:57 |
| Workblia | yet some are not | 16:57 |
| Workblia | kind of - no consistency, lack of discipline, and lack of use because everyone who tries using widgets decides that writing custom ones is easier than debuging zope ones ;) | 16:58 |
| projekt01 | I agree, we really have to cleanup the widgets part in z3. I totaly not happy with the situation right now. | 16:58 |
| projekt01 | I started already writing Style Guide in the onlinehelp | 16:59 |
| projekt01 | Or better say I added templates for writting Style Guides | 16:59 |
| projekt01 | Next step whould be to cleanup the widgets part | 16:59 |
| projekt01 | I really need all help which I can get. | 17:00 |
| Workblia | the part that seems difficult to me is - i don't know how should they work if they would work in a right way ... | 17:00 |
| projekt01 | I'm able to fix this part but I have to know what's wrong. | 17:00 |
| Workblia | widgets are wrong, and nobody seems to know how should they be ;) | 17:00 |
| projekt01 | Please start writting mails to the dev list if you see little mistakes or inconsistent widgets. | 17:01 |
| projekt01 | What do you mean with widgets are wrong? | 17:01 |
| Workblia | well i tried using them (though my coleagues tried to convince me that i should not try ;) | 17:01 |
| Workblia | and i encountered a lot of problems in - crossvalidation | 17:02 |
| Workblia | testing widget code | 17:02 |
| Workblia | and som ebugy widgets | 17:02 |
| projekt01 | Do you mean XHTML validation? Or what do you mean with crossvaildation | 17:03 |
| Workblia | if checkbox1 is checked then fields a,b,c are required | 17:03 |
| Workblia | a) widget has a required field which is not used | 17:03 |
| Workblia | b) widgets have no nice way of seting their error | 17:04 |
| Workblia | you can set self.date_widget.required = True | 17:04 |
| Workblia | and it will have no effect whatsoever | 17:04 |
| Workblia | bacause widget is using self.context.required instead | 17:05 |
| projekt01 | Errors, this is propossed in the proposal? Right? | 17:05 |
| Workblia | yes it is porposed in one of the proposals | 17:05 |
| projekt01 | Uhhh, What you describe is really bad, I know there are some bugs, but I didn't realized, that there are so many | 17:05 |
| projekt01 | Can you add some issuse in the bug tracker? I pormisse to solve the problems!!! | 17:06 |
| projekt01 | Or at least can you send ma a mail with describing or give some hints? | 17:06 |
| projekt01 | About the bugs | 17:06 |
| Workblia | well I don't know which parts are the bugs | 17:07 |
| Workblia | the code seems raw and untested | 17:07 |
| projekt01 | No, I mean just describe what's not correct | 17:07 |
| projekt01 | working | 17:07 |
| projekt01 | It's ok if you can describe, that some tags are not valid or you missing some id's etc | 17:08 |
| projekt01 | I will checkin another fix for the broken SequenceWidget, ListWidget and TupleWidget | 17:10 |
| projekt01 | All of them are broken | 17:10 |
| projekt01 | Waht do you think about to add a demo with a class and interface/schema where all fields are used? | 17:10 |
| projekt01 | Waht, what | 17:11 |
| projekt01 | In the src.zope.app.demo package? | 17:12 |
| projekt01 | Then we can write functional tests for testing the demo edit.html view | 17:12 |
| Workblia | would be kind of nice | 17:13 |
| projekt01 | I think that's the quickest way for find out which widget is working | 17:14 |
| projekt01 | And then we can fix the widgets step by step and refactoring the proposals | 17:14 |
| projekt01 | Implement the proposals | 17:14 |
| projekt01 | Ok, I think I add a demo | 17:15 |
| Workblia | and give me your mail ;) | 17:15 |
| projekt01 | Dev at projekt01.ch or roger at projekt01.ch | 17:16 |
| Workblia | so i could send you a short summary of the problems i have encountered (and can remember at the moment) | 17:16 |
| projekt01 | Great, that would be very nice and welcome | 17:16 |
| *** mgedmin has joined #zope3-dev | 17:23 | |
| projekt01 | mgedmin, we, Workblia and I were talking about widgets/bugs, he was talking about a Set bug? | 17:24 |
| projekt01 | Do you know something about it? | 17:24 |
| mgedmin | I was just reading the irc logs | 17:26 |
| mgedmin | I wanted to say that I did not commit anything widget-related to zope 3 last week | 17:26 |
| mgedmin | Workblia sent me a patch, but I didn't have the time to look at it yet | 17:26 |
| projekt01 | mgedmin, and what do you think about to add a demo which uses all widgets in zope.app.demo | 17:26 |
| projekt01 | Can you send me the patch | 17:26 |
| mgedmin | the set bug, I believe, is http://collector.zope.org/Zope3-dev/360 | 17:27 |
| projekt01 | Ok, I see | 17:27 |
| * mgedmin looks | 17:28 | |
| mgedmin | the patch is really simple | 17:28 |
| mgedmin | it adds two lines to class MultiSelectWidget | 17:28 |
| mgedmin | + def _toFieldValue(self, input): | 17:28 |
| mgedmin | + return sets.Set(ItemsMultiEditWidgetBase._toFieldValue(self, input)) | 17:28 |
| mgedmin | and an 'import sets' at the top | 17:28 |
| mgedmin | there are no unit tests :-/ | 17:28 |
| * Workblia hides under a big def ... | 17:29 | |
| Workblia | the test that test for the bug - breaks other widgets | 17:30 |
| Workblia | and the test for the function would be ducktape + cover | 17:30 |
| * Workblia hides under the def again | 17:31 | |
| projekt01 | Ok, I will take a look at this | 17:32 |
| projekt01 | Where is a Set used? | 17:33 |
| * Workblia looking | 17:37 | |
| Workblia | duno if it will help yet i can give some directions ... Zope3/src/zope/schema/tests/test_setfield.py | 17:39 |
| Workblia | the first test | 17:39 |
| Workblia | tests for input being a Set, and later after tracing a lot i found where the sets should be generated (_toFieldValue) | 17:40 |
| Workblia | the bug was - a list was being generated from the form inputs instead of a Set | 17:40 |
| projekt01 | Ok, I have to go, I will check it later, please send me mails if you see more widgets problems. Thanks a lot. | 17:45 |
| *** vlado has joined #zope3-dev | 18:21 | |
| * mgedmin was reading zcml sources and noticed that you can <include> the same package more than once without getting errors | 18:45 | |
| * mgedmin is pleasantly surprised | 18:45 | |
| philiKON | mgedmin, you can import the same *file* more than once actually | 18:47 |
| mgedmin | yes | 18:47 |
| mgedmin | the other day I was dreaming about dependency management for packages | 18:48 |
| mgedmin | say, package foo.x needs package foo.common | 18:48 |
| mgedmin | and package foo.y needs package foo.common | 18:48 |
| mgedmin | I thought that if I added <include package="foo.common" /> in both foo.x's and foo.y's configure.zcml files, I'd get errors | 18:48 |
| mgedmin | so I had to copy like seven different zcml slugs into package-includes when deploying the foo app | 18:49 |
| philiKON | jim changed the zcml machinery to allow importing a file several times | 18:50 |
| * mgedmin is about to commit the implementation of <meta:provides feature="apidoc" /> and <foo zcml:condition="has apidoc" ...> | 18:50 | |
| philiKON | about 6 months ago :) | 18:50 |
| philiKON | cool! | 18:50 |
| mgedmin | I would like to test it functionally before committing | 18:50 |
| mgedmin | which package currently breaks if I remove apidoc? | 18:51 |
| philiKON | why don't you find out by removing the slug? ;) | 18:51 |
| mgedmin | d'oh | 18:51 |
| mgedmin | committing | 19:00 |
| mgedmin | do you think I should commit a usage example as well? | 19:01 |
| mgedmin | I mean, meta:provides in apidoc's meta zcml and zcml:condition="have apidoc" in zwiki and bugtracker's configure.zcml files | 19:01 |
| philiKON | mgedmin, why not? | 19:02 |
| * mgedmin nods | 19:02 | |
| philiKON | i think z3 shoudl definitely be looked through for things like that | 19:02 |
| philiKON | apidoc, onlinehelp, etc... | 19:02 |
| *** Theuni has quit IRC | 19:09 | |
| *** vlado_ has joined #zope3-dev | 19:35 | |
| *** vlado has quit IRC | 19:38 | |
| *** bskahan has joined #zope3-dev | 20:07 | |
| bskahan | I'm trying to map an annotation to something easily usable from tal | 20:12 |
| bskahan | created an interface for an object to be stored in the annotation and added a property for it to the object to be annotated | 20:15 |
| bskahan | from the python interpreter, everything seems kosher, sets/gets, etc | 20:15 |
| bskahan | obj.anot.val1 works fine | 20:16 |
| bskahan | from tal I can get to obj.anot no problem, but tyring to get to val1 raises a "ForbiddenAttribute" error | 20:17 |
| bskahan | any ideas what would raise that? | 20:18 |
| srichter | mgedmin: hey, what does the name in feature do? | 20:24 |
| srichter | nothing? is it just for XML compliance? | 20:24 |
| srichter | mgedmin: nevermind | 20:25 |
| philiKON | bskahan, it's not really common practice to expose annotations through attribute | 20:30 |
| philiKON | s | 20:30 |
| philiKON | bskahan, usually, adapters that use annotations on objects, like IZopeDublinCore, are *trusted* adapters | 20:31 |
| philiKON | bskahan, which means they work with non-security-wrapped objects but have security declarations for themselves | 20:31 |
| bskahan | philiKON: thanks, I'll look at DC | 20:32 |
| *** GaryPoster has joined #zope3-dev | 20:47 | |
| *** mgedmin has quit IRC | 21:02 | |
| *** tvon|x31 has quit IRC | 21:40 | |
| *** tvon has joined #zope3-dev | 22:29 | |
| *** Workblia is now known as Awayblia | 22:30 | |
| *** tvon has quit IRC | 22:37 | |
| *** tvon has joined #zope3-dev | 22:37 | |
| *** tareks has joined #zope3-dev | 23:45 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!