Hi Ste, Many thanks for your kind words. I like to give a real example. Fortran is a very old language and still in progress in 2020 and its latest standard 202x was released ( first draft ) a few months ago ago. Fortran is very popular in the scientific community when it comes to high performance computation and number crunching. Its 2020 compiler (support Fortran standard 2018) can compile and run the code back to 1970. There are many deprecated features, by default compiler uses the recent standards but there are compiler switches to tell compiler to compile a legacy code with many deprecated rules.
What I propose for Tiddlywiki is like Fortran. The core can support most of the legacy tiddlers in TW5 but the TW 5.2.xx by default works based on new clean and light core and does not support deprecated rules. So what people can do if they have legacy tiddlers, plugins, ... in new TW 5.2.xx? Like Fortran which has compiler switches, TW 5.2.xx can have an official plugin e.g. backwardcompatibility plugin which can be installed on demand and support all TW 5.x.yy So while TW 5.2.xx is kept light, clean and stripped out and push users to use the new core which support good scripting styles (we can say new TW standards) , it has options (plugin) to simply used and support all legacy things (tiddlers, plugins, themes,...) So by default TW 5.2.xx is based on stripped out, clean, minimal core BUT users have option to install official backwardcompatibility plugin(s) to work with all old things. Best wishes Mohammad TW-Scripts <https://kookma.github.io/TW-Scripts/> codes, macros, and solutions in Tiddlywiki TW-Commander <https://kookma.github.io/TW-Commander/> bulk operations on tiddlers TW-Trashbin <https://kookma.github.io/TW-Trashbin/> a Tiddlywiki trashbin tool TW-Favorites <https://kookma.github.io/TW-Favorites/> a favorites and bookmarking tool TW-Todolist <https://kookma.github.io/TW-Todolist/> organize, prioritize, and plan your work https://github.com/kookma On Tuesday, November 3, 2020 at 6:50:47 PM UTC+3:30 Ste wrote: > Welcome back Mohammad! > Diving in with some heavyweight thoughts! > Fit tiddlywiki on a floppy!...(I found some in an old lap top bag the > other day....none of my students knew what it was.) > I've not been a party to the dev/ github discussions but as much as new > and shiny appeals, losing say, tidgraph...NOOOOO. But then my existing > wiki isn't going anywhere I guess (at least now I have a backup from > tiddlyspot!). > Or would it be a case of SOME things breaking, SOME things still working? > How radical an overhaul is it? > Tiddlywiki classic, 5.1-classic and shiny...hmmm > > Ste > > > > On Tuesday, 3 November 2020 at 14:58:40 UTC Charlie Veniot wrote: > >> I'm an instant fan of your thoughts. >> >> Your post makes me think of Linux (Tiny Core Linux >> <http://tinycorelinux.net/> and, even more so, the stripped-down >> version: Micro Core Linux.) It would be neat for TiddlyWiki to have a >> Debian-like >> repository <https://packages.debian.org/stable/> and something akin to a >> package manager. >> >> Yeah, I dream kind of grandiose... >> >> On Tuesday, November 3, 2020 at 3:00:21 AM UTC-4 Mohammad wrote: >> >>> Tiddlywiki is rapidly improving and you can see great features in the >>> recent releases. >>> From 2.1.17+ amazing features have been added to Tiddlywiki! One >>> question is about the size of empty.html (the virgin Tiddlywiki). See the >>> below table >>> >>> Release Size (kb) >>> 5.1.12 1820 >>> 5.1.15 2025 >>> 5.1.17 2033 >>> 5.1.19 2153 >>> 5.1.21 2235 >>> 5.1.22 2197 >>> 5.1.12 2282 >>> >>> While I love the new features, but, how big a virgin Tiddlywiki can be? >>> Assuming many users work with single file mode and using different >>> Tiddlywiki for different purposes, I think we should set a maximum size, >>> before going to have bigger empty.html >>> >>> >>> Suggestions >>> *A. Use official plugins* >>> 1. Keep the core as light as possible, go down to 1MB size (strip >>> everything extra) >>> 2. Put extra features in official plugins >>> >>> *B. Start a new generation * >>> 1.Release TW 5.2 with minimum size core (include only essential part) >>> 2. Leave all backward compatibility to Tiddlywiki 5.1.xx >>> 3. Stop developing 5.1.xx and only release bug fixes >>> >>> If Jeremy can go for a new generation of Tiddlywiki, I may also suggest >>> 1. Sweep the core from all duplicated codes and those retained backward >>> compatibility and leave them for 5.1.xx >>> 2. Rethink about filters and implement using the more versatile >>> approach, like those are going on in GitHub (e.g. Saq proposal for multi >>> input filters) >>> 3. Use flexible switchable page layout >>> 4. Think for a cleaner scripting (remove all duplication, improved >>> grammar, ... there is a lot of good discussions in the forum and GitHub) >>> 5. Think of a new name (re-branding) >>> 6. ... >>> >>> I am sure people can suggest more here >>> >>> >>> Best wishes >>> Mohammad >>> >>> TW-Scripts <https://kookma.github.io/TW-Scripts/> codes, macros, and >>> solutions in Tiddlywiki >>> TW-Commander <https://kookma.github.io/TW-Commander/> bulk operations >>> on tiddlers >>> TW-Trashbin <https://kookma.github.io/TW-Trashbin/> a Tiddlywiki >>> trashbin tool >>> TW-Favorites <https://kookma.github.io/TW-Favorites/> a favorites and >>> bookmarking tool >>> TW-Todolist <https://kookma.github.io/TW-Todolist/> organize, >>> prioritize, and plan your work >>> >>> https://github.com/kookma >>> >>> -- 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/65fc102c-633b-4796-9882-3a3ae59ff81dn%40googlegroups.com.
