Re: [Zope-dev] Work on the zope.publisher components and their genericity
For people interested in what's hiding behind that, I started a demo here : http://gitweb.dolmen-project.org/CromlechDemo.git We're trying to publish things with a simplified publisher and to keep the backward compatibility We want to make the grok components independant from zope.publisher, to be useable in more frameworks The global idea is to simplify the flow of the publishing, the auth, etc. There's no tests, , this is a proof of concept. Please, test accordingly, if you want to test and have a look. 2011/3/28 Matthias : >> http://svn.zope.org/repos/main/zope.browser/branches/publisher_definition/ >> >> Changes have been rolled back accordingly. >> Cheers >> >> - Souheil > > I'd love to se these changes being incorporated soon. They'll allow > cutting down on zope.publisher dependencies and therefor opening zope to > other frameworks. > > -Matthias > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Work on the zope.publisher components and their genericity
> http://svn.zope.org/repos/main/zope.browser/branches/publisher_definition/ > > Changes have been rolled back accordingly. > Cheers > > - Souheil I'd love to se these changes being incorporated soon. They'll allow cutting down on zope.publisher dependencies and therefor opening zope to other frameworks. -Matthias ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Work on the zope.publisher components and their genericity
Here lies the branch: http://svn.zope.org/repos/main/zope.browser/branches/publisher_definition/ Changes have been rolled back accordingly. Cheers - Souheil 2011/3/24 Jim Fulton : > On Thu, Mar 24, 2011 at 4:14 PM, Souheil CHELFOUH wrote: >> Thank you for taking the time to answer, Jim. >> >> The work, according to its descriptive nature, was done on the trunk. >> I can revert the change and make a branch, if that's more appropriate >> for this kind of evolution. >> No problem. > > Please do. Thanks. > > Jim > > -- > Jim Fulton > http://www.linkedin.com/in/jimfulton > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Work on the zope.publisher components and their genericity
On Thu, Mar 24, 2011 at 4:14 PM, Souheil CHELFOUH wrote: > Thank you for taking the time to answer, Jim. > > The work, according to its descriptive nature, was done on the trunk. > I can revert the change and make a branch, if that's more appropriate > for this kind of evolution. > No problem. Please do. Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Work on the zope.publisher components and their genericity
Thank you for taking the time to answer, Jim. The work, according to its descriptive nature, was done on the trunk. I can revert the change and make a branch, if that's more appropriate for this kind of evolution. No problem. - Souheil 2011/3/24 Jim Fulton : > On Thu, Mar 24, 2011 at 12:17 PM, Souheil CHELFOUH wrote: >> Hello, >> >> I've been working a lot on zope.publisher lately, trying to extract >> its essence to make my own publisher and flatten the publication >> process. >> This led me to the prototyping of some essential components I wanted >> to factor out of zope.publisher. >> Mainly, these are definitions, aka interfaces, therefore I created >> some new entries in zope.browser. >> >> Here are the changelogs : >> >> Added definitions to the base browser publishing process, including : >> >> * IRequest and IResponse >> * IPublisher >> * Errors definitions with : IPublishingError, IBadRequest, INotFound >> and IRedirect >> * Views publishing help : IDefaultViewName, that permits to retrieve >> the name of the default view for a context. >> >> This allows us to move toward a greater interoperability with other >> systems, severing a lot of zope packages' ties with ``zope.publisher``, >> where all these concepts were initially defined. ``zope.publisher`` will >> now use these interfaces as mixins to create zope publication >> specific definitions. Components that don't need the full blow >> definition can now register on broader interfaces, making them >> available to non ``zope.publisher`` aware applications. >> >> >> I would like very much to see that review and criticized constructively. > > Is there a branch to review? > >> zope.browser hosts some irrelevant definitions and i added things I >> thought would make sense. >> The next step would be to lighten the dependencies of some zope >> component on zope.publisher. >> If possible, i'd like to see this 1.4 released. >> >> Thank you for your attention > > Thanks for digging into this. I'd be happy to do a review and give some > feedback. > > Jim > > > -- > Jim Fulton > http://www.linkedin.com/in/jimfulton > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Work on the zope.publisher components and their genericity
On Thu, Mar 24, 2011 at 12:17 PM, Souheil CHELFOUH wrote: > Hello, > > I've been working a lot on zope.publisher lately, trying to extract > its essence to make my own publisher and flatten the publication > process. > This led me to the prototyping of some essential components I wanted > to factor out of zope.publisher. > Mainly, these are definitions, aka interfaces, therefore I created > some new entries in zope.browser. > > Here are the changelogs : > > Added definitions to the base browser publishing process, including : > > * IRequest and IResponse > * IPublisher > * Errors definitions with : IPublishingError, IBadRequest, INotFound > and IRedirect > * Views publishing help : IDefaultViewName, that permits to retrieve > the name of the default view for a context. > > This allows us to move toward a greater interoperability with other > systems, severing a lot of zope packages' ties with ``zope.publisher``, > where all these concepts were initially defined. ``zope.publisher`` will > now use these interfaces as mixins to create zope publication > specific definitions. Components that don't need the full blow > definition can now register on broader interfaces, making them > available to non ``zope.publisher`` aware applications. > > > I would like very much to see that review and criticized constructively. Is there a branch to review? > zope.browser hosts some irrelevant definitions and i added things I > thought would make sense. > The next step would be to lighten the dependencies of some zope > component on zope.publisher. > If possible, i'd like to see this 1.4 released. > > Thank you for your attention Thanks for digging into this. I'd be happy to do a review and give some feedback. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Work on the zope.publisher components and their genericity
Hello, I've been working a lot on zope.publisher lately, trying to extract its essence to make my own publisher and flatten the publication process. This led me to the prototyping of some essential components I wanted to factor out of zope.publisher. Mainly, these are definitions, aka interfaces, therefore I created some new entries in zope.browser. Here are the changelogs : Added definitions to the base browser publishing process, including : * IRequest and IResponse * IPublisher * Errors definitions with : IPublishingError, IBadRequest, INotFound and IRedirect * Views publishing help : IDefaultViewName, that permits to retrieve the name of the default view for a context. This allows us to move toward a greater interoperability with other systems, severing a lot of zope packages' ties with ``zope.publisher``, where all these concepts were initially defined. ``zope.publisher`` will now use these interfaces as mixins to create zope publication specific definitions. Components that don't need the full blow definition can now register on broader interfaces, making them available to non ``zope.publisher`` aware applications. I would like very much to see that review and criticized constructively. zope.browser hosts some irrelevant definitions and i added things I thought would make sense. The next step would be to lighten the dependencies of some zope component on zope.publisher. If possible, i'd like to see this 1.4 released. Thank you for your attention - Souheil ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
