Mat et al Just to clarify where this came from first, then I will explain why.
First, Felicia, thanks so much for this, I was confident yu would work on this and happy to wait, in part because I think you say the gap yourself. I will review and reply in more detail soon. For the last few years I have committed to tiddlywiki as a platform I intend to publish in, provide solutions and use as a business tool, as well as the joy of a collaborative community. As was the case earlier in my life when I aim to become expert in something, it takes time, because of the way I learn, very conceptually, concise and complete but via creative exploration, but once I know something well, it is usually very deeply. Apart from my working life in IT this has included, MS-DOS, Windows, Basic, Cobol, Evolution, Climate Change, Photography, WebSite Development, Sustainability and now tiddlywiki. Because I consider TiddlyWiki a platform and a future backbone to much of what I do, and being a frustrated app developer, my focus on tiddlywiki is pushing its limits, finding its flaws, identifying its gaps. With a deep understanding of procedural languages there is a class of things I would like to do (no doubt others) in tiddlywiki that it can't. Every month or so we the community tend to break another barrier expanding tiddlywikis possibilities down many paths. Off line I have the result of thousands of hours of development and exploration, documentation etc... mostly which I currently share via the forum as needed. Now perhaps this explains why I am sometimes a pain in the neck to some of my tiddlywiki colleagues, I am always looking to identify gaps and fill them. Thanks to many we continue to do so. Some very exciting stuff is about to come from work with Mario, as is often the case, but this time I has a role. *The following is from a programmers perspective* The specific Gap Felicia has worked to resolve is one I identified early, and I now have some workarounds, this "problem" means you can NOT count (or accumulate) a number of different things, using a number of widgets or accumulate over time without having a trigger, like a button to commit it to storage, in a tiddler or field. Each time you *define a variable* it in effect becomes a new variable in the current context. That is within tiddlywiki variables are fleeting definitions, although they must always be defined (eg: macro, set vars), so they they are always redefined. That is variables in tiddlywiki do not behave like variables in most programming languages, especially when you try and make them global, accessible outside one tiddler or loop etc.. and yet be able to be saved without a trigger. - global variables are possible, but they are "static global variables" without a trigger to commit them. - If you are forced to commit them with an action you force the user to know what they are doing. This kind of thing is strait forward in any computer language, including javascript but it has not being "surfaced" until now in tiddlywiki. I am very excited about Felicia's work. Feel free to question, further, even challenge my assumptions, it all about learning and developing tiddlywiki. Regards Tony/TW Tones On Monday, 14 September 2020 05:32:33 UTC+10, Mat wrote: > > @Felicia > > Thank you for this! I can believe it will be useful ... but I'm wondering > why I didn't need it thus far. Are there cases that usually can't be > accomplished, or with much difficulty, that your creation solves better? > (Maybe I should ask Tony) I also imagine it's one of those things that were > at one time, early on, decided against for some secuity reasons - anybody > knows? > > > <:-) > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/54d5dd44-0844-4d03-81f8-9dd63ace0177o%40googlegroups.com.
