>
> I intend to re-check my ability to get linux firefox 17 to work with:
> var version = {title: "TiddlyWiki", major: 2, minor: 7, revision: 0, date:
> new Date("December 15, 2012"), extensions: {}};
>
> using tiddlyfox.
>
> In the meanwile, note that I sent you a conventional email that contained
> the following observation:
>Thank you, I'm afraid I've been in email bankruptcy recently... > > As a fan and a user of Tiddlywikis for quite a while, the closing of the > privilegeManager functions in aparently all browsers is > a real problem for me. Several observations: > > With file based tiddlers: > - Tiddlyfox works with Microsoft Internet Explorer. > Is that a typo? As far as I know the ActiveX file control that TiddlyWiki uses for saving is still present in modern desktop versions of IE. However, it's never been a satisfactory solution as it is limited to handling pure ASCII text, and the workarounds that TiddlyWiki uses to work with it's UTF-8 content are brittle and compromise the design on other browsers too. > - Chrome and rekonq seem to be most uncooperative > Some people report no problems with using TiddlySaver.jar on Chrome, but it evidently rather depends on having a working Java run time environment. > - Firefox 16 and above do not appear to work with your Tiddlyfox plugin > (I am reconfirming this :^). > Correction, TiddlyFox does definitely work on Firefox 16 and 17, not only for me on my OS X machine, but other users have also reported success, too. There's something going wrong in your environment that we need to debug, but TiddlyFox is basically sound. > > The positive observation I deliver is that all of these use cases still > work perfectly when you use a ziddly-wiki. > Ziddly wiki is a Zope II implemenation for server side tiddly wiki use. > This is old and abandoned, but actually works, writes tiddly wikis > consistently. > Well, ZiddlyWiki is really very old in TiddlyWiki terms, and I wouldn't recommend using it. > > This issue is a distraction for all of us. If you have time to guide me I > would be happy to help. > My perspective is that we've enjoyed a few years where the browser has been usable on it's own as a general purpose computing environment -- by which I mean the ability to do useful work with standalone HTML files stored locally. But it's now clear that browser makers are valuing "security" above all else, and are all in their own way steadily eroding the (dangerous) standalone capabilities of browsers. That sounds bad, but in fact it is eclipsed by a much bigger trend, that of using smartphones and tablets instead of desktop computers. These devices have never supported general purpose computing in the browser. While there are some strong use cases for a read-only TiddlyWiki (eg documentation distribution), obviously the real value of the thing comes from the ability to save changes. In TiddlyWiki5 we have a range of options: - TiddlyFox will continue to be supported in desktop and mobile versions of Firefox - TW5 can be hosted on TiddlyWeb or TiddlySpaec - TW5 can be run as a node.js app (in the same manner as ZiddlyWiki) to which one navigates in the browser, and uses just like a conventional web app - TW5 can be hosted on a cloud service like Dropbox, and then changes saved using the cloud service APIs - TW5 has a lowest common denominator "download to save" option that allows changes to be saved on almost any standards compliant browser. The technique is rather manual and inconvenient, but it means that users have an "in extremis" way of saving changes when out and about. I think this is very significant: I think many users are happy to customise their "home" browser with things like TiddlyFox, but still value the ability to walk up to any browser with a USB port and do useful work More than that, there is a big trend towards environments that allow HTML5 apps like TW5 to be directly executed in a number of ways: - App.js merges node.js APIs with a built in browser allowing apps to be packaged as a desktop app - http://appjs.org - Node-Webkit packs WebKit with node.js into a desktop app - https://github.com/rogerwang/node-webkit - Windows 8 supports HTML/JavaScript apps with privileged file system access There are going to be more and more of these, frequently equipped with the node.js APIs that TW5 already uses. So, I think the future of TW5 will still be based around the single file edition as the lowest common denominator, but that it will be packaged up in a variety of ways so that you'll be able to have a good experience on Android, iOS, Windows etc. In terms of your offer to help, there are a number of explorations and investigations that would be valuable - for instance, I don't think anyone is looking at Windows 8 JS apps, or node-webkit. I'm corresponding with the developer of TWEdit with a view to adapting it for TW5. If there's any areas of particular interest for you I may be able to make more helpful suggestions, Best wishes Jeremy > Thanks for the years of tiddling and... > > Kindest Regards, > > Flint > >> >> >> >> -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
