Displaying Linked Tiddler at Current Location

[Robert Pollard]

Friends,.

Is there a way to have the option of tiddlers opening immediately at or below a tiddler link, comparable to what is made possible for external links with Eric Shulman's FramedLinksPlugin

Robert

[wolfgang]

Hi Robert,

Would sliders not do what you want?

Regards,

W.

> FramedLinksPlugin<http://www.tiddlytools.com/#FramedLinksPlugin>
>
> Robert

[Eric Shulman]

> Is there a way to have the option of tiddlers opening immediately at or
> below a tiddler link, comparable to what is made possible for external links
> with Eric Shulman's

> FramedLinksPlugin<http://www.tiddlytools.com/#FramedLinksPlugin>

You can use a basic slider to do exactly that... here's the macro
syntax:
<<slider chkMyCookie MyTiddler "label" "tooltip">>

where:
* "chkMyCookie" is used to remember whether the slider is opened or
closed, and restores that state the next time the slider is rendered.
* "MyTiddler" is the tiddler whose content will be displayed in the
slider panel.
* "label" is the clickable link text, and
* "tooltip" is text automatically displayed by the browser when you
mouseover the link.

In it's simplest form, omitting the cookie (so the slider always
starts out closed) and using the tiddler name as the label and tooltip
text, you could just write:
<<slider "" MyTiddler MyTiddler MyTiddler>>
which results in a MyTiddler "link" that opens the content directly
*inline*.
QED.

----------------------------------

Once you've gotten used to using the core's <<slider>> macro, you
might want to also have a look at:
http://www.TiddlyTools.com/#NestedSlidersPlugin

This plugin adds an 'inline' wiki syntax for sliders so that they
don't need to use separate tiddlers for holding the contents of the
slider panels. As the name implies, the syntax also permits you to
'nest' sliders, one inside the other (for as many levels as you
need!). In addition, the plugin offers many other useful features:

* toggle alternative labels - show different text for opened vs.
closed slider panels (e.g., show/hide, more/less, etc.)

* accelerator key assignment - open/close a slider with ALT-SHIFT-
letter

* floating sliders - instead of pushing other content aside when they
are opened, these panels "float" on top of other content, like a
separate window (though NOT an actual window... just an 'absolute div'
in the current page).

* transient sliders - only one slider open at a time, and clicking
anywhere outside the slider closes it. Useful for creating
"accordion" effects in vertical menus, and short-term 'popup dialog
boxes' using floating sliders (see TiddlyTools' main menu items:
About, Download, Contact, etc. for examples)

* deferred rendering - a.k.a, "lazy sliders"... normally, the slider
panel content is processed immediately upon rendering the slider, even
if the panel is initially closed. When deferred rendering is used,
the panel content isn't rendered until the first time the panel is
actually displayed. This can be VERY useful for managing slow
performance issues for content that takes a lot of processing, such as
[[TabTimeline]], which has to read through the entire document to
format and render it's output.

... plus several other features.

Here's an example of a use of nested sliders:

+++[get info...=I|click for information or press Alt-I]
put some general information here,
plus a floating panel with more specific info:
+++^10em^[view details...|click for details]
put some detail here, which could in turn contain a transient panel,
perhaps with a +++^25em^*[glossary definition]
<<tiddler GlossaryItem>>===
===
===


enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[wolfgang]

> * deferred rendering - a.k.a, "lazy sliders"... normally, the slider
> panel content is processed immediately upon rendering the slider, even
> if the panel is initially closed. When deferred rendering is used,
> the panel content isn't rendered until the first time the panel is
> actually displayed. This can be VERY useful for managing slow
> performance issues for content that takes a lot of processing, such as
> [[TabTimeline]], which has to read through the entire document to
> format and render it's output.

One question about deferred rendering:

Tabs actually render their content only when a particular tab is
opened.
Therefore, what's the reason this isn't the case with ordinary sliders
too?

Regards,

W.