RE: Writing a web application - how to make twisted/nevow "look good"
Hi, I think developing some sort of widget library would be useful to the nevow community. I have done a little tinkering with nevow UI widgets as well. Mostly I'm deconstructing some of the ui elements in plone2.0 and trying to convert them to nevow. I've gotten their action-tabs, tables and portal boxes basically working. Anyhow I'd be interesting in some sort of project like this. The question is how should this be done? Any sort of reasonably complex web ui is going to have elements of nevow + xhtml+ js + css. The js and css may also be dynamic. How would be create a catalog/library to hold these ui widgets? Would it be a web demo sort of like pastebin where you can see a widget, and then cut-n-paste the code for the nevow/css/js/xhtml? Or would it be a more formalized library that you would download. I like the idea of a web-based catalog, since you could see how each of the widgets looks. Anyhow, I like the idea of some sort of widget library or catalog. --Joel
On Tue, 2004-02-10 at 18:36, Joel Boehland wrote:
Anyhow, I like the idea of some sort of widget library or catalog.
I'm all for it; the trick is making them general-purpose enough that people can still use them, but not making them too overbroad (so that they're tough to figure out or too clunky to implement). How much have you done already? I've been working on a couple nevow widgets of my own, but they've been fairly specific to my apps; I'd be willing to help a little in working out details of some more general-purpose interface elements. Most importantly, have you put your code up anywhere yet? :) -- Alex Levy WWW: http://mesozoic.geecs.org "Never let your sense of morals prevent you from doing what is right." -- Salvor Hardin, Isaac Asimov's _Foundation_
On Wed, 2004-02-11 at 03:49, Alex Levy wrote:
On Tue, 2004-02-10 at 18:36, Joel Boehland wrote:
Anyhow, I like the idea of some sort of widget library or catalog.
I'm all for it;
Me too! The idea of widgets/components is something I've had in the back of my mind since I discovered Nevow. Components are not as easy to do with nevow.renderer as they should be but that's an implementation detail and can be fixed. In fact, the experimental rend module (in the Nevow tracker) already helps.
the trick is making them general-purpose enough that people can still use them, but not making them too overbroad (so that they're tough to figure out or too clunky to implement).
Agreed. Other than the API itself, the most obvious thing is to make sure there is a default stylesheet with the widget but that it can be replaced by the application.
Most importantly, have you put your code up anywhere yet? :)
For now, why not put the code in the Nevow wiki, http://divmod.org/users/slyphon.twistd/nevow/moin.cgi/ , and use a category to group them. Cheers, Matt -- Matt Goodall, Pollenation Internet Ltd w: http://www.pollenation.net e: matt@pollenation.net Any views expressed are my own and do not necessarily reflect the views of my employer.
participants (3)
-
Alex Levy -
Joel Boehland -
Matt Goodall