I noticed the twFile TiddlySaver driver works on all major browsers but it's not the preferred driver on IE and FF. It's great IE and FF have their own native drivers, but they both result in disruptive security dialogs.
I successfully modified twFile to always try the TiddlySaver driver first and fall back on the native drivers. Is there any reason not to do this? In addition, the Java LiveConnect driver works on FF without security dialogs. This driver is slower, but it might be faster than dismissing a security warning! (JavaLiveConnect has a definite pause in Opera, but it's pretty snappy in FF.) How about making the twFile driver order configurable? Or change it to the following order: ["tiddlySaver", "activeX", "javaLiveConnect", "mozilla"] I have attached a patch detailing the changes I made to twFile.js Any comments are appreciated. I am also thinking of adding a function: $.twFile.ready(handler) that will be called as soon as twFile can process files (it checks by intermittently trying to load the file at "document.location.") John *Notes: twFile driver support (stars* indicate number of security warnings)* ActiveX: IE*** Mozilla: FF* TiddlySaver: IE**, FF, Opera, Chrome/Safari JavaLiveConnect: FF [slight pause], Opera (v <= 10.0)[very slow] [I could swear IE supported TiddlySaver and JavaLiveConnect without security dialogs, but now I can't reproduce it... Just an empty <script> tag results in a warning; JavaLiveConnect doesn't even work.] *Browser versions* IE: 8.0 FF: 3.5.11 Opera: 10.61 + 10.00 Chrome: 6.0 Safari: 5.0.1 *Environment* Windows 7 Lenovo X301 -- www.leftium.com <http://www.leftium.com?sig_gmail> -- 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.
alter_twFile_driver_order.patch
Description: Binary data
