Script Only stacks make versioning and multiuser development environments possible, at least from the coding aspect of things. They cannot be password protected however, nor can they have properties, so even a faceless application which needed to avail these features would still need a UI stack. Also, objects whose code is unique and never changes would not benefit from a versioning system or as a behavior. It's probably simpler just to code the object. My 2¢
Bob S > On Feb 20, 2018, at 15:15 , Graham Samuel via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I’m following the Levure discussion and of course Trevor's pronouncements > with great interest. One thing strikes me - is there really a universally > understood meaning to the term “UI stack”? I do understand the concept of > separating the UI from the logic of an app, but any UI must contain **some** > logic, mustn’t it? In the LC world, by ‘logic’ of course I really mean code. > What level of coding is permissible to allow in a UI stack, do people think? > I have a feeling that some folks’ idea of this is going to be very different > from some others’. Perhaps there is an orthodoxy about this, but I am not > familiar with it. > > Graham _______________________________________________ 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
