IRC log of #zope3-dev for Saturday, 2007-07-07

*** natea_ has joined #zope3-dev00:07
*** timte has quit IRC00:08
*** nathany has quit IRC00:16
*** nathany has joined #zope3-dev00:20
*** natea_ is now known as natea|away00:24
*** nerdalert has quit IRC00:28
*** derek_richardson is now known as derek|office00:28
*** d2m has quit IRC00:28
*** dunny has quit IRC00:28
X-screamI think my head just exploded00:39
*** theuni has joined #zope3-dev00:43
*** greenman has joined #zope3-dev00:52
*** pcardune has quit IRC00:56
*** redir has quit IRC01:01
*** ktwilight_ has joined #zope3-dev01:01
*** pbugni has joined #zope3-dev01:02
*** jhauser has quit IRC01:05
*** RaFromBRC is now known as RaFromBRC|lunch01:10
*** pcardune has joined #zope3-dev01:11
*** Ariel_Calzada has quit IRC01:13
*** Ariel_Calzada has joined #zope3-dev01:13
*** ktwilight has quit IRC01:16
*** Ariel_Calzada has quit IRC01:21
*** lucielejard has quit IRC01:25
*** rcrafton has quit IRC01:28
*** greenman has quit IRC01:28
*** theuni has quit IRC01:28
*** Ariel_Calzada has joined #zope3-dev01:32
*** J1m has quit IRC01:39
*** deo has quit IRC01:43
X-screami get a ComponentLookupError.  I have defined my recipeFactory = Factory(...) and configured <utility component=".recipe.recipeFactory" name="test1" ... />01:45
X-screamand run createObject(u"test1")01:45
X-screamnot sure what to do :O01:45
*** reco has joined #zope3-dev01:47
philiKONare you sure the configuratino file is loaded?01:48
X-screamno, how do I make sure that's done? I run bin/debugzope at the moment01:48
*** Ariel_Calzada has quit IRC01:49
X-screami have a __init__.py01:49
philiKONthe easiest way is to make the zcml not well-formed xml and wait for an error01:49
*** Ariel_Calzada has joined #zope3-dev01:49
philiKONif zope starts up, your zcml isn't loaded01:49
X-screamoh, it did start up even if i removed the "<" in "<configure" :)01:50
philiKONthere you go01:50
philiKONso, you're probably missing the zcml slug in package-includes01:50
X-screamoh, doh..01:50
philiKONthis is the most common mistake01:50
X-screamyay! it worked.. now i can sleep well :)01:54
*** RaFromBRC|lunch is now known as RaFromBRC02:00
*** rcrafton has joined #zope3-dev02:02
*** torkel_ has joined #zope3-dev02:10
*** pandres has quit IRC02:15
*** Ariel_Calzada has quit IRC02:20
*** pbugni has quit IRC02:25
*** andrew_m has quit IRC02:30
*** benji has quit IRC02:31
*** nathany has quit IRC02:31
*** pbugni has joined #zope3-dev02:37
*** dunny has joined #zope3-dev02:40
*** pbugni has quit IRC02:55
*** pcardune has quit IRC03:00
*** philiKON has quit IRC03:09
*** ccomb has left #zope3-dev03:12
*** bigkevmcd has quit IRC03:27
*** reco has quit IRC03:43
*** pcardune has joined #zope3-dev03:50
*** rcrafton has quit IRC04:11
*** natea|away_ has joined #zope3-dev04:26
*** natea|away has quit IRC04:35
*** natea|away has joined #zope3-dev04:55
*** rcrafton has joined #zope3-dev05:02
*** natea|away_ has quit IRC05:04
smcongrats on the release, folks05:07
smI laughed just now reading "fixed more than 12 bugs" since april.. some projects do that on a good day05:08
smthen I thought, yeah in zope 3 land 12 is probably a high number of bugs to find!05:08
CSWookiesm: Our code rawks so hard, that we have to fabricate bugs, just to get out fx counts up.05:10
CSWookies/out fx/our fix/05:10
CSWookieOR rather their code does, since I don't contribute very much.05:10
* sm thinks zope marketing should highlight this05:12
smreliable software is so unfamiliar to most people, they may not realize it's different from the rest05:13
*** rcrafton has quit IRC05:17
CSWookiesm: Too busy hiding the fact that it doesn't work with py2.505:17
* CSWookie cries.05:18
*** RaFromBRC has quit IRC05:18
*** natea|away_ has joined #zope3-dev05:24
*** jsadjohnson has quit IRC05:27
*** natea|away has quit IRC05:30
*** alecm has quit IRC05:37
*** natea|away has joined #zope3-dev05:53
*** natea|away_ has quit IRC06:00
*** rcrafton has joined #zope3-dev06:02
*** marianom has left #zope3-dev06:04
*** rcrafton has quit IRC06:05
*** niemeyer has quit IRC06:07
*** twcook has joined #zope3-dev06:09
*** Jell-O-Fishi has quit IRC06:10
*** natea|away_ has joined #zope3-dev06:22
*** natea|away has quit IRC06:30
*** natea|away has joined #zope3-dev06:37
*** twcook has quit IRC06:39
*** natea|away_ has quit IRC06:44
*** natea|away_ has joined #zope3-dev06:52
*** natea|away has quit IRC07:00
*** natea|away has joined #zope3-dev07:07
*** natea|away_ has quit IRC07:16
*** natea|away_ has joined #zope3-dev07:24
*** natea|away has quit IRC07:33
*** dunny has quit IRC07:53
*** natea|away has joined #zope3-dev08:08
*** natea|away_ has quit IRC08:16
*** natea|away_ has joined #zope3-dev08:21
*** natea|away has quit IRC08:29
*** natea|away has joined #zope3-dev08:36
*** natea|away_ has quit IRC08:43
*** torkel__ has joined #zope3-dev09:02
*** torkel_ has quit IRC09:13
*** natea|away_ has joined #zope3-dev09:21
*** natea|away has quit IRC09:29
*** natea|away has joined #zope3-dev09:34
*** jukart has joined #zope3-dev09:37
*** jukart has quit IRC09:40
*** jukart has joined #zope3-dev09:40
*** natea|away_ has quit IRC09:41
*** torkel__ has quit IRC09:48
*** torkel_ has joined #zope3-dev09:50
*** theuni has joined #zope3-dev10:13
*** alga has joined #zope3-dev10:17
*** natea|away_ has joined #zope3-dev10:21
*** natea|away has quit IRC10:28
*** d2m has joined #zope3-dev10:47
*** pcardune has quit IRC11:00
*** greenman has joined #zope3-dev11:05
*** cursor has joined #zope3-dev11:06
*** ccomb has joined #zope3-dev11:13
*** dunny has joined #zope3-dev11:14
*** jukart has quit IRC11:16
*** jinty has joined #zope3-dev11:30
*** jinty has quit IRC11:36
*** tarek has joined #zope3-dev11:39
*** oferw has joined #zope3-dev11:42
*** theuni has quit IRC11:54
*** theuni has joined #zope3-dev11:55
*** jukart has joined #zope3-dev11:58
*** jukart has quit IRC12:01
*** jinty has joined #zope3-dev12:10
*** torkel_ has quit IRC12:10
*** oferw has quit IRC12:13
*** cursor has quit IRC12:13
*** sm is now known as sm-afk12:17
*** MJ|sprint has joined #zope3-dev12:22
*** MJ|sprint is now known as MJ12:23
*** philiKON has joined #zope3-dev12:25
*** tarek has quit IRC12:35
*** tarek has joined #zope3-dev12:37
*** dobee has joined #zope3-dev12:38
*** romanofski has joined #zope3-dev12:41
*** pelle_ has joined #zope3-dev12:41
*** dobee has quit IRC12:41
*** jfroche_ has joined #zope3-dev12:42
*** jfroche has quit IRC12:55
*** pelle_ has quit IRC12:55
* theuni breaks his fingers trying to fix the object widget13:04
*** jodok has joined #zope3-dev13:06
* theuni cries a bit13:10
philiKONthe object widget is a big hack13:11
theunitell me13:12
theuniI think I tackled the object widget, now the addform stabs me in the back13:12
theuniBecause there are two parallel places in the code that may instanciate the object: applyChanges and getInputValue13:13
theuniI wonder why the AddForm doesn't call applyChanges after instanciating the object ...13:13
theuni(talking about the *ooooold* addform here)13:13
theuniHmm. I guess that the idea was that the object doesn't have to exist to compute the actual values from the widgets, that's why getInputValue doesn't really have access to that information.13:14
theuni(object = the object being added through the addform, not through the objectwidget)13:14
theuniThe only solution to this that I can see is to make the objectfield responsible for locating an object13:19
*** dunny has quit IRC13:24
theuniphiliKON: any comment on that?13:47
philiKON"locating an object" ?13:48
theuniSetting up __parent__ and maybe creating a LocationProxy13:48
philiKONhmm. you mean field.set() should do that?13:49
theuniI'm not sure whether it should, but it seems to me like that last possibility to reliably do it.13:49
philiKONwhy can't the widget do it?13:50
theuniBecause in AddForms, the widget doesn't ever get access to the parent :/13:50
theuniI started making the widget do it and then noticed that with our form frameworks this change was  basically useless.13:51
theunistupid /me13:51
philiKONdoing it in the field would make sense13:51
philiKONi think there's even a canonical form13:51
philiKONzope.location.locate() or so13:51
philiKONthat checks whether the obj implements ILocatable13:51
philiKONif not, it wraps it in a proxy13:51
theuniaha, i didn't suspect that, i'll check for that13:51
philiKONtoo bad zope.schema will grow another dependency that way :(13:52
theuniyeah, that was one of my concerns against this solution13:52
theuniespecially as schema and location doesn't really have anything todo with each other13:52
theuniit's more an accident that we need to do this to make the security happy13:52
theuniMaybe we can separate the concerns using events?13:54
theuniThe objectfield could notify an event and another module could pick that up and establish locality(?)13:54
theuniI'm not sure into which package this would go, though.13:56
*** theun1 has joined #zope3-dev14:12
*** benji has joined #zope3-dev14:18
*** andrew_m has joined #zope3-dev14:19
*** theuni has quit IRC14:22
*** dobee has joined #zope3-dev14:25
*** jinty has quit IRC14:27
*** xxbeanxx has joined #zope3-dev14:29
*** dobee has quit IRC14:34
*** jfroche_ has quit IRC14:34
*** tarek has quit IRC14:39
*** philiKON has quit IRC14:40
*** dobee has joined #zope3-dev14:49
*** Cripps has joined #zope3-dev14:52
*** CrippsFX has quit IRC14:59
*** philiKON has joined #zope3-dev15:03
*** xbeanx has quit IRC15:06
*** alga has quit IRC15:08
*** twcook has joined #zope3-dev15:24
*** jinty has joined #zope3-dev15:49
X-screamthe only reason to use RDBMS with Zope would be if you already have existing data in such a database? Otherwise if you're starting from scratch it's wise to go ZODB all the way?15:54
X-screammy planned app will deal with alot of members (free signup) and various data added by these members. Much of the things a community would have..15:56
theun1The ZODB handles this kind of data pretty good typically. However, you have to remember that you've gotta forget a bit of what you know from RDBMs and design an object system and not tables of things.15:56
*** pcardune has joined #zope3-dev15:57
X-screamtheun1: yeah, you would have to be careful with e.g referenced objects?16:00
X-screamsort of like foreign keys in RDBMS16:00
theun1Well, kind of. Typically you want to use weak references in some places, or use int ids like foreign keys.16:01
theun1The more tricky part is to make use of indexes and catalogs at the right places to allow querying your objects.16:01
*** greenman has quit IRC16:05
X-screamtheun1: ok16:06
X-screamnot fully aware of the concepts yet (catalogues?). But I'm reading some tuts now :)16:08
*** timte has joined #zope3-dev16:09
X-screambesides, you'd have to be careful planning a RDBMS too. And since I'm not very experienced in RDBMS my mind is quite open at the moment :)16:09
theun1Catalogues allow you to access collections of objects indepedently of where they are in the object graph.16:10
theun1They provide a "more" relational view on the data in the ZODB instead of a tree/hierarchy/graph.16:11
theun1Thus you can ask them questions like "Give me all objects where the attribute 'age' is 17" without having to crawl through the whole database.16:11
theun1Pretty much the same thing that allows RDBMs to be fast, except that in RDBMs the table already provides the obvious structure where to apply indexes.16:11
theun1(obvious = if you're dutch)16:12
X-screamah ok16:15
X-screamfrom what I've read so far, there seems to be no reason to use RDMBs for our project (from scratch). I'm going to read more on it, but as it looks now, I'll probably present the ZODB version to my boss16:17
X-screamand there seems to be no ORM solution that "transparently" stores my objects..16:20
theun1Depends on what transparently means.16:21
theun1SQLAlchemy goes a long way but it requires some work to make it 'transparent'.16:21
theun1And you need to set up the mappings so that it knows how to handle 1:1, 1:n n:m relations etc.16:21
X-screamwell, not as transparent as ZODB :)16:21
theun1Yes, not as transparent. :)16:21
X-screamthanks for your info btw16:23
X-screamnow I'm off to the gym :O16:24
*** jinty has quit IRC16:28
*** roym` has joined #zope3-dev16:29
*** roym` has quit IRC16:29
*** ccomb has left #zope3-dev16:54
*** cursor has joined #zope3-dev16:59
*** philiKON has quit IRC17:36
*** ccomb has joined #zope3-dev17:50
*** tarek has joined #zope3-dev17:56
*** theun1 has quit IRC18:01
*** volvox has joined #zope3-dev18:04
*** cursor has quit IRC18:21
*** cursor has joined #zope3-dev18:21
*** volvox has quit IRC18:31
*** sm-afk is now known as sm18:41
*** mkerrin has joined #zope3-dev18:43
*** schwendinger has joined #zope3-dev18:44
*** natea|away has joined #zope3-dev18:44
*** volvox has joined #zope3-dev18:50
*** natea|away_ has quit IRC18:51
*** pcardune has quit IRC19:06
*** hazmat has joined #zope3-dev19:11
*** ChanServ sets mode: +o hazmat19:11
*** volvox has quit IRC19:39
*** pcardune has joined #zope3-dev19:45
*** philiKON has joined #zope3-dev19:55
dennis__is there an event for when an object hass been published? ideally registered on an interface, such that I would get the object and the name of the view (only care about index.html)    .. idea is to update stats when a page has been viewed, not sure if this is the right approach20:02
*** pbugni has joined #zope3-dev20:02
dennis__this way it would be transparent to the object and i could add stats to any kind of object just by marking it with a certain interface20:02
afd_dennis__: there's an event for when an object is traversed20:08
afd_zc had an extension called zc.readcatalog that does what you ask, available on download.zope.org20:08
*** philiKON_ has joined #zope3-dev20:08
afd_zc.readcatalog is not there anymore, though20:10
*** schwendinger has quit IRC20:12
dennis__beforetraverse fires for all objects on the way though, doesn't it ? so mysite - some folder - some folder - object20:19
*** MJ has quit IRC20:21
*** philiKON has quit IRC20:27
*** hazmat has quit IRC20:37
*** philiKON has joined #zope3-dev20:38
*** philiKON_ has quit IRC20:38
*** afd_ has quit IRC20:58
*** J1m has joined #zope3-dev21:01
*** philiKON has quit IRC21:11
*** rcrafton has joined #zope3-dev21:16
*** mkerrin has quit IRC21:24
*** schwendinger has joined #zope3-dev21:27
*** alecm has joined #zope3-dev21:35
*** b52lap has joined #zope3-dev21:37
*** faassen has joined #zope3-dev22:15
*** J1m has quit IRC22:23
*** marianom has joined #zope3-dev22:28
*** natea|away_ has joined #zope3-dev22:29
*** dobee has quit IRC22:29
*** natea|away has quit IRC22:38
*** cursor has quit IRC22:38
*** dunny has joined #zope3-dev22:40
*** rcrafton has joined #zope3-dev22:40
*** pcardune has quit IRC22:43
*** natea|away has joined #zope3-dev22:44
*** mkerrin has joined #zope3-dev22:48
*** natea|away_ has quit IRC22:52
*** rcrafton has quit IRC22:52
*** faassen has quit IRC23:14
*** natea|away_ has joined #zope3-dev23:17
*** mkerrin has quit IRC23:18
*** natea|away has quit IRC23:25
*** d2m has quit IRC23:29
*** natea|away has joined #zope3-dev23:32
*** natea|away_ has quit IRC23:39
*** schwendinger has quit IRC23:46

Generated by 2.15.1 by Marius Gedminas - find it at!