Re: [Zope-dev] zope.browser?
Hi Robert > Betreff: Re: [Zope-dev] zope.browser? > > Hi, > > Am Donnerstag, den 11.12.2008, 17:13 +0100 schrieb Roger Ineichen: > > > > > I just moved the zope.app.form.interfaces.ITerms interface to this > > package. Which makes it possible to implement ISource and their > > widgets in z3c.form wihtout to depend on zope.app.browser. > > (zagy branch in z3c.form) > > > > I didn't see any other (browser) interface which should go to this > > package because of real dependency problems yet. But sure > if you see > > something which can solve problems, feel free to move interfaces, > > dependency less components or helper methods to this package. > We have written browser helper tools in a package named > cornerstone.browser. especially IRequestMixin here > > http://dev.plone.org/collective/browser/cornerstone.browser/tr > unk/cornerstone/browser/interfaces.py > > might be a candidate for this or such a component. I like this. But we should not mix the cleanup refactoring with any other new things. I think this will confuse people and will give us less aceptance for the really needed cleanup. Let's keep this pending and discuss at a later time again. Regards Roger Ineichen ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Hi Martijn > Betreff: Re: [Zope-dev] zope.browser? [...] > I think we should be careful not to introduce more > functionality into zope.browser right now that isn't moved > from some other zope.* package. > The goal after all, as I understand it, is to reduce > installation dependencies. Yes, absolutly, nothing else right now. I came to a point where I really like to get rid of zope.app.rotterdam, zope.app.authentication and many other packages in my simple project setup. Right now, we have a very nice component architecture, but we can't use them as we like. There are to many packages grouped together with each other on zcml level or for just for using some minimal things. The next step whould be moving the IPasswordManager implementation from zope.app.authentication to zope.app.security. This makes it possible to provide a zope.app.authentication less zope.app.testing package. Also zope.app.keyreference and zope.app.intid should get ported to zope.* packages. Another part which I'll cleanup is the zope.app.i18n configure.zcml. This zcml file registers in line: 5 -28 different components from totaly different packages. Each of them should go to the right package where the components are defined. It doesn't make sense to configure them in zope/app/i18n/confiure.zcml. btw All I like to do is to remove the dependencies which are not needed for a minimal installation. But everything should be backward compatible and just work like before. I will not introduce new dependencies or implement new components. It's all about cleanup existing things. But as far as I can see, most people are happy with removing dependencies and make progress in this direction. Any participation or discussion is very welcome! I just like to keep the discussion to a minimum and be a more productive. I'll promiss to take care and do nothing which doesn't make sense. Does this Ok and does it make sense for you? Regards Roger Ineichen ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Dependencies question
I was looking at dependencies of various zope.* packages and see that some packages depend on other because of ZCML directives and some are not. For example: The zope.app.catalog package depends on zope.app.component, but doesn't use it anywhere in non-testing code, however it does use the ``class`` directive, registered in zope.app.component. While the zope.app.keyreference doesn't depend on zope.app.component at all, but uses ``class`` directive as well. So, the question is: what's the common policy for that? Should we depend on packages that is used in ZCML or not? Or maybe ZCML-related dependencies should be in some extras_require, say "zcml"? Personally, I think, that extras_require way is a nice compromise for that. Because many of packages can be used greatly without ZCML configuration, but getting ZCML-reqired dependencies should be easy. PS BTW, I think that zope.app.keyreference should be moved to plain zope.keyreference, because it's really lightweight, useful outside of zope and it doesn't depend on any zope.app package. What do you people think? -- WBR, Dan Korostelev ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form 2.0 release
On Thursday 11 December 2008, Adam GROSZER wrote: > size="" alt="" maxlength="" > > for *hidden* text and textarea inputs? > I'm not an HTML guru, but does not seem to make much sense. No, I think they are not even valid HTML. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
On Thursday 11 December 2008, Martijn Faassen wrote: > I think we should be careful not to introduce more functionality into > zope.browser right now that isn't moved from some other zope.* package. > The goal after all, as I understand it, is to reduce installation > dependencies. +1 Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Am Donnerstag, den 11.12.2008, 18:18 +0100 schrieb Martijn Faassen: > Hi there, > > Robert Niederreiter wrote: > [snip] > > We have written browser helper tools in a package named > > cornerstone.browser. especially IRequestMixin here > > > > http://dev.plone.org/collective/browser/cornerstone.browser/trunk/cornerstone/browser/interfaces.py > > > > might be a candidate for this or such a component. > > While this is certainly an interesting package, I think the idea behind > zope.browser is to keep dependencies to an absolute minimum. I'm not > sure I see the point of just putting the *interface* "IRequestMixin" in > zope.browser, and the implementation would almost certainly pull in more > dependencies, right? It would be possible to strip the implementation dependencies down to zope.interface and zope.component if IAbsoluteUrl (iirc) is moved as well and the ICookiePrefix default implementation returns something static. > (by the way, an interface called 'Mixin'? Isn't the > mixin nature a property of a class, not an interface?) Yes ;), the naming is not the best choice. The intention was to hint the reader how an implementation of this interface is supposed to be used. > > I think we should be careful not to introduce more functionality into > zope.browser right now that isn't moved from some other zope.* package. > The goal after all, as I understand it, is to reduce installation > dependencies. you queried ideas. right? regards, robert > > Regards, > > Martijn > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) -- Robert Niederreiter IT-Architecture & Engineering Aflingerstraße 7 A-6176 Völs +43 699 160 20 192 +43 512 89 00 77 Squarewave Computing WEB APPLICATIONS, ZOPE, PLONE, HOSTING BlueDynamics Allianceproduction: concept, development, design http://squarewave.at consulting: analysis, coaching, training http://bluedynamics.com management: projects, process, community ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Hi there, Robert Niederreiter wrote: [snip] > We have written browser helper tools in a package named > cornerstone.browser. especially IRequestMixin here > > http://dev.plone.org/collective/browser/cornerstone.browser/trunk/cornerstone/browser/interfaces.py > > might be a candidate for this or such a component. While this is certainly an interesting package, I think the idea behind zope.browser is to keep dependencies to an absolute minimum. I'm not sure I see the point of just putting the *interface* "IRequestMixin" in zope.browser, and the implementation would almost certainly pull in more dependencies, right? (by the way, an interface called 'Mixin'? Isn't the mixin nature a property of a class, not an interface?) I think we should be careful not to introduce more functionality into zope.browser right now that isn't moved from some other zope.* package. The goal after all, as I understand it, is to reduce installation dependencies. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Hi, Am Donnerstag, den 11.12.2008, 17:13 +0100 schrieb Roger Ineichen: > > I just moved the zope.app.form.interfaces.ITerms interface > to this package. Which makes it possible to implement ISource > and their widgets in z3c.form wihtout to depend on zope.app.browser. > (zagy branch in z3c.form) > > I didn't see any other (browser) interface which should go to > this package because of real dependency problems yet. But sure > if you see something which can solve problems, feel free > to move interfaces, dependency less components or helper > methods to this package. We have written browser helper tools in a package named cornerstone.browser. especially IRequestMixin here http://dev.plone.org/collective/browser/cornerstone.browser/trunk/cornerstone/browser/interfaces.py might be a candidate for this or such a component. We use it most of the time as mixin for browser views, content providers, menu items and everything else which has to deal with application state data, urls and queries. For IRequestMixin the implementation is almost finished (one function and some testing left - see base.py and base.txt if you're interested in), and for the pointed usecases there are convenience implementations. It would be great to see this or something like this in zope.browser package, dealing with request data and url's is almost every day's business and always more code than i could be. regards, robert > > I think everything which goes to zope.browser must take > very care on dependencies. > > I guess one important rule should be, zope.browser > should depend on anything. Probably an exception > whould be zope.schema, zope.messageid. > > Any other ideas? > > Regards > Roger Ineichen > > > Regards. > > > > Martijn > > > > > > ___ > > Zope-Dev maillist - Zope-Dev@zope.org > > http://mail.zope.org/mailman/listinfo/zope-dev > > ** No cross posts or HTML encoding! ** (Related lists - > > http://mail.zope.org/mailman/listinfo/zope-announce > > http://mail.zope.org/mailman/listinfo/zope ) > > > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form 2.0 release
Hello, A different question now: Do we need the attributes size="" alt="" maxlength="" for *hidden* text and textarea inputs? I'm not an HTML guru, but does not seem to make much sense. (textarea does not have a hidden pt yet, but soon) -- Best regards, Adam GROSZERmailto:[EMAIL PROTECTED] -- Quote of the day: No wonder I feel so tired - I'm older now than I've ever been before. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Hi Martijn > Betreff: Re: [Zope-dev] zope.browser? > > Martijn Faassen wrote: > > Hi there, > > > > I saw that Roger Ineichen created and released a package called > > zope.browser. > > > > I assume that this package is intended to reduce > dependencies, which > > is a project I applaud. So far I don't see any effect of this - in > > fact several packages now have an added dependency to zope.browser > > that wasn't there before. I'm sure there's a bit of the > plan I don't > > understand yet - please enlighten me? > > Looking more, I've noticed that zc.sourcefactory replaces the > dependency on zope.app.form with this package. That seems to > be an improvement. > > Since I'm quite interested in this project, I'd like to hear > much more about how we will determine which kind of > dependency surgery we'll do next. I just moved the zope.app.form.interfaces.ITerms interface to this package. Which makes it possible to implement ISource and their widgets in z3c.form wihtout to depend on zope.app.browser. (zagy branch in z3c.form) I didn't see any other (browser) interface which should go to this package because of real dependency problems yet. But sure if you see something which can solve problems, feel free to move interfaces, dependency less components or helper methods to this package. I think everything which goes to zope.browser must take very care on dependencies. I guess one important rule should be, zope.browser should depend on anything. Probably an exception whould be zope.schema, zope.messageid. Any other ideas? Regards Roger Ineichen > Regards. > > Martijn > > > ___ > Zope-Dev maillist - Zope-Dev@zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
On Thu, Dec 11, 2008 at 03:20:25PM +0100, Martijn Faassen wrote: > I'm sure there's a bit of the plan I don't > understand yet - please enlighten me? AFAIKR, it's a package that mostly contains interfaces for well accepted browser design paradigms. That way different implementations can share the same interfaces. Obviously we've gotta be careful of what goes in there. -- Brian Sutherland ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.browser?
Martijn Faassen wrote: > Hi there, > > I saw that Roger Ineichen created and released a package called > zope.browser. > > I assume that this package is intended to reduce dependencies, which is > a project I applaud. So far I don't see any effect of this - in fact > several packages now have an added dependency to zope.browser that > wasn't there before. I'm sure there's a bit of the plan I don't > understand yet - please enlighten me? Looking more, I've noticed that zc.sourcefactory replaces the dependency on zope.app.form with this package. That seems to be an improvement. Since I'm quite interested in this project, I'd like to hear much more about how we will determine which kind of dependency surgery we'll do next. Regards. Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.browser?
Hi there, I saw that Roger Ineichen created and released a package called zope.browser. I assume that this package is intended to reduce dependencies, which is a project I applaud. So far I don't see any effect of this - in fact several packages now have an added dependency to zope.browser that wasn't there before. I'm sure there's a bit of the plan I don't understand yet - please enlighten me? Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 4 OK, 2 Failed
Summary of messages to the zope-tests list. Period Wed Dec 10 12:00:00 2008 UTC to Thu Dec 11 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures - Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 10 20:32:09 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010631.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Wed Dec 10 20:33:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010632.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Dec 10 20:26:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010627.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 10 20:27:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010628.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 10 20:29:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010629.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 10 20:30:39 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010630.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] z3c.form 2.0 release
Am 09.12.2008 um 12:15 schrieb Roger Ineichen: [...] > Should I do that tomorrow? And adjust all related packages > like zope.app.form, z3c.form etc. Are there other packages > which use ITerms except the one in zope.*? > > Christian, are you fine with this? Can you based on that > merge your branch to z3c.form? I merged the zagy-sources branch to the trunk. Yours sincerely, -- Michael Howitz · [EMAIL PROTECTED] · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
