However it could be very cool if you could fetch tiddlertitles on
tiddlers tagged with a tag (alias a fieldname) from a tiddler named
after the tag into a dropdownlist with fieldvalues in the
customEditTemplate!!
This way fieldvalues could become tiddlers - and tags could become
fieldvalues... I can hear that it sounds pretty far out - and the
terminologies gets blurred - so maybe not...
But the circle of interchangeabilities does appeal to me -
Its something like this I try to accomplish when I write fETs getting
fieldvalues from tiddlers tagged with the title of the tiddler
containing the fET-table - sometimes it makes sense to have tiddlers
named after a fieldname or fieldvalue or tags with the same name as a
field or fieldvalue and the ability to make dropdownlists with
fieldvalues fetched from a list, that can be edited on the fly is
already there - why not make the list grow with tiddlers tagged with
the title of the list - and get new fieldvalues in the dropdownlist
showing new tiddlers?
Ok - I stop now - It's beginning to get messy..

YS Måns Mårtensson

On 18 Mar., 12:59, Måns <[email protected]> wrote:
> Sorry - the answer was to Kenn ....
>
> On 18 Mar., 12:08, Måns <[email protected]> wrote:
>
> > Hi Eric
> > The idea is to show a list of tiddlers tagged with the same name as a
> > field - and I have made my fETs already - in tiddlers tagged with that
> > tag (the same word as the field) - so you are right - I use double
> > wheels - and it works!
> > The reason for this is that I prefer fields to tags for many different
> > data - because i can use different inputmethods for fields - and I
> > only need a few tagnames to the overall picture...
>
> > YS Måns Mårtensson
>
> > On 18 Mar., 05:43, Ken Girard <[email protected]> wrote:
>
> > > the data in a field is not a tag, so you can't refer to it the same
> > > way as a tag. (Not that you can't have the same data in the tag field,
> > > but comparing the two is like comparing the tire in your trunk with
> > > the tire on the front driver side. They might be the same but they do
> > > different jobs)
> > > You might be able to put together a forEach contained in a slider that
> > > looks for all tiddlers with matching data in the fieldname.
>
> > > Ken Girard
>
> > > On Mar 17, 11:05 pm, Ken Girard <[email protected]> wrote:
>
> > > >  <span macro='view genre wikified'></span>
>
> > > > You have to put the [[ and ]] in the actual field, or make it a
> > > > WikiWord.
>
> > > > See:http://no-sin.com/wiki/WorkTracker.html#TrainingTemplateView
>
> > > > Ken Girard
>
> > > > On Mar 17, 3:52 pm, Måns <[email protected]> wrote:
>
> > > > > If I should want to tagview (<<tag genre>>) the fieldvalue in viewmode
> > > > > how would the syntax look like?
> > > > > Ex:
> > > > > <div>
> > > > >                 <span class='small'><i>[[fieldname]]:</i></span>
> > > > >                 <span macro='view [[genre]] wikified'></span>
> > > > >                 <span macro='tag fieldName'></span>
> > > > >         </div>
> > > > > Does someone know the right syntax to accomplish this?
>
> > > > > YS måns Mårtensson
>
> > > > > On 17 Mar., 21:33, Måns <[email protected]> wrote:
>
> > > > > > I'd like to make a wikified field input from the EditTemplate appear
> > > > > > as a link in a viewmode - without having to enclose it as a link in
> > > > > > editmode.
> > > > > > How do I accomplish that?
>
> > > > > > Can I just enclose the fieldname in square brackets like this?:
> > > > > > <div>
> > > > > >                 <span class='small'><i>[[genre]]:</i></span>
> > > > > >                 <span macro='view [[genre]] wikified'></span>
> > > > > >         </div>
>
> > > > > > YS Måns Mårtensson
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to