[Zope3-Users] z3c.form query widget
I've searched and not found a z3c.form-widget that can support a source that supports text queries (a la Plone's uberselectionwidget). The spec is not defined in Zope, but it's basically: class IQuerySource(ISource): def search(query_string): Return values that matches query. In the USW, the widget renders an input field and if applicable, a list of results from which you can make your choice. I think this widget should live in z3c.widget. Hints/suggestions? \malthe ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Attn Jim Fulton: Buildout builder
Martijn Faassen wrote: Note that Malthe (cc-ed too) is interested in: Architecting and implementing a Zope component that can extend a running application in a way that plays nicely with both the component architecture and setuptools. The extensions would typically be pulled in over the network as eggs. which is a project he proposed as a possible summer of code project. I see a lot of possible connections between the project you mention and this project. I think much of this project could be architected as a generic Python library and/or Zope 3 component (that offers some abstractions to describe, and possibly also run, a buildout), and then you could do the UI in Grok or whatever. When I first read about the buildout builder I had associations to the plone.devel debate on genesis, a code-generation tool for Plone (not sure about the scope of it). If people are supposed to read the output of this tool, then I don't see the point of using a tool to generate it. Assuming the output is actually readable, why was it then necessary to generate it? It can be a daunting task to put together a buildout from scratch that builds, say, a full Plone site with extension points like the canonical Plone buildout configuration does. But why would you? I'd like to question the objective of the buildout builder project. I remember reading something like I'd like to cache my site using varnish and the builder could then make that happen. But you could also just google buildout varnish and get: http://pypi.python.org/pypi/plone.recipe.varnish and off you are. \malthe ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Attn Jim Fulton: Buildout builder
Derek Richardson wrote: A third category of user (in addition to buildout-mavens and installer-people), perhaps specific to Plone, are systems integrators. These folks may have considerable knowledge of Plone and technical skills in some areas, but may not be buildout-mavens or even know (or want to know) Python. They may be text-averse, not wanting to manipulate a buildout.cfg. They may not want to root through the Python code of less-documented recipes to figure out configuration options. They may simply want a less-steep learning curve. They may have complex needs that they understand from a system-administration viewpoint, but may not want to learn Plone behind-the-scenes, which includes buildout. I am not defending these people's choices to not learn buildout (or Python). The simple fact is that these people exist in sizable numbers in the Plone community and their needs are important. We heard from them loudly after the 3.0 release and at the PSPS. We need to address their concerns. That was a lot of may's. That is the value in general. I, personally, have a more specific itch to scratch. I'm interested in what I call Plone-on-Demand, the ability to host Plone sites as a service. I want people who don't know Python or Zope or Plone, who simply want a website, to be able to go to a web page, fill in some options about what they would like in their website (skin, functionality, etc), and, 20 minutes later, get an email saying 'Here's the url of your new website - enjoy!'. This competes with similar services built on PHP at providers like godaddy. I want this for my university, which has a need for a web hosting solution and I think Python/Zope/Plone is appropriate. The buildout builder is a step in this direction. If I write the infrastructure for Plone-on-Demand, I intend to open-source it. It could be used by other service providers who currently shy away from Zope and Plone. It can also be used to provide demo sites for evaluation, perhaps deployed on a public grid. You're not alone here; there are a lot of people in the community that are trying to provide Plone on-demand much like you describe (and maybe profit!), but so far I haven't seen any services being launched. The technical aspect can be overcome. I think the primary difficulty is upgrades, extensions and migrations. Some are trying to tackle this by supporting a software bundle and taking the steps to properly maintain this bundle. \malthe ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: Blog naming proposals
how about z3c.weblog; depends how general it is of course. ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
