Hi Everyone This is a lovely thread, it's good to see a suggestion being answered by a prototype so quickly, and congratulations to Andreas
I'd echo Andreas' comments about it not being appropriate for the core yet. The problem that linked images can't be dragged is actually extremely limiting, and is impossible to work around. I don't think that drag and drop (as it is currently implemented) is at all suitable for the underlying need of clipping images from webpages. I think it really needs to be done at the level of TiddlyFox or TiddlyDesktop. Generally, I'd beg you not to be so eager to fold things into the core. What we need at this point is a stable core that supports a rich ecosystem of experiments like this. Each time we put something into the core that isn't solving a fundamental problem we just add to the instability and risk. For TiddlyWiki, 2015 should be the year of the plugin, with the focus of innovation moving away from the core. > From what I see, there are two options: If TiddlyWiki acknowledges the fact that not everything can be put into a tiddler or that there should be the option that not everything should be put into a tiddler (which I think is actually a big question in itself), then (on the node server) either TiddlyWiki adds full support for binary tiddlers AND a good lazy loading mechanism to keep the delivery size/memory footprint of the server to a minimum, or TiddlyWiki adds a seperate storage location for the external files (besides the tiddler folder) and links those files up with tiddlers containing canonical url's. That would also include mechanisms to manage those files. My preference is to add support for serving binary tiddlers and fixing up lazy loading: https://github.com/Jermolene/TiddlyWiki5/issues/1000 > On the standalone single-file version, you can only provide an assistant that makes it more easy to add external stuff (like really a proper copy&paste, easy to manage and use assistant) Yes, I imagine it as a more elaborate version of the current import dialog, providing options for configuring how the incoming data is converted to tiddlers. > or you can provide an automatic way to upload external files to a remote storage location (think CORS service that gets provided the image url on the web and responds with a url representing the saved image) and bake it into the wiki with _canonical_uri or both. I'd certainly like TW to be able to easily integrate with services like that. Best wishes Jeremy, Best wishes Jeremy. On Thu, Feb 19, 2015 at 12:22 PM, Andreas Hahn <[email protected]> wrote: > Am 19.02.2015 um 12:27 schrieb Tobias Beer: > > Hi Andreas, > > >> [1] http://twguides.org/wiki/dropimagePOC.html >> > > Any chance you can make a proposal for the core (pull request) > with some (not necessarily ControlPanel) way > to switch behavior between the (current) default and yours? > > > Hi Tobias, > > Short answer: No. > > Long answer: This is something you can add into your own tiddlywiki, for > personal comfort. However, I do not think this has potential to be added to > the core and also I would not want it to be added to the core. That is > because this is not a permanent solution, but rather something that hides > the true problem. For a proper drag&drop behaviour with proper file > handling, I think a much more elaborate solution is needed. > > From what I see, there are two options: If TiddlyWiki acknowledges the > fact that not everything can be put into a tiddler or that there should be > the option that not everything should be put into a tiddler (which I think > is actually a big question in itself), then (on the node server) either > TiddlyWiki adds full support for binary tiddlers AND a good lazy loading > mechanism to keep the delivery size/memory footprint of the server to a > minimum, or TiddlyWiki adds a seperate storage location for the external > files (besides the tiddler folder) and links those files up with tiddlers > containing canonical url's. That would also include mechanisms to manage > those files. > > On the standalone single-file version, you can only provide an assistant > that makes it more easy to add external stuff (like really a proper > copy&paste, easy to manage and use assistant) or you can provide an > automatic way to upload external files to a remote storage location (think > CORS service that gets provided the image url on the web and responds with > a url representing the saved image) and bake it into the wiki with > _canonical_uri or both. > > Also, these are just my guesses and they all need work and I think it > should be clear what the aim is, before starting to implement stuff like > this, especially if its something that wants to be part of the core. I > however can see functionality like this being provided by a plugin, which I > am sure will be written, when this problem gets big enough, which it > currently is not. > > /Andreas > > -- > 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. > -- Jeremy Ruston mailto:[email protected] -- 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.
