Thanks all for your continued feedback, If I may make a few comments in regards to some replies specifically. It is not that I proclaim to be an expert of the person that decides which idea is a good one, it is just an attempt to try and coral your wonderful feedback towards the objective of the Original Thread OT.
I will do a second post on funding. To all, Thank you, you have all contributed much. Okido/Mario, The key value of the use of a .tw file is simply to differentiate it from other html files, which will only ever open in the default browser unless you use open with which is a clumsy requirements. Tiddlywiki could open in a default browser without the saver available and work be done before it is discovered it will not save. Keep in mind the .tw file remains a html file as defined in its content and most browser open it successfully. This is not unlike the already possible saving as a .hta (IE Windows only?) and .aspx such as on sharepoint servers. This is in my view important when treating a tiddlywiki as a document by a given name, less so if naming it index.html on a host. TT, You make a point between Mobile and Desktop, there are good reasons for these to be treated differently, installing an app is common place. One advantage of Tiddliod including lite is you paste in a internet hosted tiddlywiki and it is "installed" into tiddloid. It would be nice if we could provide the following workflow for existing apps; - On an internet published wiki, To place this Tiddlywiki on your mobile install "appname" then share this URL with "appname" and it will download your own copy to you phone. - Jed has suggested Bob.exe can do something similar on desktop, and has extended it for single file wikis - I will review at my earliest. - TT you have a lot of good ideas there and I will consider them in more detail, I think you hint at something I would like and that is an andriod or iphone app that is a shell in which you can fit a single tiddlywiki and distribute as an app in the app stores. I would pay for this because it may have an immediate return on sales. It may give those seeking some returns an opportunity as well. TT the idea of TW as content is in effect why I want to see the content openly available to "drive by" use on the internet. I want many content instances to be available to make your own so we can all start publishing more widely. - TT as you say Maybe, "in-browser saving" linked with OS mediated safety backup could work for your aim? I think this may be the first step yes, I will outline my thoughts in this below in *First save post* Bimlas, - I think if TiddlyDesktop was installed and we had a way to share a url within the browser which it downloaded a given tiddlywiki "edition". It already solves many of the issues including browser and OS, we just to make it less than a hop, skip and jump. Imagine an option to send to TiddlyDesktop. - I agree cloud solutions may be the most common and popular approach at some point in the future as tiddlyspot already is. I would like to see gitub publishing of TiddlyWiki's similar to the core so people can raise issues and changes to specific editions. But to me this is beyond this initial experience problem. - Your suggestion once again out of the box such as flutter is great, but I suppose only a few here can consider the possibility of this. I too think trying to adopt PWA Progressive web App standards would be great, they in effect address the issues in the OT however we may not meet some of the load time criteria initially, but do we have to. Jed/Bob - I think JED is right in noting we have missed how we can use bob, he has created the single file plugin I am keen to test. Bob is so rich with features it has been hard to confirm exactly what can be done with it. Jeremy/TiddlyDesktop - Good OS platform support, easy install, would work well if .tw files could be associated with it, and or we could open in, or share to TiddlyDesktop from Internet etc.. All the rest of you Mark, Arlen Bimlas, Jed, Mario, David etc.. Lots to work through thanks Regards Tony -- 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/7e9db808-e0a8-446f-8215-318eb80757d5%40googlegroups.com.
