Re: Tool for mapping and analysing handler dependencies
oooh, shiny FORKED! On Thu, Mar 16, 2023 at 5:24 PM matthias rebbe via use-livecode < use-livecode@lists.runrev.com> wrote: > Wow, thanks for this. > > Ran it on several projects. Interesting to see the dependencies. > > Matthias > > > > Am 16.03.2023 um 22:08 schrieb Andreas Bergendal via use-livecode < > use-livecode@lists.runrev.com>: > > > > Hi guys, > > > > I’ve made a stack/tool that goes through any stacks you throw at it and > maps their script handlers, then checks which handlers are calling which, > displaying handler chains and interdependencies etc. > > > > https://github.com/wheninspace/WIS_ScriptDepedencies > > > > The purpose is to find out which are you most ”popular” handlers and how > many other handlers are, directly or indirectly, dependent on them. Or in > other words: How many handlers might malfunction if you alter or remove > those crucial ones… > > > > To get a relevant analysis, include all stacks belonging to one project, > i.e. the main stack(s) and any library stacks and behaviour stacks > connected to them. > > > > The result is presented in various views in the stack, but I’ve also > included a rudimentary report export (to plain text file), which could be > further developed if relevant. > > > > I’m not sure how useful such a tool is to most of you, but I sure found > it fun and interesting to run it on various LiveCode projects and get > insights into the interdependencies and complexity of all the scripts. So I > thought I'd share it. :) > > > > I welcome any feedback! > > > > /Andreas > > ___ > > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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
Re: Tool for mapping and analysing handler dependencies
Wow, thanks for this. Ran it on several projects. Interesting to see the dependencies. Matthias > Am 16.03.2023 um 22:08 schrieb Andreas Bergendal via use-livecode > : > > Hi guys, > > I’ve made a stack/tool that goes through any stacks you throw at it and maps > their script handlers, then checks which handlers are calling which, > displaying handler chains and interdependencies etc. > > https://github.com/wheninspace/WIS_ScriptDepedencies > > The purpose is to find out which are you most ”popular” handlers and how many > other handlers are, directly or indirectly, dependent on them. Or in other > words: How many handlers might malfunction if you alter or remove those > crucial ones… > > To get a relevant analysis, include all stacks belonging to one project, i.e. > the main stack(s) and any library stacks and behaviour stacks connected to > them. > > The result is presented in various views in the stack, but I’ve also included > a rudimentary report export (to plain text file), which could be further > developed if relevant. > > I’m not sure how useful such a tool is to most of you, but I sure found it > fun and interesting to run it on various LiveCode projects and get insights > into the interdependencies and complexity of all the scripts. So I thought > I'd share it. :) > > I welcome any feedback! > > /Andreas > ___ > 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
Tool for mapping and analysing handler dependencies
Hi guys, I’ve made a stack/tool that goes through any stacks you throw at it and maps their script handlers, then checks which handlers are calling which, displaying handler chains and interdependencies etc. https://github.com/wheninspace/WIS_ScriptDepedencies The purpose is to find out which are you most ”popular” handlers and how many other handlers are, directly or indirectly, dependent on them. Or in other words: How many handlers might malfunction if you alter or remove those crucial ones… To get a relevant analysis, include all stacks belonging to one project, i.e. the main stack(s) and any library stacks and behaviour stacks connected to them. The result is presented in various views in the stack, but I’ve also included a rudimentary report export (to plain text file), which could be further developed if relevant. I’m not sure how useful such a tool is to most of you, but I sure found it fun and interesting to run it on various LiveCode projects and get insights into the interdependencies and complexity of all the scripts. So I thought I'd share it. :) I welcome any feedback! /Andreas ___ 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
