Something's been bothering me. Perhaps someone with a grasp of Javascript/HTML5/Firefox can offer some solace.
At its core, TW works by violating a prime rule of Javascript: It saves itself (and other material) to a local machine. Javascript isn't supposed to have this ability, but FireFox and IE have some extra, optional abilities that can be exposed by clever programmers. Opera and Safari and ? do their saving via a java plugin ... or at least try to. Recently, Microsoft has tried to button up its software. The only way to enable saving with TW on recent versions of XP - ? is to deliberately undo the security that MS has put into place. At least in my case, I had to load a registry setting to even make this possible. This kind of manipulation won't be possible in a corporate environment. It appears that Opera may have hit some wall with using the Java jar file. Meanwhile Firefox seems to be becoming more like MS every day -- now causing plugins to stop working for no other reason then that the version number in the plugin doesn't match the version of FF -- a somewhat draconian approach, IMHO. So I'm wondering if we're going to wake up one day to a new version of FF that no longer allows TW to save. Nor IE. Nor alternatives via java? Will the new HTML5 basis guarantee that TW will always have a legitimate way to save itself? Or, will there always be some back door for saving TW files? Is there some browser that we can count on to always run TW? Thanks for listening, Mark -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
