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.
On Jun 20, 9:00 am, Trey <[email protected]> wrote:
> Jon,
> Thanks for your work! I will try it out tonight.
> Trey
>
> On Jun 20, 3:42 am, rakugo <[email protected]> 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
> > 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
>
> > On Jun 20, 2:07 am, Trey <[email protected]> wrote:
>
> > > 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
>
> > > On Jun 19, 7:27 pm, PMario <[email protected]> wrote:
>
> > > > On Jun 19, 9:42 pm, Eric Shulman <[email protected]> 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
>
>
--
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.
