On Tue, Apr 5, 2016 at 10:39 AM, Richard Gaskin <ambassa...@fourthworld.com> wrote:
> > But traditional custom controls have a place too, and the LiveCode Script > they rely continues to be enhanced even as LCB is expanded along with it. > > The additional object overhead of custom controls isn't that much higher > than Widgets, and with behaviors can be close to zero depending on the > complexity of the control. > > With the group message, behaviors, before and after handlers, getProp and > setProp, and other such goodies, I can't think of a project I've worked on > in recent years that hasn't made extensive use of custom controls. > > In fact, many that I need are one-offs needed only for a specific > project. They're easy enough to write on LC Script that it takes almost no > time at all, and keeps the code and property management well centralized > for easy development and maintenance. > Richard, I imagine the problem Paul is trying to solve is that of keeping a custom control up to date. It isn't about how easy the custom control is to create, it's about how easy it is to update the control across an entire project as the control evolves. -- Trevor DeVore ScreenSteps www.screensteps.com - www.clarify-it.com _______________________________________________ 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
