If more and more widgets are added, there is a potential version problem with referenced CSS/js resources they may need to share. For example, the Flot widget needs the google canvas for IE (http:// excanvas.sourceforge.net/). Actually this javascript is inside the Flot widget code and it shouldn't be there.
Another problem is, if the same widget is used twice in the same page, how do I avoid include the CSS/js resources twice? Is is a problem if the widget needs a "one time per page" initialization. In both case, a API to manage shared resource would be useful. Maybe, Lift has an elegant solution I'm not aware of and only a little documentation will suffice. Francois On Jul 12, 2:58 am, "marius d." <[email protected]> wrote: > Well widgets don't have a whole lot of commonalities besides the init > () method. Regarding destroy() that would probably be helpful for > widgets that are communicating remotely with other services. The rest > of the widget functions are mostly very specific helper functions that > renders markup, JS script tags etc, and work with very specific data > models. > > Br's > Marius > > On Jul 12, 3:03 am, Timothy Perrett <[email protected]> wrote: > > > > > > I'm not sure, depends I guess. > > > Just a simple onLoad/onUnload callback could be enough... > > > (The unload is to make sure not to leak mem if you're just reloading the > > > webapp without restarting the server) > > > That was my thinking - right now the pattern appears to be "def init" > > for booting the widget, so perhaps, init and destroy methods would be > > good appropriate. Like I said, just something to make this stuff a > > known, typeable quantity would be good. > > > > Java Specialist > > > Scala Loudmouth > > > Lift Committer > > > What happened to your rouge architect signature?! > > > Cheers, Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
