Hi David, On 11/5/05, David Bernard <[EMAIL PROTECTED]> wrote: > About your proposal to one package per widget, there is some drawback > (I've not yet found an absolute solution) : > * to many files if there is one package per widget or compount widget > (in by basic current dev, there is 4 basic widgets and 3 compounds), > * often widgets share some resources (js, css, png,...) => duplication > > So I think one package per set of widgets (1-n) is better.
As with the rest of quickstart, I'd start it off simple with the assumption that people are not going to be writing *tons* of widgets for their apps. They can always reorganize as makes sense for their application once it outgrows a single module. > An other problem is that statics resources are under x/static > directory, so resources must be : > * copied under static directory > * or declared into configuration (cherrypy and may be httpd frontend) > None is "nice", any suggestions ? I have a solution for this that I haven't checked in yet. turbogears.forms.widgets has a function to register a directory of static resources for widgets in a package. So, for example, you can point to /tg_widgets/turbogears.forms.widgets/something.css for a CSS file that is used by a widget. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
