| *** zagy has quit IRC | 00:07 | |
| *** gumpa-away has left #zope3-dev | 00:12 | |
| *** BjornT has joined #zope3-dev | 00:22 | |
| *** projekt01 has joined #zope3-dev | 00:43 | |
| *** pcardune has quit IRC | 01:08 | |
| *** SmokeyD is now known as SmokeyD|gone | 01:36 | |
| *** tonico has quit IRC | 01:41 | |
| *** benji has quit IRC | 01:44 | |
| *** nathany has quit IRC | 01:49 | |
| *** niemeyer has quit IRC | 02:02 | |
| *** pcardune has joined #zope3-dev | 02:14 | |
| *** RaFromBRC has joined #zope3-dev | 02:36 | |
| *** febb has joined #zope3-dev | 03:20 | |
| *** MiUlEr has joined #zope3-dev | 03:48 | |
| *** MiUlEr has joined #zope3-dev | 03:49 | |
| *** MiUlEr has left #zope3-dev | 03:49 | |
| *** projekt01 has quit IRC | 03:56 | |
| *** rocky is now known as rocky|Zzz | 03:57 | |
| *** MiUlEr has joined #zope3-dev | 03:57 | |
| *** whit has quit IRC | 04:07 | |
| *** whit has joined #zope3-dev | 04:10 | |
| *** MiUlEr has quit IRC | 04:21 | |
| *** MiUlEr has joined #zope3-dev | 04:21 | |
| *** RaFromBRC has quit IRC | 04:24 | |
| *** whit has quit IRC | 04:46 | |
| *** alecm has quit IRC | 04:47 | |
| *** pcardune has quit IRC | 05:03 | |
| *** vlado has joined #zope3-dev | 05:10 | |
| *** stub has joined #zope3-dev | 05:16 | |
| *** vlado has quit IRC | 05:18 | |
| *** benji has joined #zope3-dev | 05:19 | |
| *** yota has quit IRC | 05:51 | |
| *** hazmat has quit IRC | 05:57 | |
| *** hazmat has joined #zope3-dev | 05:58 | |
| *** ChanServ sets mode: +o hazmat | 05:58 | |
| *** whit has joined #zope3-dev | 06:07 | |
| *** whit has quit IRC | 06:10 | |
| *** peter_ has joined #zope3-dev | 06:10 | |
| *** baijum has joined #zope3-dev | 06:39 | |
| *** TresEquis has quit IRC | 06:45 | |
| *** peter_ has left #zope3-dev | 06:58 | |
| *** baijum has quit IRC | 07:02 | |
| *** flox has quit IRC | 07:19 | |
| *** flox_ has joined #zope3-dev | 07:19 | |
| *** flox_ is now known as flox | 07:19 | |
| *** flox has quit IRC | 07:20 | |
| *** flox_ has joined #zope3-dev | 07:21 | |
| *** flox_ is now known as flox | 07:21 | |
| *** flox has quit IRC | 07:22 | |
| *** flox_ has joined #zope3-dev | 07:23 | |
| *** flox_ is now known as flox | 07:23 | |
| *** flox has quit IRC | 07:30 | |
| *** hazmat has quit IRC | 07:32 | |
| *** hazmat has joined #zope3-dev | 07:37 | |
| *** ChanServ sets mode: +o hazmat | 07:37 | |
| *** flox_ has joined #zope3-dev | 07:38 | |
| *** flox_ is now known as flox | 07:38 | |
| *** dunny_ has joined #zope3-dev | 07:47 | |
| *** stub has quit IRC | 07:50 | |
| *** flox_ has joined #zope3-dev | 07:50 | |
| *** flox has quit IRC | 07:51 | |
| *** flox_ is now known as flox | 07:51 | |
| *** flox has quit IRC | 08:01 | |
| *** dunny has quit IRC | 08:02 | |
| *** flox_ has joined #zope3-dev | 08:03 | |
| *** baijum has joined #zope3-dev | 08:03 | |
| *** flox_ is now known as flox | 08:05 | |
| *** dunny__ has joined #zope3-dev | 08:05 | |
| *** flox_ has joined #zope3-dev | 08:12 | |
| *** flox has quit IRC | 08:12 | |
| *** flox_ is now known as flox | 08:12 | |
| *** dunny___ has joined #zope3-dev | 08:12 | |
| *** dunny_ has quit IRC | 08:14 | |
| *** dunny__ has quit IRC | 08:16 | |
| *** dunny___ is now known as dunny | 08:17 | |
| *** flox has quit IRC | 08:27 | |
| *** flox_ has joined #zope3-dev | 08:28 | |
| *** flox_ is now known as flox | 08:28 | |
| *** flox_ has joined #zope3-dev | 08:31 | |
| *** flox has quit IRC | 08:31 | |
| *** flox_ is now known as flox | 08:31 | |
| *** baijum has quit IRC | 08:32 | |
| *** hazmat has quit IRC | 08:36 | |
| *** hazmat has joined #zope3-dev | 08:37 | |
| *** ChanServ sets mode: +o hazmat | 08:37 | |
| *** hazmat has quit IRC | 08:37 | |
| *** flox_ has joined #zope3-dev | 08:39 | |
| *** flox has quit IRC | 08:40 | |
| *** flox_ is now known as flox | 08:41 | |
| *** flox_ has joined #zope3-dev | 08:43 | |
| *** flox has quit IRC | 08:44 | |
| *** flox_ is now known as flox | 08:44 | |
| *** febb has quit IRC | 08:45 | |
| *** flox_ has joined #zope3-dev | 09:05 | |
| *** flox has quit IRC | 09:05 | |
| *** flox_ is now known as flox | 09:05 | |
| *** MiUlEr has quit IRC | 09:07 | |
| *** flox_ has joined #zope3-dev | 09:07 | |
| *** flox has quit IRC | 09:08 | |
| *** flox_ is now known as flox | 09:08 | |
| *** flox_ has joined #zope3-dev | 09:09 | |
| *** flox has quit IRC | 09:10 | |
| *** flox_ is now known as flox | 09:10 | |
| *** dunny_ has joined #zope3-dev | 09:20 | |
| *** flox_ has joined #zope3-dev | 09:26 | |
| *** flox_ has quit IRC | 09:28 | |
| *** flox_ has joined #zope3-dev | 09:29 | |
| *** flox has quit IRC | 09:30 | |
| *** flox_ is now known as flox | 09:30 | |
| *** flox has quit IRC | 09:38 | |
| *** flox_ has joined #zope3-dev | 09:41 | |
| *** flox_ is now known as flox | 09:41 | |
| *** dunny has quit IRC | 09:42 | |
| *** SmokeyD|gone is now known as SmokeyD | 10:04 | |
| SmokeyD | good morning | 10:07 |
|---|---|---|
| *** dunny__ has joined #zope3-dev | 10:11 | |
| *** dunny__ has quit IRC | 10:15 | |
| *** dunny_ has quit IRC | 10:26 | |
| *** dunny__ has joined #zope3-dev | 10:27 | |
| *** philiKON has joined #zope3-dev | 10:28 | |
| *** flox_ has joined #zope3-dev | 10:30 | |
| *** flox has quit IRC | 10:31 | |
| *** flox_ is now known as flox | 10:31 | |
| SmokeyD | HEY, HOW CAN i FIND MY ZOPE VERSION | 10:43 |
| SmokeyD | sorry for the caps | 10:43 |
| SmokeyD | I know it's version 3, but there seems to be no place, either in the zmi or through command line options to see the eaxct version | 10:43 |
| SmokeyD | I can't find it in the listing from the server on screen, I can't find it anywhere in any of the executables with a -V option or something | 10:44 |
| *** dunny__ has quit IRC | 10:46 | |
| *** flox_ has joined #zope3-dev | 10:59 | |
| *** flox__ has joined #zope3-dev | 11:07 | |
| *** flox_ has quit IRC | 11:08 | |
| *** flox has quit IRC | 11:08 | |
| *** flox__ is now known as flox | 11:08 | |
| *** flox__ has joined #zope3-dev | 11:17 | |
| *** flox has quit IRC | 11:18 | |
| *** flox__ is now known as flox | 11:18 | |
| *** baijum has joined #zope3-dev | 11:36 | |
| SmokeyD | hey all, I've got a question. I want to make my own widget for Float schema fields. Nothing fancy, I just want to display thye input field, no text, title, etx | 11:46 |
| SmokeyD | what is the best place to override this | 11:46 |
| SmokeyD | should I make my complete own widget or can I inhherit from float and override just one small thing? | 11:47 |
| SmokeyD | or is it just a matter of my own template for the form? | 11:51 |
| *** flox has quit IRC | 11:58 | |
| *** flox__ has joined #zope3-dev | 11:58 | |
| *** flox__ is now known as flox | 11:59 | |
| *** baijum has quit IRC | 12:00 | |
| *** philiKON has quit IRC | 12:05 | |
| *** flox__ has joined #zope3-dev | 12:06 | |
| *** flox has quit IRC | 12:07 | |
| *** flox__ is now known as flox | 12:07 | |
| *** dunny__ has joined #zope3-dev | 12:07 | |
| *** philiKON has joined #zope3-dev | 12:09 | |
| *** batlogg has joined #zope3-dev | 12:15 | |
| *** zagy has joined #zope3-dev | 12:29 | |
| *** flox__ has joined #zope3-dev | 12:55 | |
| *** flox has quit IRC | 12:55 | |
| *** flox__ is now known as flox | 12:56 | |
| *** waglik has joined #zope3-dev | 13:13 | |
| waglik | hello! | 13:13 |
| waglik | is there a howto about workflow components in zope3? | 13:14 |
| *** dunny__ has quit IRC | 13:15 | |
| flox | waglik: see zope.wfmc, zope.app.wfmc and zope.app.workflow on svn.zope.org, maybe | 13:23 |
| waglik | ok, thx | 13:24 |
| *** dobee has joined #zope3-dev | 13:26 | |
| *** flox__ has joined #zope3-dev | 13:49 | |
| *** baijum has joined #zope3-dev | 13:55 | |
| SmokeyD | hi guys, how do I use my own template in FormBase instead of template=namedtemplate.NamedTemplate('default')? | 14:02 |
| SmokeyD | what do I pass to NamedTemplate? | 14:02 |
| *** flox has quit IRC | 14:03 | |
| *** flox__ is now known as flox | 14:04 | |
| *** flox has quit IRC | 14:08 | |
| baijum | SmokeyD: have a look at this and previous mails http://mail.zope.org/pipermail/zope3-users/2005-December/001691.html | 14:09 |
| *** flox__ has joined #zope3-dev | 14:09 | |
| *** flox__ is now known as flox | 14:10 | |
| SmokeyD | ok thanks baijum, that helps | 14:11 |
| SmokeyD | I didn't know it was done using an adapter in the configure.zcml | 14:12 |
| SmokeyD | that clears things up | 14:12 |
| SmokeyD | :) | 14:12 |
| SmokeyD | thanks a lot | 14:12 |
| baijum | SmokeyD: welcome :) | 14:13 |
| *** rocky|Zzz is now known as rocky | 14:32 | |
| *** oferw has joined #zope3-dev | 14:36 | |
| *** projekt01 has joined #zope3-dev | 14:38 | |
| *** waglik has quit IRC | 14:39 | |
| *** brupp has joined #zope3-dev | 14:58 | |
| *** yota has joined #zope3-dev | 15:01 | |
| *** BjornT has quit IRC | 15:10 | |
| *** oferw has quit IRC | 15:14 | |
| *** BjornT has joined #zope3-dev | 15:15 | |
| *** dobee has quit IRC | 15:20 | |
| flox | hi | 15:27 |
| flox | there's no clear statement that some ZCML directives are deprecated when i read /++apidoc++/ZCML/ | 15:28 |
| flox | i plan to commit some documentation changes in order to fix that. | 15:29 |
| flox | example: """ *BBB: DEPRECATED* """ at the beginning of the directive class | 15:30 |
| philiKON | flox, perhaps some more informative messages? | 15:31 |
| philiKON | e.g. BBB: This directive has beend eprecated and will be removed xyzf | 15:31 |
| flox | philiKON: maybe, but i do not want to duplicate some information that is already in the "metaconfigure.zcml" | 15:31 |
| philiKON | why not? duplicate it | 15:32 |
| flox | ok | 15:32 |
| philiKON | BBB markers can't be overstated | 15:32 |
| benji | flox: if you could find a way to reuse the existing deprecation warning text, that would be good (but might require parsing the code) | 15:34 |
| flox | benji: this implies changes on the ++Apidoc++ thing | 15:35 |
| benji | yep | 15:35 |
| *** zagy has quit IRC | 15:36 | |
| SmokeyD | sorry, but I'm gonnam bug you with another question :) | 15:36 |
| SmokeyD | How do I access a tuple in a pt? Ive got this: | 15:37 |
| SmokeyD | <tr tal:repeat="costtype view/costTypes"> | 15:37 |
| SmokeyD | <td tal:content="costtype/0"></td> | 15:37 |
| SmokeyD | <td tal:repeat="budgettype view/budgetTypes">widget</td> | 15:37 |
| SmokeyD | </tr> | 15:37 |
| SmokeyD | but I get the error that tuple indices should be integers | 15:37 |
| SmokeyD | eacht row in costTypes is indeed a tuple | 15:38 |
| SmokeyD | so I though costtype/0 should get me the first element of the tuple | 15:39 |
| flox | SmokeyD: tal:content="python: costtype[0]" | 15:39 |
| flox | bec costtype/0 is understood as string '0', i guess | 15:39 |
| SmokeyD | ok, it's not possible through path expressions. | 15:39 |
| SmokeyD | yes it is | 15:40 |
| flox | benji, phliKON: here is my proposal (for the <browser:tool> thing) http://rafb.net/paste/results/A89Ckx73.html | 15:41 |
| philiKON | fine with me | 15:42 |
| benji | I'm not real keen on duplicating all deprecation info. | 15:42 |
| philiKON | why not. the interface will go away anyways | 15:42 |
| philiKON | it should really already have a BBB marker | 15:42 |
| philiKON | in a comment | 15:42 |
| philiKON | of course, docstrings are better for apidoc | 15:43 |
| benji | if that's a policy already, then there's no question... | 15:43 |
| benji | but it seems better to me to deprecate something in only one place (DRY and all that) | 15:43 |
| flox | benji: u're righ | 15:44 |
| philiKON | benji, but if "something" is like 3 different things? | 15:45 |
| flox | but i did not find common pattern between deprecation of <browser:tool> and <browser:layer> for example | 15:45 |
| philiKON | a) interface | 15:45 |
| philiKON | b) handler | 15:45 |
| philiKON | c) snippet in meta.zcml | 15:45 |
| philiKON | flox, different people did it | 15:45 |
| philiKON | i did browser:layer | 15:45 |
| flox | and without common pattern, not easy to automate BBB retrieving | 15:45 |
| philiKON | browser:layer should have BBB markers everywhere | 15:45 |
| philiKON | i should really have put it in the docstrings | 15:45 |
| philiKON | perhaps that should become a pattern | 15:45 |
| philiKON | they're better extractable then | 15:45 |
| flox | <browser:tool> is deprecated in the "metaconfigure.py" | 15:46 |
| flox | with a warnings.warn( | 15:46 |
| benji | my point is that the more work someone has to do to do something "right", the less likely it'll get done | 15:46 |
| philiKON | benji, good point | 15:46 |
| philiKON | benji, of course, if there was a written down guide | 15:46 |
| philiKON | flox, right. that's correct | 15:46 |
| benji | it may not be practacle to do what I'm suggesting, but it'd be nice to try | 15:46 |
| philiKON | flox, stuff needs to issue warnings. | 15:46 |
| philiKON | flox, otherwise it's not relaly deprecated | 15:47 |
| flox | yes, maybe we need to parse these warning messages within apidoc, to retrieve deprecation messages. | 15:47 |
| flox | but it does not look easy for me... | 15:48 |
| flox | and i am afraid some deprecation are done differently | 15:48 |
| benji | I don't know how apidoc works, so I can't speak to how easy/hard it'll be | 15:48 |
| flox | me too | 15:48 |
| flox | easiest thing to do today, is to change the docstring for every deprecated directive, i think | 15:49 |
| benji | I'd say that if it isn't deprecated using the built-in machinery, it's not deprecated | 15:49 |
| benji | flox, (if that's not a trivial change, i.e., just a few docstrings) I fear that would set people up to be bitten in the future. All future docstrings will have to contain that information, or it quickly becomes (worse than) useless. | 15:50 |
| benji | I'm going to look at apidoc real quick. | 15:51 |
| flox | benji: ur idea is to parse the 'warnings.warn' thing? | 15:52 |
| benji | something like that | 15:52 |
| flox | or 'warnings.warn_explicit' (depending on the module) | 15:52 |
| flox | i've listed 10 deprecated directives that are still present in zope 3.3 | 15:53 |
| flox | but maybe there's more | 15:54 |
| benji | you found 10 deprecated things that are still used in Z3? or 10 that exist? | 15:54 |
| flox | 10 that are available in /++apidoc++/ZCML/ | 15:55 |
| benji | ahh, ok | 15:55 |
| flox | and u have to read source code to understand they are deprecated | 15:55 |
| benji | or try to use them and get a warning (not nice, but not awful | 15:55 |
| flox | (i was confused a little at the beginning, when i started to learn Zope3) | 15:55 |
| baijum | hmm... user first learn something and use... then he see that it is deprecated :) | 16:06 |
| benji | not ideal | 16:06 |
| * flox is reading the zope.app.apidoc.zcmlmodule thing... | 16:12 | |
| benji | flox: I've been looking for a few minutes now, and it's not clear to me how it gathers up the information about ZCML | 16:14 |
| benji | it lookst like it all starts in zope/app/apidoc/codemodule/zcml.py, in the ZCMLFile class | 16:16 |
| flox | benji: main functions are within zope.app.apidoc.codemodule.zcml | 16:16 |
| flox | :-) | 16:16 |
| benji | :) | 16:17 |
| flox | and u find the PT and the view class in 'zcmlmodule' | 16:18 |
| flox | benji: i think the apidoc only parse the function and class definitions, and the docstrings | 16:22 |
| flox | i do not find anything about parsing function source code | 16:23 |
| baijum | flox: to get warning we have to make instance of the directive classes, so the better idea is to duplicate the warning message in docstring also? | 16:36 |
| flox | i think so... | 16:38 |
| flox | risk is that when you deprecate some directive, u forget to write it in the docstring | 16:38 |
| flox | but this is not big risk, this will not cause compilation to fail | 16:39 |
| flox | and we do not deprecate things every day | 16:39 |
| flox | baijum: i will change the docstring for the 10 directives that we've listed on ur page "What's new in Zope 3.3" | 16:40 |
| baijum | flox: I am really new here, so better first ask it in list or submit a collector issue, then commit changes. | 16:43 |
| flox | since it is only docstring changes, i don't think many developers care about this | 16:47 |
| *** peter_ has joined #zope3-dev | 16:47 | |
| flox | and that will give some help to new zope3 users | 16:48 |
| baijum | flox: surely | 16:52 |
| baijum | I like the idea used in bazaar, use docstrings with string formatting for warning messages: http://bazaar-vcs.org/bzr/bzr.dev/bzrlib/errors.py | 16:56 |
| benji | what do you see as the advantage, baijum? | 16:59 |
| flox | this is not clear how i can use it | 17:00 |
| *** baijum has quit IRC | 17:03 | |
| *** projekt01 has quit IRC | 17:37 | |
| flox | i do not find anything in source code that say <localUtility> is deprecated | 18:09 |
| flox | philiKON: i assume it is deprecated? | 18:10 |
| philiKON | we missed to oficially deprecate it | 18:12 |
| philiKON | so, it really doesn't do anything special | 18:12 |
| philiKON | not useful anymore | 18:12 |
| philiKON | but not officially deprecated | 18:12 |
| philiKON | just discouraged | 18:12 |
| philiKON | it's exactly the same as <class /> | 18:12 |
| flox | so, if i prepare a patch for 3.3 branch, for the docstrings, i should not claim it is deprecated | 18:13 |
| philiKON | i guess we could still deprecate it since we're in beta | 18:14 |
| philiKON | but yeah, at this point you shouldn't claim it's deprecated | 18:14 |
| flox | i should ask on the mailing list? | 18:14 |
| philiKON | just discouraged | 18:14 |
| flox | ok | 18:14 |
| *** oferw has joined #zope3-dev | 18:26 | |
| *** dobee has joined #zope3-dev | 18:37 | |
| *** oferw has quit IRC | 18:49 | |
| *** hazmat has joined #zope3-dev | 19:02 | |
| *** peter_ has quit IRC | 19:08 | |
| *** peter_ has joined #zope3-dev | 19:10 | |
| *** philiKON has quit IRC | 19:18 | |
| *** philiKON has joined #zope3-dev | 19:19 | |
| *** philiKON has quit IRC | 19:27 | |
| *** peter_ has quit IRC | 19:50 | |
| *** peter_ has joined #zope3-dev | 19:51 | |
| *** dobee_ has joined #zope3-dev | 20:17 | |
| *** dobee has quit IRC | 20:25 | |
| *** MiUlEr has joined #zope3-dev | 20:55 | |
| *** peter_ has quit IRC | 21:11 | |
| *** peter_ has joined #zope3-dev | 21:28 | |
| * MJ curses the lack of an etc namespace registry | 21:46 | |
| MJ | I'd love for that to exist.. | 21:46 |
| * MJ has a server-wide debugger service to control and ++etc++wingdebug would have been a great place to hang the controls.. | 21:47 | |
| MJ | I'll tie it in at ++etc++process instead.. | 21:48 |
| MJ | Not that easy either as it'll have to be a subobject of the app controller methinks. | 21:51 |
| flox | MJ: you have such a registry in zope/traversing/configure.zcml | 22:05 |
| flox | maybe u need to override the <view name="etc" ...> thing. | 22:05 |
| flox | and <adapter name="etc" ...>, too | 22:07 |
| MJ | flox: I know, I'll just register my own namespace handler | 22:12 |
| MJ | flox: but the etc namespace handler is hardcoded to only accept ++etc++process and ++etc++site. | 22:12 |
| MJ | The comments state that a registry would be handy, but may be a YAGNI | 22:13 |
| * MJ is going the ++my++own-namespace route | 22:13 | |
| flox | maybe u can subclass zope.traversing.namespace.etc factory | 22:13 |
| flox | and to extend the "traverse" method | 22:14 |
| MJ | Too much trouble | 22:14 |
| MJ | I'd have to add an -overrides.zcml just for that. | 22:15 |
| MJ | I could also just submit a proposal and extend the etc namespace handler to use a Interface type | 22:15 |
| MJ | But that is also too much trouble ;) | 22:16 |
| flox | i see what you mean | 22:16 |
| *** ChanServ sets mode: +o hazmat | 22:20 | |
| *** flox is now known as flox|away | 22:35 | |
| *** brupp has quit IRC | 23:11 | |
| *** flox__ has joined #zope3-dev | 23:40 | |
| *** flox__ is now known as flox | 23:41 | |
| *** flox|away has quit IRC | 23:41 | |
| *** reco has joined #zope3-dev | 23:41 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!