Yeah, I believe NoteSelf does work this way in a sense, though I'm not sure if it is separated into multiple files. And it doesn't need to be since you never upload the whole file.
What I am describing, however, is when someone wants to edit their single TiddlyWiki on Dropbox or host a TiddlyWiki online as a static HTML document. Having the core and theme plugins stored on a CDN would decrease the amount of data that needs to be transferred from the host server, and as more TiddlyWiki sites use this method, it will become more likely that an individual will already have the files in their cache, increasing the user experience as well because the site not only navigates very quickly but also loads instantly the first time they visit it [because it is already cached]. Here is an example. I'm not sure why, but the MarkDown generator is not including the hyperlinks, so you'll need to copy and paste the links on the page. The relevant script tags are in the head. Note that the tiddlywiki.html file has the rest of the tiddlers in a second file. https://github.com/Arlen22/tiddlywiki-cdn-example https://arlen22.github.io/tiddlywiki-cdn-example/ On Sun, May 14, 2017 at 7:31 AM, Danielo RodrÃguez <rdani...@gmail.com> wrote: > Interestingly some of the stuff you have described is what NoteSelf > actually does. > We deliver a minimum file , which gets cached the first time you visit it. > Then the only things that go back and forth the wire are the tiddlers , > which are usually just a few bytes. Basically every server based tiddlywiki > edition does this, with the difference that we also work offline without > problems. > > What you want to do will require separate places to store the tiddlers and > the wiki itself or a server side thing that parses the file and delivers > just the tiddlers it contains. Of course you will have to send the required > tiddlywiki version to get from the CDN because people usually don't update > their wikis unless necessary. Again you will need a similar setup to only > upload the changed bytes up the wire, which can get so damn hard. I don't > think any of those requirements fit well in the Dropbox setup most people > uses. If someone wants to serve a public wiki then there are other better > options > > -- > 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 post to this group, send email to tiddlywiki@googlegroups.com. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/tiddlywiki/13e73917-3ff5-404e-ae3a-40087815af44%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAJ1vdSSJSyGfyO1jBOK3yBGcX4TETC4HvNE1Tfy6C7CsFsSN4w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
