IRC log of #zope3-dev for Wednesday, 2006-06-28

*** edgordon has quit IRC00:09
*** gumpa has left #zope3-dev00:13
*** mgedmin has quit IRC00:55
*** jinty has joined #zope3-dev01:01
*** J1m has quit IRC01:14
*** benji has quit IRC01:31
*** alecm has joined #zope3-dev01:33
*** hannosch has joined #zope3-dev01:43
*** tiredbones has quit IRC01:50
*** yota has quit IRC02:18
*** hannosch has quit IRC02:53
*** alecm has quit IRC02:57
*** alecm has joined #zope3-dev02:58
*** projekt01 has joined #zope3-dev03:21
*** jinty has quit IRC03:24
*** roym has quit IRC03:39
*** RaFromBRC has quit IRC03:41
*** projekt01 has quit IRC03:55
*** srichter has quit IRC04:01
*** pcardune has joined #zope3-dev04:08
*** srichter has joined #zope3-dev04:32
*** povbot` has joined #zope3-dev04:32
*** povbot has quit IRC04:32
*** ChanServ sets mode: +o srichter05:05
*** febb has joined #zope3-dev05:33
*** febb has left #zope3-dev06:07
*** jevergrl has joined #zope3-dev06:09
*** stub has joined #zope3-dev06:24
*** baijum has joined #zope3-dev06:28
*** pcardune has quit IRC06:35
*** d2m has quit IRC06:52
*** d2m has joined #zope3-dev06:52
*** flox has quit IRC06:53
*** RaFromBRC has joined #zope3-dev07:04
*** rocky has quit IRC07:08
*** RaFromBRC is now known as RaFromBRC|away07:17
*** batlogg has joined #zope3-dev07:59
*** febb has joined #zope3-dev08:06
*** sashav has joined #zope3-dev08:07
*** sashav has joined #zope3-dev08:08
febbHi all08:09
*** stub has quit IRC08:29
*** sashav has quit IRC08:31
*** eins has joined #zope3-dev08:32
einshi08:33
*** dobee has joined #zope3-dev08:36
febbhi eins , dobee08:36
einshi febb08:37
febbwhats up ?08:37
*** d2m has quit IRC08:48
*** d2m has joined #zope3-dev08:53
*** zagy has joined #zope3-dev09:03
*** stub has joined #zope3-dev09:07
febbhi all09:09
*** clasux_ has joined #zope3-dev09:21
*** baijum has left #zope3-dev09:21
*** Theuni has joined #zope3-dev09:21
*** clasux has quit IRC09:22
*** hdima has joined #zope3-dev09:28
*** romanofski has joined #zope3-dev09:37
romanofskimoin09:38
febbhi romanofski09:43
romanofskihey febb09:43
febbhow are you ?09:43
romanofskithanks fine - how are you?09:43
*** hazmat has joined #zope3-dev09:43
*** ChanServ sets mode: +o hazmat09:43
febbfine thanks.....trying to get into this Zop3 thing....but documentatio is bad. as usual.      and this is knd quiet tonight.09:45
romanofskiurks09:47
romanofskido you bought one of the zope3 books?09:47
febbwell, yes but haven't got it yet.09:49
febbi dloaded the zope 3 book in the meantime...it is very outdated.09:49
febbwe want to jump into Zope 3 but it seems as hard as a learning curve as Zope2 was...09:49
romanofskiyeah unfortunately, but there are new to come09:49
febbspecially for the "new ones".09:50
romanofskihm... I think it's much easier for the new ones to jump into zope309:50
romanofskifebb: whats the biggest problem so far febb ?09:50
febbmmm..maybe.   we are building apps (transactional applications) and are considering Zope 3 seriously ...as well as Django and turbogears....09:51
febbZope 2  was great in some sense but on the other hand it got quite messy...  so we want a Python development framework,   clean, no extra stuff.... but that helps with the tedious chores such as09:52
febbsession andling, user management, passwords, login/logout , etc.09:52
febbClear and updated documentation would be a great plus. ! of course...thats the most annoying part with Zope 2 and 3 so far.09:52
einsfebb Philipp's book is a good one09:53
einswritten in a good style:)09:54
einsand not messy at all09:54
febbof course we are willing to give back....docs, translations, docs updates, etc.. but, we have to "get it" first and decide which platform is the "good one" to work with Python, (and Apache, postgresql, ssl).09:54
febbPhilips's book.... let me look at amazon now....09:54
eins"Web component development with Zope 3"09:55
febbPhilipp von Weitershausen   got it...09:55
febblet me take a look at the index ...maybe I will order it now.09:56
einsit is worth it09:57
febbhe's got a web site also...cookery something... seems good.09:58
febbwould you say this book is current with the Zope3 latest version ?09:59
einsno10:00
einsbut the book itself is good10:00
febbmm....thats bad.   I have gotten several online Zope 3 tutorials and documentations and suddenly the reader (a Zope trainee here) discovers that the "features" on the docs are deprecated......10:01
febbDo you know if there is an electronic version and where to purchase it ?10:01
*** sashav has joined #zope3-dev10:02
philiKONfebb, http://worldcookery.com10:03
*** yota has joined #zope3-dev10:03
philiKONeins, i'm glad you like the book :_10:03
philiKON:)10:03
febbphiliKON, thanks...looks like a good book ...  ;)   (the first chapter I am looking at, so far).....10:05
febbare there plans to a new edition?  updated?10:05
philiKONyes there are plans10:05
philiKONbut no dates  yet10:05
febbI see.10:06
philiKONgotta go10:06
philiKONsee y'all10:06
febbAre there electronic versions of the book to buy it and d'load it asap ? can't find any...10:06
philiKONno, no electronic versions10:06
philiKONi need to eat too :)10:06
febbThanks philiKON.     take care.10:06
febbtoo bad no e-book version10:06
*** philiKON has quit IRC10:07
febbwell..chapter 1 reads well...but talks about Zope X3 !!!......  not really what we are looking to get into...10:08
febbquite different.10:08
einsfebb it won't be too difficult to read the book and try everything on z3.210:18
einsmost of the things works well on 3.210:18
einsjust don't panic;)10:18
febbso, a bit of patience is a good advice here, isnt it?    Did you guys developed in Zope2 before ?10:20
febbor still ?10:20
febbmostly what I need is something where a working python app (at the python interpreter level)  just gets "moved" to a web environment....with all the required bells and whistles like10:21
febbsessions, userlogin/logout, passwords, etc.10:21
febbkinda like a web wrapper for the application.  if you know what I mean.. or am looking for.10:21
einsit will be reimplementation of your web app :)10:22
einsnot just moving10:22
einsand not a simple one:)10:22
*** RaFromBRC|away is now known as RaFromBRC10:25
*** jhauser has joined #zope3-dev10:29
*** flox has joined #zope3-dev10:29
*** flox has quit IRC10:38
*** flox has joined #zope3-dev10:39
*** alecm has quit IRC10:45
*** svennhg has joined #zope3-dev10:51
*** BjornT has joined #zope3-dev11:06
*** stub has quit IRC11:07
*** roman has joined #zope3-dev11:20
*** roman has quit IRC11:21
*** romanofs1i has joined #zope3-dev11:22
*** romanofski has quit IRC11:25
*** romanofs1i is now known as romanofski11:25
*** bradb has joined #zope3-dev11:43
*** jinty has joined #zope3-dev11:50
*** RaFromBRC has quit IRC11:59
*** romanofski has quit IRC12:11
*** BjornT has quit IRC12:12
*** romanofski has joined #zope3-dev12:15
*** baijum has joined #zope3-dev12:16
*** clasux_ is now known as ClasuX12:17
*** BjornT has joined #zope3-dev12:20
*** alga has joined #zope3-dev12:32
*** flox has quit IRC12:32
*** flox has joined #zope3-dev12:35
*** faassen has joined #zope3-dev12:37
*** regebro has quit IRC12:39
*** flox has quit IRC12:40
*** flox has joined #zope3-dev12:40
*** flox has quit IRC12:43
*** alga has quit IRC12:44
*** philiKON has joined #zope3-dev12:49
*** mgedmin has joined #zope3-dev12:51
*** ignas has joined #zope3-dev13:01
*** flox has joined #zope3-dev13:02
*** alga has joined #zope3-dev13:08
*** flox has quit IRC13:15
*** flox_ has joined #zope3-dev13:15
*** flox_ is now known as flox13:15
*** mkerrin has joined #zope3-dev13:23
*** tav has quit IRC13:24
*** regebro has joined #zope3-dev13:35
*** alga has quit IRC13:55
*** philiKON has quit IRC13:56
*** rocky has joined #zope3-dev14:08
*** sashav has quit IRC14:15
*** dobee has quit IRC14:18
*** alga has joined #zope3-dev14:25
*** dobee has joined #zope3-dev14:26
*** batlogg has quit IRC14:29
*** J1m has joined #zope3-dev14:43
*** batlogg has joined #zope3-dev14:48
*** benji has joined #zope3-dev14:57
*** benji has joined #zope3-dev14:58
*** batlogg has quit IRC14:58
*** BjornT has quit IRC15:13
*** jevergrl has quit IRC15:19
*** SureshV has joined #zope3-dev15:24
*** stub has joined #zope3-dev15:34
*** Aiste has quit IRC15:39
*** sashav has joined #zope3-dev15:41
*** SureshV has quit IRC15:55
*** oferw has joined #zope3-dev15:58
*** sashav has quit IRC16:01
*** philiKON has joined #zope3-dev16:02
*** benji_york has joined #zope3-dev16:05
*** batlogg has joined #zope3-dev16:07
*** alga has quit IRC16:13
*** jukart has joined #zope3-dev16:33
*** BjornT has joined #zope3-dev16:48
*** batlogg has quit IRC16:49
*** jhauser_ has joined #zope3-dev16:52
*** baijum has left #zope3-dev16:55
*** eins has quit IRC16:58
*** BjornT_ has joined #zope3-dev16:59
*** jhauser has quit IRC17:04
floxregarding permissions and ++apidoc++17:08
floxon my dev platform, i want to give permission to zope.Anonymous17:09
floxi hav to assign 2 permissions: zope.app.apidoc.UseAPIDoc and zope.ManageApplication17:10
floxi guess we only need the APIDoc permission... is it a bug, or is it normal?17:10
*** svennhg has quit IRC17:11
floxif i give only the zope.app.apidoc.UseAPIDoc permission, I cannot reach /++apidoc++/17:14
ignashdima: ping17:14
*** BjornT has quit IRC17:14
*** alecm has joined #zope3-dev17:21
*** J1m has quit IRC17:21
*** J1m has joined #zope3-dev17:22
*** dobee has quit IRC17:27
*** BjornT_ has quit IRC17:27
hdimaignas: hi17:28
hdimaignas: something related to the bug #525?17:30
ignasyes17:31
ignaswe a.k.a. SchoolTool developers are preparing for a release17:32
ignasand as one of the parts of the application is a Calendar17:32
hdimaI think I'll rollback the change and add DateI18NWidget17:33
ignaschange in the default date format kind of breaks every integration/functional test ...17:33
hdima...before the weekend17:33
ignasoh, i hoped that there was a simple way to change the default date parser17:34
hdimaDateWidget now use zope.i18n so date/time formats now depends on the locale17:35
*** batlogg has joined #zope3-dev17:35
hdimabut the zope.i18n date/time parser is so strict for most users17:35
ignasi see :/17:36
hdimafor functional tests the format changed because the default locale (see zope/i18n/locales/data/root.xml)17:37
*** oferw has quit IRC17:37
*** BjornT has joined #zope3-dev17:38
*** BjornT_ has joined #zope3-dev17:38
hdimaThere is also a some discussion on the mail list: http://mail.zope.org/pipermail/zope3-dev/2006-June/019630.html17:38
ignasoh17:38
ignaswhat i found strange was that there is a trailing whitespace in the date format in there17:39
ignashdima: thanks for the explanation17:39
ignasi have to go now, bye17:39
hdimasee root.xml17:39
hdimaok, bye17:40
*** ignas has quit IRC17:40
*** dobee has joined #zope3-dev17:46
*** nathany has joined #zope3-dev17:52
*** stub has quit IRC17:56
*** stub has joined #zope3-dev18:02
*** nathany has quit IRC18:07
*** batlogg has quit IRC18:08
*** hdima has quit IRC18:10
Theuniwhat's the idea of a second beta? any date?18:12
*** flox has quit IRC18:37
*** strichter has joined #zope3-dev18:38
*** stub has quit IRC18:40
*** BjornT has quit IRC18:44
*** BjornT_ has quit IRC18:45
J1mTheuni, I don't think we should do a second beta until all of the critical bugs are resolves.18:48
J1m(We could decide to downgrade some, if we wish.)18:48
TheuniRight18:48
TheuniI won't be able to do anything on this until mid of next week18:48
J1mResolving bugs might be a good sprint topic for this weekend.18:48
TheuniI'm not on the sprint, though :/18:49
TheuniI'd love to help18:49
J1mYou already have quite a bit.  Of course, more help is welcome.18:49
TheuniI'll see what is left next week :)18:49
TheuniHopefully, for our release plan, nothing. :)18:50
*** BjornT has joined #zope3-dev18:50
*** gumpa has joined #zope3-dev18:53
*** srichter has quit IRC18:53
*** zagy has quit IRC19:01
*** romanofski has quit IRC19:18
SteveAis it still okay to commit to the 3.3 branch?19:26
J1mYes, for bug fixes.19:27
*** jhauser_ has quit IRC19:29
SteveAokay19:29
SteveAi made a small fix to the trunk in some BBB code for the LayerField, to allow import hooks to still work.19:29
SteveAI'd like to put that same fix on the 3.3 branch.19:30
SteveAThere is code in Zope 3 that wants to distinguish between an "immediate import failure" and an "import failure while importing something else"19:31
Theunioh yeah ... :)19:31
philiKONzope.deferredimport you mean?19:31
SteveAIt uses the number of stack frames in the ImportError to determine this.  But, this doesn't work when you have an import hook written in Python.19:31
SteveAOne way to solve this is to allow registering of code that says "I will tell you whether this is an immediate-import error or not".19:32
SteveAI don't know about zope.deferredimport.  I've seen this kind of code in a couple of places, in slightly different ways.19:32
philiKONzope.deferredimport defers improts to when the objects are acutlaly accessed19:32
mgedminthere was code somewhat like that in generations, only it checked str(exception) rather than the number of stack frames19:33
SteveAdoes it do that by poking stuff into sys.modules?19:33
mgedminit broke schooltool at the time, because str(import_error) is not very deterministic19:33
philiKONSteveA, yeah. it wraps the current module in a DeferredWrapper19:34
philiKONiirc19:34
SteveAbzr and mercurial do a similar thing19:34
SteveAto make script start-up faster19:34
Theunimgedmin:  hmm. did that happen recently?19:34
mgedmina week ago, perhaps19:34
Theunidarn19:34
Theunithat was me19:34
mgedminignas fixed it, I think19:34
SteveAthere is various badness in the standard library where importing something seemingly innoccuous causes expensive regexes in "inspect" to be compiled19:35
Theunifixed school tool or generations?19:35
SteveAwhich adds to startup time for no particular reason a lot of the time19:35
SteveAso any code which (transitively) imports inspect can be problematic.  this includes 'copy'.19:35
mgedminTheuni: generations, I think19:35
TheuniSteveA:  how much is that in absolute numbers?19:35
* SteveA was talking with lifeless (bzr developer) about this19:35
mgedminpython -c 'import copy' takes 0.142s wall clock time on my laptop19:36
mgedmintime python -c 'import inspect' takes 0.202s19:36
J1mphiliKON, I'm pretty sure he isn't talking about deferredimport19:37
philiKONi realized that too :)19:37
Theunihmm. ~ 0.056 on two of my machines over here19:38
mgedminthere seems to be a need for a single, well-tested implementation of module = optional_import('pkg.subpkg.mod')19:38
mgedminthat swallows ImportErrors when pkg.subpkg.mod does not exist19:39
mgedminbut does not do so when pkg.subpkg.mod tries to import something else, which fails19:39
Theuniyup19:39
SteveAso, there is apparently a well-tested import thinggie in bzr19:39
SteveAlifeless is getting me a reference for it19:39
philiKONmgedmin, agreed. wehat would 'module' be when pkg.subpkg.mod doesnt' exist?19:39
mgedminphiliKON: None?19:39
philiKONsounds good to me19:39
SteveAthis could be open sourced nicely (not GPL) and packaged separately if it will be useful to Zope 3 etc.19:40
Theunithat would be good19:40
Theunii know of at least two places in zope 3 (somewhere deep core and generations) that make a dance for this right now19:40
SteveAbzr branch is here: http://bzr.arbash-meinel.com/branches/bzr/demandload/19:41
Theunione inspecting the stack frame of the exception, the other one aproxiguessing the str(exc)19:41
mgedminI guess grepping for ImportError will uncover all those places19:41
Theunilikely19:41
Theunihmm. anybody knows what the intended behaviours for fields operating on new objects is?19:44
TheuniIf an object doesn't have the attribute corresponding to the field, will you get an attribute error, or take the default?19:45
TheuniI think i discovered attribute errors somewhere19:45
philiKONnot sure what you're doing19:45
* mgedmin would expect an attribute error19:45
philiKONwhere would you get the attribute error exactly?19:46
J1mattribute error19:46
J1mdefault doesn't actually make sense imo :)19:47
philiKONhmm, you all seem to know what Theuni's doing already :)19:47
J1mNo, I'm just answering his question at face value.19:47
J1mI'm not actually trying to help him. ;)19:47
philiKONperhaps he's talking about widgets :)19:47
TheuniI'm talking about fields :)19:48
mgedminthe way to use a field to get a value is field.get(obj), right?19:48
Theunijupp19:48
philiKONah19:48
mgedminand if obj doesn't have the attribute, I would expect field.get to raise an error19:48
philiKONwhat does IField say?19:48
SteveAhttp://article.gmane.org/gmane.comp.version-control.bazaar-ng.general/13491/match=demandload19:48
Theuni        """Get the value of the field for the given object."""$19:48
philiKONhmmm19:49
SteveAabout import speeds and demandload19:49
Theunion the (broken) naming convention of get() in zope 3 i'd expect an attributeerror too, now that i'm thinking more about it19:49
philiKONbroken?19:49
Theuniget/set/query19:49
J1mThere are different kinds of fields.19:49
J1mOf coursem fields shouldn't have a get method.19:50
Theuniinstead of python's notion of get19:50
SteveApython has a flexible notion of get19:50
J1mPython doesn't have one.19:50
philiKONdicts have one19:50
J1mYeah, flexible.19:50
Theuniright, that's what i'm referring to19:50
SteveAalthough, I've found Zope's 'query' API confuses people19:50
Theunipeople over here where at least annoyed by it19:51
J1mgetattr vs d.get19:51
Theunijupp19:51
Theuniin that way the z3 api is a bit unpythonic19:51
SteveAget and getdefault may be less confusing19:51
J1mhm19:51
philiKONyeah, come to think of it, it might've been better to swap 'get' and 'query' in the z3 apis...19:51
philiKONnever thought about it, actually19:51
Theunidarn! we all didn't speak up because we thought you know what you're doing!19:52
Theuni;)19:52
mgedminthe way recent bugfixes have been breaking people's software we might try to sneak that change into 3.3, and nobody would notice ;)19:52
Theunilol19:52
Theuniis it *that* bad?19:53
philiKONyeah, let's do that19:53
philiKONi think only dmitry's premature datewidget-ru fix19:53
Theuniyupp19:53
mgedminwell, maybe not that bad, but I know someone complained about one of my bugfixes19:53
mgedminand I know I complained about one of Theuni's bugfixes19:53
philiKONmgedmin, big deal, i get this all the time :)19:53
Theunitell me his name and address ... i'll stop him complaining :)19:53
Theunitip-toeing around those problems is reaaaally hard and in the end it still doesn't work19:54
Theunibut anyway, the get/set/query stuff is understood by most people by now and the need for a change is pretty small19:55
TheuniJ1m:  why did you say fields shouldn't have a 'set' method?19:55
Theunis/set/get/19:55
SteveATheuni: get/query is understood by people who already understand it.19:55
J1mBecause fields were meany to be specifications.19:55
J1mmeant19:55
philiKONSteveA, let's make zope.component2 :)19:55
J1mWe should do some sort of adaptation to get get and set.19:56
TheuniJ1m:  so you mean bound Fields would have to have those?19:56
J1msomeday19:56
SteveAit is not so easily understood by those who don't yet understand it.  And 'query' has caused semantic conflicts with a desire to make a zope3-compliant API and also support a "query" interface for querying over a collection of things.19:56
philiKON+1 to NoMoreSchemaBinding19:56
J1mTheuni, right19:56
TheuniSteveA:  hmmmm19:56
Theunik19:56
*** alga has joined #zope3-dev19:56
Theunibut the behaviour of the current get method is as you expect: raising attributeerror, right?19:57
J1mphiliKON, a few months ago I made peace with schema binding, but I don't remeber why. :)19:57
philiKONJ1m, i remember that you did, but i don't remember either why you did :)19:57
J1mYes, unless it is on an accessor.19:57
TheuniOk, i think my question is answered, then ...19:58
*** zagy has joined #zope3-dev19:59
* SteveA wonders what the schema binding issue is20:00
SteveAhttp://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/NoMoreSchemaBinding20:01
* Theuni discovers a small annoyance in the data flow between widgets and fields20:02
TheuniTo have the presentation issues totally separated between field and widget, i'd need to store the input value (getInputValue) in a slightly different form for future re-display than in the form that gets passed to field.set() later on20:04
J1mThere is a need for storage of raw input.20:05
J1mThis would be used, for example, to store incomplete and possibly incorrect input in sessions.20:05
Theuniexactly20:05
Theunithe second one is my use case20:05
*** flox_ has joined #zope3-dev20:06
J1mRight, we know we need that.20:06
Theuniok20:06
Theuni:)20:06
J1mIt has been proposed for a looong time.20:06
* mgedmin has this dream where authentication errors triggered on POST requests store the form data in a session and redirect back to the pre-filled form after a successful login20:06
mgedmin(out of the box)20:06
*** flox_ is now known as flox20:06
Theunihmm20:07
Theunididn't find a proposal immediately20:07
Theunihmm. maybe cleanup of schema and widgets20:07
Theunihm. nope.20:09
mgedminSteveA: bzr get http://bzr.arbash-meinel.com/branches/bzr/demandload/ is incredibly slow here (stuck at 20% in fetch phase 0/4 after 30 minutes)20:09
*** volvox has joined #zope3-dev20:11
SteveAmgedmin: it will take a while.  bzr get is still not optimised well, and you're downloading all of bzr :-(20:13
SteveAfortunately, there is interesting work afoot to optimize bzr a whole lot20:14
BjornTmgedmin: it'd probably be quicker to rsync down a copy of bzr and then use bzr pull --overwrite20:19
BjornTmgedmin: i guess this is the file you want, though: http://people.ubuntu.com/~bjorn/demandload.py20:20
mgedminBjornT: thanks20:21
*** strichter is now known as srichter20:22
*** ChanServ sets mode: +o srichter20:22
*** mkerrin has quit IRC20:28
Theuniwow20:31
Theunizope 3 is more than 8 years old20:31
Theunihttp://svn.zope.org/Zope3/trunk/?rev=3565&view=rev20:31
*** RaFromBRC has joined #zope3-dev20:32
Theuniand it's birthday was about a month ago20:32
*** flox has quit IRC20:35
*** flox_ has joined #zope3-dev20:36
*** flox_ is now known as flox20:36
benji/me hums "Happy Birthday to You"20:38
* benji wonders why /me wasn't escaped20:38
*** volvox has quit IRC20:38
philiKONTheuni, *Zope* is more than 8 years old20:39
Theunii know20:39
philiKONTheuni, the Zope2 CVS tree was copied over to Zope3 at some point20:39
Theunii wanted to know about zope 3 specifically20:39
philiKONZope 3 started in 2001, i believe.20:40
philiKONwe both started with it in april 2002 :)20:40
Theuniyupp20:40
Theunii know20:40
Theunigood bbq back then20:40
philiKONyup20:40
philiKONgod save the applicationcontroller20:40
* philiKON afk20:41
* mgedmin would like to hear opinions on http://www.zope.org/Collectors/Zope3-dev/65820:41
TheuniIt's say that's a URL20:42
mgedmingood guess!20:42
* Theuni wants a fish20:42
* mgedmin gives Theuni a book about fishing20:42
* Theuni eats the first picture in the book20:42
*** regebro has quit IRC20:48
* mgedmin would like to fix issue 658, but does not know which of the options to choose20:53
* Theuni initializes his random number generator20:54
*** avoine has joined #zope3-dev20:55
* mgedmin has a failing test now20:56
*** bradb has quit IRC21:02
*** Theuni has quit IRC21:03
*** romanofski has joined #zope3-dev21:06
*** batlogg has joined #zope3-dev21:31
*** J1m_ has joined #zope3-dev21:36
*** oferw has joined #zope3-dev21:36
*** J1m_ has quit IRC21:42
*** J1m has quit IRC21:42
*** J1m has joined #zope3-dev21:45
*** BjornT has quit IRC21:46
*** faassen has quit IRC21:47
*** svennhg has joined #zope3-dev21:50
*** alga has quit IRC21:53
*** mgedmin has quit IRC21:57
*** hazmat has quit IRC22:13
*** dobee has quit IRC22:22
*** mgedmin has joined #zope3-dev22:31
*** whit is now known as whit|backin522:35
*** batlogg has quit IRC22:52
*** hazmat has joined #zope3-dev23:01
*** ChanServ sets mode: +o hazmat23:01
floxbest practice is to use 'viewlets' for presentation components. right?23:04
floxwith the <browser:viewlet> and <browser:viewletManager> directives23:05
*** batlogg has joined #zope3-dev23:05
benjiflox some people use them, some don't.  I haven't yet23:07
floxi guess this is something similar to 'portlets' in Plone23:08
floxwhere u choose which boxes should appear on the left column, and right column in ur browser23:09
rockyflox: as a matter of fact there's a plip being planned for inclusion for plone 3.0 that would reimplement all the plone portlet stuff based on z3 viewlets23:10
benjiI think viewlets are more than that23:10
floxyes, more generic... and more versatile23:10
floxi will try them, i think it can fit our project23:11
* flox has found the '++skin++Debug' thing... to track errors23:15
* flox is reading fairy tales... inside ++apidoc++...23:18
srichterI like viewlets a lot23:24
srichter:-)23:24
*** projekt01 has joined #zope3-dev23:25
romanofskiyeah - thats pretty neat stuff23:25
*** dunny has joined #zope3-dev23:26
*** oferw has quit IRC23:33
*** Theuni has joined #zope3-dev23:37
*** vlado has joined #zope3-dev23:38
*** hannosch has joined #zope3-dev23:38
*** whit|backin5 is now known as whit23:39
*** mgedmin has quit IRC23:55

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