Hello,
On Mar 26, 6:01 am, xen <[email protected]> wrote:
> Thank you both.
>
> BookmarkViewTemplate. I don't really like the idea of
> loading the page referenced into an iframe when the
> tiddler containing the bookmark is opened. I'd rather
> just see the tiddler contents and my own data. I
I agree. That's why I made my own template for viewing bookmarks. I
like the idea of a thumbnail image of a site to remind me what the
site was like.
> Why should your
> address book be in addressbook.html and your
> bookmarklist be in bookmarks.html?
Well, it doesn't. You can just use a different template for viewing
the two different types of information.
> I notice that my personal "bookmark" structure might
> not be as universal as I (tacitly) assumed it was.
> Not everone needs "topic", "category" or "summary".
> "description" would be more universal. My bookmarks
> are all about articles. I should call them "article
> bookmarks", "article stubs" or "article nodes". Their
> purpose is to enclose the article itself within a
> metadata wrapper that provides for me a research
> history, research summary, and point of personal
> access. They are really stubs. How to tag them then?
You might investigate Zotero if you really need this level of detail.
Its hard for a general purpose software like TW to compete with an
application-specific design like Zotero.
> But what I would like to do is to make the resulting
> package so easy to modify that you could even have
> two separate systems of bookmarks (one for regular
> bookmarks and one for article bookmarks) that share a
> common tag ("bookmark") and actually display and/or
> manage them using the same interface, as long as they
> have some primary fields in common. "article
> bookmark" would in that respect be a subclass of
> "bookmark".
Well, you could write a template that included all the fields, even if
they weren't needed for all bookmarks. Or a template that turned on/
off fields if you were in one kind of bookmark type. Or, use a naming
system (e.g. bookmark1, bookmark2, ) for different kinds of bookmarks.
> One question: is putting multiple records into the
> same tiddler a Bad Thing? I think the whole slicing
TW is based on tiddlers, which can be thought of as records in other
systems. The underlying available code is based on tiddlers. So it
just makes sense to set up your data to have one-tiddler-one-record.
At least from the programming perspective. The only time it makes
sense to veer away from that model is when you have lots of one-item
data chunks (like grocery list items).
> Actually, Mark, you are also hiding the description
> even though it is not a field; how do you retrieve
> this data if it's not a slice? Do you use it in your
> ViewTemplate?
There are slices, and there are sections. Sections are data between
headers (!!!) and can hold multiple lines including linebreaks. The
description is kept in a section. Think of sections as "memo" or
"note" fields in other database systems.
The /%...%/ hide the contents from the standard wikifier when viewed
without a special template, but don't hide it from code that addresses
slices or sections.
Mark
--
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.
