I simply wanted:
1) A table with several rows for better visual overview
2) Yet another way to benefit from a list, that I already use in
another context.
a) For each new use of a source (list) - inside the same TW the
nearer it gets to be a real database.
b) Economics - less input - more output - I like that!
3) I wikikilinked the listitems in the hr-list (with double brackets)
- which I use in the Qoute of the dayPlugin - to open the
corresponding tiddlers from their titles in the QOTD - Quite handy. -
a) I use of the Qoute of the day Plugin to autogenerate proposals
for sets of songs (repertoire).
I can click near the title and get a new proposal - or click
directly on the songtitle - and open the songs tiddler. (I've made
tables with several QOTD's to get a list of different songs each time
I refresh display )
b) In the table with all songs from the songbook I get an overview
- and the ability to click a title to open a song.
Songtitles are often short - and they fit nicely in a large
tablerepresentation ...
A very long hr-list with small list items doesn't provide a
good overview - and it seems like a waste of space - when you have to
do a lot of scrolling..
I haven't finished modifying the hr-list yet - I'd like to add
toggletags to each listitem - ...
I hope this answers your question..
Regards Måns Mårtensson
On 7 Sep., 17:33, Tobias Beer <[email protected]> wrote:
> Sorry, no Danish language skills on my part... What's the general purpose of
> your table as compared to the tiddler simply containing the hr-separated
> list?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
