| *** ChrisW has left #zope3-dev | 00:13 | |
| *** projekt01 has joined #zope3-dev | 00:22 | |
| *** bskahan has quit IRC | 00:25 | |
| *** stub has joined #zope3-dev | 00:32 | |
| J1m | srichter, I dunno, want me to look at it? | 00:43 |
|---|---|---|
| srichter | J1m: I have communicated with Fred | 00:43 |
| srichter | and got it bit further | 00:43 |
| J1m | great | 00:44 |
| srichter | J1m: so now I know how to add top-level packages, and zope.app pacakges | 00:45 |
| srichter | now I have to figure out what to do with zope.* packages | 00:45 |
| srichter | J1m: looks pretty good; I am getting very few test failures now | 01:04 |
| *** mohsen has joined #zope3-dev | 01:04 | |
| J1m | cool | 01:15 |
| J1m | Thanks for doing this | 01:15 |
| J1m | See ya tomorrow | 01:15 |
| *** J1m has quit IRC | 01:15 | |
| *** yota has quit IRC | 01:16 | |
| *** BjornT has quit IRC | 01:36 | |
| *** BjornT has joined #zope3-dev | 01:36 | |
| *** srichter has quit IRC | 01:50 | |
| *** nisha_cgx has joined #zope3-dev | 02:04 | |
| *** projekt01 has left #zope3-dev | 02:05 | |
| *** ChrisW has joined #zope3-dev | 02:19 | |
| ChrisW | hi | 02:19 |
| ChrisW | what in zope.pagetemplate decides where macros are found? | 02:19 |
| ChrisW | ie: if I want macros to come from other file system files, what do I have to implement? | 02:19 |
| *** RaFromBRC is now known as RaFromBRC|afk | 02:33 | |
| *** efge has left #zope3-dev | 02:33 | |
| *** ChrisW has left #zope3-dev | 02:38 | |
| *** BjornT has quit IRC | 02:41 | |
| *** mohsen has quit IRC | 02:59 | |
| *** srichter has joined #zope3-dev | 03:03 | |
| *** ChanServ sets mode: +o srichter | 03:05 | |
| *** bradb has quit IRC | 03:10 | |
| *** nisha_cgx has quit IRC | 03:42 | |
| *** RaFromBRC|afk is now known as RaFromBRC | 04:07 | |
| *** BjornT has joined #zope3-dev | 04:20 | |
| *** RaFromBRC has quit IRC | 04:36 | |
| *** SteveA has joined #zope3-dev | 04:38 | |
| *** andrew_m has quit IRC | 04:49 | |
| *** andrew_m has joined #zope3-dev | 04:59 | |
| *** hazmat has quit IRC | 05:18 | |
| *** RaFromBRC has joined #zope3-dev | 05:20 | |
| *** Aiste has quit IRC | 05:41 | |
| *** th1a has quit IRC | 05:41 | |
| *** th1a has joined #zope3-dev | 05:42 | |
| *** Aiste has joined #zope3-dev | 05:42 | |
| *** d2m has quit IRC | 06:09 | |
| *** Aiste has quit IRC | 07:23 | |
| *** Aiste has joined #zope3-dev | 07:23 | |
| *** RaFromBRC has quit IRC | 07:30 | |
| *** RaFromBRC has joined #zope3-dev | 07:32 | |
| *** MacYET has joined #zope3-dev | 07:35 | |
| *** Aiste has quit IRC | 08:24 | |
| *** Aiste has joined #zope3-dev | 08:27 | |
| *** Aiste has quit IRC | 08:30 | |
| *** Aiste has joined #zope3-dev | 08:33 | |
| *** Aiste has quit IRC | 08:36 | |
| *** Aiste has joined #zope3-dev | 08:38 | |
| *** Aiste has quit IRC | 08:43 | |
| *** Aiste has joined #zope3-dev | 08:44 | |
| *** Aiste has quit IRC | 08:49 | |
| *** Aiste has joined #zope3-dev | 08:52 | |
| *** hazmat has joined #zope3-dev | 09:08 | |
| *** srichter has quit IRC | 09:09 | |
| *** srichter has joined #zope3-dev | 09:09 | |
| *** hazmat has quit IRC | 09:17 | |
| *** hazmat has joined #zope3-dev | 09:17 | |
| *** Aiste has quit IRC | 09:32 | |
| *** yota has joined #zope3-dev | 09:41 | |
| *** RaFromBRC has quit IRC | 10:05 | |
| *** lunatik has joined #zope3-dev | 10:16 | |
| *** lunatik has left #zope3-dev | 10:18 | |
| *** d2m has joined #zope3-dev | 10:38 | |
| *** tarek has joined #zope3-dev | 11:19 | |
| *** faassen has joined #zope3-dev | 11:55 | |
| *** ignas has joined #zope3-dev | 12:02 | |
| *** ignas has joined #zope3-dev | 12:03 | |
| *** hazmat has quit IRC | 12:04 | |
| *** mexiKON has joined #zope3-dev | 12:08 | |
| *** philiKON has quit IRC | 12:14 | |
| *** projekt01 has joined #zope3-dev | 12:32 | |
| *** SteveA has quit IRC | 12:33 | |
| *** stub has quit IRC | 12:34 | |
| *** alga has joined #zope3-dev | 12:41 | |
| *** Aiste has joined #zope3-dev | 12:54 | |
| *** mexiKON is now known as philiKON | 12:56 | |
| *** stub has joined #zope3-dev | 13:01 | |
| *** ChanServ sets mode: +o srichter | 13:08 | |
| * MacYET checks if philiKON implements IAnswersAllMyQuestions | 13:13 | |
| MacYET | upss..provides :) | 13:13 |
| philiKON | i provide it, but that doesn't mean i fulfill the contract :) | 13:13 |
| *** srichter has quit IRC | 13:13 | |
| MacYET | pahh :-) | 13:13 |
| MacYET | "old" objects (plone,cmf content-types) don't implement my TXNG interfaces to be indexed...can I adapt them using adapters? | 13:14 |
| *** srichter has joined #zope3-dev | 13:15 | |
| *** ChanServ sets mode: +o srichter | 13:15 | |
| philiKON | sure. that's usually what you want to do, provide an adapter from IThisIsMyStupidContentObject to IICanTellYouWhatDataYouNeedToIndex | 13:15 |
| philiKON | that way you only work with IICanTellYouWhatDataYouNeedToIndex on the index side | 13:16 |
| MacYET | and if these content-type have no __implement__ ? :) | 13:16 |
| philiKON | use <five:implements class="Products.CMFPlone...." interface="..." /> | 13:17 |
| philiKON | note that interface="..." needs to specify a *new style* interface (zope 3 interface) | 13:17 |
| MacYET | ah..ok | 13:17 |
| philiKON | however, Five has an interface converter built in | 13:17 |
| philiKON | <five:bridge /> | 13:17 |
| MacYET | thanks for the pointer | 13:17 |
| philiKON | np | 13:18 |
| * MacYET dances around | 13:19 | |
| srichter | hey guys | 13:19 |
| srichter | two questions: | 13:19 |
| srichter | 1. Do we want to distribute bforest? | 13:19 |
| srichter | 2. I think we need another ZCML condition verb, like "isInstalled <package>" or just "installed <package>" | 13:21 |
| srichter | any ideas? | 13:21 |
| philiKON | when does <package> qualify for the 'installed' verb to be true? | 13:21 |
| philiKON | when it's importable? | 13:21 |
| srichter | yes | 13:21 |
| philiKON | what's the verb we have now? | 13:22 |
| philiKON | right now, some package can "provide" a feature and another can require it, right? | 13:22 |
| srichter | have feature | 13:22 |
| philiKON | s/require/have/g then :) | 13:22 |
| srichter | yes, but the feature must be set through a ZCML directive | 13:22 |
| philiKON | mmh | 13:22 |
| philiKON | that's not enough? | 13:22 |
| srichter | what if the package does not have a configure.zcml | 13:23 |
| philiKON | can the feature be specified anywhere in the zcml tree? | 13:23 |
| srichter | for example, if zope.bforest is available I want to publish its documentation in the Book Module of the API doc | 13:23 |
| srichter | sure | 13:23 |
| srichter | of course, I could just create a zope.app.bforest package, but it seems overkill and a bad design decision | 13:24 |
| philiKON | yes | 13:24 |
| philiKON | i agree | 13:24 |
| philiKON | +1 then | 13:24 |
| *** __gotcha has joined #zope3-dev | 13:25 | |
| philiKON | (i just wanted to make sure we got the use case right :)) | 13:25 |
| srichter | ok, any better idea for the verb name? | 13:25 |
| philiKON | i was inclined to say +1 already | 13:25 |
| srichter | :-) | 13:25 |
| philiKON | 'package'? | 13:25 |
| srichter | I thought about this too, but it should be a verb | 13:25 |
| philiKON | mmh | 13:25 |
| srichter | I also thought about available | 13:26 |
| philiKON | have should really be have_feature | 13:26 |
| philiKON | so then we could say have_package | 13:26 |
| srichter | I can do that, but might cause name conflicts or unwanted side effects | 13:26 |
| philiKON | yeah, we dont wanna mess with it this shortly before a release | 13:27 |
| philiKON | available is too general | 13:27 |
| srichter | maybe have package:zope.bforest | 13:27 |
| philiKON | anything can be available | 13:27 |
| philiKON | ah... mmh | 13:27 |
| philiKON | i think i'd go for installed | 13:27 |
| philiKON | zcml:condition="installed zope.bforest" | 13:27 |
| srichter | I think we need this feature now though | 13:27 |
| srichter | ok | 13:27 |
| philiKON | i think that reads well | 13:27 |
| srichter | yes, I agree | 13:29 |
| *** mkerrin has joined #zope3-dev | 13:42 | |
| srichter | yipee the release is starting up! :-) | 14:05 |
| ignas | srichter, maybe you can tell me where should i look for the new request recording functionality mgedmin added to zope ? | 14:05 |
| *** alga has quit IRC | 14:09 | |
| srichter | zope.app.recorder | 14:09 |
| srichter | read the README.txt on how to get it going | 14:09 |
| srichter | (it's trivial) | 14:09 |
| ignas | thank you | 14:10 |
| *** bskahan has joined #zope3-dev | 14:11 | |
| ignas | srichter, i guess, unless you want to backport it to some older Zope revision ... | 14:14 |
| srichter | what? | 14:15 |
| ignas | well i got a pogram that is tied to zope3 revision that has no recording yet ... | 14:15 |
| ignas | did mgedmin do any changes to Zope3 to make the recorder work ? or he just added the new server ? | 14:15 |
| srichter | nope | 14:16 |
| srichter | the package is self-contained | 14:16 |
| srichter | and since no work was done on ZServer since, it should be easy to back-port | 14:16 |
| ignas | hope so ;) | 14:17 |
| philiKON | srichter, will the recorder be in x3.1? | 14:27 |
| ignas | the porting was easy, the only difference was zope.app.tests was renamed to zope.app.testing ... | 14:29 |
| philiKON | ignas, actually, zope.app.tests was split into testing and tests | 14:29 |
| philiKON | but yes | 14:29 |
| srichter | philiKON: see my mail to zope3-dev | 14:33 |
| srichter | bad thing is, a lot of ftests fail in the release :-( | 14:33 |
| philiKON | what? why? | 14:33 |
| philiKON | btw, the only one i can truly say yes on is zope.app.recorder | 14:34 |
| srichter | something about security problems :-( | 14:34 |
| srichter | I think if we fix the security issue, most if not all ftests will pass | 14:35 |
| philiKON | what security issue is that? | 14:35 |
| srichter | no clue | 14:35 |
| philiKON | do the ftests pass on a checkout? | 14:35 |
| srichter | of course | 14:35 |
| srichter | so someone has to dig into this | 14:36 |
| srichter | I have to write a paper today, so it won't be me | 14:36 |
| *** stub has quit IRC | 15:01 | |
| *** th1a has quit IRC | 15:10 | |
| *** srichter has quit IRC | 15:15 | |
| *** srichter has joined #zope3-dev | 15:15 | |
| *** ChanServ sets mode: +o srichter | 15:15 | |
| *** mp has joined #zope3-dev | 15:33 | |
| *** niemeyer has joined #zope3-dev | 15:46 | |
| *** projekt01 has left #zope3-dev | 16:02 | |
| *** alga has joined #zope3-dev | 16:15 | |
| *** J1m has joined #zope3-dev | 16:17 | |
| srichter | J1m: I got a release running | 16:49 |
| srichter | J1m: however, many functional tests in the released package fail because of some security problem. | 16:50 |
| srichter | J1m: unfortunately, I have to write a Zope 3 paper for a conference today, so I will not have time to investigate further | 16:50 |
| srichter | to all, here is the script I use to test the release: | 16:52 |
| srichter | echo "Building Zope X3 Release ..." | 16:52 |
| srichter | Python zpkgtools/bin/zpkg -ca ZopeX3 | 16:52 |
| srichter | echo "Removing old Release Directory ..." | 16:52 |
| srichter | rm -rf ZopeX3-0.0.0 | 16:52 |
| srichter | echo "Unpacking new Release ..." | 16:52 |
| srichter | tar xvzf ZopeX3-0.0.0.tgz | 16:52 |
| srichter | echo "Entering Release Directory ..." | 16:52 |
| srichter | cd ZopeX3-0.0.0 | 16:52 |
| srichter | echo "Configuring Release ..." | 16:52 |
| srichter | ./configure --prefix ./Z3 --with-python /opt/python2.4/bin/python | 16:52 |
| srichter | echo "Building Release ..." | 16:52 |
| srichter | make | 16:52 |
| srichter | echo "Installing Release ..." | 16:52 |
| srichter | make install && cd Z3 | 16:52 |
| srichter | #echo "Running Tests ..." | 16:52 |
| srichter | #./bin/zopetest -vpu1 | 16:52 |
| srichter | echo "Making an Instance ..." | 16:52 |
| srichter | ./bin/mkzopeinstance -d ZI -u foo:bar && cd ZI | 16:52 |
| srichter | echo "Starting Zope 3 ..." | 16:53 |
| srichter | ./bin/runzope | 16:53 |
| srichter | it is not advanced and specific to my machine, but it demonstrates the necessary steps | 16:53 |
| *** Damascene has quit IRC | 16:56 | |
| *** regebro has quit IRC | 17:09 | |
| *** th1a has joined #zope3-dev | 17:15 | |
| *** th1a has quit IRC | 17:26 | |
| *** __gotcha has quit IRC | 17:34 | |
| *** th1a has joined #zope3-dev | 17:40 | |
| *** th1a has quit IRC | 17:41 | |
| * MacYET praises z3 | 17:51 | |
| srichter | yipee! | 17:52 |
| *** BjornT has quit IRC | 17:57 | |
| *** th1a has joined #zope3-dev | 18:02 | |
| srichter | Theuni: zagy: congrats on finishing the security eval document! | 18:10 |
| srichter | Looks insane to me. :-) | 18:11 |
| J1m | srichter, what is bforest? | 18:14 |
| srichter | J1m: something someone from Zope Corp checked in, I think | 18:15 |
| srichter | let me see whom we wanna blame | 18:15 |
| srichter | BTree-based dicts, IIRC | 18:16 |
| J1m | oh yeah | 18:16 |
| J1m | Gary | 18:16 |
| srichter | ok | 18:16 |
| philiKON | Theuni, what do you want us to do with comments on the document? check them in? | 18:18 |
| J1m | We're using it in our projects. | 18:18 |
| J1m | It doesn't really matter to us whether it's in 3.1, so I sugest leaving it out. | 18:18 |
| MacYET | btreebased dicts? what#s the difference to OOBtrees? | 18:24 |
| J1m | No, more like multimappings | 18:25 |
| MacYET | k | 18:27 |
| *** Damascene has joined #zope3-dev | 18:27 | |
| Theuni | philiKON, srichter: Don't do anything yet. We have to arrange the tables still. If you have comments, please post the to zope3-dev. It needs some thought to make changes to that document to keep it consistent. I think Jim will look at it in depth as he already knows the procedure and the things we talked about endlessly. But you're of course invited to share your thoughts as well. :) | 18:29 |
| Theuni | of course it is insane, btw. ;) | 18:29 |
| J1m | Theuni, I have a proposal for you to consider. | 18:29 |
| J1m | Four our Zope 3 project, we've implemented a much simpler security policy that we'd be happy to open source if it would help the certification. | 18:30 |
| J1m | Interested? | 18:30 |
| Theuni | i think so. only if we don't have to step back too far. i really want to proceed (without rushing of course) finally. | 18:31 |
| Theuni | anyway, i'm interested in looking at it. | 18:31 |
| Theuni | gotta move now, to keep my girl happy. have a nice weekend, all of you. | 18:32 |
| J1m | I don't think we want to go through the bother of open sourcing it unless it helps the certification process. | 18:32 |
| Theuni | that's ok. can you mail me some description or something? | 18:33 |
| J1m | Theuni, please let me know how you'd like to look at it. | 18:33 |
| J1m | sure | 18:33 |
| srichter | J1m: ok | 18:33 |
| Theuni | great. i'll be back on monday | 18:33 |
| J1m | k | 18:33 |
| J1m | srichter, ok what? | 18:33 |
| Theuni | *woosh | 18:33 |
| *** Theuni has quit IRC | 18:33 | |
| srichter | J1m: leaving out bforest | 18:33 |
| J1m | oh | 18:33 |
| J1m | k | 18:33 |
| J1m | :) | 18:33 |
| J1m | srichter, less is more :) | 18:34 |
| srichter | yes | 18:35 |
| srichter | J1m: could you have a look at the failing ftests in the release? | 18:35 |
| srichter | this is the last outstanding issue | 18:35 |
| srichter | there is also one unit test failing in zdaemon | 18:35 |
| J1m | ok, in a bit | 18:36 |
| srichter | ok, back to writing my paper, sigh | 18:37 |
| J1m | :) | 18:41 |
| srichter | it is for a fairly prestigous conference | 18:42 |
| J1m | Great | 18:42 |
| srichter | it would be good for Zope 3 to have a talk there | 18:42 |
| *** MiUlEr has quit IRC | 18:45 | |
| MacYET | can implements() handle z3 and z2 interfaces? /me hides | 18:47 |
| J1m | no, just z3 interfaces | 18:48 |
| J1m | No need to hide | 18:48 |
| MacYET | just wonder how marry both with five | 18:48 |
| J1m | You don't | 18:49 |
| J1m | Over time, we should convert existing interfaces and deprecate the old interfaces. | 18:50 |
| J1m | If someone had time, it would be nice to do this for 2.8, but I guess we won't. | 18:50 |
| MacYET | for my index i need __implements__ make the index available to zope 2 and on the other hands five since to require implements() to register additional browser:pages | 18:50 |
| J1m | You can use both | 18:50 |
| srichter | MacYET: yeah, Zope 2 can handle Zope 3's interfaces as far as I know, right? | 18:51 |
| MacYET | srichter: not really | 18:52 |
| srichter | :-( | 18:53 |
| J1m | MacYET, z3 and z2 interfaces can coexist | 18:53 |
| J1m | They don't interfere with one another | 18:53 |
| MacYET | __implements__=(IZ2, IZ3) won't work with five | 18:53 |
| J1m | No | 18:53 |
| J1m | But | 18:54 |
| J1m | __implements__ = IZ2 | 18:54 |
| MacYET | ah | 18:54 |
| J1m | implements(IZ3) | 18:54 |
| J1m | will work | 18:54 |
| MacYET | this works, tnx | 18:54 |
| *** MiUlEr has joined #zope3-dev | 19:10 | |
| *** hazmat has joined #zope3-dev | 19:11 | |
| *** philiKON has quit IRC | 19:17 | |
| *** philiKON has joined #zope3-dev | 19:17 | |
| faassen | MacYET: there's a bridge. | 19:17 |
| faassen | MacYET: so turn a z2 interface into a z3 interface, if you need it. | 19:17 |
| MacYET | just fighting to get a browser:page configured | 19:20 |
| faassen | MacYET: the docs aren't helping? | 19:20 |
| MacYET | they should...got my page configure, zope 2 starts up but why try to call the page on an object: can not locate objects.. | 19:21 |
| faassen | MacYET: hm. | 19:23 |
| MacYET | paste.plone.org/1572 | 19:23 |
| faassen | you shouldn't need the five:implements | 19:29 |
| faassen | as you're alread doing it on the class. | 19:29 |
| MacYET | right | 19:30 |
| faassen | five:implements is only useful if you are messing about with classes you don't control, like Five does with the basic Zope 2 objects. | 19:30 |
| MacYET | this way from my last try | 19:30 |
| faassen | just reporting the first that struck me. | 19:30 |
| faassen | you need to make your object five:traversable | 19:31 |
| MacYET | btw. the manual.htmlfile on codespeak has an error...it used <five:implements.... with implements instead of interface | 19:31 |
| faassen | MacYET: oh, okay, thanks..I need to go through the docs and clean them up.. | 19:31 |
| faassen | MacYET: anyway, making it a five:traversable should help. | 19:31 |
| MacYET | anway using old-style view=PageTemplateFIle() for now :) | 19:32 |
| MacYET | aha | 19:32 |
| faassen | MacYET: that's to tweak in a traversal hook. | 19:32 |
| faassen | MacYET: basically Five takes the approach that the Zope 3 ZCML should work as much a they do in Zope 3, but we add some extra five things to bully Zope 2 into behaving right. :) | 19:32 |
| faassen | we don't want to bully all Zope 2 objects into this new traversal behavior, so that's why the special structured monkey patch five:traversable | 19:33 |
| MacYET | ahhhhhh...this works | 19:33 |
| MacYET | GREAT | 19:33 |
| * faassen grins. | 19:33 | |
| MacYET | you saved my day | 19:33 |
| faassen | you're welcome. :) | 19:34 |
| MacYET | can i configure the manage_addXXXForm through zcml? likely, no | 19:35 |
| faassen | actually.. | 19:36 |
| faassen | there is some code that is rather new and raw, so you may not want to use it now. | 19:36 |
| faassen | to implement Zope 3 adding forms in Zope 3. we're using it. | 19:36 |
| faassen | for a project here. | 19:36 |
| faassen | so basically you can do obj/+/myaddform.html | 19:36 |
| MacYET | ok, nothing important | 19:36 |
| faassen | MacYET: if you want to play with that and improve it, we'd be happy. it's actually quite neat, though also hairy. :) | 19:37 |
| MacYET | currently sticking with the version in z2.8? | 19:37 |
| faassen | but basically that doesn't mean things would show up in the z2 add list. | 19:37 |
| MacYET | there are still enough walls to drive against :) | 19:37 |
| faassen | MacYET: it's not *that* new and hairy, it's actually a month or two old, it's just somewhat limited. | 19:37 |
| faassen | MacYET: and Lennart found a security issue with it on wednesday, which Sidnei will look into hopefully. | 19:38 |
| faassen | MacYET: by the way, we're planning a further synchup with Zope 2.8 next week, with some bugfixes and a few tweaks. | 19:38 |
| faassen | MacYET: after we release Five 1.0, which we'll do next week. | 19:38 |
| MacYET | i read that already | 19:39 |
| faassen | MacYET: ah, okay, good. :) | 19:39 |
| faassen | MacYET: just making sure. | 19:39 |
| MacYET | putting five into 2.8 was a good choice | 19:42 |
| faassen | MacYET: glad to hear that from you! | 19:42 |
| MacYET | hehe | 19:42 |
| faassen | MacYET: it was interesting how fast there was consensus about it at the sprint. I brought it up as an "out there" proposal and then everybody started nodding, which took me aback a bit. :) | 19:43 |
| MacYET | it's sometimes hard to convince me | 19:43 |
| faassen | but lots of people are itching to start using this in their codebases, and bundling it (especially the zope 3 library bits) makes that a lot easier. | 19:43 |
| faassen | MacYET: same here with me. :) | 19:43 |
| MacYET | right, and i can see that we could use it as well | 19:44 |
| andrew_m | has anyone ever used page templates (.pt) to generate XML that is rendered into XHTML with XSLT on client side? | 19:48 |
| andrew_m | content and xml extension work fine but the mime-type is still html which confuses the browser | 19:49 |
| *** nisha_cgx has joined #zope3-dev | 19:52 | |
| *** hazmat has quit IRC | 19:58 | |
| philiKON | andrew_m, put a <?xml version="1.0" ?> on top of your zpt | 20:00 |
| andrew_m | philiKON: i have that.. everything the browser gets is ok, except the mime-type | 20:00 |
| *** ignas has quit IRC | 20:07 | |
| andrew_m | philiKON: hmm, i need to investigate that further to find out what the difference is between an XML file comming from zope and one loaded from the harddisk. only the latter are transformed by firefox somehow | 20:12 |
| philiKON | it's definitely the mime header | 20:14 |
| philiKON | you could set it manually | 20:14 |
| philiKON | but i'm sure there's a way to do that from zpt | 20:14 |
| andrew_m | oh, that would be cool of course | 20:14 |
| philiKON | without doing tal:define="foo python:request.response.setHeader('mime-type', 'text/xml') | 20:14 |
| *** nisha_cgx has quit IRC | 20:19 | |
| *** faassen has quit IRC | 20:23 | |
| *** hazmat has joined #zope3-dev | 20:23 | |
| MacYET | is there a way to figure out why a registered browser view is not available from the 'view' namespace? | 20:26 |
| philiKON | don't use the 'view' namespace | 20:27 |
| philiKON | no idea where you got it from | 20:27 |
| philiKON | but it's deprecated | 20:27 |
| philiKON | use context/@@view_name instead | 20:27 |
| MacYET | from your book? | 20:27 |
| MacYET | or sr'sbook | 20:28 |
| J1m | philiKON, that is shorthand for context/++view++view_name | 20:28 |
| MacYET | don't know :) | 20:28 |
| J1m | The long form isn't deprecated | 20:28 |
| J1m | You are thinking of views, which si deprecated | 20:28 |
| philiKON | context/@@view_name == context/++view++view_name | 20:28 |
| MacYET | tal:content="view/myview" | 20:28 |
| philiKON | ah, view | 20:28 |
| philiKON | 'view' is your view object | 20:28 |
| philiKON | i thought you meant 'views' | 20:28 |
| MacYET | ok,ok | 20:29 |
| philiKON | as in views/standard_macros (which should be context/@@standard_macros) | 20:29 |
| *** bskahan has quit IRC | 20:31 | |
| andrew_m | philiKON: thanks for the hint. that sets the mime-type fine, but still no rendering when it comes from zope. i'll keep you posted.. | 20:32 |
| MacYET | can i pass arguments to a method of the view object? | 20:33 |
| * MacYET is confused | 20:34 | |
| MacYET | a registered browser view should be available as view/view_name? | 20:34 |
| philiKON | no | 20:43 |
| philiKON | view lookup in zpt is through context/@@view_name | 20:43 |
| philiKON | or some_obj/@@view_name | 20:43 |
| philiKON | like, some_obj/@@absolute_url | 20:43 |
| MacYET | and how can i pass args to a view? | 20:44 |
| philiKON | this looks up the view and per zpt automatition calls it | 20:44 |
| philiKON | tal:define="myview some_obj/@@some_view" tal:content="python:myview(foo)" | 20:44 |
| MacYET | tnx, works | 20:46 |
| andrew_m | philiKON: renders fine now - the XSLT file also had to come from zope somehow (same server, same port). didn't know that | 20:50 |
| andrew_m | kinda weird.. | 20:52 |
| MacYET | philiKON: some_obj/@@some_view calls the view instead of getting a reference | 20:53 |
| philiKON | nocall: | 20:54 |
| philiKON | or python:path('some_obj/@@some_view') | 20:55 |
| philiKON | sorry | 20:55 |
| philiKON | wasn't thinking | 20:55 |
| * MacYET grumbles *nocall:* :) | 20:55 | |
| philiKON | though, i'm not sure if path('...') would imply the obj is called as well | 20:55 |
| J1m | It would be nice to change define so that nocall was the default. | 20:56 |
| philiKON | yeah | 20:57 |
| philiKON | though that would be a major break of compatability | 20:57 |
| J1m | Might be worth adding a new tal: attribute. | 20:57 |
| J1m | tal:set | 20:57 |
| J1m | or whatever | 20:58 |
| philiKON | with what purpose? | 20:58 |
| J1m | tal:set would be like define but without an implicit call. | 20:58 |
| philiKON | well, ok | 20:58 |
| philiKON | but it's really a TALES thing | 20:58 |
| philiKON | not a TAL | 20:58 |
| philiKON | implicit calling | 20:58 |
| J1m | We would then document set as the prefered thing to use. | 20:58 |
| philiKON | tal:content and tal:replace behave like that too | 20:58 |
| J1m | It's far less inappropriate in those other contexts. | 20:59 |
| philiKON | not sure | 20:59 |
| J1m | I don't think it's a TALES thing, but I'd have to check. | 20:59 |
| philiKON | i think it is | 20:59 |
| philiKON | tal:attributes="href context/@@absolute_url" | 20:59 |
| * MacYET defeated browser views | 20:59 | |
| J1m | Right, it's useful there | 21:00 |
| philiKON | MacYET: 1 browser views: 1e24 | 21:00 |
| philiKON | J1m, i don't think we want to dictate tales behaviour judging by the tal directive you use it in | 21:00 |
| J1m | I don't think it's tales behavior. | 21:01 |
| philiKON | it may not be | 21:01 |
| philiKON | i could think of another way | 21:01 |
| J1m | I'm not sure though | 21:01 |
| philiKON | introduce a new TAL namespace | 21:01 |
| J1m | nah | 21:01 |
| philiKON | xml.zope.org/namespaces/tal2 | 21:01 |
| philiKON | that way you deliberately have to switch yoru templates to the new system | 21:02 |
| J1m | true | 21:02 |
| philiKON | and you don't have to remember any new directives | 21:02 |
| philiKON | s/directives/tal commands/ | 21:02 |
| J1m | yes | 21:02 |
| J1m | OTOH, it could be prett confusing for someone reading template source, | 21:03 |
| J1m | OTOH, it could be pretty confusing for someone reading template source, | 21:03 |
| philiKON | yes, that's the only disadvantage i can think of | 21:04 |
| philiKON | woa... reading TAL sources is like pulling your finger nails out | 21:07 |
| *** RaFromBRC has joined #zope3-dev | 21:10 | |
| philiKON | J1m, it's a TALES thing, i just checked the code. It's pretty obvious anyway, since it's specific to Path expressions and doesn't occurr with python expressions or so | 21:10 |
| J1m | hm | 21:11 |
| *** Aiste has quit IRC | 21:13 | |
| *** alga has quit IRC | 21:31 | |
| *** hazmat has quit IRC | 21:33 | |
| *** hazmat has joined #zope3-dev | 21:35 | |
| *** MacYET has left #zope3-dev | 21:39 | |
| *** mkerrin has quit IRC | 21:40 | |
| *** ignas has joined #zope3-dev | 21:45 | |
| *** `anthony has joined #zope3-dev | 21:50 | |
| *** ignas has quit IRC | 21:51 | |
| *** MiUlEr has quit IRC | 22:02 | |
| *** RaFromBRC is now known as RaFromBRC|food | 22:07 | |
| J1m | I have no frigging idea what testRetryNotAllowed is supposed to be testing. | 22:11 |
| *** hazmat has quit IRC | 22:13 | |
| *** hazmat has joined #zope3-dev | 22:28 | |
| srichter | J1m: he he | 22:41 |
| J1m | non-doctest tests are a recipe for pain | 22:47 |
| srichter | :-) | 22:48 |
| srichter | yes, they are | 22:48 |
| srichter | I am trying to evangelize the twisted folks to use doc tests | 22:48 |
| srichter | but their testing framework is a mess | 22:48 |
| srichter | so it is not as easy to integrate as in Zope. | 22:49 |
| *** palmTreex has joined #zope3-dev | 22:57 | |
| *** palmTreex has quit IRC | 23:06 | |
| *** RaFromBRC|food is now known as RaFromBRC | 23:09 | |
| *** hazmat has quit IRC | 23:12 | |
| *** palmTreex has joined #zope3-dev | 23:25 | |
| *** gintas has joined #zope3-dev | 23:40 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!