Hi Andreas, Hi Yakov, > > I took a look at the FancyBox2Plugin and it is actually quite nice and I > can also imagine something like that for TW5, which brings me to 2 > suggestions I have: > > - While it is totally fine to use TWC, there is a lot to be done for TW5 > and I would presume that TW5 currently has a bigger audience than TWC. > > Yes, sure, TW5 has a bigger audience, but 1) it's a unreasonably difficult for me to migrate all my stuff to TW5 from TWc (including different used extensions) while I'm not very interested in developing plugins that I won't use at all (I mean, for TW5 if I don't migrate); 2) FancyBox is a jQuery plugin and TW5 doesn't use jQuery, so in fact it's better to use smth else for TW5 (LightBox?).
So, the point is, are the efforts of publishing those extensions for TWc are of interest at all? (and which are of greater demand) > - For many plugins it is hard to imagine what to use them for, if it is > not entirely obvious. The reason al lot of people don't end up using > certain plugins is because they see no connection to their use case for TW. > So instead of focussing on individual plugins, which are essentially just > building blocks, you might want to build entire applications with TW so > people immediately see what its used for and the value that it provides. > You are right in several points; that's why I do my best to provide demos/examples in the repositories (and FancyBox repo does contain such stuff). But for yet unpublished plugins, creating demos would require similar amount of efforts as full releases. On the other hand, I use TW in different ways on different devices, so I can't create a repo similar to MPTW which will be built around some "common philosophy" and contain all the extensions (for instance, DisqusPlugin and NightModePlugin will hardly be in the same TW anywhere; or SaveAsPlugin and TwFormulaePlugin). > > /Andreas > Hi Mario, I see your point. I use CodeMirror locally, that's why I'm talking about complicated installation, for TiddlySpace what you are describing should be nice (still, aside including, your version requires changing EditTemplate and ToolbarCommands). In fact, what documentation is missing (to my taste) is a simple how-to-install sequence. If you think it's a good idea, I can establish a separate repository and put there codemirror.js v3.18 and other compatible stuff (may be try to update it at least to the latest 3.x), add my tweaks and cook one plugin (using CookTiddlerPlugin) which is to be supplemented only by tiddlers like tiddlywiki.js and tiddlywiki.css. I think CodeMirror is nice stuff for TiddlyWiki markup itself, only it needs some tweaking of the search options, displaying a newly created tiddler and also it would be nice to combine QuickEdit and AutoSuggest with it. Best regards, Yakov. -- 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/d/optout.
