> With this fabulous trick by Eric I just reduced QuickEditPackage > (without StyleSheetSortcuts) from 53040 bytes (19 tiddlers) down to > 37679 bytes within 2 tiddlers - while only remaining dependent to > StickyPopupPlugin - and having added quite some custom formats!
* All necessary 'supporting' functions are contained in QuickEditPlugin, so StickyPopupPlugin is not needed. * Using a single plugin to load the supporting functions as startup is MUCH more efficient than constantly re-defining all those functions every time each QuickEdit button is rendered, which can result in increased memory usage and a general slowdown in performance due to increased 'garbage collection' processing and well as the potential for 'memory leaks' in some older browsers. * Individual QuickEdit buttons are stored in separate tiddlers so that specific buttons can be optionally transcluded simply by adding/ removing the appropriate <<tiddler>> macro in QuickEditToolbar (or just delete the referenced QuickEdit_* tiddler and leave the macro in place). Separate tiddlers also makes it easier to change the order of the buttons or add your own buttons without having to edit a massive, monolithic tiddler full of code. * Using sections to define the fontList and customFormat lists will break the "[edit list...]" command that is included in the droplists. The list definitions really should be kept in separate tiddlers so a standard tiddler editor can be used to view/modify their content without having to wade through all the QuickEdit code. * Most of the size savings you report were achieved merely by removing the separate documentation (slice table and usage) from each tiddler when you combined the QuickEdit_* tiddlers. > Or, for example, MiniBrowserPlugin, by using its last inline script > before it was converted, from 16683 bytes down to 8450 bytes: > http://menuflex.tiddlyspot.com/#Browser While you are free to use whatever obsolete scripts you want, I'd strongly prefer that you *don't* re-distribute this inline script, which I retired and removed from distribution a very long time ago. > Eric, is there a good reason for still keeping such Plugins on one > hand dependent to InlineJavascriptPlugin - on the other, why keep them > even dependend to a systemConfig tag at all, as they appear working > almost as well without? There was only one minor use of inline scripting, which was in [[QuickEditToolbar]]. No other parts of QuickEditPackage depends upon InlineJavascriptPlugin in any way... and, spurred in part by your experimentation, I've now eliminated the dependency in QuickEditToolbar as well (by using the <<tiddler {{code;'';}}>> technique). The *only* dependency is to install a single 'systemConfig' tiddler: QuickEditPlugin. enjoy, -e --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
