Mark, As I understand it this is already possible. External Javascript.
I also wonder if one could selectively remove code not used, however this would need an analysis process. And an exclusion on save, perhaps an alternate core plugin. The dynamic range of application of tiddlywiki would possibly be enhanced with a lower size however in todays world we most often have sufficient overheads that reduction has less benefit than being comprehensive or self documented. Regards Tony On Thursday, 5 November 2020 08:12:12 UTC+11, Mark S. wrote: > > If TW5 could be made to run like javascript, then you could separate the > core from the working files. So you could have a local core library which > all your tiddlywiki files could resource, without having to include them in > every download/upload/save. > > On Monday, November 2, 2020 at 11:00:21 PM UTC-8, 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/849b14d2-cfa3-46b8-be83-3c68ce74c306o%40googlegroups.com.
