Re: Your scripts as a flowchart
Latest WIS_ScriptDependencies update: 1.1.6 (12 Dec 2023) - Enhancement: If the Kroki service is down, so no png/svg can be produced, a dialog is presented giving the choice to render the flowchart as html instead - Enhancement: Improved design of the help section and the flowchart settings pane - Enhancement: Mermaid version can now be modified (affects html rendering only). This is not something you’d normally need to do, but it has turned out that the latest versions of Mermaid implement some kind of hard limit on the number of edges, preventing large flowcharts from rendering. So for now, Mermaid v10.5.1 is default (no edge limit), but can be changed to a later version by advanced users. - Fixed bug: Some actions in the mainstack triggered flowchart updates even if the flowchart substack was closed - Other minor fixes Download here: https://github.com/wheninspace/WIS_ScriptDependencies/releases/latest ___ 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: Your scripts as a flowchart
My apologies, Andreas, I forget about Dark Mode being a bit finicky on my daily driver. Purely a personal preference which I've resolved, but I dropped the snapshots in the forum if you're still interested. Please disregard. Otherwise I appreciate the quick response. I'm back on track, and will drop more on the forum if I find anything :-) Thank you, Derek Bump On 12/3/23 13:29, Andreas Bergendal wrote: 3. Hmm, I don’t usually use any gray texts. All texts are black, except for a few big buttons that have ”midnight blue” text, which is also the colour of most of the icons. Is something happening to the UI on Linux? It would be interesting to see a screenshot of how it looks for you. Here’s a screenshot of part of the UI, posted in the LC forum, that shows how it looks on Mac and Windows: https://forums.livecode.com/viewtopic.php?f=9=37644=75 Best, Andreas 3 dec. 2023 kl. 19:00 skrev Derek Bump via use-livecode: Thank you, Andreas, this is very cool and quite helpful! Some feedback to pass along for consideration: 1. I keep getting an Error 400 when creating a flowchart, and it seems to have something to do with the "Group per handler host" checkbox. If you toggle it in the right order, the chart will generate without an error. 2. Clicking any of the buttons to save files is not resulting in anything appearing on my Desktop. (Mint 21.2) 3. The teal backgrounds and gray text throughout the UI blends together and disappears when I look at it. I hope this is helpful, Derek Bump On 11/30/23 14:45, Andreas Bergendal via use-livecode wrote: Hi all, Finally I can answer Yes to the question on exporting script flowcharts! New version of WIS_ScriptDependencies available: v1.1.5 (30 Nov 2023) /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
Re: Your scripts as a flowchart
Thanks for the feedback, Derek! 1. I get an Error 400 when trying for a flowchart of a monster stack with 180+ handlers with many interdependencies. This seems to be due to exceeding the upper limit of what the Mermaid/Kroki services can handle in therms of ”edges”. The graph is simply too complex. Try excluding substacks, or excluding handlers by adding them to the handler exclusion filter field, to reduce ”uninteresting” complexity. (I tend to exclude mouse*, and commands/functions that are called many times put only do simple things like adding quotes, or utf conversion or something.) The "Group per handler host” feature adds complexity to the graph, so using that could also tip it over the error threshold. Unfortunately, the error message passed back from Mermaid/Kroki is not very enlightening. 2. I realise that I have not put in any error catching for the case where the user has not yet chosen a save file destination. Try opening the flowchart settings pane (which should already set a default save path if empty) and click the folder icon to make an active choice. If it still doesn’t work for you then it might be a Linux issue, which unfortunately I’m unable to test. 3. Hmm, I don’t usually use any gray texts. All texts are black, except for a few big buttons that have ”midnight blue” text, which is also the colour of most of the icons. Is something happening to the UI on Linux? It would be interesting to see a screenshot of how it looks for you. Here’s a screenshot of part of the UI, posted in the LC forum, that shows how it looks on Mac and Windows: https://forums.livecode.com/viewtopic.php?f=9=37644=75 Best, Andreas > 3 dec. 2023 kl. 19:00 skrev Derek Bump via use-livecode > : > > Thank you, Andreas, this is very cool and quite helpful! > > > Some feedback to pass along for consideration: > > 1. I keep getting an Error 400 when creating a flowchart, and it seems to > have something to do with the "Group per handler host" checkbox. If you > toggle it in the right order, the chart will generate without an error. > > 2. Clicking any of the buttons to save files is not resulting in anything > appearing on my Desktop. (Mint 21.2) > > 3. The teal backgrounds and gray text throughout the UI blends together and > disappears when I look at it. > > > I hope this is helpful, > > Derek Bump > > > On 11/30/23 14:45, Andreas Bergendal via use-livecode wrote: >> Hi all, >> >> Finally I can answer Yes to the question on exporting script flowcharts! >> New version of WIS_ScriptDependencies available: >> >> v1.1.5 (30 Nov 2023) >> >> /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
Re: Your scripts as a flowchart
Thank you, Andreas, this is very cool and quite helpful! Some feedback to pass along for consideration: 1. I keep getting an Error 400 when creating a flowchart, and it seems to have something to do with the "Group per handler host" checkbox. If you toggle it in the right order, the chart will generate without an error. 2. Clicking any of the buttons to save files is not resulting in anything appearing on my Desktop. (Mint 21.2) 3. The teal backgrounds and gray text throughout the UI blends together and disappears when I look at it. I hope this is helpful, Derek Bump On 11/30/23 14:45, Andreas Bergendal via use-livecode wrote: Hi all, Finally I can answer Yes to the question on exporting script flowcharts! New version of WIS_ScriptDependencies available: v1.1.5 (30 Nov 2023) /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
Re: Your scripts as a flowchart
Hi all, Finally I can answer Yes to the question on exporting script flowcharts! New version of WIS_ScriptDependencies available: v1.1.5 (30 Nov 2023) - Enhancement: Flowcharts can now be produced and exported as PNG or SVG. On Windows and Linux the flowchart is now always displayed in-stack, as a PNG. On all platforms the flowchart can be exported as PNG, SVG and HTML. - Enhancement: Node text size can now be set - Adjustment: Handler type naming convention changed in LC10 (apparently), making ”M” mean ”on” and ”C” mean ”command” (and changing ”PM” into ”CM” for ”private command”). This is now correctly handled when using WIS_ScriptDependencies in either LC9 or LC10. - Fixed bug: Arrow colouring failed for private commands/functions - Fixed bug: The (rarely used) constructions ”before *command name*” and ”after *command name*” now get included in analysis and flowchart (displayed as ”command *command name*”). - Other minor fixes Download link: https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest /Andreas > 18 sep. 2023 kl. 03:38 skrev Geoff Canyon via use-livecode > : > > Is there a way to export the entire flowchart, instead of just the portion > currently displayed? ___ 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: Your scripts as a flowchart
Hi Andreas, quick note - I've not read the full thread - but I have a code graph browser that I have been using for a number of years - it is a big piece of work - so not easy to distribute - and many of the parts should probably be done better / differently. I would Love to make use / integrate that work - rather than see it all stay on my laptop - but either way I'd like to get involved. This is what I have / the current approach: - Script Indexing project - libraries to recursively crawl an object or a stacks script to find handlers, and calls from each type of handler - Experimental caching and database based versions to speed up graph analysis and reporting (currently dropped) - Integration with IDE / Script Editor (using behaviors attached to "Apply" button etc - Projects arranged more or less as Levure projects - SVG graph export with interactive browsing of handlers (using graphviz) - Native graph export creating native Livecode layouts of shapes from Graphviz or Mermai d(experimental) - Filtering, and processing of graphs (experimental) What I'd like to do is: 1. Finish integration with Levure 2. Focus on Mermaid implementation 3. Test and improve the code parsing and graph creation to ensure it works properly with different coding styles Happy to demo / jump on a Zoom call and share ideas / discuss. On Mon, 18 Sept 2023 at 13:11, Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: > Getting a full export is a tricky business, and I’m looking at various > solutions. > > The easiest workaround is to launch the flowchart in a web browser and > print to PDF from there. > On Windows/Linux the flowchart is shown that way anyway, and on Mac you > load it in a web browser by shift-clicking the Create flowchart button. The > obvious downside of printing to pdf is that you get page breaks that split > up the flowchart. > > Another workaround is to paste the Mermaid code into an online editor like > https://mermaid.live and then export to PNG from there. > > What looks more promising for actually solving it in-stack though, is > using the command-line interface (CLI) for Mermaid to generate an > svg/png/pdf file: > https://github.com/mermaid-js/mermaid-cli > > I’ll experiment with that and see what I can come up with. :) > > > As an aside, I don't know whether to be proud or horrified at the map > > Navigator produces… > > Yeah, I know the feeling… :D > > /Andreas > > > > 18 sep. 2023 kl. 03:38 skrev Geoff Canyon via use-livecode < > use-livecode@lists.runrev.com>: > > > > Is there a way to export the entire flowchart, instead of just the > portion > > currently displayed? > > > > As an aside, I don't know whether to be proud or horrified at the map > > Navigator produces... > > > > On Sat, Sep 16, 2023 at 8:04 PM Geoff Canyon wrote: > > > >> Ah, okay, that explains it. In Navigator, *everything* is a script-only > >> stack behavior. In a few of the substacks there are scripts for a few > >> template objects or where script-only-stack behaviors were inconvenient > (I > >> don't remember why, honestly). > >> > >> That has it working, and the resulting diagram is nice. Navigator does a > >> similar survey (without the visualization, that's a neat trick). > >> > >> Navigator reports: > >> > >> 302986 characters in > >> 8092 lines in > >> 112 scripts in > >> 885 objects. > >> > >> ScriptDependencies reports: > >> > >> 341 unique handler names - 407 commands, 124 functions, 1 setProps > >> > >> regards, > >> > >> Geoff > >> > >> On Sat, Sep 16, 2023 at 6:24 PM Andreas Bergendal via use-livecode < > >> use-livecode@lists.runrev.com> wrote: > >> > >>> As long as you include all the script-only stacks in the analysis, they > >>> will be handled. > >>> The tool will not look for behaviors and auto-include them. Every stack > >>> that has relevant code must be included manually in the project pane. > If > >>> you have many SoSs, you can quickly add them all by adding the whole > folder > >>> they are in. > >>> > >>> How many handlers does the analysis find? > >>> > >>> /Andreas > >>> > >>> > 16 sep. 2023 kl. 22:43 skrev Geoff Canyon via use-livecode < > >>> use-livecode@lists.runrev.com>: > > I didn't change anything before generating, and the flow chart is > >>> literally > blank -- unless it: > > 1. scrolls invisibly > 2. keeps returning the project name to the upper left while scrolling > 3. has *at least* 30 screens' worth of blank space at the top? > > On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > That happened to me too with a very long script. To keep everything > in > > view > > there's a lot of white space. Keep scrolling. This happens only if > you > > have > > set it to use unlimited sizing. > > -- > > Jacqueline Landman Gay | jac...@hyperactivesw.com > > HyperActive Software
Re: Your scripts as a flowchart
Getting a full export is a tricky business, and I’m looking at various solutions. The easiest workaround is to launch the flowchart in a web browser and print to PDF from there. On Windows/Linux the flowchart is shown that way anyway, and on Mac you load it in a web browser by shift-clicking the Create flowchart button. The obvious downside of printing to pdf is that you get page breaks that split up the flowchart. Another workaround is to paste the Mermaid code into an online editor like https://mermaid.live and then export to PNG from there. What looks more promising for actually solving it in-stack though, is using the command-line interface (CLI) for Mermaid to generate an svg/png/pdf file: https://github.com/mermaid-js/mermaid-cli I’ll experiment with that and see what I can come up with. :) > As an aside, I don't know whether to be proud or horrified at the map > Navigator produces… Yeah, I know the feeling… :D /Andreas > 18 sep. 2023 kl. 03:38 skrev Geoff Canyon via use-livecode > : > > Is there a way to export the entire flowchart, instead of just the portion > currently displayed? > > As an aside, I don't know whether to be proud or horrified at the map > Navigator produces... > > On Sat, Sep 16, 2023 at 8:04 PM Geoff Canyon wrote: > >> Ah, okay, that explains it. In Navigator, *everything* is a script-only >> stack behavior. In a few of the substacks there are scripts for a few >> template objects or where script-only-stack behaviors were inconvenient (I >> don't remember why, honestly). >> >> That has it working, and the resulting diagram is nice. Navigator does a >> similar survey (without the visualization, that's a neat trick). >> >> Navigator reports: >> >> 302986 characters in >> 8092 lines in >> 112 scripts in >> 885 objects. >> >> ScriptDependencies reports: >> >> 341 unique handler names - 407 commands, 124 functions, 1 setProps >> >> regards, >> >> Geoff >> >> On Sat, Sep 16, 2023 at 6:24 PM Andreas Bergendal via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> As long as you include all the script-only stacks in the analysis, they >>> will be handled. >>> The tool will not look for behaviors and auto-include them. Every stack >>> that has relevant code must be included manually in the project pane. If >>> you have many SoSs, you can quickly add them all by adding the whole folder >>> they are in. >>> >>> How many handlers does the analysis find? >>> >>> /Andreas >>> >>> 16 sep. 2023 kl. 22:43 skrev Geoff Canyon via use-livecode < >>> use-livecode@lists.runrev.com>: I didn't change anything before generating, and the flow chart is >>> literally blank -- unless it: 1. scrolls invisibly 2. keeps returning the project name to the upper left while scrolling 3. has *at least* 30 screens' worth of blank space at the top? On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > That happened to me too with a very long script. To keep everything in > view > there's a lot of white space. Keep scrolling. This happens only if you > have > set it to use unlimited sizing. > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode > wrote: > >> Does it not handle script-only stack behaviors? I get a blank display >>> for >> Navigator (which has no code other than SoS behaviors). >> >> gc >>> >>> >>> ___ >>> 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
Re: Your scripts as a flowchart
Is there a way to export the entire flowchart, instead of just the portion currently displayed? As an aside, I don't know whether to be proud or horrified at the map Navigator produces... On Sat, Sep 16, 2023 at 8:04 PM Geoff Canyon wrote: > Ah, okay, that explains it. In Navigator, *everything* is a script-only > stack behavior. In a few of the substacks there are scripts for a few > template objects or where script-only-stack behaviors were inconvenient (I > don't remember why, honestly). > > That has it working, and the resulting diagram is nice. Navigator does a > similar survey (without the visualization, that's a neat trick). > > Navigator reports: > > 302986 characters in > 8092 lines in > 112 scripts in > 885 objects. > > ScriptDependencies reports: > > 341 unique handler names - 407 commands, 124 functions, 1 setProps > > regards, > > Geoff > > On Sat, Sep 16, 2023 at 6:24 PM Andreas Bergendal via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> As long as you include all the script-only stacks in the analysis, they >> will be handled. >> The tool will not look for behaviors and auto-include them. Every stack >> that has relevant code must be included manually in the project pane. If >> you have many SoSs, you can quickly add them all by adding the whole folder >> they are in. >> >> How many handlers does the analysis find? >> >> /Andreas >> >> >> > 16 sep. 2023 kl. 22:43 skrev Geoff Canyon via use-livecode < >> use-livecode@lists.runrev.com>: >> > >> > I didn't change anything before generating, and the flow chart is >> literally >> > blank -- unless it: >> > >> > 1. scrolls invisibly >> > 2. keeps returning the project name to the upper left while scrolling >> > 3. has *at least* 30 screens' worth of blank space at the top? >> > >> > On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < >> > use-livecode@lists.runrev.com> wrote: >> > >> >> That happened to me too with a very long script. To keep everything in >> >> view >> >> there's a lot of white space. Keep scrolling. This happens only if you >> >> have >> >> set it to use unlimited sizing. >> >> -- >> >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> >> HyperActive Software | http://www.hyperactivesw.com >> >> On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode >> >> wrote: >> >> >> >>> Does it not handle script-only stack behaviors? I get a blank display >> for >> >>> Navigator (which has no code other than SoS behaviors). >> >>> >> >>> gc >> >> >> ___ >> 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
Re: Your scripts as a flowchart
Ah, okay, that explains it. In Navigator, *everything* is a script-only stack behavior. In a few of the substacks there are scripts for a few template objects or where script-only-stack behaviors were inconvenient (I don't remember why, honestly). That has it working, and the resulting diagram is nice. Navigator does a similar survey (without the visualization, that's a neat trick). Navigator reports: 302986 characters in 8092 lines in 112 scripts in 885 objects. ScriptDependencies reports: 341 unique handler names - 407 commands, 124 functions, 1 setProps regards, Geoff On Sat, Sep 16, 2023 at 6:24 PM Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: > As long as you include all the script-only stacks in the analysis, they > will be handled. > The tool will not look for behaviors and auto-include them. Every stack > that has relevant code must be included manually in the project pane. If > you have many SoSs, you can quickly add them all by adding the whole folder > they are in. > > How many handlers does the analysis find? > > /Andreas > > > > 16 sep. 2023 kl. 22:43 skrev Geoff Canyon via use-livecode < > use-livecode@lists.runrev.com>: > > > > I didn't change anything before generating, and the flow chart is > literally > > blank -- unless it: > > > > 1. scrolls invisibly > > 2. keeps returning the project name to the upper left while scrolling > > 3. has *at least* 30 screens' worth of blank space at the top? > > > > On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > >> That happened to me too with a very long script. To keep everything in > >> view > >> there's a lot of white space. Keep scrolling. This happens only if you > >> have > >> set it to use unlimited sizing. > >> -- > >> Jacqueline Landman Gay | jac...@hyperactivesw.com > >> HyperActive Software | http://www.hyperactivesw.com > >> On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode > >> wrote: > >> > >>> Does it not handle script-only stack behaviors? I get a blank display > for > >>> Navigator (which has no code other than SoS behaviors). > >>> > >>> gc > > > ___ > 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
Re: Your scripts as a flowchart
As long as you include all the script-only stacks in the analysis, they will be handled. The tool will not look for behaviors and auto-include them. Every stack that has relevant code must be included manually in the project pane. If you have many SoSs, you can quickly add them all by adding the whole folder they are in. How many handlers does the analysis find? /Andreas > 16 sep. 2023 kl. 22:43 skrev Geoff Canyon via use-livecode > : > > I didn't change anything before generating, and the flow chart is literally > blank -- unless it: > > 1. scrolls invisibly > 2. keeps returning the project name to the upper left while scrolling > 3. has *at least* 30 screens' worth of blank space at the top? > > On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> That happened to me too with a very long script. To keep everything in >> view >> there's a lot of white space. Keep scrolling. This happens only if you >> have >> set it to use unlimited sizing. >> -- >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> HyperActive Software | http://www.hyperactivesw.com >> On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode >> wrote: >> >>> Does it not handle script-only stack behaviors? I get a blank display for >>> Navigator (which has no code other than SoS behaviors). >>> >>> gc ___ 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: Your scripts as a flowchart
I didn't change anything before generating, and the flow chart is literally blank -- unless it: 1. scrolls invisibly 2. keeps returning the project name to the upper left while scrolling 3. has *at least* 30 screens' worth of blank space at the top? On Sat, Sep 16, 2023 at 1:35 PM J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > That happened to me too with a very long script. To keep everything in > view > there's a lot of white space. Keep scrolling. This happens only if you > have > set it to use unlimited sizing. > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode > wrote: > > > Does it not handle script-only stack behaviors? I get a blank display for > > Navigator (which has no code other than SoS behaviors). > > > > gc > > > > On Fri, Sep 15, 2023 at 10:32 AM Andreas Bergendal via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > >> Hi all! > >> > >> Those frequenting the forums may have seen this already, but I thought > I'd > >> share it here too now: > >> > >> If you want to see a graphic map of the inter-relations of all the > >> handlers in the scripts of your LiveCode projects, my tool > >> ScriptDependencies now features an extremely cool flowchart output > (using > >> the Mermaid javascript lib). > >> > >> Here’s an example of how a script flowchart can look: > >> > https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png > >> > >> A few easy steps to test it on your own scripts: > >> > >> 1) Download ScriptDependencies here: > >> https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest > >> > >> 2) Open the stack, click the top left cog wheel and add at least one > stack > >> (that has at least some handlers calling other handlers) to a project. > >> 3) Close the project pane and click "Start mapping and analysis”. > >> 4) Click ”Create flowchart”. Boom! :) > >> > >> On Mac, the browser widget can display the flowchart in-stack, enabling > >> some interactivity (click a node to highlight the arrows to and from > it). > >> On Windows and Linux, where the browser widget has, er... room for > >> improvement…, the flowchart is instead displayed in an external browser > >> window (minus interactivity). > >> > >> My intention with ScriptDependencies is to provide a code analysis and > >> live documentation tool (of some kind) for LiveCode projects. I need it > >> myself for some big LC projects, and thought it might be useful also for > >> other LC devs. > >> > >> The tool has been thoroughly tested by LC veterans like bn (Bernd), > jacque > >> (Jacqueline) and mwieder (Mike), who have all provided invaluable > feedback > >> and improvement suggestions, bringing the tool up to quite a > professional > >> level. > >> > >> I hope you’ll find use for it - or at least enjoy seeing your scripts > >> presented as a bouquet of flowers, a piece of art! :) > >> > >> Any feedback is very welcome! > >> > >> /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 > > > > > ___ > 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
Re: Your scripts as a flowchart
That happened to me too with a very long script. To keep everything in view there's a lot of white space. Keep scrolling. This happens only if you have set it to use unlimited sizing. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On September 16, 2023 11:15:00 AM Geoff Canyon via use-livecode wrote: Does it not handle script-only stack behaviors? I get a blank display for Navigator (which has no code other than SoS behaviors). gc On Fri, Sep 15, 2023 at 10:32 AM Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: Hi all! Those frequenting the forums may have seen this already, but I thought I'd share it here too now: If you want to see a graphic map of the inter-relations of all the handlers in the scripts of your LiveCode projects, my tool ScriptDependencies now features an extremely cool flowchart output (using the Mermaid javascript lib). Here’s an example of how a script flowchart can look: https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png A few easy steps to test it on your own scripts: 1) Download ScriptDependencies here: https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest 2) Open the stack, click the top left cog wheel and add at least one stack (that has at least some handlers calling other handlers) to a project. 3) Close the project pane and click "Start mapping and analysis”. 4) Click ”Create flowchart”. Boom! :) On Mac, the browser widget can display the flowchart in-stack, enabling some interactivity (click a node to highlight the arrows to and from it). On Windows and Linux, where the browser widget has, er... room for improvement…, the flowchart is instead displayed in an external browser window (minus interactivity). My intention with ScriptDependencies is to provide a code analysis and live documentation tool (of some kind) for LiveCode projects. I need it myself for some big LC projects, and thought it might be useful also for other LC devs. The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback and improvement suggestions, bringing the tool up to quite a professional level. I hope you’ll find use for it - or at least enjoy seeing your scripts presented as a bouquet of flowers, a piece of art! :) Any feedback is very welcome! /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 ___ 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: Your scripts as a flowchart
Does it not handle script-only stack behaviors? I get a blank display for Navigator (which has no code other than SoS behaviors). gc On Fri, Sep 15, 2023 at 10:32 AM Andreas Bergendal via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi all! > > Those frequenting the forums may have seen this already, but I thought I'd > share it here too now: > > If you want to see a graphic map of the inter-relations of all the > handlers in the scripts of your LiveCode projects, my tool > ScriptDependencies now features an extremely cool flowchart output (using > the Mermaid javascript lib). > > Here’s an example of how a script flowchart can look: > https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png > > A few easy steps to test it on your own scripts: > > 1) Download ScriptDependencies here: > https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest > > 2) Open the stack, click the top left cog wheel and add at least one stack > (that has at least some handlers calling other handlers) to a project. > 3) Close the project pane and click "Start mapping and analysis”. > 4) Click ”Create flowchart”. Boom! :) > > On Mac, the browser widget can display the flowchart in-stack, enabling > some interactivity (click a node to highlight the arrows to and from it). > On Windows and Linux, where the browser widget has, er... room for > improvement…, the flowchart is instead displayed in an external browser > window (minus interactivity). > > My intention with ScriptDependencies is to provide a code analysis and > live documentation tool (of some kind) for LiveCode projects. I need it > myself for some big LC projects, and thought it might be useful also for > other LC devs. > > The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque > (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback > and improvement suggestions, bringing the tool up to quite a professional > level. > > I hope you’ll find use for it - or at least enjoy seeing your scripts > presented as a bouquet of flowers, a piece of art! :) > > Any feedback is very welcome! > > /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
Re: Your scripts as a flowchart
I was gonna say, I didn’t know he had a brother who was a LiveCoder too! Bob S > On Sep 15, 2023, at 9:12 AM, Andreas Bergendal via use-livecode > wrote: > > Thanks, that’s great to hear, Mark! (And terribly sorry for the credit > misnaming - it’s Mark! I’ll remember that now!) > >> 15 sep. 2023 kl. 17:47 skrev Mark Wieder via use-livecode >> : >> >> Just want to add that Andreas has been super-responsive to suggestions re >> adding features and improving things and this tool has gone from being >> moderately useful to something I can't do without. And is a textbook example >> in how to incorporate a javascript library into LiveCode. >> >> -- >> 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
Re: Your scripts as a flowchart
Thanks, that’s great to hear, Mark! (And terribly sorry for the credit misnaming - it’s Mark! I’ll remember that now!) > 15 sep. 2023 kl. 17:47 skrev Mark Wieder via use-livecode > : > > Just want to add that Andreas has been super-responsive to suggestions re > adding features and improving things and this tool has gone from being > moderately useful to something I can't do without. And is a textbook example > in how to incorporate a javascript library into LiveCode. > > -- > 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
Re: Your scripts as a flowchart
Very cool! Thank you for sharing it, Andreas. Roger > On Sep 15, 2023, at 7:30 AM, Andreas Bergendal via use-livecode > wrote: > > Hi all! > > Those frequenting the forums may have seen this already, but I thought I'd > share it here too now: > > If you want to see a graphic map of the inter-relations of all the handlers > in the scripts of your LiveCode projects, my tool ScriptDependencies now > features an extremely cool flowchart output (using the Mermaid javascript > lib). > > Here’s an example of how a script flowchart can look: > https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png > > A few easy steps to test it on your own scripts: > > 1) Download ScriptDependencies here: > https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest > > 2) Open the stack, click the top left cog wheel and add at least one stack > (that has at least some handlers calling other handlers) to a project. > 3) Close the project pane and click "Start mapping and analysis”. > 4) Click ”Create flowchart”. Boom! :) > > On Mac, the browser widget can display the flowchart in-stack, enabling some > interactivity (click a node to highlight the arrows to and from it). > On Windows and Linux, where the browser widget has, er... room for > improvement…, the flowchart is instead displayed in an external browser > window (minus interactivity). > > My intention with ScriptDependencies is to provide a code analysis and live > documentation tool (of some kind) for LiveCode projects. I need it myself for > some big LC projects, and thought it might be useful also for other LC devs. > > The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque > (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback > and improvement suggestions, bringing the tool up to quite a professional > level. > > I hope you’ll find use for it - or at least enjoy seeing your scripts > presented as a bouquet of flowers, a piece of art! :) > > Any feedback is very welcome! > > /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
Re: Your scripts as a flowchart
Just want to add that Andreas has been super-responsive to suggestions re adding features and improving things and this tool has gone from being moderately useful to something I can't do without. And is a textbook example in how to incorporate a javascript library into LiveCode. -- 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
Re: Your scripts as a flowchart
Very cool. I’ll give it a try. But whereas most people’s code will look like a bowl of spaghetti, mine will probably look like Whoppi Goldberg’s hair. Bob S > On Sep 15, 2023, at 7:30 AM, Andreas Bergendal via use-livecode > wrote: > > Hi all! > > Those frequenting the forums may have seen this already, but I thought I'd > share it here too now: > > If you want to see a graphic map of the inter-relations of all the handlers > in the scripts of your LiveCode projects, my tool ScriptDependencies now > features an extremely cool flowchart output (using the Mermaid javascript > lib). > > Here’s an example of how a script flowchart can look: > https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png > > A few easy steps to test it on your own scripts: > > 1) Download ScriptDependencies here: > https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest > > 2) Open the stack, click the top left cog wheel and add at least one stack > (that has at least some handlers calling other handlers) to a project. > 3) Close the project pane and click "Start mapping and analysis”. > 4) Click ”Create flowchart”. Boom! :) > > On Mac, the browser widget can display the flowchart in-stack, enabling some > interactivity (click a node to highlight the arrows to and from it). > On Windows and Linux, where the browser widget has, er... room for > improvement…, the flowchart is instead displayed in an external browser > window (minus interactivity). > > My intention with ScriptDependencies is to provide a code analysis and live > documentation tool (of some kind) for LiveCode projects. I need it myself for > some big LC projects, and thought it might be useful also for other LC devs. > > The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque > (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback > and improvement suggestions, bringing the tool up to quite a professional > level. > > I hope you’ll find use for it - or at least enjoy seeing your scripts > presented as a bouquet of flowers, a piece of art! :) > > Any feedback is very welcome! > > /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
Re: Your scripts as a flowchart
Very cool Andreas. I look forward to trying this out. Mark > On 15 Sep 2023, at 3:30 pm, Andreas Bergendal via use-livecode > wrote: > > Hi all! > > Those frequenting the forums may have seen this already, but I thought I'd > share it here too now: > > If you want to see a graphic map of the inter-relations of all the handlers > in the scripts of your LiveCode projects, my tool ScriptDependencies now > features an extremely cool flowchart output (using the Mermaid javascript > lib). > > Here’s an example of how a script flowchart can look: > https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png > > A few easy steps to test it on your own scripts: > > 1) Download ScriptDependencies here: > https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest > > 2) Open the stack, click the top left cog wheel and add at least one stack > (that has at least some handlers calling other handlers) to a project. > 3) Close the project pane and click "Start mapping and analysis”. > 4) Click ”Create flowchart”. Boom! :) > > On Mac, the browser widget can display the flowchart in-stack, enabling some > interactivity (click a node to highlight the arrows to and from it). > On Windows and Linux, where the browser widget has, er... room for > improvement…, the flowchart is instead displayed in an external browser > window (minus interactivity). > > My intention with ScriptDependencies is to provide a code analysis and live > documentation tool (of some kind) for LiveCode projects. I need it myself for > some big LC projects, and thought it might be useful also for other LC devs. > > The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque > (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback > and improvement suggestions, bringing the tool up to quite a professional > level. > > I hope you’ll find use for it - or at least enjoy seeing your scripts > presented as a bouquet of flowers, a piece of art! :) > > Any feedback is very welcome! > > /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
Your scripts as a flowchart
Hi all! Those frequenting the forums may have seen this already, but I thought I'd share it here too now: If you want to see a graphic map of the inter-relations of all the handlers in the scripts of your LiveCode projects, my tool ScriptDependencies now features an extremely cool flowchart output (using the Mermaid javascript lib). Here’s an example of how a script flowchart can look: https://wheninspace.com/browseranimation/WIS_ScriptDependencies_example.png A few easy steps to test it on your own scripts: 1) Download ScriptDependencies here: https://github.com/wheninspace/WIS_ScriptDepedencies/releases/latest 2) Open the stack, click the top left cog wheel and add at least one stack (that has at least some handlers calling other handlers) to a project. 3) Close the project pane and click "Start mapping and analysis”. 4) Click ”Create flowchart”. Boom! :) On Mac, the browser widget can display the flowchart in-stack, enabling some interactivity (click a node to highlight the arrows to and from it). On Windows and Linux, where the browser widget has, er... room for improvement…, the flowchart is instead displayed in an external browser window (minus interactivity). My intention with ScriptDependencies is to provide a code analysis and live documentation tool (of some kind) for LiveCode projects. I need it myself for some big LC projects, and thought it might be useful also for other LC devs. The tool has been thoroughly tested by LC veterans like bn (Bernd), jacque (Jacqueline) and mwieder (Mike), who have all provided invaluable feedback and improvement suggestions, bringing the tool up to quite a professional level. I hope you’ll find use for it - or at least enjoy seeing your scripts presented as a bouquet of flowers, a piece of art! :) Any feedback is very welcome! /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
