Tobias said: > The main intention of any "bare-bones" edition — as I see it — would probably not be to create alternative wiki-ui's, but to have a bare core that runs smoothly, ui-less that is (less ui) ...and then a step by step implementation of things maybe a published "site" might need, a result that is not meant to be edited like TW, however TW perhaps being the editing environmnent that created it, perhaps using node.
That sounds to me that the goal of the "bare bones" edition is to start again with a simpler UI. That's already do-able without having to fork the core plugin; as discussed above, one just redefines $:/PageTemplate to create a custom UI. The only goal I'm hearing for the slimmed down core plugin is to save space. As I've said before, there's much easier ways to achieve that goal. Just imagine that we did create an alternative core plugin that had less in it. Then every change to TW, and every change by every plugin author, would need to be verified in both environments. The workload is terrifying for a project like this. Best wishes Jeremy. On Tue, Sep 22, 2015 at 12:21 AM, Rustem <[email protected]> wrote: > > On Saturday, September 19, 2015 at 4:21:37 AM UTC-7, Jeremy Ruston wrote: >> >> ... I worry that this discussion will devolve into a long debate about >> which shadow tiddlers to omit ... >> >> You had no idea :) > > -- Jeremy Ruston mailto:[email protected] -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAPKKYJYrzS7eJymgTA-PzGOeUdq_wALx8_gmGuS-NN%2BFH9SACg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
