Yes different but the same because if you do use more than one you do need a way to get into the manager. If you can make an icon or command line to open the default you get your default wiki.I Actualy launch tiddlydesktop in startup sometimes so my first click opens my key wiki.
Perhaps you could illustrate a little more Your idea. And we pass that on to Jeremy in git hub.
Regards
Tony
I forgot to add. With an association and command line options I can add an option on html files to open with, rather than the default browser, however I have also used a .tw extension which if sent to a browser, and I expect tiddlydesktop it still opens as it is defined as html internally.
I have posted a few times on this.
Regards
Tony
I will revisit again but I had timimi, node and tiddlyserver and others with this working.
I believe what is critical is the browser opens the html file and sees it is declared as html in its header. Regardless of the use of another extension I believe its working is demonstration of correct html file structure.
I won't regurgitate the arguments for the ability to use an extension here but the powerful reasons are.
Being able to identify tiddly wiki files on the host and treat the files as documents. This is even more pronounced with timimi allowing direct access and update of local wikis. This allows management of tiddlywiki with all the os tools available including search when many html files look the same.
The other is if we can assign tiddlywiki files to open in a nominated browser if not the default and in an "application" such as tiddlydesktop so a file accociation can be set. No need use command lines.
Other local smarts can be written if tiddlywiki files can easily identified. I already rename them to .hta and .aspx successfully.
Regards
Tony