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 <timo...@getintheloop.eu> 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 liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
