Josiah,
You last post was clear and I "get it", I understand the need to TiddlyWiki
to have a more obvious usage, the new users are not seeing tiddlywiki at
its potential best, and it is hard for them to get the vision shared by
enthusiasts.
I am sure I don't have the full answer but can I suggest you reread my last
post and imagine the approach I am suggesting, although I have not detiled
all the possibilities.
To be clear, I am trying to answer your Question, and if it is not,
consider if this set of ideas is still the answer :)
I agree the answers are bleeding obvious, lets make the required features
bleeding obvious.
As I say "If you can see what I am doing here, is building in features that
help me achieve a lot through an intuitive addition to tiddlywiki to
turbocharge the development of existing and future tiddlywikis"
I believe the gap you are seeking, the missing piece(s) to fill, is not in
the core, or in finished examples, but in features that help expose to the
imagination what can be done, and make this, what can be done, easier. I do
not believe another SHOWCASE is necessary if it can only be created by a
developer.
I will give another example "Tags"
Tagging tiddlers is a key feature of tiddlywiki, and even drives its whole
structure, however we do little to illustrate what tags can be used for by
the end user, and when we do those features can only be achieved with
plugins and code so there is a barrier to realising the potential of tags,
people will get there eventually, but only if they do not abandon
tiddlywiki first.
Here is an example of what is difficult for new and enthusiast alike to
discover easily; its used to illustrate my point below.
Tags can
be used like tags in other systems
be uses as categories
build lists
indicate membership
show status
capture hierarchies
capture network relationships
alter appearance, or hide and display content
use color in tags and tiddlers
be sorted, in lists and within tag line
be documented in a tiddler of the same name
be managed as a list within a field
be dragged and dropped to move
and more
The point is using tags to do the above, is what the user wants to learn
and do, and it is not straightforward to do these things. Needing to resort
to plugins or particular editions is overkill when you are learning.
I believe we need to fill this gap with techniques and helpers to maker
these things obvious and easy.
This is a solution for a Specific Example to illustrate, Using tags to
indicate status, requires something like cycletags, which allows you to
step through a set of statuses eg; "new wip completed" removing the last
when assigning the next. Why cant we create a tag/tiddler called status and
use new here to create "new wip and completed" tiddlers tagged with status,
then set a value on status that says when used as a tag allow an OR
selection of tagged tiddlers. This feature with an AND selection could
allow tagging with one or more tags.
Simple problems are solved quickly and all that remains are new and
difficult problems. I think this problem is haunting us because the answer
lies between the core and plugins yet needs to answer the needs of the user.
I am ready to proceed.
Tony
--
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/d0d59150-9fa5-4924-9e79-4d203680d889%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
