![]() Or using an addOn only with the limitation to write files to the browser Downloads directory and their subfolders. … Overwriting an existing file was only possible using a browser addOn in combination with a native-app like: Timimi. … With TiddlyDesktop – it just worksĪs Tony pointed out, we did have to invent some workarounds, since browser vendors have increased the security restrictions for direct file-system access, in the last years. I think that was a good choice to start with, since you don’t have to mess around with the different “saving options”. There is now some nice webDav servers as well.To share wikis on the LAN and with other users, I tend to use Bob.exe that allows you to serve a farm of single file/ or folder wikis to yourself or on the LAN (unfortunately it’s missed the recent tiddlywiki versions).Wikis with deeper interaction with my desktop eg running apps use TiddlyDesktop.Single file wikis : use Timimi on all my browsers for saving, ie open from and auto-save to file locations.However you access your wiki you need to save changes see options below in.Servers can share single file wikis and/or “folder wikis” and they can just share them at a local address eg localhost 127.x.x.x.if at a http address it follows that there is a “server” doing the sharing. Tiddlywiki can be accessed in browsers at either file:// or Http:// addresses.Because this is a limited browser it does not have the options and customisability of common browsers.Tiddlywiki is always accessed in a browser, TiddlyDesktop has one built in, and as its browser is not used internet surfing it can have additional access to the local computer.I apologize if I do not know Tiddlywiki well enough to have framed my questions perhaps rather than answer your questions directly I can make a few points that may help Node.js w ‘wiki folders’ served/self-hosted (w changes merging) Please add anything I haven’t thought of and if it would be better that I use a different entry point to make the decisions of how I build my Tiddlywiki. Thank you so much for sharing your thoughts. available plugins, performance, etc)?Īre there differences in functionality among the various browsers (Chrome/FF/Edge/Beaker/etc)? ![]() ![]() singlefile.html, wiki folders, local or hosted options and all the available flavours in-between)? Does using TiddlyDesktop or a browser influence or limit my backend options?Īre there differences in functionality between TiddlyDesktop and a browser (eg. I have had difficulty though finding information that clearly details their differences.Īm I correct in understanding that using a browser or the desktop app is independent of any backend decisions (eg. deal breakers, compromises, dependencies) that may move me in a particular direction. I’m hoping to understand any specific behaviours (eg. I wasn’t sure whether to begin with the backend or how I interface with my Tiddlywiki…so thought I would start with (what I thought the easiest) making the decision between using a browser or TiddlyDesktop. One of the greatest things about Tiddlywiki is how flexible and customizable it is, but because I do not have any real limitations with how I ultimately setup my own Tiddlywiki I am finding it quite the challenge as I try to make decisions around my configuration. ![]() ![]() I’m still quite new to using Tiddlywiki and absolutely love it…thank you and Community for all the work you have put in its development and support! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |