On Saturday, April 18, 2015 at 1:48:39 AM UTC+2, c pa wrote:
>
> What I want to do is build a macro that will evaluate and return the
> results of an expression such as {{!!fieldname}} within the current
> context. That would solve so many of my macro problems. I've wasted too
> many days working out the context differences between <<variableName>>,
> $variableName$, $(variableName)$, <$macrocall $name="variableName"> etc.
> etc. etc. Because macro strings are not evaluated within the macro, only
> after they have been returned into the calling tiddler context.
>
I think the problem here is, that the TW definition of the "current
context", is different to what you expect. (mainly for performance reasons)
... But the currentTiddler context is just a definition and can be changed
/ extended by the user using core widgets.
.. Reading your 1,2,3 description, I think there is no new macro needed.
....
but I'm still not sure, what TW does and, how your data / dataflow looks
like.
Let me explain, what I understand:
There are 2 different types of json config tiddlers.
- one defines a "from", "to" relation
- second ... I can't construct in my mind, but it is different because it
is tagged "xlate"
- There are 100+ sourcetablename and targettablename tiddlers that contain
the a data to create an "anlyst view".
- sourcetablename uses the "list" field to point to target tables
- targettablename uses fields to define, what should be shown to the
analyst.
- That "view" can be used by an analyst to see if data table export /
import mechanism was done right.
The data "migration" is done outside of TW but the data migration mechanism
created the tiddlers, that are used to create the views.
... is that right?
*And you can't have a statement <$macrocall $name="macroname"
> variablename="<$macrocall $name="anothermacro"/>" />*
>
> *I think there's a whole github discussion about this.*
>
Yes, you can, but it looks different.
-------------
Can you provide a small example tiddlywiki, that contains some tiddlers
with real data, that allows us to follow your data flow.
- I think of the 2 JSON tiddlers (one standard and one tagged xlate)
- eg: 3 sourcetablename, 3 targettablename containing minimal data.
- We probably may need the views and viewtemplates too.
I think, there is a conceptual problem. ... eg: {{!!fieldname}} is a very
high level abstraction for the <$transclude> and / or <$view> widget. So
imo {{}} shouldn't be used in your macros. IMO we need to find the right
widgets for your macros.
TW has a very powerful iteration tool. The <$list> widgets. .. By default
it sets its context to the "currentTiddler" variable. But its also possible
to use a different variable name here. So you can nest 2 or more list
widgets without loosing the parents context. ...
but since I can't really grasp your data structure, it's very hard to tell,
how a working configuration can look like.
-mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/62879b83-cccf-4d1d-a497-b3d07d5e035e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
