Re: [Zope3-Users] best practice for serving static content by front-end webserver?
On 1/13/07, Sascha Ottolski [EMAIL PROTECTED] wrote: Now, when grepping the zope sources, and third party packages, the included files are spread around. that seems to make it impossible to write proper rewrite rules. if a request wants /++resource++/image.gif the webserver couldn't possibly know if image.gif is found in app/Zope-3.3.0/lib/python/zope/app/i18n/browser/ or in app/Zope-3.3.0/lib/python/zope/app/rotterdam/ or in various other directories that carry images. It seems that your objective is to not have Zope serve images. I think the easiest way to do that is to use a cache that has a very long cache-timeout for images. I've found Varnish to be very flexible and useable. The way to figure out where an image is located and then returning it is called traversal and Zope already does that, and you are unlikely to actually be able to make it signficantly faster that Zope already does. ;) -- Lennart Regebro: Python, Zope, CPS, Plone. +33 661 58 14 64 ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] best practice for serving static content by front-end webserver?
Am Sonntag, 14. Januar 2007 09:49 schrieb Lennart Regebro: On 1/13/07, Sascha Ottolski [EMAIL PROTECTED] wrote: Now, when grepping the zope sources, and third party packages, the included files are spread around. that seems to make it impossible to write proper rewrite rules. if a request wants /++resource++/image.gif the webserver couldn't possibly know if image.gif is found in app/Zope-3.3.0/lib/python/zope/app/i18n/browser/ or in app/Zope-3.3.0/lib/python/zope/app/rotterdam/ or in various other directories that carry images. It seems that your objective is to not have Zope serve images. correct, I would like to delegate this to the front-end webserver. I think the easiest way to do that is to use a cache that has a very long cache-timeout for images. I've found Varnish to be very flexible and useable. thanks for the pointer, looks promising. The way to figure out where an image is located and then returning it is called traversal and Zope already does that, and you are unlikely to actually be able to make it signficantly faster that Zope already does. ;) fair enough :-) anyway, I still would argument that it is suboptimal to generate different URLs for the same static object as in img tal:attributes=src context/++resource++zope3logo.gif / both for the the proxy, and the caching the browser handles itself. or am I missing something here? Cheers, Sascha -- Lalisio GmbH www.lalisio.com Puschkinstraße 1 fon +49-(0)361/541 43 80 99084 Erfurt fax +49-(0)361/541 43 79 [EMAIL PROTECTED] ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] prettier edit widgets..
Hi Folks, I need prettier edit widgets than the stock Rotterdam/Basic skin versions. Is there a collection of such widgets that maybe use dojo/mochikit/scriptaculous. Or is it reasonable to simple re-style (w/css) the stock widgets, or programmatically (in editform) manipulate parameters, to get reasonable edit widgets. -- Thanks, Roy Mathew. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: prettier edit widgets..
Roy Mathew wrote: I need prettier edit widgets than the stock Rotterdam/Basic skin versions. The skins have little to do with it, except for the CSS styles that apply to pretty much all HTML. Is there a collection of such widgets that maybe use dojo/mochikit/scriptaculous. Or is it reasonable to simple re-style (w/css) the stock widgets, or programmatically (in editform) manipulate parameters, to get reasonable edit widgets. There are several options. First of all, you can style the existing widgets with CSS. If you want to change their behaviour (JavaScript, etc.), then you're probably best of writing your own widgets. Often you can simply subclass the original ones in zope.app.form.browser and override the __call__ method (which returns the widget's HTML). To use your custom widgets in your forms, you have two options: a) explicitly refer to them in form_fields: class MyForm(EditForm): form_fields = Fields(IMySchema) form_fields['afield'].custom_widget = MyCoolWidget b) register them for the fields you use, so they get picked up automatically whenever a TextLine, Int, Choice, etc. field is used in a form (even in Zope 3 itself). See zope.app.form.browser/configure.zcml for exmaples of how the standard Zope 3 widgets are registered. By the way, instead of using IBrowserRequest, you probably may want to specify the interface of your custom layer or skin the 'type' argument to view /. Or you have to use overrides.zcml, otherwise you'll get conflicts (obviously). HTH -- http://worldcookery.com -- Professional Zope documentation and training 2nd edition of Web Component Development with Zope 3 is now shipping! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: prettier edit widgets..
Roy Mathew wrote: Hi Folks, I need prettier edit widgets than the stock Rotterdam/Basic skin versions. Is there a collection of such widgets that maybe use dojo/mochikit/scriptaculous. Or is it reasonable to simple re-style (w/css) the stock widgets, or programmatically (in editform) manipulate parameters, to get reasonable edit widgets. Don't know if you consider Plone's standard widgets pretty, but the plone.app.form package[1] makes formlib widgets fit into Plone's standard layout, which may be similar to what you want. That's not using JS libraries though; in general, it's a bad idea to *depend* on such JS libraries; rather they should be additional benefits for those with browsers that support it. Incidentally, if you're feeling adventurous, you may want to check out KSS, which is the JS meta-framework Plone 3 will use (meta, because it can use prototype or mochikit or whatever; it's just a way of binding JS behaviour to the page using a CSS-like syntax, and writing server side logic in python). KSS has a plain-JS bit (called kukit) which does the binding and command handling and a plain-Zope 3 bit (for server side actions and resource management). Plone has its own bindings and Plone-specific actions of course, but there's nothing Plone- or Zope2-specific about the framework or common actions. Cheers, Martin [1] http://svn.plone.org/svn/plone/plone.app.form/trunk/plone/app/form/ ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Blog for Zope3
Hello, is there a blog package for Zope3? It doesn't need to mature just usable would be ok... Thanks, Florian ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: prettier edit widgets..
Philipp, Thanks for taking the time to respond - your answer helps me at a couple of levels: a) I know now how to do it. b) It suggests that it is good practice to use the builtin widgets for your own UI. Roy. Philipp von Weitershausen writes: Roy Mathew wrote: I need prettier edit widgets than the stock Rotterdam/Basic skin versions. The skins have little to do with it, except for the CSS styles that apply to pretty much all HTML. Is there a collection of such widgets that maybe use dojo/mochikit/scriptaculous. Or is it reasonable to simple re-style (w/css) the stock widgets, or programmatically (in editform) manipulate parameters, to get reasonable edit widgets. There are several options. First of all, you can style the existing widgets with CSS. If you want to change their behaviour (JavaScript, etc.), then you're probably best of writing your own widgets. Often you can simply subclass the original ones in zope.app.form.browser and override the __call__ method (which returns the widget's HTML). To use your custom widgets in your forms, you have two options: a) explicitly refer to them in form_fields: class MyForm(EditForm): form_fields = Fields(IMySchema) form_fields['afield'].custom_widget = MyCoolWidget b) register them for the fields you use, so they get picked up automatically whenever a TextLine, Int, Choice, etc. field is used in a form (even in Zope 3 itself). See zope.app.form.browser/configure.zcml for exmaples of how the standard Zope 3 widgets are registered. By the way, instead of using IBrowserRequest, you probably may want to specify the interface of your custom layer or skin the 'type' argument to view /. Or you have to use overrides.zcml, otherwise you'll get conflicts (obviously). HTH -- http://worldcookery.com -- Professional Zope documentation and training 2nd edition of Web Component Development with Zope 3 is now shipping! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Blog for Zope3
On Sunday 14 January 2007 13:48, Florian Lindner wrote: is there a blog package for Zope3? It doesn't need to mature just usable would be ok... There is http://codespeak.net/svn/z3/zblog, but I am not sure how good it is. 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
Re: [Zope3-Users] Zope 3.3.1
On Friday 12 January 2007 17:00, Robert Hicks wrote: I read on the wiki that 3.3.1 is Delayed for a while. Can anyone in the know define a while? I know the Python 2.4.4 fix is in there and I really would like to get it on my OSX box so I can play with it (evaluation for work). Zope 3.3.1 was released today. Unfortunately I cannot access wiki.zope.org right now to get you the release link. However, you can also always use the trunk to do an evaluation. (Most of us work with the trunk.) 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
Re: [Zope3-Users] Blog for Zope3
I'm currently playing with zblog. It's very basic, you can just add blog entries as text and display them. But it's a good starting point and I'm currently adding category management. Christophe Florian Lindner a écrit : Hello, is there a blog package for Zope3? It doesn't need to mature just usable would be ok... Thanks, Florian ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
