Hi Eric, On Mar 7, 6:48 pm, Eric Shulman <[email protected]> wrote: > However, it would appear that, based on your research, an 'dragover' > event listener is needed: > > window.addEventListener('dragover',  // FireFox3.6+ >  function(e){e.stopPropagation();e.preventDefault();}, true); >
I added this to the FileDropPlugin with the other window addEventListener code, and it worked like a charm. What I don't understand is what this code is inside a "if(!window.event)" structure. I'm sure there's a good reason, it just seems counterintuitive ... like why isn't it inside a "if(window.event)" structure instead? > I agree that it seems the FF people are moving forward without > worrying about backward support for existing pages.  However, I think > you are overstating the problem with regard to TW: nearly all > functions in TW are cross-platform compatible, or have well defined > platform-specific alternative implementations (when possible). > ... > Regrettably, some browser implementations are non-standard or > incomplete.  Nonetheless, TW can operate with a reasonable degree of > success on FF, IE, Opera, Safari, and Chrome, as well as other webkit- > based browsers. Its not the cross-platform issues that concern me. In many ways TW does well on that score, under FireFox. But in many ways TW is really a Firefox application. Sure, you can use it with other browsers, but saving is only possible with a supporting java file and/or, in the case of Internet Explorer, administrator level rights. MS has made the "local" zone on your computer, out of the box, both more restrictive AND hidden from non-nerd users (for our protection, we're told). I believe saving is currently AWOL on Opera 10 even with the saver file. Unless you're running some sort of kiosk, saving is essential to any modern application. And advanced features, like drag-drop, embedded file attachments, and advanced CSS manipulations are only available under FireFox on a windows system. And the problem with Firefox is that they're releasing updates at a maddening rate. And their latest "feature", reminiscent of something the Redmond giant would do, is to block old add-ons from working (for our protection, we're told). So supporting applications, like Zotero and Tiddlysnip are breaking at regular intervals. Its hard to build a work-flow around tools that are going down every two-weeks. But my overarching concern with TiddlyWiki is TW5, which, if I understand correctly, will mean that virtually all plugins that we've come to depend on will cease. Which in turn means that any TW-based tools and work-flows one has come to depend on will also be functional orphans. Which wouldn't be so bad, if the underlying technology, firefox, wasn't mutating constantly. When file drag-dropping suddenly breaks in firefox, and TW has moved on to vsn 5, how likely is it that authors like yourself are going to be willing to go back and fix the plugin? If I'm wrong about everything breaking under TW5, it would be comforting to know this. Or if the probable development of TW5 is a couple years out, that would be good to know. For those of us not on the cutting edge, I might point out that none of the major publication players (O'Reilly, Wrox, Riders) are releasing books on HTML5 (basis for TW5) until Spring/Summer 2010! Thanks, 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.
