I do it both ways, the problem is that behavior scripts created for maintaining a stack (version control) are inconvenient in the IDE. I've thought about suggesting a multiple step scriptify for IDE tools. The first step would be to create a card to house all behavior buttons. The first round would scriptify everything to buttons on that card. The second round would generate the script only stacks. Prior to distribution, the second round would be reversed to have a cleaner namespace inside the IDE.
I've taken a different approach for my own work (Script Tracker). I just have my tool export all of the scripts to files. I can version control the files and edit them outside of the IDE. My tool keeps them in sync. Then the distributed tool doesn't have any external file requirements. I still need to go back and move my SvgIconTool into this model (and will before the next update). On Fri, Aug 10, 2018 at 7:36 PM, Geoff Canyon via use-livecode < use-livecode@lists.runrev.com> wrote: > Are you working with "LiveCode UI elements appear in lists of stacks" > enabled? I specifically named all the script behaviors for Navigator > starting with "rev" and they don't show up in the Project Browser for me. > Not that I had looked before this, I use Navigator for everything. ;-) > > On Sat, Aug 4, 2018 at 11:42 AM Mark Wieder via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > On 08/04/2018 11:23 AM, Mark Waddingham via use-livecode wrote: > > > > > However, over time I'd suggest we look at it sitting in a > > > mobile-permissions script library. Given the dynamic nature of handler > > > dispatch in LC, there's all kinds of things we can do to make it really > > > easy to adapt for particular projects. > > > > Although I do have to bemoan the proliferation of script stacks in the > > Project Browser list. This especially became onerous when the Navigator > > plugin started using script-only stacks. It's a pain having to scroll > > through all those stacks that I'm never going to edit, and it's a pain > > having to remove the plugin each time a new build comes out so that I > > don't have to scroll through them just to work on system stacks. > > > > -- > > Mark Wieder > > ahsoftw...@gmail.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 > > > _______________________________________________ > 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
