> Much as I admire Eric's dedication to helping others (including me),
> his post demonstrates precisely what the issue is.
> When you click on his link it tells you how to get started save a
> TW ...etc. Then you get to the customising bit e.g.
> "set styles (optional)
> If desired, edit the StyleSheet to suit your aesthetic sensibilities"
> but there are no instructions/information about how to edit the
> StyleSheet or simply what to do.

TiddlyTools' basics.html QuickStart document is just that.... a quick
starting point.  It's doesn't try to provide an introductory tutorial
on how to use TiddlyWiki or how to write CSS.  Rather, it's purpose is
to merely reduce or eliminate the efforts involved in locating,
selecting, importing, and installing a set of plugins and
customizations that provide basic enhancements to the core TW feature
set.

There are many ways to determine what level of pre-configured
customization is appropriate or desired in any given document.  One
criteria that I used when building basics.html was that it should be a
general-purpose set of enhancements that are not specifically
optimized for any particular use-case.  If your objective is to just
start using the document, "straight out of the box", then you can
ignore the *optional* parts of the GettingStarted instructions, and
just start working.  There's no need to delve into deep 'tech stuff'
if you don't know how (or just aren't interested)... basics.html is
ready for use "as-is".

Of course, if your particular use-case is more complex than just
general information storage, then you might want to start from a
document that has been more highly pre-configured and "tuned" with
just the right set of features for supporting your activities.

This is where such fine documents as Dave's and Morris' fit in... they
are *also* excellent starting points... if you want/need those
features.  Of course, if you want to start adding customizations
beyond what is pre-installed, then a certain amount of TW-specific
skills and knowledge are needed, regardless of how simple or complex
the initial document definition is.

Nonetheless, I definitely agree that there's an obvious gap in
TiddlyWiki documentation, especially in regards to how to make
customizations.  I've been working on writing a guidebook/technical
reference, "InsideTiddlyWiki", off and on for quite a while, but it's
been slow going (I keep getting sidetracked), and it's no where near
ready for sharing... and it's probably going to be more technical than
what you are hoping for.  If you'd like to offer suggestions for
topics, it might provide me with some direction to help spur my
writing.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to