Thanks Mark,
I am trying to use this now. I have duitfuly tagged it $:/tags/Macro saved
and reloaded
in Both the key tiddler and below placed
<<editnsave objecttabs>> used other field names and ways of referencing the
field name yet nothing apears.
I have looked around but can not see why this would not work, editnsave is
not apearing in dumpvariables as would be expected
Thanks so far.
Tony
On Thursday, August 10, 2017 at 11:36:11 AM UTC+10, Mark S. wrote:
>
> Here's an improved (?) version that uses the existing field value as a
> default:
>
> \define editnsave(field)
> <$vars tid="$:/temp/$(currentTiddler)$" fld=
> "$:/temp/$(currentTiddler)$!!$field$" fldx=
> "{{$:/temp/$(currentTiddler)$!!$field$}}" >
>
> $field$: <$edit-text tiddler=<<tid>> field="$field$" default={{!!$field$}}
> tag="input"/>
> <$button>Save<$wikify name=val text="<<fldx>>"><$action-setfield $field=
> "$field$" $value=<<val>> /></$wikify>
> </$button>
>
> </$vars>
> \end
>
>
>
> On Wednesday, August 9, 2017 at 5:16:15 PM UTC-7, TonyM wrote:
>>
>> Mark,
>>
>> I am yet to test this but could it be extended as follows
>>
>> <<editnsave myfield "stringvalue">>
>>
>> But idealy
>> <<editnsave myfield "{{!!myfield}}">>
>>
>> to prepopulate it?
>>
>> It is often helpful to utilise the edit of a value to display it as well
>> so that you can save screen realestate.
>>
>>
>> Regards
>> Tony
>>
>> On Thursday, August 10, 2017 at 1:12:47 AM UTC+10, Mark S. wrote:
>>>
>>> Re request #2, use the following macro. Put it in a tiddler tagged
>>> $:/tags/Macro.
>>>
>>> Then put <<editnsave myfield>> anywhere in the tiddler that you want to
>>> edit the field. This will create an edit field and a reset button. Use the
>>> * button the first time you use the field to synch it with the current
>>> values. Edit in the field. Press Save when you're done.
>>>
>>> HTH
>>> Mark
>>>
>>> \define editnsave(field)
>>> <$vars tid="$:/temp/$(currentTiddler)$" fld=
>>> "$:/temp/$(currentTiddler)$!!$field$" fldx=
>>> "{{$:/temp/$(currentTiddler)$!!$field$}}" >
>>>
>>> $field$: <$edit tiddler=<<tid>> field="$field$"/>
>>> <$button>*<$wikify name=val text="{{!!$field$}}"><$action-setfield
>>> $tiddler=<<tid>> $field="$field$" $value=<<val>> /></$wikify>
>>> </$button>
>>> <$button>Save<$wikify name=val text="<<fldx>>"><$action-setfield
>>> $field="$field$" $value=<<val>> /></$wikify>
>>> </$button>
>>>
>>> </$vars>
>>> \end
>>>
>>>
>>>
>>> On Tuesday, August 8, 2017 at 6:55:03 PM UTC-7, TonyM wrote:
>>>>
>>>> Folks,
>>>>
>>>> Please forgive my being so brash to propose some TW5 core additions but
>>>> I am in the middle of a learing curve that may inform some improvements to
>>>> the core that will help others on this learning curve. I would liove your
>>>> feedback and if you are a GitHub proficiant person for you to submitt
>>>> them.
>>>> First I will explain what I want with a small explination and hope the
>>>> reasons prove self evident, however I will put a longer argument if
>>>> requested. I acknowledge there may be a gap in my knowledge and are happy
>>>> to be set straight. I am no Genius but I am not stupid and a clear way to
>>>> do the following would have made adopting TW5 much easier. I hope I am
>>>> using the correct terminology.
>>>>
>>>> Psudo-Constants
>>>> Provide tools to create "constants" within a given tiddler and any
>>>> sub-tiddlers (transcluded, called, macros etc...)
>>>> I have finaly learned I can do this using the below
>>>>
>>>> \define currentobjectsrc()
>>>> {{!!title}}
>>>> \end
>>>> <$wikify name="currentobject" text=<<currentobjectsrc>>>
>>>>
>>>> Such that <<currentobject>> has the same value in all sub-tiddlers
>>>>
>>>> *This is still not sufficent as <<currentobject>> can only be used in
>>>> some places*.
>>>>
>>>> Why cant we have an established syntax that allows this as a built in
>>>> feature?
>>>>
>>>> The current methods are way to convoluted and I fear act as a barier to
>>>> someone using tiddlywiki as their knowledge must be much deeper than it
>>>> need be before they can do something most people will think of while they
>>>> are learing about tiddlywiki. In this case much can be done without
>>>> learning to navigate a lot of complexity by providing values that are not
>>>> so context sencitive.
>>>>
>>>> Edit fields in Current Tiddler
>>>> Provide the tools to edit fields in the Current Tiddler
>>>>
>>>> The complexity of editing fields in the current tiddler, whilst it has
>>>> its technical reasons, runs counter to the intuitive value of tiddlywiki.
>>>> The most practical way is to use the tiddler edit function in which case
>>>> the user has to see all possible fields and values. I would like to
>>>> provide
>>>> access to edit fields in the current tiddler through the View Template,
>>>> without needing to use two additional tiddlers to achive this.
>>>>
>>>> I understand the issue is the rendering of each key stroke and the loss
>>>> of focus, but why can we not have a method where you nominate a field and
>>>> its value is placedn in an external tiddler, you then edit the field value
>>>> and on pressing a (field) save button, it is written back to the calling
>>>> tiddler in one shot?
>>>>
>>>> Once again the current methods are way to convoluted and I fear act as
>>>> a barier to someone using tiddlywiki as their knowledge must be much
>>>> deeper
>>>> than it need be before they can do something most people will think of
>>>> while they are learing about tiddlywiki.
>>>>
>>>>
>>>> Regards
>>>> Tony
>>>>
>>>
--
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/eff2db1f-91d3-4d66-83ef-bb28dc64696e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
