I have being working with one of the releases to get a feel for the current implementation. It is wonderfully fast on windows.
Things that would be valuable to me is if TiddlyDesktop;
Local IP Address and port settings
We could alter the local ip address and port, used to access a node wiki (everyone wants to own 127.0.0.1) and I like using the port 80 so no port needs to be provided.
- This would allow us to publish to an IP address on the local network (other than the host) to host an intranet LAN wiki for teams
If single file wikis could also be published to their own local IP address allowing if needed access via a browser where we can overlay it with browser tools and features when needed, particularly bookmarklets;
- TiddlyServer did this
- The would reduce the need for the following, although it is still desirable.
I would appreciate it it were possible for us to access the backend wiki currently saved in index.html and currently serving the groups/wiki listing.
Index wiki
I would particularly like it if I could modify it in a way to present custom links at the top of the index list, I have a number of common links I would like to host and if possible the next item;
Independent wiki window bar
It would also be nice if we could have a global “bar” hosted from the index wikis that would appear at the top of the independent wiki windows, where I could add link triggers of javascript functions that would be applied to the underlying wiki. When I distribute such bookmarklets in a tiddler they do work well in the current implementation of TiddlyDesktopTS
- Bookmarklets are a powerful way to quickly apply powerful settings and reconfigurations, install plugins etc… Without browser bookmarklets being available my tiddlywiki designer tools are diminished when in TiddlyWikiDestopTS
- Being able to use a filter to determine on which wikis to display content would be fantastic eg
[<currentWikiname>prefix[Design]]
Automatic static tiddlers from Node.
I recall the ability to host a node wiki along side its own automatically generated static tiddlers, I think tiddlywiki.com does this statically, these can then be linked to or iframed from single file wikis as a content publishing method. I would be happy to research this however since I am not sure how to influence the command line that loads the node listen I dont know where to start.
The above are primarily customisations that would multiply the options to users of TiddlyDesktopTS to customise