On Tuesday, July 29, 2014 2:12:41 PM UTC-7, 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.
> I would like advice about whether it's worth pursuing, and,
> if so, further advice about how to accomplish certain goals.
>
> A friend and I have been developing a functional programming library in
> Javascript [1] ... deal with ... documentation... TW has pretty well
>
everything that I would want...
>
<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.
...what I really want to do is to remove everything which makes this a
> dynamic Wiki, leaving behind only an excellent micro-content viewer.
> I have no idea yet how to do any of that, but before I even ask about
> that, I first want to know if this seems so antithetical to the spirit
> of TW that I'd offend people here by even trying it. You see, although I
> really love TiddlyWiki for what it is and what it can do, I also really
> like the UI it presents for simply viewing micro-content. That's all I
> really want to use from it in this case.
>
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'. 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.
> 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*. Plugins and configuration work somewhat differently in
TiddlyWiki5.
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.
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
YOUR DONATIONS ARE VERY IMPORTANT!
HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
http://TiddlyTools.github.com/fundraising.html#MakeADonation
Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact
--
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.
