IRC log of #zope3-dev for Saturday, 2006-09-30

*** ktwilight has quit IRC00:10
*** ktwilight has joined #zope3-dev00:14
*** reco has quit IRC00:18
*** harobed has quit IRC00:18
*** ianbicking has joined #zope3-dev00:31
timteI see two different patterns in code.00:37
timtefrom zope import component00:38
timtecomponent.provideAdapter(...)00:38
timteor00:38
timtefrom zope.component import provideAdapter(...)00:38
timteprovideAdapter(...)00:38
timteWhat's preferred?00:38
*** ktwilight has quit IRC00:41
*** ktwilight has joined #zope3-dev00:42
*** natea has joined #zope3-dev00:52
*** ktwilight has joined #zope3-dev00:55
*** timte has quit IRC01:04
*** ErikRose has quit IRC01:06
*** dlk has left #zope3-dev01:14
*** ofer has quit IRC01:18
*** benji has quit IRC01:19
*** ktwilight has quit IRC01:21
*** edgordon_ has joined #zope3-dev01:29
*** dobee has quit IRC01:46
*** edgordon_ has quit IRC01:48
*** ErikRose_ has joined #zope3-dev01:59
*** ofer has joined #zope3-dev02:04
*** edgordon has joined #zope3-dev02:06
*** ErikRose_ has quit IRC02:12
*** J1m has quit IRC02:18
*** flox has quit IRC02:19
*** dunny has quit IRC03:09
*** ofer has quit IRC03:23
*** philiKON has joined #zope3-dev03:27
*** batlogg has joined #zope3-dev03:28
*** batlogg has quit IRC03:30
*** wrobel has quit IRC03:41
*** edgordon has quit IRC03:41
*** vlado has joined #zope3-dev05:17
*** alecm has quit IRC05:31
*** benji has joined #zope3-dev05:34
*** alecm has joined #zope3-dev05:37
*** yota has quit IRC05:39
*** niemeyer has quit IRC07:00
febbhello all !07:36
*** febb has quit IRC08:03
*** natea_ has joined #zope3-dev08:10
*** natea has quit IRC08:21
*** alecm has quit IRC08:31
*** timte has joined #zope3-dev08:39
*** natea_ has quit IRC09:34
*** dobee has joined #zope3-dev10:41
*** ktwilight has joined #zope3-dev10:56
*** ktwilight_ has joined #zope3-dev11:16
*** ktwilight has quit IRC11:26
*** ktwilight_ is now known as ktwilight11:26
*** ktwilight_ has joined #zope3-dev11:36
*** dlk has joined #zope3-dev11:36
*** ktwilight has quit IRC11:38
*** ktwilight_ is now known as ktwilight11:38
*** harobed has joined #zope3-dev11:41
*** ktwilight_ has joined #zope3-dev11:45
*** dobee has quit IRC11:50
*** ktwilight has quit IRC11:52
*** harobed has quit IRC11:54
*** harobed has joined #zope3-dev11:54
*** ktwilight has joined #zope3-dev11:57
*** flox has joined #zope3-dev12:01
*** jukart has joined #zope3-dev12:05
*** ktwilight_ has quit IRC12:10
*** ktwilight_ has joined #zope3-dev12:16
*** ktwilight has quit IRC12:24
*** ktwilight_ is now known as ktwilight12:24
harobedphiliKON: you are here ?12:26
*** jukart has quit IRC12:33
*** vlado has quit IRC12:35
timteIf I add and register a utility using zmi, shouldn't I be able to queryUtility(IMyInterface, 'utilityname') ?12:44
timteit returns None12:44
*** ktwilight has quit IRC12:49
*** flox has quit IRC13:01
philiKONtimte, sure, but only in that site13:02
timteI use the default one13:02
philiKONoh, and 'utilityname' has to be the name with which you registered the utility13:02
timteyes it is13:03
philiKONnot the URL name of the object13:03
philiKONharobed, yes, what is it13:03
timtezmi registration says "events.interfaces.IEventUtility utility named 'eventtool'"13:04
timtequeryUtility(IEventUtility, 'eventtool') returns None though13:04
philiKONwhere do you do the queryUtility call?13:04
timtedoes queryUtility know which site to look in?13:04
timtein a zopectl debug session13:05
philiKONit knows after traversal13:05
philiKONwell, that's your problem13:05
philiKONyou haven't traversed to anything yet13:05
philiKONhow would it know where to look13:05
philiKONyou need to imitate traversal to the site13:05
timtethat's what the magic of zope should solve  ;)13:05
philiKONthere's no magic13:05
philiKONfrom zope.app.component.site import setSite13:05
philiKONsetSite(root)13:06
timtecool, it works13:07
timtethanks13:08
timteDoes it make sense to store events in an event utility? To me it doesn't make sense to store them in a certain folder, I think they should be placeless and then I think of utiliities.13:09
*** baijum has joined #zope3-dev13:11
philiKONwhat kind of events?13:12
timtecontent types with start, end and location13:15
*** jukart has joined #zope3-dev13:21
philiKONtimte, doesn't feel like a utility to me13:28
philiKONbut it's your call :)13:28
timtecertainly  :)13:32
timtebut I don't know what alternatives there are13:32
harobedphiliKON: you are see that http://mail.zope.org/pipermail/zope3-users/2006-September/004646.html13:33
philiKONharobed, read the docs!13:33
philiKONyou're asking many many questions that are answered by the docs13:34
harobedok, I read13:34
*** zagy has joined #zope3-dev13:35
philiKONharobed, please don't ask further questions till you have read the docs13:35
timtewhat are the alternatives? Is there any other alternative than storing them in a certain event-folder?13:36
philiKONstore them where you want13:36
philiKONit all depends on your use case13:36
timteit's not a folder users are meant to visit13:37
harobedphiliKON: I read zope/app/keyreference/persistent.txt but I don't solve my issue13:37
harobeddocumentation is very scatter13:38
philiKONpersistent.txt explain NotYet13:38
harobedyes, I know, but in my last test I use ztapi.provideAdapter(IPersistent, IConnection, connectionOfPersistent)13:39
harobedand it doesn't work13:39
philiKONyou have to save your object in the zodb first (e.g. transaction.commit() or transaction.savepoint()), or have its __parent__ be a saved object13:39
philiKONharobed, don't use ztapi13:39
philiKONharobed, documentation is not scattered, it's collectedin the apidoc book13:41
harobedok, I'm going study13:42
*** ofer has joined #zope3-dev13:43
harobedI think than I don't understand the base of Zope 313:44
harobedI'm going to reread persistent layer13:44
philiKONwhatever13:45
*** jukart has quit IRC13:52
*** jukart has joined #zope3-dev14:38
*** zagy has quit IRC14:38
*** dunny has joined #zope3-dev15:00
*** flox has joined #zope3-dev15:19
*** mexiKON has joined #zope3-dev15:25
*** projekt01 has joined #zope3-dev15:26
projekt01benji, ayt15:27
*** jukart has quit IRC15:28
projekt01Does anybody know why a Data.fs generated during generation tests is 4 times bigger on linux then on windows?15:29
*** philiKON has quit IRC15:33
*** jukart has joined #zope3-dev15:33
*** regebro has joined #zope3-dev15:38
*** rocky|away has quit IRC15:42
*** rocky has joined #zope3-dev15:46
*** ofer has quit IRC15:54
*** jukart has quit IRC15:56
*** natea has joined #zope3-dev16:01
*** baijum has quit IRC16:03
romanofskimoin :)16:10
*** projekt01 has left #zope3-dev16:16
*** regebro has quit IRC16:22
*** regebro has joined #zope3-dev16:23
*** alecm has joined #zope3-dev16:41
*** batlogg has joined #zope3-dev16:42
*** natea is now known as natea|away16:48
*** dobee has joined #zope3-dev16:52
*** yota has joined #zope3-dev16:58
*** natea|away has quit IRC17:30
*** natea has joined #zope3-dev17:33
*** dunny has quit IRC17:50
*** regebro has quit IRC18:01
*** jukart has joined #zope3-dev18:16
*** jkakar has quit IRC18:22
*** batlogg has quit IRC18:24
*** batlogg has joined #zope3-dev18:25
*** mexiKON is now known as philiKON18:26
*** tonico has joined #zope3-dev18:33
*** regebro_ has joined #zope3-dev19:57
*** regebro_ is now known as regebro19:57
*** flox has quit IRC19:59
*** Aiste has quit IRC20:00
*** MiUlEr has joined #zope3-dev20:01
timtewhat is this a symtom of?20:03
timteTypeError: ('object.__new__(Event) is not safe, use persistent.Persistent.__new__()', <function _reconstructor at 0xb7e0d064>, (<class 'events.event.Event'>, <type 'object'>, None))20:03
benjitimte: it doesn't appear that persistent objects are meant to be used that way20:06
timtemy Event class inherited from object before, but I changed to Persistent20:07
radixdid you fix all the upcalls?20:07
timtewhat?20:08
MiUlErhi20:08
radixtimte: upcalling is when you call a superclass' method from an overridden method20:08
timteradix: ah, I have an init method without an upcall, maybe that's what20:09
timtewhat's wrong20:09
*** regebro has quit IRC20:13
timteIt was caused by me changing the superclass method. It didn't like that.20:15
timteDo you have to write migration scripts if you choose a new superclass to inherit from?20:16
d2mi get this when running from a custom site.conf "ConfigurationError: ('Invalid value for', 'menu', "ImportError: Couldn't import zmi_views, No module named zmi_views")" -- any hints what to include to make that go away ?20:19
*** jukart has quit IRC20:20
d2mthe error is triggered from a <page ... menu="zmi_views"> directive20:21
timtewhat if you specify browser:page?20:22
d2mi already did <include package="zope.app.publisher.browser" file="meta.zcml" />, but "zmi_views" is defined somewhere a place i could not find so far20:24
radixtimte: generally, you need to migrate data when assumptions about data change. it's not unlikely at all that changing which superclass to use for a class will change assumptions about data.20:24
timtebah, I renamed my utility to IEventUtility, now when I want to add an Event it thinks I want to add EventUtility20:24
timteradix: I have no idea how to write such migration scripts though  :/20:26
*** flox has joined #zope3-dev20:26
timted2m: what happens if you add the browser namespace in the configure tag?20:31
*** harobed has quit IRC20:32
d2mtimte: its already there, as default namespace of the included config file20:34
d2mi think there is a machinery setting up zmi_views (and zmi_actions) that is not done through configuration20:35
philiKONd2m, is this in five?20:35
d2mno, i 'simply' try to bootstrap a site.conf in order to a songle package (apidocs) running20:36
d2mso i created an site.conf, only included the "zopeskel/etc/package-includes/apidoc-*.zcml" files and now try to include all dependencies to get the config run20:38
philiKONright. you need to define the zmi_views menu20:38
philiKON<browser:menu name="zmi_views" /> or something like that20:39
timte"This object isn't yet registered."20:39
timteWhat does this mean?20:39
philiKONit's not registered as a local utility yet20:42
d2mphiliKON: cool, <browser:menu id="zmi_views" /> did it so far, thanks20:42
philiKONnp20:42
*** regebro has joined #zope3-dev20:42
timtebut it's a content type I'm trying to add, not a utility20:43
philiKONthen don't register it :)20:43
timtebut it suggests me to, that's confusing  :)20:43
philiKONthen disable it20:44
philiKONyou can register it any object20:44
philiKONso that's why the view is there for all objects20:44
philiKONjust like you could use <utility /> with any object20:45
timteok, so if I don't have a "view" view, then I get the registration view20:45
timtecan the registration view be disable for all objects that are not utilities?20:46
philiKONhow would you know it's a utility?20:46
timteutilities are specified in zcml, no?20:47
philiKONlocal utilities aren't20:47
philiKONnot necessarily at least20:47
timteoh20:48
philiKONthat's what the Registration tab is for, dude20:48
philiKONregistering an object as a local utility20:48
timteI see20:49
regebroOK, having the local registration view end up as default may not be very intuitive. Maybe we should fix that.20:56
regebroLike when you get the undo-screen in the ZMI because you haven't defined anything else. :)20:56
* regebro has 2 cents20:57
*** regebro has quit IRC20:57
*** dobee has quit IRC21:01
*** batlogg has quit IRC21:11
*** batlogg has joined #zope3-dev21:30
*** alecm has quit IRC21:30
*** russf has joined #zope3-dev21:40
*** ktwilight has joined #zope3-dev21:40
*** RaFromBRC has quit IRC21:46
*** Aiste has joined #zope3-dev22:02
*** ktwilight has quit IRC22:02
*** alecm has joined #zope3-dev22:10
*** alecm has quit IRC22:19
*** jukart has joined #zope3-dev22:20
rockyanyone know if i can use multiple component.adapts() lines to adapt multiple interfaces individually ?22:22
rockyzope.component.adapts()22:22
*** alecm has joined #zope3-dev22:24
philiKONno22:28
rockythat's too bad22:28
philiKONadapts(), implements() etc. can only occur ones22:28
philiKONonce22:28
philiKONyup22:28
benjirocky: if it's technically possible, I'm sure that feature would be accepted if you want to add it22:29
*** ktwilight has joined #zope3-dev22:33
rockyindeed22:41
*** batlogg has quit IRC22:44
*** ktwilight has quit IRC22:52
*** dunny has joined #zope3-dev23:21
*** jinty has joined #zope3-dev23:32
*** ofer has joined #zope3-dev23:35
*** jukart has quit IRC23:37
*** timte has quit IRC23:49
*** oggers has joined #zope3-dev23:51
*** MiUlEr has quit IRC23:55

Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!