*** batlogg has quit IRC | 00:04 | |
*** mexiGOOOL is now known as philiGOOOL | 00:46 | |
*** jinty has joined #zope3-dev | 01:38 | |
*** jinty has quit IRC | 02:29 | |
*** oferw has joined #zope3-dev | 02:47 | |
*** oferw has quit IRC | 02:53 | |
*** oferw_ has joined #zope3-dev | 02:53 | |
*** oferw_ is now known as oferw | 02:53 | |
*** flox has quit IRC | 03:14 | |
*** yota has quit IRC | 03:49 | |
*** philiGOOOL has quit IRC | 04:02 | |
*** oferw has quit IRC | 04:29 | |
*** hazmat has quit IRC | 05:21 | |
*** lordMiUlEr has quit IRC | 05:48 | |
*** tarek has quit IRC | 06:43 | |
*** Aiste has quit IRC | 06:44 | |
*** Aiste has joined #zope3-dev | 06:46 | |
*** jbb has quit IRC | 06:47 | |
*** SteveA has quit IRC | 06:47 | |
*** tav has quit IRC | 06:47 | |
*** dunny has quit IRC | 06:48 | |
*** d2m has quit IRC | 06:48 | |
*** genconc has quit IRC | 06:48 | |
*** vinsci has quit IRC | 06:48 | |
*** zagy_ has quit IRC | 06:52 | |
*** TrevorP has quit IRC | 06:52 | |
*** clasux has quit IRC | 06:52 | |
*** benji has quit IRC | 06:52 | |
*** nouri has quit IRC | 06:52 | |
*** dokai has quit IRC | 06:52 | |
*** Aiste has quit IRC | 06:52 | |
*** rocky has quit IRC | 06:52 | |
*** srichter has quit IRC | 06:52 | |
*** tonico has quit IRC | 06:52 | |
*** povbot has joined #zope3-dev | 07:12 | |
*** zelazny.freenode.net sets mode: +ns | 07:12 | |
-zelazny.freenode.net- *** Notice -- TS for #zope3-dev changed from 1151208756 to 1151208719 | 07:19 | |
*** irc.freenode.net sets mode: -s | 07:19 | |
*** tonico has joined #zope3-dev | 07:19 | |
*** clasux has joined #zope3-dev | 07:19 | |
*** dunny has joined #zope3-dev | 07:19 | |
*** zagy has joined #zope3-dev | 07:19 | |
*** Aiste has joined #zope3-dev | 07:19 | |
*** nouri has joined #zope3-dev | 07:19 | |
*** TrevorP has joined #zope3-dev | 07:20 | |
*** tav has joined #zope3-dev | 07:30 | |
*** jbb has joined #zope3-dev | 07:31 | |
*** srichter has joined #zope3-dev | 08:01 | |
*** ChanServ sets mode: +o srichter | 08:03 | |
-zelazny.freenode.net- *** Notice -- TS for #zope3-dev changed from 1151208719 to 1076821724 | 08:03 | |
*** irc.freenode.net sets mode: -o srichter | 08:03 | |
*** jukart has joined #zope3-dev | 08:03 | |
*** vinsci has joined #zope3-dev | 08:03 | |
*** d2m has joined #zope3-dev | 08:03 | |
*** SteveA has joined #zope3-dev | 08:03 | |
*** genconc has joined #zope3-dev | 08:03 | |
*** dokai has joined #zope3-dev | 08:03 | |
*** irc.freenode.net sets mode: +b *!*Albesure*@*.comcast.net | 08:03 | |
*** irc.freenode.net changes topic to "logs available at http://zope3.pov.lt/irclogs/ || paste code examples into http://zope3.pastebin.com/" | 08:03 | |
*** ChanServ sets mode: +o tav | 08:06 | |
*** genconc has quit IRC | 08:47 | |
*** jukart has quit IRC | 08:47 | |
*** dokai has quit IRC | 08:47 | |
*** vinsci has quit IRC | 08:47 | |
*** SteveA has quit IRC | 08:47 | |
*** d2m has quit IRC | 08:47 | |
*** genconc has joined #zope3-dev | 08:47 | |
*** dokai has joined #zope3-dev | 08:47 | |
*** vinsci has joined #zope3-dev | 08:47 | |
*** SteveA has joined #zope3-dev | 08:48 | |
*** d2m has joined #zope3-dev | 08:48 | |
*** jukart has joined #zope3-dev | 08:48 | |
*** batlogg has joined #zope3-dev | 09:39 | |
*** baijum has joined #zope3-dev | 09:40 | |
*** RaFromBRC has joined #zope3-dev | 09:51 | |
*** RaFromBRC has quit IRC | 09:52 | |
*** oferw has joined #zope3-dev | 11:24 | |
*** flox has joined #zope3-dev | 11:29 | |
*** oferw has quit IRC | 11:30 | |
*** philiGOOOL has joined #zope3-dev | 11:37 | |
*** batlogg has quit IRC | 11:49 | |
*** batlogg has joined #zope3-dev | 11:54 | |
*** baijum has left #zope3-dev | 12:19 | |
*** batlogg has quit IRC | 12:38 | |
*** batlogg has joined #zope3-dev | 12:43 | |
*** yota has joined #zope3-dev | 13:25 | |
*** dunny has quit IRC | 13:32 | |
d2m | anyone knows when zope.browsertestrecorder was removed from trunk ? svn up left me with an empty folder and a configfile in etc/package-includes | 13:48 |
---|---|---|
philiGOOOL | d2m, i removed it yesterday | 13:55 |
philiGOOOL | the checkin message says you should remove some stuff | 13:55 |
flox | about skinning... what is the best practice on Zope3.3+ ? | 13:57 |
d2m | philiGOOOL: ahh ;) thanks | 13:57 |
flox | is it better to use layers (the same as 'Rotterdam' skin with 'rotterdam' layer) | 13:58 |
philiGOOOL | flox, ppl like using viewlets | 13:58 |
flox | when u declare a <browser:page> or a <browser:ressource>, you put attribute layer=zope.app.rotterdam.Rotterdam (the IBrowserSkinType) | 14:00 |
d2m | another question: i managed to run zope from wsgiref (simple_server), only oddity is, that "devmode on" starts unittests (maybe a sideffect of appsetup.config()) , "devmode off" works fine though | 14:00 |
philiGOOOL | flox, yup | 14:00 |
philiGOOOL | flox, or any other interface extendin gIBrowserRequest | 14:00 |
philiGOOOL | flox, a layer doesn't have to be an IBRowserSkinType | 14:01 |
philiGOOOL | d2m, weird | 14:01 |
flox | philiGOOOL: u mean it is better to use a class declaration like it is for the Rotterdam skin | 14:02 |
flox | philiGOOOL: class Rotterdam(rotterdam, IDefaultBrowserLayer): | 14:02 |
philiGOOOL | class declaration? | 14:02 |
philiGOOOL | there's no class created there | 14:02 |
philiGOOOL | don't let the 'class' statement fool you | 14:02 |
philiGOOOL | those are interfaces | 14:02 |
philiGOOOL | and i don't understand you rquestion :) | 14:03 |
flox | philiGOOOL: factly, i saw examples where the pages and ressources are registered on a "IBrowserSkinType" directly | 14:05 |
philiGOOOL | sure, you can do that | 14:05 |
flox | philiGOOOL: but when i see the Rotterdam skin, i see that the pages and ressources are registered on the layer 'class rotterdam(IBrowserRequest):' | 14:05 |
philiGOOOL | yup | 14:06 |
philiGOOOL | it doesn't matter | 14:06 |
philiGOOOL | you decide what you want to do | 14:06 |
philiGOOOL | if things are registered for rotterdam and Rotterdam extends rotterdam, things are also available for Rotterdam | 14:06 |
flox | i understand that both examples work the same... | 14:07 |
flox | i was wondering if one of this implementation was deprecated... or in the way to be deprecated | 14:08 |
flox | i prefer the way implemented in "Rotterdam" skin... since all specific things are registered on an extra layer | 14:09 |
philiGOOOL | no, the point is to give you flexibility | 14:10 |
philiGOOOL | if you feel that you need the flexibility of having things on an extra layer, you can do so | 14:10 |
philiGOOOL | if you dont' need that flexibility (and i would say that in most cases you don't), you can register things directly for the skin interface now | 14:10 |
philiGOOOL | in fact, the way i look at it: | 14:10 |
philiGOOOL | everything extending IBrowserRequest is a layer | 14:11 |
philiGOOOL | you combine layers the way you want the overall layout to work | 14:11 |
philiGOOOL | then you select whichever layer is the one you want to "see", you turn it into a skin | 14:11 |
philiGOOOL | in fact, you just register it with an additional interface | 14:11 |
flox | this is the 'class Rotterdam(rotterdam, IDefaultBrowserLayer):' line | 14:12 |
philiGOOOL | no | 14:12 |
flox | :-( | 14:12 |
philiGOOOL | this just combines the layers | 14:12 |
philiGOOOL | to another layer | 14:12 |
philiGOOOL | rotterdam = layer | 14:12 |
philiGOOOL | Rotterdam = layer that combines rotterdam and IDefaultBrowserLayer | 14:12 |
philiGOOOL | Rotterdam is made a skin in ZCML | 14:12 |
flox | through the <intterface> directive | 14:13 |
flox | ok | 14:13 |
philiGOOOL | <interface interface='...Rotterdam' type='...IBrowserSkinType' name='Rotterdam' /> | 14:13 |
philiGOOOL | right | 14:13 |
flox | ok, i hv the point | 14:14 |
flox | is there an easy way to have a custom login page? or an example? | 14:15 |
flox | okok, i've found it on chapter 19... | 14:15 |
philiGOOOL | chapter 19 is outdated, though | 14:15 |
philiGOOOL | look at zope.app.authentication | 14:16 |
philiGOOOL | you want your own credentials plugin | 14:16 |
flox | philiGOOOL: i look for something similar to the 'Plone' login page | 14:16 |
philiGOOOL | flox, tried the cookie auth plugin for PAU? | 14:17 |
flox | philiGOOOL: not yet... | 14:17 |
philiGOOOL | try it :) | 14:17 |
flox | philiGOOOL: i'll do, after reading source code | 14:18 |
philiGOOOL | i'd try it first :) | 14:19 |
flox | philiGOOOL: i would like to hv different 'skins' for Anonymous access and Authenticated access... | 14:20 |
flox | philiGOOOL: is it easy to set up? | 14:21 |
philiGOOOL | probably best done in the credentials plugin | 14:21 |
philiGOOOL | it's not very ahrd to do | 14:22 |
*** volvox has joined #zope3-dev | 14:26 | |
*** stub has joined #zope3-dev | 14:34 | |
flox | directive <browser:resourceDirectory> still exists? | 14:39 |
philiGOOOL | sure | 14:42 |
flox | ok, thks | 14:42 |
*** flox is now known as flox|away | 14:43 | |
*** rocky has joined #zope3-dev | 14:44 | |
*** volvox has quit IRC | 14:50 | |
*** mexiKON has joined #zope3-dev | 14:54 | |
*** mexiKON is now known as philiKON | 14:54 | |
*** volvox has joined #zope3-dev | 15:10 | |
*** philiGOOOL has quit IRC | 15:10 | |
*** flox|away is now known as flox | 15:15 | |
*** J1m has joined #zope3-dev | 15:38 | |
*** jukart has left #zope3-dev | 16:10 | |
*** batlogg has quit IRC | 16:34 | |
*** hannosch has joined #zope3-dev | 16:47 | |
*** volvox has quit IRC | 17:10 | |
SteveA | thanks srichter or philiKON :-) | 17:12 |
philiKON | SteveA, you're welcome :) | 17:12 |
*** philiKON has left #zope3-dev | 17:13 | |
*** philiKON has joined #zope3-dev | 17:13 | |
*** volvox has joined #zope3-dev | 17:14 | |
*** jinty has joined #zope3-dev | 17:28 | |
flox | for the <browser:resource> directive | 17:37 |
flox | all resources are relative to current directory, by default.. | 17:37 |
flox | or to current object | 17:37 |
flox | how i can change the directive so that the resource are lookup at the same place for every object? | 17:38 |
flox | ex: if i visit http://127.0.0.1/dossier1/texte.html, the icon is requested with URL http://127.0.0.1/dossier1/@@/icon.png | 17:40 |
flox | then when i visit http://127.0.0.1/dossier2/autretexte.html, the icon is requested with URL http://127.0.0.1/dossier2/@@/icon.png | 17:40 |
flox | i want to do that to improve caching. | 17:42 |
flox | after other tests, i see i a m wrong | 17:46 |
*** stub has quit IRC | 17:47 | |
philiKON | flox, resources are looked up at the nearest site | 17:47 |
flox | factly, it is weird... | 17:47 |
flox | philiKON: yes, i just figured out this thing | 17:47 |
flox | philiKON: except the 'pl.gif' and 'mi.gif' that are looked up at the root of the instance | 17:48 |
philiKON | gotta, go, sorry | 17:50 |
*** epx has joined #zope3-dev | 17:50 | |
flox | at first i was lost, bec i set up 2 sites, and i did not understand the logic. factly, i htink the behaviour is ok. | 17:51 |
flox | s/htink/think/ | 17:51 |
flox | to implement a skin selector, how i can build the list of available skins? | 18:02 |
*** flox is now known as flox|away | 18:09 | |
*** hannosch has quit IRC | 18:10 | |
*** oferw has joined #zope3-dev | 18:18 | |
*** oferw has quit IRC | 18:59 | |
*** alecm has joined #zope3-dev | 19:16 | |
*** chen has joined #zope3-dev | 19:57 | |
chen | how about ajax in zope3.3? | 19:58 |
*** zagy_ has joined #zope3-dev | 20:07 | |
philiKON | chen, what about it? | 20:07 |
chen | is there any ajax capability builtin zope3.3? | 20:09 |
chen | hi , philikon, | 20:09 |
chen | or some official ajax package support zope3.3,please tell me ,thanks | 20:11 |
*** benji has joined #zope3-dev | 20:13 | |
philiKON | chen, no, no official ajax package | 20:13 |
chen | ok, thanks | 20:15 |
*** chen has quit IRC | 20:15 | |
*** romanofski has joined #zope3-dev | 20:15 | |
*** chenqiong has joined #zope3-dev | 20:16 | |
*** zagy has quit IRC | 20:19 | |
*** chenqiong has left #zope3-dev | 20:19 | |
*** chenqiong has joined #zope3-dev | 20:20 | |
*** batlogg has joined #zope3-dev | 20:27 | |
*** sashav has joined #zope3-dev | 20:30 | |
volvox | I've seen on the ancient proposal about "no owner role" that the core devs think it's important for principals to have only one role at a time. Is it still so? | 20:38 |
*** dobee has joined #zope3-dev | 20:41 | |
philiKON | volvox, no | 20:43 |
philiKON | volvox, principals can have more than 1 role | 20:43 |
volvox | philiKON: i know how it's implemented. i've also read an old philosophical stance by Jim about that, and didn't understand the reason :-) | 20:48 |
volvox | "Furthermore, having a role like this does not really fit into the Zope 3 security model, since we would like a user to have only one role at a time." | 20:48 |
volvox | http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/NoOwnershipRole | 20:48 |
philiKON | volvox, note that roles are just part of a particular (default) security policy | 20:49 |
philiKON | there is another security policy that doesn't use roles for zope3 (zc.sharing) | 20:49 |
volvox | ok. i'm happy to know i'm doing nothing wrong, tnx | 20:50 |
*** mkerrin has joined #zope3-dev | 21:05 | |
*** chenqiong has quit IRC | 21:15 | |
*** chenqiong has joined #zope3-dev | 21:20 | |
*** dobee has quit IRC | 21:40 | |
*** flox|away is now known as flox | 21:52 | |
*** enterloper has joined #zope3-dev | 22:00 | |
enterloper | Hi all, if there is a kind soul with knowledge of Zope3 authentication machinery (esp. sessioning) around here, i am a developer working on an extension of zope who could really use a few good pointers! mostly in regards to the publisher module under z3. in particular, when in the publish function, IClientIdManager seems not to be initialized without a request.traverse into the ZODB. why would this be? (have a few peripheral | 22:01 |
philiKON | enterloper, your msg is too long, got truncated | 22:01 |
enterloper | sorry, let me try again.. | 22:02 |
philiKON | break it up into specific questions | 22:02 |
enterloper | in regards to the publisher module under z3. in particular, when in the publish function, IClientIdManager seems not to be initialized without a request.traverse into the ZODB. why would this be? (have a few peripheral guesses) | 22:02 |
enterloper | always gotta have an intro sentence :p | 22:02 |
enterloper | pardon if it's not a square question. I'm playing in the publisher function in zope/publisher/publish.py | 22:03 |
philiKON | hmm, why? | 22:03 |
enterloper | an experimental extension of zope | 22:03 |
philiKON | uh huh | 22:04 |
enterloper | that does things that would make you upset, but it's fun and exciting | 22:04 |
philiKON | client id managers are typically persistent | 22:04 |
philiKON | at least the one for HTTP clients is | 22:04 |
enterloper | and so it's a proven thing in zope2 and i am trying to move what i have to zope 3 | 22:04 |
philiKON | hence, you'll need to find sites first where a client id manager is stored | 22:04 |
philiKON | in order to be able to look it up | 22:04 |
enterloper | right. thought so - can i make a few statements, then see what ya think? here goes | 22:05 |
enterloper | what i'm doing is testing request.get('PATH_INFO') and IF it's a url i want to munge - i divert it into another system | 22:06 |
enterloper | now when in zope2 i did this, the credentials (user/session/etc) for the current user didn't exist until (i found out trial/error) AFTER i did a request.traverse | 22:06 |
philiKON | enterloper, why not implement this as a wsgi middleware? | 22:06 |
benji | enterloper, you might be better off with wsgi | 22:06 |
philiKON | benji, :) | 22:06 |
benji | heh | 22:06 |
philiKON | hey benji | 22:07 |
benji | hey philiKON | 22:07 |
enterloper | i will look, hope to get this out first | 22:07 |
enterloper | to you guys | 22:07 |
philiKON | we'll probably just ocntinue to tell you that you're hooking into the wrong places | 22:07 |
enterloper | Im cool with that. here is what i did in zope2 - | 22:07 |
enterloper | dummyObj=request.traverse('', validated_hook=validated_hook) | 22:08 |
enterloper | after i did this - i had good auth info from the security machinery in zope2 - i suppose this is because it was acquring from a toplevel user folder object | 22:09 |
enterloper | in zope3 it looks almost the same | 22:09 |
enterloper | but now i have to traverse to a an actual object somewhere before it will pick this info up | 22:10 |
enterloper | so having looked over all the code.. | 22:10 |
enterloper | at least alot of it :) | 22:10 |
enterloper | i was wondering how one would 'fake' it - how could i get authenication info setup for a request (against perhaps a preset manager in the instance) | 22:11 |
enterloper | (whatever object does that biz) | 22:11 |
philiKON | what's your (high-level) use case? | 22:11 |
enterloper | so that i can have my cake and eat it too - diversion to my system - authentication from zope | 22:11 |
philiKON | aha. you want authentication from zope but stuff come from another system? | 22:12 |
enterloper | yeah -- and previously with zope2 i did this - all in the same process which is very cool and important to the project | 22:12 |
enterloper | that 'other system' is really just a python module i load into the publish.py namespace | 22:13 |
enterloper | so imagine a url '/1/2/3' and the system is set up to recognize 1 as my area - then the response to 1/2/3 comes from me and puiblish.py returns. | 22:14 |
enterloper | else 2/3/4 comes from zope as normal | 22:14 |
philiKON | i think hacking publish.py is not a good option | 22:15 |
enterloper | but when i 'divert' in the publish.py module, something about calling request.traverse is what finally fills out the session and client info (cookies and all) and i wanted to find out how to fake it | 22:15 |
philiKON | try a custom traversal adapter | 22:15 |
*** sashav has quit IRC | 22:15 | |
*** sashav has joined #zope3-dev | 22:15 | |
enterloper | in my mind it is good because i want to filter all outgoing content - and it all leaves out of there. it's a fulcrum point. | 22:16 |
enterloper | a custom traversal adapter is new news to me. | 22:16 |
enterloper | that is filter all outgoing html, actually. | 22:16 |
philiKON | you either want a wsgi middleware, a custom traversal adapter, or a combination | 22:17 |
philiKON | the hacks you're trying to do sound just too wild | 22:17 |
enterloper | the funny thing is that this actually works man | 22:17 |
enterloper | i've been using the exact same thing in zope2 for quite a while | 22:17 |
enterloper | works well. | 22:17 |
philiKON | good for you | 22:18 |
philiKON | i wouldn't advise the same thing in z3 though | 22:18 |
philiKON | because there are just simpler measure | 22:18 |
philiKON | s | 22:18 |
enterloper | hmm gotcha. | 22:18 |
enterloper | notes to take are wsgi and custom traversals huh? the idea of course is that i did this in 4 lines the old way, but if there is 'simpler' in z3 i'm all about it. | 22:19 |
philiKON | well, it might be more lines | 22:19 |
philiKON | but it'd be less brittle i guess | 22:19 |
philiKON | plus, i'd be surprised if it was just 4 line sin z3 :) | 22:19 |
philiKON | after all, if the hack worked in zope 2, who is to say that it still works in z3 | 22:20 |
enterloper | i do notice that it probably worked in z2 cause it just acquired a auth source from the top level - but not in z3 cause it needs a site folder - | 22:20 |
enterloper | i already have it working half way in z3 - all i'm missing is the step where auth info in created and wished to know where how to force caling a auth source in a site folder to trick it | 22:21 |
philiKON | auth is done during traversal | 22:21 |
philiKON | zope.app.pulbication | 22:21 |
enterloper | now - if i have a site | 22:21 |
philiKON | search for maybeplacefullyauthenticate or so | 22:21 |
enterloper | how would i traverse to it with out having an actual request to that area - that's what's trickin me | 22:22 |
enterloper | (i had looked there previously, good long night with that code) | 22:22 |
philiKON | you need to get hold of the root object | 22:22 |
philiKON | root database object | 22:22 |
philiKON | which isn't the root folder, though | 22:22 |
philiKON | the root db object contains the root folder | 22:22 |
philiKON | the root folder usually is a site | 22:22 |
enterloper | i saw that in the maybeauthplacefully - | 22:23 |
enterloper | i can dupe that, then take that object and traverse to it perhaps? | 22:24 |
philiKON | perhaps | 22:24 |
philiKON | sorry, need to get back to work... | 22:24 |
enterloper | fine lead anyway | 22:24 |
enterloper | thanks. | 22:24 |
philiKON | np | 22:25 |
enterloper | totally perverse! | 22:36 |
enterloper | try: | 22:36 |
enterloper | publication.beforeTraversal(request) | 22:36 |
enterloper | object = publication.getApplication(request) | 22:36 |
enterloper | object = request.traverse(object) | 22:36 |
enterloper | publication.afterTraversal(request, object) | 22:36 |
enterloper | except: | 22:36 |
enterloper | interface.divert(request) | 22:36 |
enterloper | works thanks philiKON | 22:37 |
* philiKON shivers | 22:37 | |
philiKON | :) | 22:37 |
enterloper | yessir i know 20 pushups right now | 22:37 |
*** chenqiong has quit IRC | 22:37 | |
philiKON | :) | 22:37 |
*** romanofski has quit IRC | 22:53 | |
*** enterloper has quit IRC | 22:59 | |
*** zagy_ has quit IRC | 23:05 | |
*** dunny has joined #zope3-dev | 23:08 | |
*** flox has quit IRC | 23:18 | |
*** flox has joined #zope3-dev | 23:19 | |
*** alecm has quit IRC | 23:21 | |
*** RaFromBRC has joined #zope3-dev | 23:43 | |
flox | about the Rotterdam skin, again | 23:47 |
flox | there's 2 templates, 'template_tablelayout.pt' and 'template.pt' | 23:49 |
flox | but 2nd one is not used | 23:49 |
flox | is it because it is buggy, or other reason? | 23:50 |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!