Just putting my little pinky into the widget world.

Frequently we use small groups to instantiate "objects" which are made of of 
several controls grouped together. These are then replicated across some card 
for whatever purpose. I think that is the underlying model for the DataGrid.

Would such a small group be better created as a widget?

Put another way, can we, in generalized "framework speak" define what uses 
cases best call for a widget and when they are best *not* used?

In the case of any given widget, if it were is duplicated 50 times. Is all that 
code added X 50  added to the total overhead/size of the app? or is a "class" 
whose code reused and only the content the presentation layer is adding the 
file size?




_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to