List of Open Tidders

[Trey]

Hello All,
I'm looking for a plugin (or method) that will let me display a self-
updating list of all tiddlers that are currently open.

I think I remember there being a plugin by Mr. Shulman to auto-refresh
a certain tiddler every time the display changes...so if there is a
forEachTiddler script to list "open" tiddlers, the combination might
work.

All suggestions appreciated. Thanks!

Trey

[PMario]

Have a look at TW toolbar "more: jump" command.
-m

[colmjude]

I'm sure the AMBIT project uses something that would meet your
requirements. They have a "You Are Reading" section in the sidebar
which mirrors what is open in the story.
I think the plugin they use is called " YouAreReadingWidget"

You should be able to find it here:
http://ambit-theme.tiddlyspace.com/

Hope that helps

Colm

[Bauwe Bijl]

Hi Trey
Perhaps the BreadcrumbsPlugin is something to use?

http://tiddlytools.com/#BreadcrumbsPluginInfo

Bauwe

[rakugo]

No need for plugins for this in the latest TiddlyWiki alpha version
which can be downloaded from http://tiddlywiki.com/alpha/empty.html

You just need to do:
<<list all template:Template>>

and create a tiddler called Template with text
<<view wikified text>>

I'm not sure how long it is still the next TiddlyWiki release... but
would be great to get people using the alpha and giving feedback.

Best wishes
Jon

[rakugo]

Forgot to add..
There is some code in http://filters.tiddlyspace.com/recipes/filters_private/tiddlers/ExtraFiltersPlugin.txt
which provides a filter [is[open]]
so you would be able to do
<<list filter [is[open]] template:Template>>
to display all open tiddlers in a refreshable list.

I think this code is TiddlySpace specific but doesn't need to be... so
I would be happy to refactor the code if it's of use.

Best wishes
Jon

On Jun 15, 11:22 am, Bauwe Bijl <bauweb...@gmail.com> wrote:

[rakugo]

There's a proof of concept here:
http://frankenstein-plugins.tiddlyspace.com/#%5B%5BList%20Open%20Tiddlers%5D%5D

On Jun 15, 12:49 pm, rakugo <jdlrob...@gmail.com> wrote:
> Forgot to add..

> There is some code inhttp://filters.tiddlyspace.com/recipes/filters_private/tiddlers/Extra...

[rouilj]

On Jun 14, 2:19 pm, Trey <ionobr...@gmail.com> wrote:
> Hello All,
> I'm looking for a plugin (or method) that will let me display a self-
> updating list of all tiddlers that are currently open.

Try looking for the DisplayOpenTiddlersPlugin. It puts a list of open
tiddlers
at the top of the story column, so it may not be exactly what you want
but you
could use code from it to fulfill your use case.

-- rouilj

[Trey]

All,
Thanks very much for this detailed list of options. These solutions
are exactly what I was looking for.
I like the ambit implementation, because it includes functionality for
closing a tiddler from the list, I was hoping for that.
I'm going to try to modify it to display a custom tiddler field
"summary" I have created, as well.
Again, thanks.

Trey

[Yakov]

rakugo,

that's great news! Is it planned to introduce the represent-by-
template mechanism into all the "list" macros (list, timeline, tag,
tagging, tags, allTags)? It's a great step forward since it's a
separation of selection and representation. Though, for complex
selection plugins are usually used, so it's not that simple with just
"separation".

Another thing I can see in frankenstein-plugins is that the list is
live-updating which is nice too.

Trey,

you really should try this since template can contain toolbar macro as
well which in turn can contain "close" button (presumably it will
close the opened tiddler).

[Trey]

Sure, that seems less complicated - use of built in macro vs. plugin,
for one thing - but, I'd like to display other fields like my custom
defined "tiddler.fields.summary". Will the template specification be
able to handle that? If so...a very powerful function and one I'm
excited for. How stable are the alphas?

[Trey]

Unfortunately after messing around with the Ambit YouAreReading plugin
for several hours, I noticed that it disabled all in-tiddler links.
Not competent enough to debug it. I'll try the alpha version with
built in filter functionality tomorrow.
Trey

[Yakov]

> I'd like to display other fields like my custom
> defined "tiddler.fields.summary".  Will the template specification be
> able to handle that?

Depends on what do you mean by "display". If you want just display
text which is the value of a field, it should be as simple as

<<view customFieldName>>

(you can check this with a current version of TW by adding this thing
into the veiw template and <<edit customFieldName>> into the edit
template)

> How stable are the alphas?

It's a question of testing. As you really want the feature which is
provided by the new code, your testing will be especially valuable.
Of'course developers don't add bugs so it can be called alpha, it's
just usual practice -- first software is created, next it's tested,
then it's fixed and so on.

[Yakov]

> <<view customFieldName>>

Oops, sorry, I mean <span macro='view customFieldName'></span>.

[Trey]

I guess it's a bit of a silly question, of course alphas have
bugs...but not all alphas are created equal :)
I will check it out soon, I've been messing with my TW too much,
neglecting other responsibilities. I'll post here when I get some
result though.

[Sub]

Please let us know if it worked with the alpha. I couldn't get it
working as described above.

[Eric Shulman]

> > How stable are the alphas?
>
> It's a question of testing. As you really want the feature which is
> provided by the new code, your testing will be especially valuable.
> Of'course developers don't add bugs so it can be called alpha, it's
> just usual practice -- first software is created, next it's tested,
> then it's fixed and so on.

In addition to early testing of the code, Alpha's are, in practical
terms, a "field review" of the specific functionality and design for
new features. This is especially true for TiddlyWiki, which has no
formal design proposal and review process.

In this particular instance, one design concern I have is the use of
"template" to refer to a tiddler that contains *wiki-formatted*
content. However, the well-established TiddlyWiki template system
(i.e., PageTemplate, ViewTemplate, EditTemplate) uses HTML-formatted
content... and, with the use of TiddlyTools' TaggedTemplateTweak, this
method is already widely-used to display alternative renderings of
tiddler content. Of course, rendering tiddlers from wiki content
'templates' allows for simplified formatting, which is all that is
needed for *some* use cases.

What I would like is for TWO new parameters, "template:TiddlerName",
would apply the TWCore standard template processing to render output
from HTML, while "format:TiddlerName", could apply wikify() processing
to render output from wiki syntax.

This would provide a more complete solution, enabling use of the
TWCore's HTML template syntax as an alternative when wiki-syntax
formatting falls short, or when you just want to re-use existing
custom templates that already format the tiddler output as desired.

Your thoughts?

-e

[Måns]

Hi

>... and, with the use of TiddlyTools' TaggedTemplateTweak, this
> method is already widely-used to display alternative renderings of
> tiddler content.  Of course, rendering tiddlers from wiki content
> 'templates' allows for simplified formatting, which is all that is
> needed for *some* use cases.

I do that all the time via the <<tiddler>> macro embedded in custom
HTML formatted Edit- and ViewTemplates - like this: <div
macro='tiddler TiddlerTitle'></div>. TiddlerTitle is often a tiddler
with a wikitable and some wikiformatted macros like <<wikify %0
somefieldname@>> which work fine. (I know I can use the wikifymacro
directly in a ViewTemplate, but I like to be able to make simple
wikitables )

If I however want to embed the <<edit>> macro in a wikiformatted
template I have to use HTML syntax like this:
| Contact:|<html><span macro='edit contact'></span></html>|
| Phone:|<html><span macro='edit phone'></span></html>|

if I want it to work in all situations...

> What I would like is for TWO new parameters, "template:TiddlerName",
> would apply the TWCore standard template processing to render output
> from HTML, while "format:TiddlerName", could apply wikify() processing
> to render output from wiki syntax.


> This would provide a more complete solution, enabling use of the
> TWCore's HTML template syntax as an alternative when wiki-syntax
> formatting falls short, or when you just want to re-use existing
> custom templates that already format the tiddler output as desired.

Would this make TaggedTemplateTweak redundant?

Cheers Måns Mårtensson

[Eric Shulman]

> > This would provide a more complete solution, enabling use of the
> > TWCore's HTML template syntax as an alternative when wiki-syntax
> > formatting falls short, or when you just want to re-use existing
> > custom templates that already format the tiddler output as desired.
>
> Would this make TaggedTemplateTweak redundant?

not at all. TaggedTemplateTweak is a *selector* of templates, invoked
directly by the TWCore whenever a tiddler is to be displayed. It
applies a series of tests and rules to determine which template to
use.

In contrast, the "template:..." and "format:..." parameters I
suggested are for use within *macros* such as <<list [tag[...]]
template:...>>.

Note: I have a plan to similarly extend the <<tiddler>> macro, so that
you can write:
<<tiddler TiddlerName template:SomeTemplateName>>
to render the tiddler using TWCore HTML Template syntax instead of
just wikifying the tiddler's *text* content. I'll post a follow-up
when I've got something coded.

enjoy,
-e

[Trey]

Rakugo: I tested your suggestion.

However I'm a little confused: your first post doesn't seem to address
my question, it simply lists all tiddlers, regardless of their being
open or closed.
As you indicated in your second message, the plugin that enables the
isopen filter doesn't work in TW releases, apparently not the alpha
either.
The version you have enabled on tiddlyspace (frankenstein) is exactly
what I'm looking for (as I said above, the Ambit plugin caused all my
in-tiddler links to stop working). It looks like the template would
be very easy to modify too.
If you are willing to refactor that code, I for one would certainly
"test" it for you :)
Would that require using the latest alpha? Don't really mind, just
wondering.

Long Live TiddlyWiki

[PMario]

On Jun 19, 9:42 pm, Eric Shulman <elsdes...@gmail.com> wrote:
> What I would like is for TWO new parameters, "template:TiddlerName",
> would apply the TWCore standard template processing to render output
> from HTML, while "format:TiddlerName", could apply wikify() processing
> to render output from wiki syntax.

I think this would be a good issue at TW github [1], if you could
decide to jump in there :)

> This would provide a more complete solution, enabling use of the
> TWCore's HTML template syntax as an alternative when wiki-syntax
> formatting falls short, or when you just want to re-use existing
> custom templates that already format the tiddler output as desired.
>
> Your thoughts?

+1

-m
[1] https://github.com/TiddlyWiki/tiddlywiki/issues

[Trey]

Jon- I actually just noticed that your implementation sorts open
titles alphabetically. Is there a way to make it simply append newly
opened titles, or somehow more closely reflect the real organization
of the page? Based on what I know about TW list-sorting options, that
sounds kind of intractable with your method.

I already have the Ambit code working, except for this problem where
it messes up all my links. This discussion here has gone in other
directions so I am going to post a new topic - anyone please check it
out and help me fix Ambit for non-tiddlyspace use if you've got the
know-how.

Trey

[rakugo]

Yakov - the timeline macro already has this functionality. The same
was done for the allTags plugin but this has not yet been folded into
the alpha - the groupBy macro provided in TiddlySpace by the
GroupByPlugin [1] allows you to group by things other than tags -
fields and attributes. It probably needs a bit of attention and
feedback on usage of the list/timeline macros before being considered
for the core though.

Trey - as Yakov points out pretty much anything can go into a
template - to display a field bar you can run <<view bar text>> or
<<view bar link>> or <<view bar wikified>> depending on what the field
contains. As Eric quite rightly points out alphas are a field review
and a great time to say things like "this is wrong", "why doesn't it
do this" etc. It also speeds up the process as it increases demand for
a new release.

Apologies, for the confusion I caused. Essentially I was recommending
using the alpha, as the list macro was rewritten with the purpose of
supporting this kind of thing and allowing more freedom to customise.
I've done some refactoring of the code now, and basically with the
latest alpha all you should need is:
https://raw.github.com/jdlrobson/TiddlyWikiPlugins/master/plugins/Filters/StoryFiltersPlugin.js

Note the syntax has now changed and you should use the filters
[story[open]] and [story[sort]] to get the list.
<<list filter "[story[open]][story[sort]]" template:TemplateOpen>>
should be all you need to generate the correct list of tiddlers.
The template at http://frankenstein-plugins.tiddlyspace.com/#TemplateOpen
should give you some ideas on how to format you tiddler.

On the subject, Eric, I completely understand your concerns - it would
be great if this conversation - and the one regarding tiddler macro -
could be started on the TiddlyWikiDev group. In my opinion you should
be able to mix the two but I have slightly differing views on the
how...

Enjoy!

[1] http://tiddlyspace.com/bags/system-plugins_public/tiddlers/GroupByPlugin


Hi Trey

[Trey]

Jon,
Thanks for your work! I will try it out tonight.
Trey

On Jun 20, 3:42 am, rakugo <jdlrob...@gmail.com> wrote:
> Yakov - the timeline macro already has this functionality. The same
> was done for the allTags plugin but this has not yet been folded into
> the alpha - the groupBy macro provided in TiddlySpace by the
> GroupByPlugin [1] allows you to group by things other than tags -
> fields and attributes. It probably needs a bit of attention and
> feedback on usage of the list/timeline macros before being considered
> for the core though.
>
> Trey -  as Yakov points out pretty much anything can go into a
> template - to display a field bar you can run <<view bar text>> or
> <<view bar link>> or <<view bar wikified>> depending on what the field
> contains. As Eric quite rightly points out alphas are a field review
> and a great time to say things like "this is wrong", "why doesn't it
> do this" etc. It also speeds up the process as it increases demand for
> a new release.
>
> Apologies, for the confusion I caused. Essentially I was recommending
> using the alpha, as the list macro was rewritten with the purpose of
> supporting this kind of thing and allowing more freedom to customise.
> I've done some refactoring of the code now, and basically with the

> latest alpha all you should need is:https://raw.github.com/jdlrobson/TiddlyWikiPlugins/master/plugins/Fil...

>
> Note the syntax has now changed and you should use the filters
> [story[open]] and [story[sort]] to get the list.
> <<list filter "[story[open]][story[sort]]" template:TemplateOpen>>
> should be all you need to generate the correct list of tiddlers.

> The template athttp://frankenstein-plugins.tiddlyspace.com/#TemplateOpen

[Trey]

I have created a plugin. Behold, Ramplist:

config.macros.ramplist = {};

config.macros.ramplist.handler = function
(place,macroName,params,wikifier,paramString,tiddler){
// this will run when macro is called from a tiddler
story.forEachTiddler(function(title,element) {

createTiddlyLink(createTiddlyElement(place,"li"),title,true,null,false,null,true);
});

}

It's totally simple, I just copied the Jump command out of TW core and
figured out how to invoke it in a tiddler. It doesn't auto-refresh, I
couldn't figure that out. But, anyway, this is a significant victory
given my lack of experience.

I'm gonna try Jon's method with the alpha now. I'm going to be
relying on this, so I'm a little worried about using an alpha, but
what the heck. I'll post a sample copy of my TW here to show off the
UI I've been creating when I'm done.

Thanks TW group.

[Trey]

FYI, I have it mostly working now, thanks very much, functions exactly
as I'd envisioned.

[Tobias Beer]

Just in case you are not tired yet of exploring 'TiddlyCoding'... :-D

1) Instead of using a macro, use a plugin and define a placeholder
with a unique id in your PageTemplate.

2) Then define your "refresh" function in your plugin equivalent to
that of your macro but w/o the need for those macro parameters and
render your list into the DomNode of that unique Id, in case
getElementById(YourId) actually finds anything.

3) To ensure that your refresh function and macro use the same id,
you
might actually use a macro to render that container box with its
unique id as stored in the same variable used by your function.

4) For valid HTML, wrap your li elements in an outer ul.

5) So now, how do you trigger your refresh function?

Well, you will have to HIJACK the core's functions for opening and
closing tiddlers.

6) Consider implementing a global flag turning refresh off for the
CloseAll macro so that your container wont get refreshed at every
single tiddler being closed.

Cheers, Tobias.

[iono...@gmail.com]

Thanks, Tobias,
not tired of it at all!  But I will direct my efforts elsewhere because Jon's solution works exactly as I need it to.  Making my own version, albeit a weaker one, was a good exercise.  Thanks for your thoughts, I'm sure I will be making a plugin at some point in the future and I will refer to this.
I'm working on learning Python now, for a school project.
Trey

--

You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To post to this group, send email to tiddl...@googlegroups.com.
To unsubscribe from this group, send email to tiddlywiki+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.