On 11/27/05, Jason Chu <[EMAIL PROTECTED]> wrote: > If you look at a newly quickstarted project, you'll see lines that refer to > tg_css, tg_js_head, etc. You need all of those lines to have the css and > javascript added.
Yes. This is the part that I'm thinking will move to sitetemplate so that people will not need to change master.kid files at all (and besides, you really only want the javascript and CSS to appear once per page anyhow... putting these in sitetemplate just makes more sense.) > Also, you have to display your calendar widget within a form. I think this > part is a little broken w.r.t. widgets and forms right now, but, if you put > your widget in the TableForm or something, turbogears.controller will pick > it up and pull out the javascript and css and send it to the template. You don't actually have to *display* the calendar within a form. The Form objects handle the aggregation of CSS and JS plus the input/output conversion of the data. So, you can create a form and reference it, but still pass the widget through for direct rendering independent of a form. It's an interesting point, though. It may be possible, with a little API smoothing, to make *all widgets* usable in places where you'd currently have to use a form. If that sounds good to people, it's worth opening a ticket on... opinions? Kevin
