Danielo, I see noteself as providing great solutions for online tools, visit, interact, save (in browser) which is a real potential strength of tiddlywiki, if we could only then connect to a counch DB or save to local file and retain the content outside that browser (should the need arise) further installing it on my android was one of the most impressive features with a dedicated Icon and saving capabilities. No need for nodeJS or fiddly folders.
I would be keen to see a little more work to take noteself a little further because It has a powerful use case to make TiddlyWiki more popular, it helps in the first interaction and adoption process, even with only pouchDB not couchDB, it is an immediately functional solution. This is a single user approach. With a little work I believe we can take the existing techniques CounchDB and other savers and wrap a little logic around it to allow a single instance be checked in/out enabling multiple users across time to work on the same instance. Somehow I feel that moving it from an edition to a plugin would be a big step in that direction. I also think this is a opportunity for some degree of commercialisation, which I think I recall you expressing an interest it. I would be keen to continue the conversation on this, privately or in the forum. Regards Tony On Saturday, January 27, 2018 at 7:36:42 AM UTC+11, Danielo Rodríguez wrote: > > Hello Mat > From Noteself point of view this does not make much sense. Noteself is > designed as an application for working offline on your browser with support > for an specific kind of backend for server side storage. Any scenario out > of that one is not officially supported and I didn't take it in account > while designing Noteself. > Please note that Noteself is a tiddlywiky edition and it relies on a set > of heavily opinionated modifications over the normal tiddlywiky edition. > > That said, I have always aimed at providing maximum compatibility with > tiddlywiky and it's ecosystem (not sure why, to be honest). This can lead > to some people making fun experiments that work and some others that does > not. For example, the recent bug fixes allows you to download your entire > wiki as an standalone file with the tiddlers hard-coded on the html as > usual while keeping the ability of adding more tiddlers on top of the local > database. Like some short of snapshot system. > I'm not sure right now how the download mechanism works. It may be my own > plugin baking the tiddlers and then downloading the file or it may allow > the next saving mechanism handle the work. > The error you are reporting seems to be more related to one limitation > tiddlywiky has. If you install a plugin that requires raw tiddlers to be > installed on the head section of the html file (like tiddlypouch does) you > will have to reload the wiki twice. This is not a problem on the file > edition, but it is a real pain in the neck for cloud saving mechanisms. > Your best bet is to go to the online version, configure your tiddlyspot > credentials and attempt to upload from there. > > Good luck > > -- 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 post to this group, send email to [email protected]. 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/22683168-6ded-43a8-8c3a-e28d6f692c6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
