Thanks for your detailed perspective. > >> > talk about stripping TW to its really essential core, externalizing > >> > what's not really essential to external plugins to choose from. It > >> > appears just the opposite happening now ? > > As I say, there's been a lot of discussion over the years about the > microkernel approach, I think it has a rather elemental appeal as a > concept. ... > ... > I don't think there's been a policy change, or it doesn't feel like that to > me. >
So I must have been mislead to think so by these discussions and such stripping of non-essential functionality out of the core and into plugins with Version 2.3. > > Or could 'elsewhere' mean this new approach is actually //adding// > > plugins - not via a systemConfig tag, but by adding them to the core - > > and making the TiddlyWiki core to sort of a code repository to use > > with htmls other than TiddlyWikis? > > I'm not sure if I understand the question. ... > ... > It sounds complicated to have two different types of plugin, but they > are exposed to completely different people. TiddlyWiki users use > TiddlyWiki plugins to extend the platform; jQuery developers may use > the TiddlyWiki jQuery plugins to add TiddlyWiki features to other HTML > applications. > ... > So, making, say, the saving code be a systemConfig plugin really > wouldn't help that situation.. My differentiation lies exactly in modularizing AND replacing existing essential functionality - like the saving code - which I think is a very good idea. And on the other side DOUBLING functionality, which for no uses or plugins are existing yet - as this seems the case with jQuery.twStylesheet, because there are already existing TW ways to toggle css. For such a later case I would wish this would be introduced as a systemConfig plugin, so I would only have to upgrade to, if this would work in any way 'better' - as in this example - to SwitchThemePlugin by Eric, or SelectThemePlugin by Simon. But now it's to late anyway, as I just realized by trying to stripe 2.5.2 of jQuery unsuccessfully: If I want to use TreeviewPlugin I can upgrate to TW 2.5.2 - for all remaining uses I'm free to downgrade :-) > Yes, TiddlyWiki has got bigger - alongside processors and RAM etc. > I've always felt the kilobyte count was a bit misleading; it affects > the time to transfer the bytes of TiddlyWiki to a browser. But it > turns out in most situations it's actually the execution speed of the > code that's the issue, not the loading time. > I agree with you on text bytes and when execution speed is improved with some more js - but certainly not when it comes to additional unnecessary javascript kilo bytes invoked at startup. Though processors and RAM became bigger every year, I hope you don't expect me to buy the latest computer every two years (gosh, just now I would have to get out and get a new one! Despite the notebook I've got working perfectly all right, with the same battery still running for 6 hrs). And what's with the majority of the world population which haven't even got an Internet connection at home, but available Internet cafes with terrible speed at high costs? That will always be the most frequent situation. (And unsustainable consumerism what caused the mess paper money is in now, with much worse still to follow.. or should I say much better? ..when it therefore might come to a full stop in a few decades?) Please don't take my differing opinion - by trying to look at it from a bigger perspective - the wrong way, I greatly appreciate the innovations which were possible by being sponsored by BT. And just as likely could be proven wrong - which in this case I only hope for. However, this just has a little bid the flavor of going the corporate way, for me at this moment. Just some food thought not only for the left side of the brain... kind regards.. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
