Andreas > sorry I am responding so late, but I didn't have time earlier. > > #heheh you are super fast and thanks for responding with the solutions. Once I read your post I said d'oh!!! like three times
> I dragged from Firefox to Firefox the "Drag *this*" file and this error > came up > I tested with Chrome too and the same issue > Undefined widget 'dropimagezone' > > This suggests that after dragging, you didn't reload (which you should > do, because TiddlyWiki only loads the widget after a reload). Changing the > PageTemplate while the widget isn't loaded will result in this error, since > the PageTemplate changes immediately > Yes this was 'dumb' of me.(d'oh!!! #1) You drag and drop the drag 'this' from your site and SAVE and then RELOAD > > I saved the Firefox version and reloaded the browser and this shows up > at the bottom of the page > > </$navigator> > > </div> > > </$set> > > </$set> > > </$set> > > </$set> > > </$set> > > Hmm take a look, if the <$/dropimagezone> tag is correctly placed. I > had this happen in my tests a few times, but in all cases it was caused by > tags not being closed properly in the PageTemplate > So if you open the <$dropimagezone> twice that won't work correctly #heheh. d'oh!!! #2 Open then CLOSE </$dropimagezone>(mistake above) I really opened it twice so really d'oh!!!! > When it comes to the cross-browser dragging issues, then you are correct. > I noticed that while testing too. Fro CHrome and Firefox, this happens: > > > * Chrome -> Firefox : The image URL is dragged as pure plaintext, which > makes TiddlyWiki not recognize it as a URL. In this case you see the old > behaviour of it being put in the tiddler text as normal link. This is > theoretically fixable, since the same URL recognition just has to be > applied to plain/text drags too. This case also applies to pretty much all > other URL's dragged in from other application, such as an editor, your > email client, word/excel and so on. > > * Firefox -> Chrome: The image somehow gets transported as binary data ? > .. Or Firefox encodes the actual image.. but then converts the MIME type to > image/bmp, which causes TiddlyWiki to create a weird tiddler with a "*.bmp" > name and unreadable binary data inside with lots of funny little black and > white questionmarks in it. However, this really confused me in my tests and > all I can say here is.. it just doesn't work and whatever Firefox > transmits, TW can't handle it at the moment. (Looks like it triggers the e > file import routing though) > Phewww no more d'oh!!! Thanks for testing this as I thought I might have been going a bit looney when I was testing. Now that I have fixed all the Open and Closed <$dropimagezone> </$dropimagezone> and made sure to save and reload before changing that, EVERYTHING works GREAT. So again this is fun to work with and makes my life easier. Rich Shumaker -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
