Editable fields - Qualified "data" tiddler?

[Brian Gates]

I'm trying to implement editable fields.  I hit the whole re-render issue so I thought instead I might use the qualified macro to have a sort of underlying "data" tiddler but I don't see any means of "joining" a tiddler back to its data via filters.

What's the best way to do this?

[Jed Carty]

You can have the name of the data tiddler stored in a field of the other tiddler and make a macro that references fields in the data tiddler instead if referencing the fields directly. I am not in a position to make an example at the moment, but some of the things I made for the Dashboard on inmysocks.tiddlyspot.com use this idea. Specifically http://inmysocks.tiddlyspot.com/#Dictionary but in your case you may need to use the set widget to define a variable for the data tiddler instead of having it hard coded like in that example.

[Tobias Beer]

The best option is to show us what you've got and we can work from there.

That way we can see precisely what is failing, otherwise it's a little bit of guesswork.

Best wishes, Tobias. 

[Brian Gates]

I found a much better solution.

I just tagged an edit view with $:/tags/EditTemplate.  Seems this view does not suffer the same edit/render issues as the ViewTemplate does!  Much more elegant solution.

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/pK7u6kic40Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Tobias Beer]

I just tagged an edit view with $:/tags/EditTemplate.  Seems this view does not suffer the same edit/render issues as the ViewTemplate does!  Much more elegant solution.

Of course, editing should be done in edit mode, it's designed to handle that.

If you find the time and place to show, let's have a look at some point

what you came up with, for other's to learn.

Best wishes, Tobias.

[Brian Gates]

Here's a couple examples:

https://github.com/brian-gates/alara/blob/420d0ea9a369ad7f3a4c1cb26663cdf9d650456d/wiki/tiddlers/PCView.tid

https://github.com/brian-gates/alara/blob/420d0ea9a369ad7f3a4c1cb26663cdf9d650456d/wiki/tiddlers/PCEdit.tid

--

[Tobias Beer]

Neat. Thanks, Brian...

 

https://github.com/brian-gates/alara/blob/420d0ea9a369ad7f3a4c1cb26663cdf9d650456d/wiki/tiddlers/PCView.tid

https://github.com/brian-gates/alara/blob/420d0ea9a369ad7f3a4c1cb26663cdf9d650456d/wiki/tiddlers/PCEdit.tid

I remember in TWc there was this desire for WikiPedia style boxes...

It's pretty much what you're doing here.

Only, TW5 with code like yours makes all that so much more flexible,

using actual fields.

Looks like three aspects to one common goal...

• custom view-template section to show a thingy
• custom edit-template section to edit a thingy
• custom button to create a new thingy

There's gotta be some room to standardize this stuff

so as to further automate the process for different types of thingies.

Best wishes, Tobias.