Re: [twdev] Re: TiddlyWiki Mod-Loader Plugin (a safer way to change the core)

1) No. The modloader's function is rather simple and it implements that function more-or-less completely.† 2a) In principle you can, by embedding the modloader plugin's contents in another plugin. But this might result in only being able to use one such plugin, and might conflict with the

Re: [twdev] Re: Feature Request: high-priority "bootloader" module-type

Hey, Jeremy — With what you've told me about the preboot approach on the call, it's starting to sound a bit better for modloader's needs. Learning that the serialization DOM format is fixed across all TW5 platforms helps me to visualize a solution. I'm wondering if this pre-boot approach

[twdev] Re: TiddlyWiki 5 Dev Hangout #105 will be on Friday 9th February 2018 at 3pm GMT

> > Many PR are better off as plugins. > The new Mod-Loader could help, in cases where plugins need to change core functionality. I'm designing this facility to provide an option "in between" core-shadowing and pull requests, as well as easier distribution of branch functionality in the

Re: [twdev] Re: Feature Request: high-priority "bootloader" module-type

Hey, Jeremy — Bootloader modules feel a bit like an admission of defeat with respect to > the startup module mechanism. > Potentially this functionality could be an extension of the startup mechanism. Trouble is, in order to load and execute them one-by-one you'd need to be able to

Re: [twdev] Re: Feature Request: high-priority "bootloader" module-type

Hey, Jeremy — > Yes, but your proposed solution is just an escalation in an ongoing arms > race to be the first module to run. This is almost, but not quite, the issue. My modloader *is* the first module to have any method called on it. However, TiddlyWiki currently *loads* (via

Re: [twdev] Re: Feature Request: high-priority "bootloader" module-type

Hey, Jeremy — So, as mentioned in the OP I'm pretty leery of the "pre-boot" approach here. The modloader process uses quite a lot of $:/boot library functionality to identify and inspect

[twdev] Re: Feature Request: high-priority "bootloader" module-type

in scope between bootloader functionality (modifying the tiddler store) and startup functionality (preparing functionality), but that's a loose opinion. On Monday, 12 February 2018 13:05:06 UTC-6, Evan Balster wrote: > > Hey, all — > > *(I had a Twitter discussion > <https://twitt

[twdev] TiddlyWiki Mod-Loader Plugin (a safer way to change the core)

Hey, all — Introducing the *Mod-Loader Plugin*: https://evanbalster.com/tiddlywiki/formulas.html#Mod-Loader%20Plugin This plugin allows shadow tiddlers in a wiki to be patched at boot-time. This makes it possible to change the TiddlyWiki core without creating conflicts or errors when the

Re: [twdev] Diff/Patch in the bootloader for core-modifying plugins

And I forget to upload the files. :) On Tuesday, 23 January 2018 18:52:01 UTC-6, Evan Balster wrote: > > As promised, here is an early draft of the modloader plugin, as well as an > "attribute-modules" plugin which mods widget.js and parseutils.js. > > The modloader plu

Re: [twdev] Diff/Patch in the bootloader for core-modifying plugins

modloader asks for permission to apply (requiring a save and reload). On Tuesday, 23 January 2018 16:42:28 UTC-6, Evan Balster wrote: > > Hey, Jeremy — > > I've been continuing my work on the modloader and I've added tools to > generate patches and visualize them nicely (see attached).

[twdev] Re: An "errors and warnings" display for tiddlers?

Hey, Tony — My suggestion for simple logging would be to build an "append" action, which could be made in WikiText with action-setfield and some macros, as a JavaScript macro, or as a widget similar to action-setfield. Again, that's a different mechanism from what I have in mind for the

Re: [twdev] Diff/Patch in the bootloader for core-modifying plugins

Very pleased to report that I have a working prototype of the modloader plugin now, complete with a tool to generate patch files. This is going to need some testing. On Saturday, 20 January 2018 12:36:13 UTC-6, Evan Balster wrote: > > Hey, Jeremy — > > I think that this can be wri

[twdev] Re: My First Release Plugin

Hello, Tony — This looks more or less correct. The plugin tiddler's "list" field can be used to list (without the full prefix) any subtiddlers to be displayed as tabs when viewing it. The other tiddlers in your wiki don't need to be prefixed — only the ones you plan on including in the

Re: [twdev] Diff/Patch in the bootloader for core-modifying plugins

gt; > Best wishes > > Jeremy. > > > > On 20 Jan 2018, at 08:11, Evan Balster <balste...@gmail.com > > wrote: > > Hey, Jeremy — > > I'm still itching to have this functionality as a tool for developing and > community-testing some of my suggested optimiz

Re: [twdev] Diff/Patch in the bootloader for core-modifying plugins

Hey, Jeremy — I'm still itching to have this functionality as a tool for developing and community-testing some of my suggested optimizations, and I'm willing to make a plugin of some kind myself. Starting into this, it's rather unclear how it's to be accomplished within the bootloader's

[twdev] An "errors and warnings" display for tiddlers?

Hey, all — I've been thinking recently about how TiddlyWiki could benefit from something like the "errors and warnings" list provided by a compiler. When displayed or previewed, the tiddler would display a small "problems" badge that could be expanded to display an accumulated list of any

[twdev] Re: My First Release Plugin

It's a convention to prefix the plugin with $:/plugins// and to put all tiddlers "inside" that. You can transgress that convention if you like, but it might be a little messy when it's unpacked into a wiki-folder. You can include tiddlers of any name in plugins, and bundle them all up with

Re: [twdev] Re: TiddlyWiki 5 Dev Hangout #104 will be on Wednesday 17th January at 3pm GMT

Reviewing some of the optimizations discussed with a mind for their impact potential: - Selective implementation of Widget.prototype.assignAttributes - This is cheap and easy! - Change Widget assignAttributes() to support selective assignment - Change ElementWidget refresh()

[twdev] Re: TiddlyWiki 5 Dev Hangout #104 will be on Wednesday 17th January at 3pm GMT

I may be a few minutes late to this one; apologies in advance if that's the case. On Monday, 15 January 2018 15:47:21 UTC-6, Jeremy Ruston wrote: > > There will be another developer-oriented TiddlyWiki 5 hangout this > Wednesday 17th January at 3pm GMT. > > At Evan's request, we'll spend some

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

gt; > It would have to, yes (just as we currently separately cache the inline > vs. block parsing of a tiddler). > > Best wishes > > Jeremy > > > On Friday, 12 January 2018 02:02:19 UTC-6, Jeremy Ruston wrote: >> >> Hi Evan >> >> I think that

Re: [twdev] Proposing a plaintext parse & render mode for attributes & more

gt; > The proposal still reflects my thinking in this area. > > Best wishes > > Jeremy. > > > On 12 Jan 2018, at 04:58, Evan Balster <balste...@gmail.com > > wrote: > > Hey, all — > > Currently TiddlyWiki implements plain-text wikification by applying >

[twdev] Re: Timer plugin, and iterative computation in TiddlyWiki

On Monday, 15 January 2018 08:38:22 UTC-6, coda coder wrote: > > > > On Sunday, January 14, 2018 at 11:25:17 PM UTC-6, Evan Balster wrote: >> >> Hey, all — >> >> Show-and-tell time! >> >> > It's probably benign, Evan, but there's an unterminat

[twdev] Timer plugin, and iterative computation in TiddlyWiki

Hey, all — Show-and-tell time! Here's the (undocumented) first draft of my timer plugin, and a simple simulation I've implemented with it as a proof-of-concept. The plugin includes a single widget, which triggers action widgets inside at a specific time (TiddlyWiki timestamp) or at a regular

[twdev] Proposing a plaintext parse & render mode for attributes & more

Hey, all — Currently TiddlyWiki implements plain-text wikification by applying WikiText parsing to generate a DOM, then extracting and concatenating any text-widgets in the DOM while discarding everything else. While this functionality is very useful, it has some tricky drawbacks —

Re: [twdev] Re: Creating a test rig for TiddlyWiki optimizations

Hey, Mario — I get the idea you might be thinking about a broader set of test functionality that I have in mind. Can you give me some background? Right now the only parts I can visualize are this sync and DOM monitoring mechanisms. On Thursday, 11 January 2018 06:00:52 UTC-6, PMario wrote: >

Re: [twdev] Re: Creating a test rig for TiddlyWiki optimizations

Hey, all — So, my primary concerns all lie in the realm of rendering and refresh logic. I've seen places where widgets are needlessly constructed, executed or refreshed multiple times, as well as many situations where refresh costs could be significantly reduced. I'm interested in diving

[twdev] Creating a test rig for TiddlyWiki optimizations

Hey all — I'm fired up about optimizing TiddlyWiki, and I'm not the only one. For my part, I'm fixing to propose a slew of changes to refresh mechanisms, attribute handling and other facilities... To ensure any efforts in that direction don't create errors, we need a test suite. I assume

Re: [twdev] Performance note: Adding variables to selective refresh

ng zillions of > Tiddlers, but IME its an issue. > > Best wishes > Josiah > > Evan Balster wrote: >> >> The test-case mentioned in my last E-mail can be seen here: >> https://evanbalster.com/tiddlywiki/formulas.html#Harmonic%20Lattice >> >>

Re: [twdev] [TW5] TiddlyWiki 5 Dev Hangout #103 will be on Saturday 6th January at 3pm GMT

ZHiLpEQJuaFYeV2xMLinklLz0nQgERPdw=?hl=en_US > > Please let me know if you run into any problems joining, > > Best wishes > > Jeremy > > On 6 Jan 2018, at 13:52, Jeremy Ruston <jeremy...@gmail.com > > wrote: > > Just a reminder that the hangout will b

[twdev] Re: Implementing a timer to trigger action widgets?

performance cost. These little sims I've been building promise to be useful for profiling all the unnecessary work TiddlyWiki has to do when one or two tiddler fields are updated... On Monday, 8 January 2018 05:38:21 UTC-6, PMario wrote: > > On Sunday, January 7, 2018 at 8:54:19 PM UTC+1, Evan B

[twdev] Re: Prototype: extensible attribute modules

idgets to compute attributes. Implement a method for rendering the attribute-enabled widgets above to text. - Introduce a new attribute object type which is widget-like but text-oriented, as in my current pull request. I don't think this is a choice we should make hastily. On Thursd

[twdev] Re: Implementing a timer to trigger action widgets?

y, 6 January 2018 07:08:11 UTC-6, PMario wrote: > > On Friday, January 5, 2018 at 8:10:24 PM UTC+1, Evan Balster wrote: >> >> Is there any prior art for this? Are there gotchas related to >> server-side rendering I should be aware of? >> > > Ther

Re: [twdev] [TW5] TiddlyWiki 5 Dev Hangout #103 will be on Saturday 6th January at 3pm GMT

Few remarks: - A rough early version of the CSV unpacker plugin has been released: https://evanbalster.com/tiddlywiki/csv_unpack.html - There was some discussion about using widgets to model and compute attributes values — text, macrocall, transclude etc... - I made the rather

[twdev] Implementing a timer to trigger action widgets?

Hey, all — Related to my work on Formulas, and several things I'm currently building, I'm trying to figure out how I can build a widget that triggers actions after a certain amount of time has passed, or at a regular interval. I want to use this to implement things like simulations and clocks

Re: [twdev] [TW5/TWX] Replacing macros with WikiText functions

On Thursday, 4 January 2018 14:45:53 UTC-6, BJ wrote: > > > > On Thursday, January 4, 2018 at 9:40:09 PM UTC+1, BJ wrote: >> >> >> >> On Thursday, January 4, 2018 at 8:56:29 PM UTC+1, Evan Balster wrote: >>> >>> there is caching in the core -

Re: [twdev] [TW5/TWX] Replacing macros with WikiText functions

context. As noted by other users <https://groups.google.com/forum/#!topic/tiddlywiki/eQRf8Wun3Zo>, however, this "feature" can be unexpected or undesirable. On Thursday, 4 January 2018 13:09:18 UTC-6, BJ wrote: > > > > On Thursday, January 4, 2018 at 7:48:00 PM UTC+

Re: [twdev] [TW5/TWX] Replacing macros with WikiText functions

Hey, all — I have a plugin that defines parametrized tiddlers as components, there is > a demo here: > Neat! So under the hood this is functionally equivalent to <$vars><$transclude/> right? What I'd really like to see in the future is a "parse-tree cache" for more efficient transclusions.

[twdev] Diff/Patch in the bootloader for core-modifying plugins

Hey all — Small idea with big ramifications: What if we made a deserializer module that could use diff files to patch previously-loaded Tiddlers as part of the bootloading process? This would make it possible to write plugins that patch the core (or other plugins) and have those plugins

Re: [twdev] [TW5/TWX] Replacing macros with WikiText functions

d become a > widget; the tiddlers that it defines would be available within the scope of > the widget. The ancestor cascade would take care of the shadow tiddler > mechanism. > > So, “global macros” would be transclusions of tiddlers defined in the main > store, and “local macros” woul

[twdev] [TW5/TWX] Replacing macros with WikiText functions

Hey, all — A while ago I noticed Jeremy expressing some regrets about how TiddlyWiki has become dependent on text substitution macros, and suggesting that TWX will do something differently: *Jeremy Ruston:* Thus, there are lots of quite prominent features that were introduced early > on and

[twdev] Re: [TW5] TiddlyWiki 5 Dev Hangout #103 will be on Saturday 6th January at 3pm GMT

- Widgets with multiple bodies (see my $condition plugin <https://groups.google.com/forum/#!topic/tiddlywiki/mbQ5FcXAqms>) On Tuesday, 2 January 2018 15:51:46 UTC-6, Jeremy Ruston wrote: > > At the suggestion of Evan Balster (see > https://twitter.com/EvanBalster/status/94828

Re: [twdev] Performance note: Adding variables to selective refresh

3:25 UTC-6, Evan Balster wrote: > > I did a little experiment today. I have an "explorable explanation" > prototype in my formulas development wiki, which renders a large and > expensive SVG with a few thousand dynamic elements. (The primary structure > is a two-dimen

Re: [twdev] Performance note: Adding variables to selective refresh

I did a little experiment today. I have an "explorable explanation" prototype in my formulas development wiki, which renders a large and expensive SVG with a few thousand dynamic elements. (The primary structure is a two-dimensional list, a $formula-vars widget that sets some computed

[twdev] Re: Prototype: extensible attribute modules

Added a "refreshAttributes(changedTiddlers)" function to the PR and fixed a few bugs in the initial implementation. On Wednesday, 27 December 2017 13:03:29 UTC-6, Evan Balster wrote: > > Opened a pull request: https://github.com/Jermolene/TiddlyWiki5/pull/3072 > > I exp

Re: [twdev] Re: [TW5] Accessing JSON tiddler data

: > > Oooh. Thanks for that. I have also been considering JsonPath syntax ( > http://goessner.net/articles/JsonPath/) and this library: > > https://www.npmjs.com/package/jsonpath > > I will have to compare them. > > Best, > Joshua Fontany > > On Thu, Dec 28, 2

[twdev] Re: [TW5] Accessing JSON tiddler data

path syntax > > Best, > Joshua Fontany > > On Wednesday, December 27, 2017 at 7:17:55 PM UTC-8, Evan Balster wrote: >> >> I have to assume that it's just a limitation in how the JSON structure is >> translated to and from text references. JSON doesn't actually have

[twdev] Re: [TW5] Accessing JSON tiddler data

I have to assume that it's just a limitation in how the JSON structure is translated to and from text references. JSON doesn't actually have an "official" addressing scheme for sub-objects, only add-on standards like JSON pointer. TiddlyWiki allows most characters (including dots) in field

[twdev] Re: Prototype: extensible attribute modules

de, and post my findings. > Thanks for your work! > > have fun! > mario > > On Monday, December 25, 2017 at 7:27:05 AM UTC+1, Evan Balster wrote: > >> P.S. This seems like a missed opportunity to deprecate the clunky >> <$set filter=> idiom. >> >

[twdev] Re: "Lateral Variables" (TWX/TW5)

Explaining the use-case is pretty simple: Most users of TiddlyWiki are looking at markup and start off thinking linearly rather than in terms of widget trees. Requiring them to grok the internal architecture puts limits on TiddlyWiki's learnability. For my part, I stumbled a lot while trying

[twdev] "Lateral Variables" (TWX/TW5)

Hello, all — In the other thread Jeremy mentioned his interest in implementing "lateral variables" in TiddlyWiki. These would be variables that can be set somewhere in wikitext and accessed further below without requiring the user to worry over position in the widget tree. I think it's a

[twdev] Prototype: extensible attribute modules

Hello all — As part of my work on the formulas plugin I'm adding attribute modules to TiddlyWiki. I wanted to run my approach past people here, as it's something I'll likely be advancing as a pull request. Currently: - *$tw.utils.parseAttributes* (parseutils.js) uses an if-else chain to

Re: [twdev] Re: Performance note: redundant computation in built-in widgets

Hey, Jeremy — Absolutely! And this fact allowed me to sidestep the issue in the latest formulas release by changing the call graph a little. Nevertheless, as a convention it's potentially problematic. I've written a crude datamining script here to produce overviews of the internal calls in

Re: [twdev] Performance note: Adding variables to selective refresh

Hey, Jeremy — > I think it would be possible to do this with a new signature for the > .refresh() method, and then have widget.js emulate the old behaviour for > widgets that don’t implement the new signature. That way we can retain > backwards compatibility. > This sounds like a good

[twdev] Re: Performance note: redundant computation in built-in widgets

My assessment: The issue here stems from poor separation of concerns between *render* and *execute*. *render* typically calls *computeAttributes* and execute before performing some unique steps. It gets called on first render and re-render. *refresh* gets called on a potential re-render and

[twdev] Performance note: Adding variables to selective refresh

Hey, all — Under TiddlyWiki's current architecture, a change in any of a widget's variables instigates a full refresh of the contained widgets and elements, destroying and rebuilding the DOM inside. This means any dynamic program involving variables needs to be re-building its whole UI quite

[twdev] Performance note: redundant computation in built-in widgets

Hey all — I've been designing my formula widgets for high performance, and I've been bothered by some undesirable behaviors it inherited from the widgets they were based on ($count and $vars among others). Specifically, many widgets call computeAttributes() and/or execute() twice when

Re: [twdev] Making a CSV deserializer module... Error reports & wizard steps in the importer?

Hey, Jeremy — OK, good to know this stuff is on your radar. For the time being, my plugin is functional (just less convenient than it could be). My inclination would be to stand by for any future developments in TiddlyWiki's import workflow, and jump in and upgrade the plugin if and when

[twdev] Making a CSV deserializer module... Error reports & wizard steps in the importer?

Hey, all — I'm working on this CSV "unpacker" plugin: http://evanbalster.com/tiddlywiki/csv_unpack.html The introduction of deserializer modules, which I only discovered half-way through the process, made things a lot easier. But I'm a bit troubled at the lack of a good mechanism for

Re: [twdev] Proposing more sane fault tolerance for "unclosed" tags & markup

Hey, Tobias — I fear we will just delay the parsing error ...to the next closing tag > which now operates as a new opening tag. > > So, with... > > ''foo //bar'' baz// mumble and then some //more italics// but is it really? > > ...what happens if we forcefully close the italics at the second '',

[twdev] Proposing more sane fault tolerance for "unclosed" tags & markup

TML tags and widgets. Here's a slightly more onerous example: <<< > Evan Balster says ''Fault tolerance is awesome! > <<< He later died of exhaustion This results in Evan Balster says *Fault tolerance is awesome! <<< He later died of > exhaustion* &g

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

Hey, Mario — I definitely wouldn't be implementing date processing from scratch. There's built-in support for dates in TiddlyWiki and JavaScript itself, and I would almost certainly build on those. Support for dates seems pretty essential, both because it's a staple of classic spreadsheet

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

> > In your Try Me example box, > <> > does not work. Macros with arguments aren't supported yet, sadly — so you'll have to resort to monkeying with $set for now. I'll note that it should be pretty straightforward to add a (preliminary) date & time datatype to the plugin, and I might do

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

TonyM — I've added an issue on GitHub about date and time features; feel free to comment here: https://github.com/EvanBalster/TiddlyWikiFormula/issues/5 On Thursday, 14 December 2017 22:06:27 UTC-6, Evan Balster wrote: > > Hey, all — > > Version 0.1.0: > > https://evanbals

[twdev] Re: Making a formulas/computing plugin; seeking feedback & advice

Ideally allowing us to take the result and > add it back to another date with the correct units. > > I imagine the libraries and source you are using may have such functions. > > Anyway, Do as you wish with this request, including ignoring it, if it is > too much. > > Than

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

Whoops, meant to say "after I add some more functions I'll put it up on the main TiddlyWiki group and get some broader feedback there". On Thursday, 14 December 2017 14:04:58 UTC-6, Evan Balster wrote: > > Right but we should give it some time, to settle. ... >> &g

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

> > Right but we should give it some time, to settle. ... > Haha, yeah, it's got some rough edges yet. After I add some Is there any way to add a new attribute value syntax without overriding a shadow tiddler? For now my provisional solution is a JavaScript macro, but that prevents

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

Version 0.0.3: https://evanbalster.com/tiddlywiki/formulas.html - + Comparison operators - + Boolean values - + Logical functions - + Selection and IFERROR functions - Fixed percentage operator - Code cleanup - Tweaked compiler errors I'll be trying to conform a lot of

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

Hello, all — Here's a GitHub I've created for the project: https://github.com/EvanBalster/TiddlyWikiFormula Feel free to open issues, make comments, etc. On Tuesday, 12 December 2017 20:56:00 UTC-6, Evan Balster wrote: > > OK, well, I continued to overdo it today: > https://evanba

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

ight-associativity isn't implemented yet. No GitHub repo yet but that would be my next step. On Tuesday, 12 December 2017 14:46:37 UTC-6, Mat wrote: > > Evan Balster wrote: >> >> ... That said, something like {{{=formula}}} could work (though this is >> arguably mo

Re: [twdev] Making a formulas/computing plugin; seeking feedback & advice

Hello, all — Sorry about the certificate issues. Fixed now: https://evanbalster.com/tiddlywiki/formulas.html *Mario*: Did you upload it to github? ... How is your programming workflow > atm? Which tools do you use? *Jeremy*: Is the code on GitHub? > No, not yet. So far I've been

[twdev] Making a formulas/computing plugin; seeking feedback & advice

Hello, all — For perhaps a year or two now I've had my own ideas about how to approach making something like "spreadsheet formulas for TiddlyWiki", something I know many other folks are interested in. Currently I use a macro-based facility in my accounting wiki. I'm also aware of Tobias