> > You're perfectly "on the rails" with that approach :) Even more, if the > widget is of enough common-use (like the inexisting "star-rater" which > was discussed a few days ago ;)) you can pack it along with it's > related javascript, css, valiators, etc... into an egg and easily reuse > it in any TG app.
I'll have to look into that. An example of the smart way to package the js and css up with the widget would be a great wiki addition. How in brief do you do that, link the js source file and css from the widget directly? Would it be smart to have the widget use a default css that can just be overridden in a contructor paramater or something? > > BTW, widgets have been refactored out from TG into TGWidgets > (http://tgwidgets.toscat.net) and will not ship with FirstClass (TG > 1.1) anymore. This means that a widget written for TGWidgets could be > reused in *any* WSGI compliant python web-app :) That's awesome. And also why I'm liking gears even more by the day. =) Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
