Secondly, /fileedit, for various reasons, explicitly does not permit adding a new file via the web interface. If that setting is empty, the /fileedit page does not work (and it only allows editing of files matching one of the given globs). Note that that setting, by design, does not sync to clones - it has to be explicitly set on any repository copy where it should be enabled. It sounds like the above option would give you at least part of what you're looking for, with two very minor caveats:įirst, you would also need to enable /fileedit by setting the (non-syncing) fileedit-glob setting: fossil set fileedit-glob '*.html.other wildcards' Noting that "current branch" means nothing without a checkout. , a commit on the current branch would be done. Hypothetically, of you set the project's home page to something like /fileedit?filename=tiddly.html&checkin=trunk, when you run fossil ui then you would land directly in the editor. That's effectively how the /fileedit page works. The TiddlyWiki would be a single HTML file stored inside a Fossil repository and when you launch the Fossil UI and browse, let's say the trunk version of such file and hit save on it Where could I start such exploration? Any ideas, pointers, half prototypes, reading suggestions, are pretty appreciated. #Tiddlydesktop import plugins portable#This would provide an easy way to have a multiplatform portable wiki with saving, history and collaboration, that can be particularly useful in low/intermittent connectivity scenarios (that was what made me think of such combination), but also elsewhere, empowered by two simple and pretty self-contained and powerful tech stacks: Fossil and TiddlyWiki. A commit process is triggered in a similar way to Stephen's experiments on enabling Wiki editing and saving functionality.Ī single Fossil file repository containing the TiddlyWiki HTML file and its history could be launched (and even packaged) with a Fossil executable. The important issue here is that TiddlyWiki user has a way to access commit functionality from its web interface by pressing save inside TiddlyWiki. #Tiddlydesktop import plugins password#A Fossil configuration Tiddler would be the one saving the name and password of the current user in the repository (or the user can use Fossil's login UI). The TiddlyWiki would be a single HTML file stored inside a Fossil repository and when you launch the Fossil UI and browse, let's say the trunk version of such file and hit save on it, a commit on the current branch would be done.Ī Tiddler is the minimal unit of information storage and functionality in TiddlyWiki. TiddlyWiki has Git saving support (see 1 and 2) and I wonder what needs to be done to have a similar experience but with the advantages of using Fossil. #Tiddlydesktop import plugins full#Once installed, you can save the tiddlywiki files without any extra steps, like the original Tiddlyfox addon.I have recently come full circle, finding again TiddlyWiki, a technology I used intensively from 2005 to 2007 and I want to connect it with Fossil (which has become integral part of my workflow since 2011). Timimi is a web-extension accompanied by a native host that allows you to save and backup your standalone HTML tiddlywiki files anywhere in your hard-drive. I use it with Firefox and sync with Dropbox. Have you tried using Timmi with your browser ? I had problems initially with the file save workflow till I found Timmi. I find the TiddlyDesktop to be too heavy for what can be done in the browser itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |