One of the reasons (the only reason?) I don't do something like this with Navigator is that there are at least a few people that clone the Navigator repo directly. I'd rather have everyone (Except Brian!) using the same exact form of Navigator rather than some using the version with script-only stacks and the rest using binary.
But I agree that Navigator having a crap-ton of script-only behaviors is cumbersome in the IDE if you're showing IDE stacks. gc On Thu, Mar 14, 2019 at 5:32 PM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 3/14/19 9:53 AM, Brian Milby via use-livecode wrote: > > > I noticed that the plugin was a single file and wondered how you did > that. When I convert Navigator, I create a single sub stack and map each > behavior to a new button with the same name as the script only stack name. > I’ll need to read your script a little more closely to see what is > happening. > > Yeah... if only we could treat script-only stacks as substacks, eh? > > -- > 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