TT, It is important to discuss this, because in time TiddlyWiki can provide a compelling application with full desktop interaction, on multiple OS's in addition to website, Apps and server functionality.
By posting this tip however I wanted to bring to the attention of Windows users that by using a local app like TiddlyDesktop you can almost use native windows commands and links to get the desktop interaction. When you build a "dedicated" wiki for a specific desktop, even specific computer, you don't need to be able to handle cross platform and browser etc... so for any primary windows users this seems to me simple and compelling. I have not tested it but I expect the same would be for the case for other platforms as "*It can be installed on Windows, Mac OS X or Linux. It is compatible with TiddlyWiki <https://tiddlywiki.com/static/TiddlyWiki.html> version 5 and the older TiddlyWikiClassic <https://tiddlywiki.com/static/TiddlyWikiClassic.html>*." And that one each platform I imagine the same can be done there with native links executions etc... > Right. But only slightly different. Same with Bob. > We should provide examples that reduce this gap, but With bob an Timimi there needs to be message sent on the way to getting a result. > > I think it might be interesting to look at common methodology. > Totally agree, and in the discussions thread from which Polly became a thing, I was suggesting an identical process to save tiddlywiki on any platform, you and was it Mark - took this a lot further in a slightly different direction to me. > FYI, Timimi requires that "scripts" be in its "...\Timimi\Scripts\" > sub-dir. Same with Bob's "scripts", they go in a specified sub-dir. > (One good thing with Bob & Timimi, of course, is that their script methods > take parameters). > Yes, it would be nice to document this with both tools documented together, and considering each OS below it. > > Personally I'd rather not write different scripts for Timimi, Bob & > TiddlyDesktop. A way round this is to have a script (Bob, Timimi) or link > (TD) that is simply *a pointer to repository of one's own batch/shell > files*. That seems quite like what you are doing? > I agee, but in the case of tiddlydesktop I did not write any scripts/batchfiles etc...I just referenced them, ie executables, batchfiles, folders or file names. Including using <object width="100%" height="930" data= "file:///C:\Data\batches\networkcheck.txt"></object> To make local files, or the result of a native OS script visible. > So, yes, customisation is highly variable. But the o/s logic I think has a > consistent pattern that can be illustrated. > Yes, I agree, it is just less needed with straight TiddlyDesktop to local OS interactions > > BTW, part of the thoughts behind Polly were to facilitate all this in an > *integrated* cross-platform way. > With Polly started you could provide the services you illustrated for any > wiki. And with Bob, Timimi & TD you could also launch Polly from the wiki > itself. > This is a noble objective, but one I find hard to speculate too far given I am a windows Expert, not linux or MAC. I offer my support on windows but need others to extend it across OS's. > > Thoughts! > Thanks for asking. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/02520041-3e9e-4195-969f-6d461502915c%40googlegroups.com.
