Perhaps you did not notice yet but on your comment;
*So much discussion here is on "technical means" not "final aims/ends" I
think we in in danger of excluding some kinds of user who is looking at TW
to achieve exactly that issue about posterity.*
I some ways this is my key focus, I am keen to develop, and have started, a
whole range of tools that make tiddlywiki more accessible, and to unlock
more of its fundamental features without others having to resort to code or
prepackaged solutions. These tools need to be intuitive, respectful of the
powerful underlying principals yet quick and easy to use by a novice.
Here is some examples
- The tagging system is exquisitely powerful, but using tags to set and
change "status", develop tags for keyword search and document the purpose
of tags is all unstructured.
- Fields provide a highly extensible environment, but using them to
collect data in a form, or documenting their usage is also unstructured.
A lack of structure gives rise to more possible permutations but we can
have structured layers that support common uses without compromising the
underlying philosophy, in fact I would argue we can extend the philosophy
into a usability perspective.
I have n enormous list of "features" I want in tiddlywiki, its not that you
cant already achieve them, its that they cost too much time to acquire, and
the often have unforeseen consequences, if they are not crafted in such a
way as to not result in compromises.I do not want to tax the community too
much so I am developing these solutions myself and will publish them in
time. However I would love some help.
Now this may sound like a newbie desperately seeking knowledge, but I can
confidently say I am no longer a newbie. The thing is if I do not have
quick easy and adaptable ways to achieve reoccurring needs I am slowed down
in the sophistication of the solutions I can develop.
Here is an example;
I have extended the existing edit template view of fields to provide a link
to a tiddler by that field name (a field tiddler).
It allows me to document the purpose and use of that field, even list
tiddlers using that field
I would like to add an Info Icon that shows a tooltip for each field,
ideally from a tooltip field in the "field tiddler"
This would allow someone to lookup the purpose of a field, and define (self
Document) their own fields.
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.
If I had a bit more cash-flow I would fund a crowd-sourced competition to
provide such solutions. Someone with coding skills could do this more
quickly than I, and would win some funds as a result. The advantage to me
is I would be able to reduce development time and produce more solutions.
I think in someways Josiah, you come from a similar perspective to me. What
I can bring to the community is a clarity of design and requirements that
have both technical strength and usability strength. After all I have a 30+
years of professional experience doing such things. The difficulty is
obtaining a reputation in the community and having people in the community
valuing and responding to these suggestions. I need this reputation because
although I welcome suggestions and criticism of these ideas, I also need
people to share my vision and implement them.
Some more food for thought!
PS On this occasion I have found it hard to buy into the Grannie metaphor.
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@example.com.
To post to this group, send email to ***@googlegroups.com.
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/42d5def7-470b-4391-959a-ea454e2ec629%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.