Eric Shulman wrote: > Scott Sauyet wrote: >> using TW5 for something that might be slightly off the beaten path >> for TiddlyWiki. > There is no "beaten path" for TiddlyWiki5... there's a lot of power > and potential in the new architecture, and the ability to create a > highly customized presentation and user interaction has always been a > key feature of TiddlyWiki.
That's what I was seeing. I'm glad to hear that it doesn't seem out-of-bounds to use it the way I'm suggesting. >> [ ... ] >> <http://ramdajs.com/tw/tiddly.html> >> >> There's still plenty to do, of course. But I would like some feedback >> about both the feasibility and the rationality of the approach before I >> put too much more into it. > Without even looking at your proof-of-concept... I can easily say that > TiddlyWiki lends itself very nicely to documentation projects... > especially those with very formalized structures, such as API > references, code samples, etc. Perfect! >> [... questions about read-only API ... ] > TiddlyWiki has long been used to provide "read-only" presentations. > Because the interface is intended to be customized to your specific > use-case(s), it is relatively easy to hide the editing features, > while retaining the full TWCore functionality 'behind the scenes'. That's what I was hoping. It seemed to be the case, but I wasn't certain, as I've never tried to use it that way. > Read-only TiddlyWiki5 documents can be served locally via nodeJS, or > written to a single-file, stand-alone HTML document for easy sharing. > You can also use TiddlyWiki5 to generate static output for each > tiddler, allowing you to publish a set of simple HTML files for > online reading, without *any* underlying code at all. That might also be useful to us. >> If doing that seems reasonable, then I would like to know if there are >> decent references around to show me how to turn a TW into this read-only >> mode. (What I saw about `zzConfig` or some such I think had something to >> do with older versions; at least it didn't work when I tried it; perhaps >> the old `systemConfig` is no longer very useful.) > Indeed, 'zzConfig' and 'systemConfig' tags are part of TiddlyWiki > *Classic*. I suspected as much, and I think I've already started to see some of the replacement, but I haven't gotten my head wrapped around it yet. > Plugins and configuration work somewhat differently in TiddlyWiki5. Is there any documentation yet? Or should I just plan on poking around and asking questions when I get stuck? > Although documentation for TiddlyWiki5 is still fairly sparse, there's > a very active group participation here. You've provided quite a bit of > detail in your "brief" outline of goals you are trying to achieve, so > I'm sure people will be able to address your specific issues and ideas > in follow-up responses. Is there a central location for whatever documentation does exist? I did see some very good high-level architectural documents, but that doesn't help with the day-to-day stuff. Thank you very much for your help. -- Scott -- 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.
