t; Betreff: Re: AW: AW: [Zope-dev] Proposal: zope.app.publisher
> refactoring
>
> Am 25.08.2009 um 14:39 schrieb Roger Ineichen:
> [...]
> > I was looking another time at the z3c.layer.pagelet package.
> >
> > I agree that the added authentication support is useful
Am 25.08.2009 um 14:39 schrieb Roger Ineichen:
[...]
> I was looking another time at the z3c.layer.pagelet package.
>
> I agree that the added authentication support is useful and
> was missing in the first releases. The loginForm.html pagelet
> should stay there. But we should move the viewlets to
Dan Korostelev wrote:
> 2009/8/25 Martijn Faassen :
>
>> You have zope.browsermenu, zope.browserpage, zope.browserresource. I
>> propose instead we name them zope.menu, zope.page and zope.resource.
>
> -1 These things are really only for browser, and ZCML directives are
> in "browser" namespace,
2009/8/25 Martijn Faassen :
> You have zope.browsermenu, zope.browserpage, zope.browserresource. I
> propose instead we name them zope.menu, zope.page and zope.resource.
-1 These things are really only for browser, and ZCML directives are
in "browser" namespace, while, for example, "zope.resource
Hi there,
Here are some steering-groupish responses.
General note: I'm quite enthusiastic about the general plan to clean up
zope.app.publisher! Thanks for bringing this up!
Dan Korostelev wrote:
> Menu mechanism (the browser:menuItem directive and friends) - move
> this to the new "zope.brow
Dan Korostelev wrote:
> 2009/8/24 Stephan Richter :
>> On Friday 21 August 2009, Dan Korostelev wrote:
>>> BrowserSkinsVocabulary - this can be moved to zope.publisher.browser
>>> and rewritten with zope.schema's SimpleVocabulary not to introduce
>>> dependency on zope.componentvocabulary.
>> -1. W
Dan Korostelev wrote:
> 2009/8/21 Dan Korostelev :
>
>> Browser view directives (browser:page and friends) - move this to some
>> "zope.browserpage" package and make its structure more clean, so
>> people could understand the magic of browser page class generation.
>> :-)
>
> Silly me, I forgot t
Hey,
Shane Hathaway wrote:
[snip]
> Few developers care about XML-RPC these days. Most web developers are
> now working with REST, JSON, and other similar stuff. It's probably
> best to move all XML-RPC artifacts, including those in zope.publisher,
> to a single package, so that most develope
Hi Michael
> Betreff: Re: AW: [Zope-dev] Proposal: zope.app.publisher refactoring
>
> Am 24.08.2009 um 22:55 schrieb Roger Ineichen:
> [...]
> > Everything which has to do with login has nothing to do in
> > z3c.layer.pagelet.
> > z3c.layer.pagelet should
Am 24.08.2009 um 22:55 schrieb Roger Ineichen:
[...]
> Everything which has to do with login has nothing to do
> in z3c.layer.pagelet.
> z3c.layer.pagelet should only offer a working setup for
> pagelet based traversal stuff and error handling.
Until we find a better place for it I'd like to keep
Am 24.08.2009 um 19:02 schrieb Dan Korostelev:
> 2009/8/22 Michael Howitz :
>> Am 21.08.2009 um 21:06 schrieb Dan Korostelev:
[...]
>> z3c.layer.pagelet also uses these interfaces to re-implement login/
>> logout
>> like zope.app.security but by using pagelets and viewlets.
>> So it would be nice
Hi Dan
> Betreff: Re: [Zope-dev] Proposal: zope.app.publisher refactoring
>
> 2009/8/22 Michael Howitz :
> > Am 21.08.2009 um 21:06 schrieb Dan Korostelev:
> > [...]
> >>
> >> ILogin, ILogout from zope.app.publisher.interfaces.http -
> looks like
>
2009/8/22 Michael Howitz :
> Am 21.08.2009 um 21:06 schrieb Dan Korostelev:
> [...]
>>
>> ILogin, ILogout from zope.app.publisher.interfaces.http - looks like
>> these don't really mean anything and are used only in
>> zope.app.security. I'd move them to zope.app.security even without BBB
>> import
2009/8/24 Stephan Richter :
> On Friday 21 August 2009, Dan Korostelev wrote:
>> BrowserSkinsVocabulary - this can be moved to zope.publisher.browser
>> and rewritten with zope.schema's SimpleVocabulary not to introduce
>> dependency on zope.componentvocabulary.
>
> -1. Why? The reason we wrote the
On Friday 21 August 2009, Dan Korostelev wrote:
> BrowserSkinsVocabulary - this can be moved to zope.publisher.browser
> and rewritten with zope.schema's SimpleVocabulary not to introduce
> dependency on zope.componentvocabulary.
-1. Why? The reason we wrote the zope.componentvocabulary code origi
Am 21.08.2009 um 21:06 schrieb Dan Korostelev:
[...]
> ILogin, ILogout from zope.app.publisher.interfaces.http - looks like
> these don't really mean anything and are used only in
> zope.app.security. I'd move them to zope.app.security even without BBB
> imports (not to make zope.app.publisher depe
Am 21.08.2009 um 23:14 schrieb Dan Korostelev:
> 2009/8/22 Shane Hathaway :
>> Hi Dan,
>>
>> I'll provide feedback for a few parts of your proposal.
> Thanks
>
>> Few developers care about XML-RPC these days. Most web developers
>> are now
>> working with REST, JSON, and other similar stuff. It
2009/8/21 Dan Korostelev :
> Browser view directives (browser:page and friends) - move this to some
> "zope.browserpage" package and make its structure more clean, so
> people could understand the magic of browser page class generation.
> :-)
Silly me, I forgot that browser page directives have t
2009/8/22 Shane Hathaway :
> Hi Dan,
>
> I'll provide feedback for a few parts of your proposal.
Thanks
> Few developers care about XML-RPC these days. Most web developers are now
> working with REST, JSON, and other similar stuff. It's probably best to
> move all XML-RPC artifacts, including th
Hi Dan,
I'll provide feedback for a few parts of your proposal.
Dan Korostelev wrote:
> xmlprc - move the IXMLRPCView interface and XMLRPCView base class to
> zope.publisher as a counterpart to zope.publisher.browser.BrowserView.
> Move MethodPublisher, MethodTraverser, xmlrpc:view ZCML directive
2009/8/21 Dan Korostelev :
> I think it's time to clean the mess in the zope.app.publisher package.
> Currently it contains many things that could be moved into separate
> packages or merged with base zope packages. So here's a sketch plan
> about where to move things:
BTW, I am also waiting for c
2009/8/21 Fabio Tranchitella :
> * 2009-08-21 21:07, Dan Korostelev wrote:
>> IXMLRPCPublisher adapters for zope.container - move them to
>> zope.container. The IBrowserPublisher adapters that are already there, so
>> it won't make things worser. The zope.container package may be refactored
>> late
* 2009-08-21 21:07, Dan Korostelev wrote:
> IXMLRPCPublisher adapters for zope.container - move them to
> zope.container. The IBrowserPublisher adapters that are already there, so
> it won't make things worser. The zope.container package may be refactored
> later to break dependency on zope.publish
Hi all.
I think it's time to clean the mess in the zope.app.publisher package.
Currently it contains many things that could be moved into separate
packages or merged with base zope packages. So here's a sketch plan
about where to move things:
Menu mechanism (the browser:menuItem directive and fri
24 matches
Mail list logo
