Thanks guys - all very interesting.
Had an offline talk with marius and it seems that there was an effort
to standardize the api from the outset which subsequently didnt work
out...
Im happy to leave this for now as im not sure there is any tangible
benefit.
Cheers, Tim
On Jul 12, 4:23 pm,
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
Any technical feedback Viktor? Suggestions for possible ways to
enforce a structure / life-cycle?
Cheers, Tim
I like it
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send
On Sat, Jul 11, 2009 at 10:15 PM, Timothy Perrett
timo...@getintheloop.euwrote:
Any technical feedback Viktor? Suggestions for possible ways to
enforce a structure / life-cycle?
I'm not sure, depends I guess.
Just a simple onLoad/onUnload callback could be enough...
(The unload is to make
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,
