Hmmm… Isn’t Levure almost completely based on script only stacks? Bob S
> On Dec 22, 2020, at 4:09 PM, J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Unless you specifically need text files for git or some other reason, you > don't really need script-only stacks. Put the script in a button and then put > it in use or use it as a backscript. It will be encrypted when the stack is. > Another advantage to keeping scripts in the stack is that they work with > remote debugging, unlike text based scripts. > > Brian Milby's script tracker is also a way to get the best of both worlds. It > saves scripts out to text files for uploading to github while keeping the > advantages of stack-based scripts. > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On December 22, 2020 3:24:11 PM Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> What he said. The promise of creating standalones and encrypted stacks >> containing code sounds promising, but there are caveats. It begs the >> question, how do we encrypt script only stacks or libraries? I don’t use >> encrypted stacks because my code is for internal use only, but if I ever >> went commercial, this would be something I would need. >> >> Bob S >> >> >>> On Dec 13, 2020, at 4:02 PM, Richard Gaskin via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> Ron Noice wrote: >>> >>> ? My program (built with LC 9.6.1 Indy Windows) contains a large number >>> > of references to fields by variables. >>> ... >>> > only when I encrypt it does it fight back. Here's a simplified example >>> > of what I'm doing: >>> > >>> > create group "grpTree" >>> > ... >>> > copy fld "baseBox" to grp "grpTree" >>> >>> ^ that's your issue. >>> >>> Copying objects is disallowed in an encrypted stack, since of course once >>> an object is copied it could be pasted into an unencrypted stack, and thus >>> expose the source. >>> >>> You might consider moving the code from the encrypted stack to an encrypted >>> behavior object, leaving the stack where copying must be done unencrypted. >>> >>> But if these objects are being copied only by script for the purpose of >>> automatically building out a UI, without a need to alter the user's >>> clipboard, you might consider using the clone command instead. >>> >>> -- >>> Richard Gaskin >>> Fourth World Systems >>> Software Design and Development for the Desktop, Mobile, and the Web >> >> _______________________________________________ >> 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 > > > > > _______________________________________________ > 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 _______________________________________________ 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
