Hi Dave
1. How CSS for the story river, sidebar, etc need to be applied. Nothing I
> try works. Granted, I am no web designer. Particularly interested in:
> background color for the page, and link colors for both story river and
> sidebar, and what to put in front of general CSS for tiddlers to make it
> work.
>
Knowing that may just help me figure out everything else.
>
The big change is that the body element now has the class 'tw-body'. This
was needed because adding support for embedding HTML fragments within SVG
images opens up the possibility of multiple body elements in a document, so
we need the class to identify the correct one.
> 2. In <$list filter="[is[current]links[]]
> [is[current]backlinks[]!is[system]] +[sort[title]]"/>, the results don't
> add line breaks after each item.
>
The <$list> widget doesn't generate any HTML elements by default. If you
don't supply a template then it does fall back to a default that is a div
or a span containing a link and the title of the current tiddler. Whether
you get a DIV or a SPAN depends on whether the list widget is in block or
inline mode. To ensure it is in block mode the list widget will need to be
preceded and followed by a newline. In some situations, you may find it
easier to control things if you specify your own template as the body of
the list widget.
> 3. In a tiddler with this code
>
> -----
> <$list filter="[is[current]tagging[]sort[title]]">
> <$link to={{!!title}}><$view field="title"/></$link>
> <$view field="description" format="wikified"/>
> <$view field="text" format="wikified"/>
> -----
> </$list>
>
> The text loses formatting when entries are displayed: new paragraphs start
> on the same line, and <br> and are displayed.
>
The view widget no longer supports format="wikified". Transclude the
tiddler with <$transclude/> instead (the default title is the current
tiddler, and the default field is the text field).
I forgot to put that in the documentation, but will push an update shortly
with it.
> I am pretty pumped about the clone this tiddler feature!!!! I created a
> bunch of system tiddlers that act as templates - checklist, contact,
> contact list, image link, table with CSS, etc, and made a tiddler with
> clone buttons based on those system tiddlers. The tags and fields get added
> as well as the content. Very cool!
>
Great. As I mentioned in the commit, I don't think it's right that the new
tiddler uses the title of the skeleton tiddler as a base; it means that one
can't use system tiddlers as a skeleton without making the user have a
system title by default.
>
> I will be revising the TW5 mall once I can figure a few more things out. I
> could already start doing a few of the items, but I want to wait until I
> can do the majority.
>
Great, do shout with any other issues.
Best wishes
Jeremy
>
> Blessings,
>
> Dave
>
> --
> 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 http://groups.google.com/group/tiddlywiki.
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Jeremy Ruston
mailto:[email protected]
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.
