Hi Kafran, I don't know if the Nathan's code was really a good and necessary > improvement but it was possible because someone found the error. And this > is how I can contribute, using the tool in my way, with all the > possibilities to go wrong ^^, and report the errors, what I think good or > bad, easy or hard, etc. > > =) >
Sure, that's all certainly very welcome, no doubt about it. I'm mostly concerned about emerging patterns that suggest quick-wins which ever so swiftly turn out a chronical disorder in terms of "But I am now used to just drag and drop stuff into it. So, what could possibly be 'wrong' about that?" Especially when discussed often, these things creep in rather quickly and thus require debating the same problems over and over while there is a cure to that "desease", more sustainable patterns and expectations, that are equally straight forward. In fact, I believe they should be worked on instead. Dropping an image onto TiddlyWiki might just as well result in it being persisted as an image file... at least I don't quite see why TW should be able to save itself, some text files or rss, yet not those binaries which nowadays can be embedded using Base64 encoding. And, if there's a serverside storing mechanism, or some authenticated image hosting service, PUT the binary there ...as configured ...or selected from configured options... and then use this very reference in the wiki markup... Github-style. Their image uploading mechanism is top-nudge. Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
