Re: [Zope3-Users] Re: Zope 3.1.0 & Zope3 Developer's Book
On Saturday 18 June 2005 01:08 pm, Corey wrote: > Does the online Zope3 reflect the dead-tree version? > Ack, my bad - looks like this is stated to not be the case right there on the front page, sorry! http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FrontPage/Zope3Book "It also has not been edited based on Sams comments and editions. " Appologies for the noise! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: Zope 3.1.0 & Zope3 Developer's Book
Thanks for the response, Stephan; your efforts are appreciated! Maybe I can be of some help by going through the book using the new 3.1b and make notes of whatever stuff ( code and/or text ) that could be changed to better reflect the changes from 3.0 to 3.1. Or maybe if the Zope3 Book was wiki'fied, like the Zope2 Book ( http://www.zope.org/Documentation/Books/ZopeBook/2_6Edition/ ), it would be easier for others to contribute change suggestions and report issues/discrepancies. Does the online Zope3 reflect the dead-tree version? On Saturday 18 June 2005 12:32 pm, Stephan Richter wrote: > On Saturday 18 June 2005 15:19, Corey wrote: > > Question: with all these new changes since 3.0 ( which all look very > > good! ), approximately how much of the Zope3 Dev Book becomes > > misleading/incorrect/obsolete? Primarily I'm wondering whether it is > > still possible to use the Zope3 dev book , follow along with it's > > examples/excersises without constantly running into troubles? > > Yeah, I think that most of it will still work just fine. I think someone > reported that step 7 or 8 of the messageboard product was still working on > the trunk, which is impressive. Before the final release I will take some > time and make sure that all the packages will still work without > modification. > > > Right off the bat, I can see that the stuff on Services will be a point > > of hassle and confusion for many people starting off w/ Zope 3.1 and the > > current Zope3 dev guide. > > Right, this cannot be avoided. But I already talk very little about > services in the book. > > > Are there prospective plans to keep the book updated with the releases, > > or are there simply not enough resources/time available at this point to > > do so? > > I am not sure how much time I will have. I am very booked till school > starts again. I would need at least a week to get everything updated, not > to mention covering new features. > > Regards, > Stephan ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: Zope 3.1.0 & Zope3 Developer's Book
On Saturday 18 June 2005 15:19, Corey wrote: > Question: with all these new changes since 3.0 ( which all look very good! > ), approximately how much of the Zope3 Dev Book becomes > misleading/incorrect/obsolete? Primarily I'm wondering whether it is still > possible to use the Zope3 dev book , follow along with it's > examples/excersises without constantly running into troubles? Yeah, I think that most of it will still work just fine. I think someone reported that step 7 or 8 of the messageboard product was still working on the trunk, which is impressive. Before the final release I will take some time and make sure that all the packages will still work without modification. > Right off the bat, I can see that the stuff on Services will be a point of > hassle and confusion for many people starting off w/ Zope 3.1 and the > current Zope3 dev guide. Right, this cannot be avoided. But I already talk very little about services in the book. > Are there prospective plans to keep the book updated with the releases, or > are there simply not enough resources/time available at this point to do > so? I am not sure how much time I will have. I am very booked till school starts again. I would need at least a week to get everything updated, not to mention covering new features. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Zope 3.1.0 & Zope3 Developer's Book
On Saturday 18 June 2005 11:50 am, Stephan Richter wrote: > Most Important Changes Since 3.0 Question: with all these new changes since 3.0 ( which all look very good! ), approximately how much of the Zope3 Dev Book becomes misleading/incorrect/obsolete? Primarily I'm wondering whether it is still possible to use the Zope3 dev book , follow along with it's examples/excersises without constantly running into troubles? Right off the bat, I can see that the stuff on Services will be a point of hassle and confusion for many people starting off w/ Zope 3.1 and the current Zope3 dev guide. Are there prospective plans to keep the book updated with the releases, or are there simply not enough resources/time available at this point to do so? Many thanks! ( not trying to be a squeeky wheel, just curious ) Cheers, Corey ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Zope 3.1.0 beta 1 released!
Hello everyone, The Zope 3 development team is proud to announce Zope 3.1.0 beta 1. Zope 3 is the next major Zope release and has been written from scratch based on the latest software design patterns and the experiences of Zope 2. It is in our opinion that Zope 3.1 is more than ready for production use, which is why we decided to drop the 'X' for experimental from the name. We will also continue to work on making the transition between Zope 2 and Zope 3 as smooth as possible. As a first step, Zope 2.8 includes Zope 3 features in the form of Five. Please test this release carefully and send us any feedback! In particular, we have tried very hard to keep backward-compatibility with the previous X3 3.0 release, so please let us know if the new release breaks your code. Downloads http://zope.org/Products/Zope3/ Installation instructions for both Windows and Un*x/Linux are now available in the top level 'README.txt' file of the distribution. The binary installer is recommended for Windows. Zope 3.1 requires Python 2.3.5 or 2.4.1 to run. You must also have zlib installed on your system. Most Important Changes Since 3.0 - New Pluggable Authentication Utility (PAU), which is similar in philosophy to the Zope 2 PAS. The following features are available in the in the basic PAU facility: + Credentials Plugins: Basic HTTP Auth, Session + Authenticator Plugins: Principal Folder, Group Folder For a detailed description of the pluggable authentication utility, see 'zope/app/authentication/README.txt'. - Major simplifications to the component architecture: + Removal of the concept of a service. All outstanding services were converted to utilities: Error Reporting, FSSync, Authentication. + Site Managers are global and local now; adapters and utilties are directly registered with the site manager. Now global and local component registration and lookup behaves very similar. + Local registrations can now only have two states: active and inactive. This simplified the code so much, that 'zope.app.utility', 'zope.app.registration' and 'zope.app.site' were all merged into 'zope.app.component'. + Implemented menus as utilities. The API also supports sub-menus now. + Implemented views as adapters. Skins and layers are now simply interfaces that the request provides. - Added an integer-id facility for assigning integer identifiers to objects. - Added basic catalog and index frameworks. - Added "sources", which are like vocabularies except that they support very large collections of values that must be searched, rather than browsed. - Created a new granting UI that allows advanced searching of principal sources. - Implemented a generic user preferences systsem that was designed to be easily used in TALES expressions and via Python code. Preferences can be edited via 'http://localhost:8080/++preferences++/'. A demo of the preferences can be found at:: http://svn.zope.org/Zope3/trunk/src/zope/app/demo/skinpref/ - ZCML now supports conditional directives using the 'zcml:condition' attribute. The condition is of the form "verb argument". Two verbs, 'have feature' and 'installed module' are currently implemented. Features can be declared via the 'meta:provides' directive. - Improved API doctool: Code Browser now shows interfaces, text files and ZCML files; the new Book Module compiles all available doctext files into an organized book; the new Type Module lets you browser all interface types and discover interfaces that provide types; views are shown in the interface details screen; views and adapters are categorized into specific, extended and generic; user preferences allow you to customize certain views; 3rd party modules can now be added to the Code Browser. - Improved I18n-based number and datetime formatting by integrating 'pytz' for timezone support, implementing all missing format characters, and reinterpreting the ICU documentation to correctly parse patterns. - Added '++debug++' traversal adapter that allows you to turn on debugging flags in 'request.debug'. Currently the following flags are defined: source, tal, errors. - Improved logout support. - Added the HTTP request recorder, which lets you inspect raw HTTP requests and responses. It can be used to create functional doctests without requiring third-party tools such as TCPWatch. - Developed a generic 'browser:form' directive. It is pretty much the same as the 'browser:editform' directive, except that the data is not stored on some context or adapted context but sent as a dictionary to special method (by default). For a complete list of changes see the 'CHANGES.txt' file. Resources - "Zope 3 Development Web Site":http://dev.zope.org/Zope3 - "Zope 3 Dev Mailing List":http://mail.zope.org/mailman/listi
RE: [Zope3-dev] Utility Registration was:RE: [Zope3-Users] pluggableauthentication utility
Roger Ineichen wrote:
> pluggableauthentication utility
>
>
> Hi Jim,
>
> perhaps we can discuss this on zope3-dev.
>
> From: Jim Fulton [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, June 16, 2005 12:03 PM
>> To: [EMAIL PROTECTED]
>> Cc: 'GMane'; zope3-users@zope.org
>> Subject: Re: [Zope3-Users] pluggable authentication utility
>>
>> Roger Ineichen wrote:
>>> Hi Ricki
>>>
>>> On Behalf Of GMane
>>>
Sent: Wednesday, June 15, 2005 5:52 PM
To: zope3-users@zope.org
Subject: [Zope3-Users] pluggable authentication utility
Hi,
I have a simple question about pluggable authentication.
I created a folder and I made it a site.
In the default Site-Management Folder I created a Pluggable
Authentication Utility (named plaut).
Inside it I made a PrincipalFolder (Partner) and added a user soc1.
>>>
>>>
>>> Don't give a name (plau). Pluggable authentication utilities
>>> are as dfault unnamed. All components right now will lookup the
>>> PAU with name=''.
>>
>> For 3.2, we need to find a way to make this clearer. Either we need
>> to provide a more verbose description of what the name is for or
>> perhaps, as Stephan has suggested, for components that are always
>> looked up without names, we should not provide the option of
>> entering a name and, for others, we should require a name.
>
> We have to totaly hide this part and offer a different concept.
> Of corse the normal registration will be available too.
>
> I propose to add something like a policy. A policy should register
> a utility. This means we can add policies via ZCML and the user can
> only process this policy which registers the utility in a predefind
> way.
>
> Then we can provide a task like. "register PAU" and everything gets
> registred. There could also be a different policy like:
> "register PAU with initial principal folder" etc.
>
> A ZCML directive could look like:
>
> name="Add PAU with principal Folder"
> for=".interfaces.IPluggableAuthentication"
> class=".authentication.AddPAUWithPrincipalFolderPolicy"
> />
>
> Then we can offer adding utilities via this policies.
>
> If somebody likes to register a utility in a different way, he can
> add own policies for a utility.
>
> I use this pattern in a own registry in a different usecase. It makes
> it very simple for anduser and even me to register components in a
> registry. And you don't have to know every little about the
> registration process.
>
> What do yo think about that? Any other ideas?
It looks like you've identified a common enough use case: PAUs are
typically used with a common set of plugins. The current PAU design
accommodates all sorts of use cases that most users would never face.
Rather than add more complexity to the registration process with
"utilityPolicy" (even though it's an attempt to make things easier for
the user), I'd suggest creating a SimplePluggubleAuthenticationUtility
that supported the most common use cases.
Something like this perhaps:
class ISimplePAU(Interface):
authentication = Choice(values=('HTTP-Auth', 'Session'))
allowUserChangeOnUnauthorized = Bool()
principals = Attribute("A PrincipalsFolder plugin.")
This would be far easier to deal with than the current PAU for those
that don't need PAU's flexibility.
-- Garrett
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
RE: [Zope3-Users] pluggable authentication utility
Jim Fulton wrote: > Roger Ineichen wrote: >> Hi Ricki >> >> On Behalf Of GMane >> >>> Sent: Wednesday, June 15, 2005 5:52 PM >>> To: zope3-users@zope.org >>> Subject: [Zope3-Users] pluggable authentication utility >>> >>> Hi, >>> I have a simple question about pluggable authentication. >>> >>> I created a folder and I made it a site. >>> In the default Site-Management Folder I created a Pluggable >>> Authentication Utility (named plaut). >>> Inside it I made a PrincipalFolder (Partner) and added a user soc1. >> >> >> Don't give a name (plau). Pluggable authentication utilities >> are as dfault unnamed. All components right now will lookup the >> PAU with name=''. The PAU registration doesn't accept a name. He's likely talking about the PAU's name itself, which can be anything. > For 3.2, we need to find a way to make this clearer. Either we need > to provide a more verbose description of what the name is for or > perhaps, as Stephan has suggested, for components that are always > looked up without names, we should not provide the option of entering > a name and, for others, we should require a name. IMO, the PAU pattern of not taking a name works well. The confusion above may be a hold-over from the time when PAU regs did accept names. -- Garrett ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] zpt using the skin
Amigo's, Since everyone seems to be having fun in the sun, no answers on irc. Let me restate it on the users' list: How can I access the standard_macros from a page template that I add using the management interface? results in the following error Module zope.pagetemplate.pagetemplate, line 118, in pt_render Warning: Macro expansion failed Warning: exceptions.KeyError: 'views' can anyone help me out? My goal is to present content in a slot in the current default skin. Should be possible I think. greetings from The Hague, Robert-Reinder -- ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Updating preferences from ZPT
Am Dienstag, 14. Juni 2005 22:29 schrieb Florian Lindner: > What is the best way to redirect or directly output the template the view class is associated with? Ok, I redo my question. Just this part. How can I just ouput the template from a view class: class view: def __call__(self): return template How to do that? Thanks, Florian ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
