On 12/4/05, aw <[EMAIL PROTECTED]> wrote: > I saw the widgets stuff. It is my understanding that widgets are items > to be placed on a form. Would a series of forms like a module or like > Catwalk be considered a widget?
Widgets no longer need to be on a form. They're basically packaged bits of HTML/CSS/JavaScript with some input/output behavior. They could conceivably be as large or as small as you like. Catwalk is more like an app than a widget. There are some technical issues (largely addressed in the next CherryPy release, 2.2) that make it difficult to easily "mount" as many apps as you want in different parts of your URL hierarchy. (Catwalk is actually an interesting beast as well, because it's part of the Toolbox, which will also accept new tools via plugins) > It looks like setup tools will do the downloading as necessary. I know > that TG is all about not re-inventing the wheel. But wouldn't there > need to be a set naming convention so the functions, tables, and static > files do not overwrite each other? Not necessarily programming but > just documentation so people don't step on each other. You just use the standard Python mechanism to get around naming collisions: packages. In Javaland, it's well-defined that everyone puts their code in a hierarchically named unique package (com.mycompany.myproject.mypackage). Python is not quite that structured, but you can certainly eliminate name collisions by choosing good package names and being conservative about top level package names. (Also, the .egg packaging format will ensure that you don't get files overwriting each other because the packages all have their own directories... with eggs, it's not just a big blob of packages in site-packages.) Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
