On Mar 28, 4:21 pm, rakugo <[email protected]> wrote:
> > No. I want to create a multi column view, using <<list filter
> > [tag[myTag]] [sort[sortField]] template:xx>>. Since I have a
> > widescreen, it is more readable that way.
>
> > *Since an old TW will ignore the named parameter, it just creates a
> > clickable list -> fall back.
> > *If the right macros are installed it creates a beautiful multicolum
> > view.
>
> I'm not sure I understand what you mean by multi column view in this
> context....
I should have written <<tiddler asdf 'twocolumn'>>
some CSS
.twocolumn, .dp50{width:50%;*width:49.9%;}
.twocolumn, .dp50{float:left; display: inline; }
> > Didn't think about multi level templates. But IMO it should work.
> > <<tsScan ...>> does. [1]
>
> That's only because the tsScan macro instead invents a syntax where $1
> is the space name.
> This is not very extensible. What if you wanted to run
> <<tsScan $1 tag:@news template:"SearchTemplate">>
> where $1 was something other than the space?
You are right. This is an other thing to discuss:
a) $1 $2 is also used with <<tiddler asdf with:"some text>> templating
b) MatchTagsPlugin which also adds some functionality to <<list filter
"[tag[expression]]">> uses
%0 - %6 as a placeholder string. see [1]
c) TobiBeer made a macro (can't remember its name), where he uses a
different template placeholder.
d) I am using a function() approach. See createElement() [2]. Which is
powerfull, but not end user friendly
e) ....
Having something, that is standardized outside the tiddly community,
may help here. IMO we are not good at designing standards. May be,
because it's to easy to tweak TW functions. We are hijacking
functions, if we don't like there default behaviour. Which is fine for
stand alone TWs but not for TSpaces.
> For instance we might imagine many different syntaxs, for example.
> <<tsScan $title$ tag:@news template:"SearchTemplate">>
> or
> <<tsScan %title% tag:@news template:"SearchTemplate">>
> <<tsScan {title} tag:@news template:"SearchTemplate">>
> where the value in brackets is treated as a tiddler field/attribute/
> slice.
If it is readable and consistent, I will use everything. But at the
moment we don't have anything, that is consistent. $1 %1 &0 §0 ... is
"simple" for programming, but it's _not_ readable, nor useable for
"default users".
> > > I'm a bit confused by your example however.
> > > If I understand correctly:
> > > <<tiddler /%tiddler.title%/ 'dp50'>> wikifies the wikitext of the....
> <snip>
> > > but the same could be achieved in a template via
> > > {{dp50{
> > > <<view text wikified>>}}}
>
> > no!
> > <<tiddler asdf 'dp50'>> produces
> > <span class="dp50" refresh="content" tiddler="asdf">..</span>
>
> > which does some nice refreshing if tiddler asdf is changed.
>
> __But__ it still produces the same content. The auto refreshing is a
> side effect of the tiddler macro. ...
No. It's a wanted behaviour.
> ... The view macro could in theory be
> extended to support refreshing too... although I'm aware of some side
> effects.
"in theory" + "known side effects" -> no go :(
-m
[1] http://www.tiddlytools.com/#MatchTagsPluginInfo
[2] http://fancybox-plugin.tiddlyspace.com/#FancyBoxPlugin
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev?hl=en.
