[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-12 Thread TonyM
Folks,

Because it related to work here I will share this with you first. Publish 
later.

The attached json bundle contains the "new from template tiddler" tools. On 
installation you will get a "new" sidebar tab that will lead you to all the 
information you need. This is not a plugin so no reload required.

Apart from a few macros you can use in any tiddler, or inside a list on the 
current tiddler there is a simple manager and a view template button that 
allows you to flag a tiddler as a template then simply create new instances 
of it via a dropdown list of templates.

Let me know if you have any problems or the information is not enough.

I see this as being a rapid development method to build standard tiddlers 
with the text fields and content such as a standard task field, then 
quickly create as many tasks as you want.

To list such tiddlers you could list those with a tag or field you placed 
on the template or all those with the tiddler-source field equal you the 
template tiddler. It is wise to make the template tiddlers system tiddlers 
so they do not appear in basic lists.

Please enjoy and providefeedback

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/7d931291-80c0-4b34-a57f-8853fe49d921%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


new-tiddler-from-template.bundle.json
Description: application/json


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Folks,

With thanks to all and in this case mostly Mark S. My working solution is 
as follows

\define fieldname-value() <$text text="""$(fieldname-value-temp)$"""/>
\define fieldsvalues()
<$list filter="[all[current]fields[]] -[[tiddler-template-caption]] 
-[[text]] -[[title]] -[[created]] -[[modified]] 
-[[tiddler-template-caption]]" variable="field"><$set name=
"fieldname-value-temp" tiddler=<> field=<> emptyValue
=""><>="<>"  
\end
\define clone-current-actions() 
<$action-createtiddler $basetitle={{!!title}} $savetitle=
"$:/temp/clone-current-title" $(attribs)$ text={{!!text}} />
<$action-navigate $to={{$:/temp/clone-current-title}}/>
\end
\define clone-template-actions() 
<$action-createtiddler $basetitle={{!!instance-of}} $savetitle=
"$:/temp/clone-template-title" $(attribs)$ text={{!!text}} />
<$action-navigate $to={{$:/temp/clone-template-title}}/>
\end
\define clone-tiddler(tiddlername)
<$set name=tiddlername value="$tiddlername$" emptyValue=<> >
<$tiddler tiddler=<> >
<$wikify name="attribs" text=<> >
<$button actions=<>class=<> 
>Clone




\end
\define new-template-instance(tiddlername,tags)
<$set name=tiddlername value="$tiddlername$" emptyValue=<> >
<$tiddler tiddler=<> >
<$wikify name="attribs" text=<> >
<$button actions=<> 
class=<> >New Instance
<$action-sendmessage $message="tm-edit-tiddler" 
$param={{$:/temp/clone-template-title}}/>




\end

;Named tiddler

New Order<> Clone

New Order<> Template

;On current tiddler

Clone this<> 

Template this<> Only works if the current tiddler 
has an "instance-of" field with a basetitle

I will be building this into a Tiddler Template solution and aim to share 
that.

I altered same names to help me understand marks code. See the macro 
invocations at the bottom

   - clone-tiddler simply copies the tiddler to a new tiddler with the name 
   iterated, with the exception of some fields. But all tags and the text.
   - new-template-instance does the same as clone but gets the new tiddler 
   name from instance-of field (usually in a template tiddler) and has a 
   different save title.
   - Both record the source tiddler in the new one

I hope this helps someone!

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/987afde2-c7f8-4d1f-872e-28a077f6c807%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Frd,

Thanks for that. I can use Marks answer for this issue, but your utility 
will most likely assist in some of the advanced solutions I suggest in my 
reply to Marks last comment.

Generate NewTitle sounds like something that should be more available to 
tiddlywiki users.

Lovely
Regards
Tony

On Saturday, 11 August 2018 18:14:27 UTC+10, FrD wrote:
>
> Hi TonyM,
>
> There is a function in the core that generates a new title based on a 
> given title (from task, it generates task 1, task 2, ...).
> I've wrapped it in a js macro. You could try it. Import save and reload 
> (in a test wiki or in a copy of your wiki !!!)
>
> Just enter <> or < tiddler">>
>
> Be careful with your data, try it on a copy.
>
> Regards
>
> FrD
>
> Le samedi 11 août 2018 09:53:40 UTC+2, TonyM a écrit :
>>
>> Frd,
>>
>> Thanks for your effort. Unfortunately I do not know the name before hand 
>> as I am cloning to create multiple instances of say tasks. They may be 
>> renamed or named task 1 task 2 etc...
>>
>> This is a messy part of the available code.
>>
>> So I am currentlt working on a copy selected fields to a new tiddler, 
>> which does create a new tiddler, but does not include the increment of 
>> duplicate tiddler names.
>>
>> Agh, I can't win.
>>
>> Perhaps I determine the new name myself and make it unique. This will be 
>> easier in the next release with the range operator.
>>
>> Regards
>> Tony
>>
>> On Saturday, 11 August 2018 17:40:33 UTC+10, FrD wrote:
>>>
>>> Hi TonyM,
>>>
>>> Finally I found a way to do what you want. The drawback is that you need 
>>> to know in advance the name of the tiddler you want to create.
>>>
>>> Go to https://tiddlywiki.com/
>>> Create a tiddler, for instance "testtemplate" with a tag ("MyTag"), some 
>>> text and two fields : field1 and field2.
>>> Create a tiddler, say "testcreate" with this code inside :
>>>
>>> \define actions()
>>> <$action-setfield $tiddler="testtemplate" $field="title" $value=
>>> "MyNewTiddler" />
>>> <$action-deletefield $tiddler="MyNewTiddler" $field="field2" />
>>> \end
>>>
>>> <$button actions=<>>
>>> Create and remove field
>>> 
>>>
>>> When you click the button, testtemplate is cloned (without being 
>>> deleted) and field2 is removed from the cloned tiddler.
>>> I think it's a convoluted way to use action-setfield and probably not 
>>> the way it was intended to be used. But it seems to work.
>>>
>>> Regards
>>>
>>> FrD
>>>
>>> Le samedi 11 août 2018 09:12:03 UTC+2, TonyM a écrit :

 Mark,

 Just to clarify, the "idea of [your] own and FrD's suggestion" just did 
 not work?

 I was relay smart because I decided to use a subtiddler such as 
 task/template to indicate it was a template tiddler so task no longer held 
 the removeme field and would not be cloned. This is a good idea but 
 somewhere I decided this was a useful tip for creating templates for 
 subTiddlers, and I returned it the above method only to be reminded it 
 does 
 not work again.


 I am using the following to clone tiddlers I am using as templates;

 <$button message="tm-new-tiddler" param=<> 
 tooltip="Clone this 'template'" aria-label="Clone this 'template'" class=<
 > >
 <$action-setfield $field=template-source $value=<>/>
 {{$:/PSaT/newTiddler/icon.svg}}
 

 So to restate the problem

 *This works nicely except I have to remove a field from the new Tiddler 
 eg removeme*
 *<$action-deletefield $field=removeme/>*

 *Unfortunately if I use this in the above tiddler it removes the field 
 from the source tiddler before the cloning.*

 As Mark suggested I may need resort to the ActionCreateTiddler so a 
 Final call to see if anyone knows a workaround or has build a clone tool 
 using ActionCreateTiddler?

 Regards
 Tony

 On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:
>
> Folks/Team,
>
> I am creating a tool to create tiddlers from template tiddlers and 
> will share today (if I resolve this).
>
> However to do so I am using the following to clone the tiddler to a 
> new tiddler name eg "task 1" and open for edit (which the user then 
> modifies)
>
> \whitespace trim
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=< toolbar-class>> >
> <$action-setfield $field=template-source $value=<>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> 
>
>
>- I identify which tiddlers are templates by the existence of the 
>field *tiddler-template-caption*
>- During the clone which works perfectly the 
>tiddler-template-caption also gets cloned
>- Unfortunately this means the new tiddlers now appear in the list 
>of tiddler templates
>- In the above code *<$action-deletefie

[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Mark,

Great work, I had a hunch it could be done, and you got there 1st, "good on 
ya".

It is quite elegant, and I will re-engineer it for a global macro and named 
templates. Thanks very much.

I will keep it in my own repository and when I get around to building a 
community website, I will put it there however I think we can take this and 
modularise it differently.

What interests me is, if you include text in the <> you have 
actually stored a tiddler in a field.  This allows us to store multiple 
tiddlers in one tiddler using its fields, or in a data tiddler (Aside from 
JSON files) and generate tiddlers from these in addition to cloning.

By providing $(attribs)$ to the buttonactions action-createtiddler we can 
leverage its $basetitle $savetitle and $timestamp so we can also provide 
the naming standard, get the title of the resultant tiddler and decide if 
it is time stamped as a clone or a new tiddler.

If we can generalise this effectively it makes a number of otherwise 
difficult things quite easy. See the inspiration that has followed below.

I am thinking of the following macros, 

   1. One to pack the current or named tiddler into a "parametised tiddler" 
   including or excluding details as desired. Field or variable.
   2. One to unpack (or create a tiddler) from a "parametised tiddler" to a 
   new tiddler including or excluding details as desired
   The following use the 1st & 2nd or will be options of them
   3. One to do both 1 and 2 at the same time (as we have discussed in this 
   thread)
   4. One to unpack a "parametised tiddler" to "the current" tiddler 
   including or excluding details as desired
   5. One to do both 1 and 4 at the same time (add/replaces fields from 
   another tiddler)

You have inspired me to think of then using the above to support,

   - Archiving multiple tiddlers in one (packing tiddlers)
   - Provide an unpack as well Generate a set of different tiddlers from 
   one tiddler
   - Making a copy of a tiddler inside one of its own fields
   - Creating a tiddler with its own unpack button
   - Creating a tiddler than can generate multiple sets of tiddlers with 
   unique names eg; A New Project may have 5 tiddlers 
  - View all project items
  - Create that projects items
  - Edit a projects items details
  - etc..
   - Using a stored macro tiddler and generating a customised macro tiddler 
   with custom settings.
   - Using a set of packed tiddlers for Wizards, demos, templated processes 
   etc...
   - and more

I love a good algorithium

Regards
Tony


On Sunday, 12 August 2018 04:56:19 UTC+10, Mark S. wrote:
>
> This code is deceptively short, but it appears to do what you want:
>
> \define catvalue() <$text text="""$(value2)$"""/>
> \define fieldsvalues()
> <$list filter="[all[current]fields[]] -[[tiddler-template-caption]] 
> -[[text]]" variable="field"><$set name="value2" tiddler=<> 
> field=<> emptyValue=""><>="<>"  
> \end
> \define buttonactions() <$action-createtiddler $basetitle={{!!title}} $(
> attribs)$ text={{!!text}} /> 
>
> <$wikify name="attribs" text=<> >
>
> <$button actions=<>>Create clone
> 
> 
>
>
> I say deceptively because of all the wrong paths I went down before 
> getting to it. It turns out that actioncreatetiddlerwidget has this weird 
> thing that when you attempt to add fields to a just-created tiddler it 
> makes a perfect clone  but wipes out the original! If real, that seems 
> like a bug to me. So that path didn't work.
>
> You'll be happy to know that part of this solution requires the 
> wikify-a-list trick you demonstrated in another thread. Note that the text 
> field is handled separately in order to avoid recursion. 
>
> This code needs to be "remembered" or stored somewhere, but not sure where.
>
> HTH
> -- Mark
>
>
> On Thursday, August 2, 2018 at 7:46:30 PM UTC-7, TonyM wrote:
>>
>> Folks/Team,
>>
>> I am creating a tool to create tiddlers from template tiddlers and will 
>> share today (if I resolve this).
>>
>> However to do so I am using the following to clone the tiddler to a new 
>> tiddler name eg "task 1" and open for edit (which the user then modifies)
>>
>> \whitespace trim
>> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
>> this 'template'" aria-label="Clone this 'template'" class=<> toolbar-class>> >
>> <$action-setfield $field=template-source $value=<>/>
>> *<$action-deletefield $field=tiddler-template-caption/**>*
>> {{$:/core/images/clone-button}}
>> 
>>
>>
>>- I identify which tiddlers are templates by the existence of the 
>>field *tiddler-template-caption*
>>- During the clone which works perfectly the tiddler-template-caption 
>> also 
>>gets cloned
>>- Unfortunately this means the new tiddlers now appear in the list of 
>>tiddler templates
>>- In the above code *<$action-deletefield 
>>$field=tiddler-template-caption/*> deletes the field from the 
>>template tiddler not the new one.
>>- How can I delete this field from

[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread 'Mark S.' via TiddlyWiki
This code is deceptively short, but it appears to do what you want:

\define catvalue() <$text text="""$(value2)$"""/>
\define fieldsvalues()
<$list filter="[all[current]fields[]] -[[tiddler-template-caption]] 
-[[text]]" variable="field"><$set name="value2" tiddler=<> 
field=<> emptyValue=""><>="<>"  
\end
\define buttonactions() <$action-createtiddler $basetitle={{!!title}} $(
attribs)$ text={{!!text}} /> 

<$wikify name="attribs" text=<> >

<$button actions=<>>Create clone




I say deceptively because of all the wrong paths I went down before getting 
to it. It turns out that actioncreatetiddlerwidget has this weird thing 
that when you attempt to add fields to a just-created tiddler it makes a 
perfect clone  but wipes out the original! If real, that seems like a 
bug to me. So that path didn't work.

You'll be happy to know that part of this solution requires the 
wikify-a-list trick you demonstrated in another thread. Note that the text 
field is handled separately in order to avoid recursion. 

This code needs to be "remembered" or stored somewhere, but not sure where.

HTH
-- Mark


On Thursday, August 2, 2018 at 7:46:30 PM UTC-7, TonyM wrote:
>
> Folks/Team,
>
> I am creating a tool to create tiddlers from template tiddlers and will 
> share today (if I resolve this).
>
> However to do so I am using the following to clone the tiddler to a new 
> tiddler name eg "task 1" and open for edit (which the user then modifies)
>
> \whitespace trim
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=< toolbar-class>> >
> <$action-setfield $field=template-source $value=<>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> 
>
>
>- I identify which tiddlers are templates by the existence of the 
>field *tiddler-template-caption*
>- During the clone which works perfectly the tiddler-template-caption also 
>gets cloned
>- Unfortunately this means the new tiddlers now appear in the list of 
>tiddler templates
>- In the above code *<$action-deletefield 
>$field=tiddler-template-caption/*> deletes the field from the template 
>tiddler not the new one.
>- How can I delete this field from the new tiddler with the yet to be 
>determined name?
>
> I believe I need to use message="tm-new-tiddler" param=<> 
> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
> use the $savetitle.
> I want the clone to work regardless of the fields and their content so I 
> do not want to explicitly create the fields, I just want them to come from 
> the template tiddler except for *tiddler-template-caption.*
>
> Note: <$action-setfield $field=template-source 
> $value=<>/> updates the template tiddler before the clone, 
> this saves the user doing it.
>
> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
> on the new tiddler after it is named/created without an additional 
> "trigger"*
>
> Thanks
> 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/624024b9-91a0-48ef-8a6c-890a710ff8d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Thanks Frd,

I will try it on sunday morning in around 10 to 11 hours.

I appreciate your help.

I must remember to document the final solution well because have wasted too 
much time on this even although I have learned some new things.

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/21524f7f-b834-4a5b-bf63-7341f70fcc9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread FrD
Hi TonyM,

There is a function in the core that generates a new title based on a given 
title (from task, it generates task 1, task 2, ...).
I've wrapped it in a js macro. You could try it. Import save and reload (in 
a test wiki or in a copy of your wiki !!!)

Just enter <> or <>

Be careful with your data, try it on a copy.

Regards

FrD

Le samedi 11 août 2018 09:53:40 UTC+2, TonyM a écrit :
>
> Frd,
>
> Thanks for your effort. Unfortunately I do not know the name before hand 
> as I am cloning to create multiple instances of say tasks. They may be 
> renamed or named task 1 task 2 etc...
>
> This is a messy part of the available code.
>
> So I am currentlt working on a copy selected fields to a new tiddler, 
> which does create a new tiddler, but does not include the increment of 
> duplicate tiddler names.
>
> Agh, I can't win.
>
> Perhaps I determine the new name myself and make it unique. This will be 
> easier in the next release with the range operator.
>
> Regards
> Tony
>
> On Saturday, 11 August 2018 17:40:33 UTC+10, FrD wrote:
>>
>> Hi TonyM,
>>
>> Finally I found a way to do what you want. The drawback is that you need 
>> to know in advance the name of the tiddler you want to create.
>>
>> Go to https://tiddlywiki.com/
>> Create a tiddler, for instance "testtemplate" with a tag ("MyTag"), some 
>> text and two fields : field1 and field2.
>> Create a tiddler, say "testcreate" with this code inside :
>>
>> \define actions()
>> <$action-setfield $tiddler="testtemplate" $field="title" $value=
>> "MyNewTiddler" />
>> <$action-deletefield $tiddler="MyNewTiddler" $field="field2" />
>> \end
>>
>> <$button actions=<>>
>> Create and remove field
>> 
>>
>> When you click the button, testtemplate is cloned (without being deleted) 
>> and field2 is removed from the cloned tiddler.
>> I think it's a convoluted way to use action-setfield and probably not the 
>> way it was intended to be used. But it seems to work.
>>
>> Regards
>>
>> FrD
>>
>> Le samedi 11 août 2018 09:12:03 UTC+2, TonyM a écrit :
>>>
>>> Mark,
>>>
>>> Just to clarify, the "idea of [your] own and FrD's suggestion" just did 
>>> not work?
>>>
>>> I was relay smart because I decided to use a subtiddler such as 
>>> task/template to indicate it was a template tiddler so task no longer held 
>>> the removeme field and would not be cloned. This is a good idea but 
>>> somewhere I decided this was a useful tip for creating templates for 
>>> subTiddlers, and I returned it the above method only to be reminded it does 
>>> not work again.
>>>
>>>
>>> I am using the following to clone tiddlers I am using as templates;
>>>
>>> <$button message="tm-new-tiddler" param=<> 
>>> tooltip="Clone this 'template'" aria-label="Clone this 'template'" class=<
>>> > >
>>> <$action-setfield $field=template-source $value=<>/>
>>> {{$:/PSaT/newTiddler/icon.svg}}
>>> 
>>>
>>> So to restate the problem
>>>
>>> *This works nicely except I have to remove a field from the new Tiddler 
>>> eg removeme*
>>> *<$action-deletefield $field=removeme/>*
>>>
>>> *Unfortunately if I use this in the above tiddler it removes the field 
>>> from the source tiddler before the cloning.*
>>>
>>> As Mark suggested I may need resort to the ActionCreateTiddler so a 
>>> Final call to see if anyone knows a workaround or has build a clone tool 
>>> using ActionCreateTiddler?
>>>
>>> Regards
>>> Tony
>>>
>>> On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:

 Folks/Team,

 I am creating a tool to create tiddlers from template tiddlers and will 
 share today (if I resolve this).

 However to do so I am using the following to clone the tiddler to a new 
 tiddler name eg "task 1" and open for edit (which the user then modifies)

 \whitespace trim
 <$button message="tm-new-tiddler" param=<> tooltip="Clone 
 this 'template'" aria-label="Clone this 'template'" class=<>>> toolbar-class>> >
 <$action-setfield $field=template-source $value=<>/>
 *<$action-deletefield $field=tiddler-template-caption/**>*
 {{$:/core/images/clone-button}}
 


- I identify which tiddlers are templates by the existence of the 
field *tiddler-template-caption*
- During the clone which works perfectly the 
tiddler-template-caption also gets cloned
- Unfortunately this means the new tiddlers now appear in the list 
of tiddler templates
- In the above code *<$action-deletefield 
$field=tiddler-template-caption/*> deletes the field from the 
template tiddler not the new one.
- How can I delete this field from the new tiddler with the yet to 
be determined name?

 I believe I need to use message="tm-new-tiddler" param=<>>> >> rather than ActionCreateTiddlerWidget to clone the tiddler, where I 
 would use the $savetitle.
 I want the clone to work regardless of the fields and their content so 
 I do not want to explicitly create the fields

[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Frd,

Thanks for your effort. Unfortunately I do not know the name before hand as 
I am cloning to create multiple instances of say tasks. They may be renamed 
or named task 1 task 2 etc...

This is a messy part of the available code.

So I am currentlt working on a copy selected fields to a new tiddler, which 
does create a new tiddler, but does not include the increment of duplicate 
tiddler names.

Agh, I can't win.

Perhaps I determine the new name myself and make it unique. This will be 
easier in the next release with the range operator.

Regards
Tony

On Saturday, 11 August 2018 17:40:33 UTC+10, FrD wrote:
>
> Hi TonyM,
>
> Finally I found a way to do what you want. The drawback is that you need 
> to know in advance the name of the tiddler you want to create.
>
> Go to https://tiddlywiki.com/
> Create a tiddler, for instance "testtemplate" with a tag ("MyTag"), some 
> text and two fields : field1 and field2.
> Create a tiddler, say "testcreate" with this code inside :
>
> \define actions()
> <$action-setfield $tiddler="testtemplate" $field="title" $value=
> "MyNewTiddler" />
> <$action-deletefield $tiddler="MyNewTiddler" $field="field2" />
> \end
>
> <$button actions=<>>
> Create and remove field
> 
>
> When you click the button, testtemplate is cloned (without being deleted) 
> and field2 is removed from the cloned tiddler.
> I think it's a convoluted way to use action-setfield and probably not the 
> way it was intended to be used. But it seems to work.
>
> Regards
>
> FrD
>
> Le samedi 11 août 2018 09:12:03 UTC+2, TonyM a écrit :
>>
>> Mark,
>>
>> Just to clarify, the "idea of [your] own and FrD's suggestion" just did 
>> not work?
>>
>> I was relay smart because I decided to use a subtiddler such as 
>> task/template to indicate it was a template tiddler so task no longer held 
>> the removeme field and would not be cloned. This is a good idea but 
>> somewhere I decided this was a useful tip for creating templates for 
>> subTiddlers, and I returned it the above method only to be reminded it does 
>> not work again.
>>
>>
>> I am using the following to clone tiddlers I am using as templates;
>>
>> <$button message="tm-new-tiddler" param=<> 
>> tooltip="Clone this 'template'" aria-label="Clone this 'template'" class=<
>> > >
>> <$action-setfield $field=template-source $value=<>/>
>> {{$:/PSaT/newTiddler/icon.svg}}
>> 
>>
>> So to restate the problem
>>
>> *This works nicely except I have to remove a field from the new Tiddler 
>> eg removeme*
>> *<$action-deletefield $field=removeme/>*
>>
>> *Unfortunately if I use this in the above tiddler it removes the field 
>> from the source tiddler before the cloning.*
>>
>> As Mark suggested I may need resort to the ActionCreateTiddler so a Final 
>> call to see if anyone knows a workaround or has build a clone tool using 
>> ActionCreateTiddler?
>>
>> Regards
>> Tony
>>
>> On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:
>>>
>>> Folks/Team,
>>>
>>> I am creating a tool to create tiddlers from template tiddlers and will 
>>> share today (if I resolve this).
>>>
>>> However to do so I am using the following to clone the tiddler to a new 
>>> tiddler name eg "task 1" and open for edit (which the user then modifies)
>>>
>>> \whitespace trim
>>> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
>>> this 'template'" aria-label="Clone this 'template'" class=<>> toolbar-class>> >
>>> <$action-setfield $field=template-source $value=<>/>
>>> *<$action-deletefield $field=tiddler-template-caption/**>*
>>> {{$:/core/images/clone-button}}
>>> 
>>>
>>>
>>>- I identify which tiddlers are templates by the existence of the 
>>>field *tiddler-template-caption*
>>>- During the clone which works perfectly the tiddler-template-caption 
>>> also 
>>>gets cloned
>>>- Unfortunately this means the new tiddlers now appear in the list 
>>>of tiddler templates
>>>- In the above code *<$action-deletefield 
>>>$field=tiddler-template-caption/*> deletes the field from the 
>>>template tiddler not the new one.
>>>- How can I delete this field from the new tiddler with the yet to 
>>>be determined name?
>>>
>>> I believe I need to use message="tm-new-tiddler" param=<>> >> rather than ActionCreateTiddlerWidget to clone the tiddler, where I 
>>> would use the $savetitle.
>>> I want the clone to work regardless of the fields and their content so I 
>>> do not want to explicitly create the fields, I just want them to come from 
>>> the template tiddler except for *tiddler-template-caption.*
>>>
>>> Note: <$action-setfield $field=template-source 
>>> $value=<>/> updates the template tiddler before the clone, 
>>> this saves the user doing it.
>>>
>>> How can I trigger *<$action-deletefield 
>>> $field=tiddler-template-caption/**> on the new tiddler after it is 
>>> named/created without an additional "trigger"*
>>>
>>> Thanks
>>> Tony
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ti

[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread FrD
Hi TonyM,

Finally I found a way to do what you want. The drawback is that you need to 
know in advance the name of the tiddler you want to create.

Go to https://tiddlywiki.com/
Create a tiddler, for instance "testtemplate" with a tag ("MyTag"), some 
text and two fields : field1 and field2.
Create a tiddler, say "testcreate" with this code inside :

\define actions()
<$action-setfield $tiddler="testtemplate" $field="title" $value=
"MyNewTiddler" />
<$action-deletefield $tiddler="MyNewTiddler" $field="field2" />
\end

<$button actions=<>>
Create and remove field


When you click the button, testtemplate is cloned (without being deleted) 
and field2 is removed from the cloned tiddler.
I think it's a convoluted way to use action-setfield and probably not the 
way it was intended to be used. But it seems to work.

Regards

FrD

Le samedi 11 août 2018 09:12:03 UTC+2, TonyM a écrit :
>
> Mark,
>
> Just to clarify, the "idea of [your] own and FrD's suggestion" just did 
> not work?
>
> I was relay smart because I decided to use a subtiddler such as 
> task/template to indicate it was a template tiddler so task no longer held 
> the removeme field and would not be cloned. This is a good idea but 
> somewhere I decided this was a useful tip for creating templates for 
> subTiddlers, and I returned it the above method only to be reminded it does 
> not work again.
>
>
> I am using the following to clone tiddlers I am using as templates;
>
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=<
> > >
> <$action-setfield $field=template-source $value=<>/>
> {{$:/PSaT/newTiddler/icon.svg}}
> 
>
> So to restate the problem
>
> *This works nicely except I have to remove a field from the new Tiddler eg 
> removeme*
> *<$action-deletefield $field=removeme/>*
>
> *Unfortunately if I use this in the above tiddler it removes the field 
> from the source tiddler before the cloning.*
>
> As Mark suggested I may need resort to the ActionCreateTiddler so a Final 
> call to see if anyone knows a workaround or has build a clone tool using 
> ActionCreateTiddler?
>
> Regards
> Tony
>
> On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:
>>
>> Folks/Team,
>>
>> I am creating a tool to create tiddlers from template tiddlers and will 
>> share today (if I resolve this).
>>
>> However to do so I am using the following to clone the tiddler to a new 
>> tiddler name eg "task 1" and open for edit (which the user then modifies)
>>
>> \whitespace trim
>> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
>> this 'template'" aria-label="Clone this 'template'" class=<> toolbar-class>> >
>> <$action-setfield $field=template-source $value=<>/>
>> *<$action-deletefield $field=tiddler-template-caption/**>*
>> {{$:/core/images/clone-button}}
>> 
>>
>>
>>- I identify which tiddlers are templates by the existence of the 
>>field *tiddler-template-caption*
>>- During the clone which works perfectly the tiddler-template-caption 
>> also 
>>gets cloned
>>- Unfortunately this means the new tiddlers now appear in the list of 
>>tiddler templates
>>- In the above code *<$action-deletefield 
>>$field=tiddler-template-caption/*> deletes the field from the 
>>template tiddler not the new one.
>>- How can I delete this field from the new tiddler with the yet to be 
>>determined name?
>>
>> I believe I need to use message="tm-new-tiddler" param=<> 
>> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
>> use the $savetitle.
>> I want the clone to work regardless of the fields and their content so I 
>> do not want to explicitly create the fields, I just want them to come from 
>> the template tiddler except for *tiddler-template-caption.*
>>
>> Note: <$action-setfield $field=template-source 
>> $value=<>/> updates the template tiddler before the clone, 
>> this saves the user doing it.
>>
>> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
>> on the new tiddler after it is named/created without an additional 
>> "trigger"*
>>
>> Thanks
>> 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/f897888c-1d2e-4cc5-a42f-c2fbb658c0bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-11 Thread TonyM
Mark,

Just to clarify, the "idea of [your] own and FrD's suggestion" just did not 
work?

I was relay smart because I decided to use a subtiddler such as 
task/template to indicate it was a template tiddler so task no longer held 
the removeme field and would not be cloned. This is a good idea but 
somewhere I decided this was a useful tip for creating templates for 
subTiddlers, and I returned it the above method only to be reminded it does 
not work again.


I am using the following to clone tiddlers I am using as templates;

<$button message="tm-new-tiddler" param=<> tooltip="Clone 
this 'template'" aria-label="Clone this 'template'" class=<
> >
<$action-setfield $field=template-source $value=<>/>
{{$:/PSaT/newTiddler/icon.svg}}


So to restate the problem

*This works nicely except I have to remove a field from the new Tiddler eg 
removeme*
*<$action-deletefield $field=removeme/>*

*Unfortunately if I use this in the above tiddler it removes the field from 
the source tiddler before the cloning.*

As Mark suggested I may need resort to the ActionCreateTiddler so a Final 
call to see if anyone knows a workaround or has build a clone tool using 
ActionCreateTiddler?

Regards
Tony

On Friday, 3 August 2018 12:46:30 UTC+10, TonyM wrote:
>
> Folks/Team,
>
> I am creating a tool to create tiddlers from template tiddlers and will 
> share today (if I resolve this).
>
> However to do so I am using the following to clone the tiddler to a new 
> tiddler name eg "task 1" and open for edit (which the user then modifies)
>
> \whitespace trim
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=< toolbar-class>> >
> <$action-setfield $field=template-source $value=<>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> 
>
>
>- I identify which tiddlers are templates by the existence of the 
>field *tiddler-template-caption*
>- During the clone which works perfectly the tiddler-template-caption also 
>gets cloned
>- Unfortunately this means the new tiddlers now appear in the list of 
>tiddler templates
>- In the above code *<$action-deletefield 
>$field=tiddler-template-caption/*> deletes the field from the template 
>tiddler not the new one.
>- How can I delete this field from the new tiddler with the yet to be 
>determined name?
>
> I believe I need to use message="tm-new-tiddler" param=<> 
> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
> use the $savetitle.
> I want the clone to work regardless of the fields and their content so I 
> do not want to explicitly create the fields, I just want them to come from 
> the template tiddler except for *tiddler-template-caption.*
>
> Note: <$action-setfield $field=template-source 
> $value=<>/> updates the template tiddler before the clone, 
> this saves the user doing it.
>
> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
> on the new tiddler after it is named/created without an additional 
> "trigger"*
>
> Thanks
> 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/4c2973ec-7849-4802-87b3-cb3afb89e9d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-04 Thread TonyM
Welcome

-- 
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/7afc82f0-ea95-4bae-93d8-c9da878040fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-04 Thread FrD
H Tony,

I see. thanks for your explanation.

Regards.

FrD

Le samedi 4 août 2018 10:34:20 UTC+2, TonyM a écrit :
>
> Frd
>
> I am using sub to suggest subordinate. Using the /template name after the 
> tiddlername.
>
> Tiddlername (actual template)
> Tiddlername/template existing means tiddlername is a template.
>
> Thus every tiddler with suffix[/template] says there is a template tiddler 
> called removesuffix[/template]
>
> When I clone templatename to templateinstance the subtiddler is not cloned 
> and I do not need to modify the new tiddler 
>
> 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/91843b70-318c-42be-b3eb-fe4e84f8dd3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-04 Thread TonyM
Frd

I am using sub to suggest subordinate. Using the /template name after the 
tiddlername.

Tiddlername (actual template)
Tiddlername/template existing means tiddlername is a template.

Thus every tiddler with suffix[/template] says there is a template tiddler 
called removesuffix[/template]

When I clone templatename to templateinstance the subtiddler is not cloned and 
I do not need to modify the new tiddler 

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/6e703c8c-bf55-4874-bb01-de1fa0559e29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-04 Thread FrD
Hi Tony,

Could you elaborate a bit about your solution and the use of a "subtiddler" 
? This word seems to relate only to plugin tiddlers on 
https://tiddlywiki.com/. But I think you give it another meaning here and 
use it for something else.

Regards

FrD

Le samedi 4 août 2018 05:33:30 UTC+2, TonyM a écrit :
>
> Mark,
>
> As I posted I am happy to use the existence of a /template subtiddler 
> because I can simply use a custom clone button. In fact I can see being 
> able store additional info about the template or even listing the resulting 
> tiddlers.
>
> However I have thought of allowing check boxes on each field of one 
> tiddler to copy or append to a target tiddler. Similer to how you suggest.
>
> 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/68052413-35a7-4503-8c5f-614682d58786%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-03 Thread TonyM
Mark,

As I posted I am happy to use the existence of a /template subtiddler because I 
can simply use a custom clone button. In fact I can see being able store 
additional info about the template or even listing the resulting tiddlers.

However I have thought of allowing check boxes on each field of one tiddler to 
copy or append to a target tiddler. Similer to how you suggest.

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/bc08ef88-2022-4cf7-9a2d-d3fcd9faa4da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-03 Thread 'Mark S.' via TiddlyWiki
I've tried an idea of my own and FrD's suggestion. The problem is, that 
once the tm-new-tiddler message is sent the current macro stops. So you 
can't do any clean-up back in the original macro. 

Here's the code I tried using FrD's approach. The last setfield never gets 
run, even though it's simple text:

\whitespace trim
<$button tooltip="Clone this 'template'" aria-label="Clone this 'template'" 
class=<> >{{$:/core/images/clone-button}}
<$vars tiddler-template-caption={{!!tiddler-template-caption}}>
<$action-deletefield $field="tiddler-template-caption"/>
<$action-setfield $field=template-source $value=<>/>
<$action-sendmessage $message="tm-new-tiddler" $param=<>  >
<$action-setfield $field="tiddler-template-caption" 
 $value=<>/>
<$action-setfield $field="do-i-happen"  $value="Important stuff"/>

Enter code here...

The sendmessage pre-empts the rest of the code. I think you're stuck with 
using ActionCreateTiddler. But it shouldn't be that hard to cycle through 
all the fields and insert them into the new tiddler.

-- Mark



On Friday, August 3, 2018 at 2:14:20 AM UTC-7, TonyM wrote:
>
> Frd
>
> Thanks, I have used the work around to indicate template tiddlers by 
> creating a matching tiddler templatename/template 
>
> In someways this may be better because the templatetiddler is now totaly 
> cloned.
>
> 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/fa900663-123b-4a63-b579-c0f351ee08d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-03 Thread TonyM
Frd

Thanks, I have used the work around to indicate template tiddlers by creating a 
matching tiddler templatename/template 

In someways this may be better because the templatetiddler is now totaly cloned.

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/1e54d214-7db5-4863-aab1-0f510542fdab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-03 Thread FrD
Hi,

I've not written the code so it's not tested.

Perhaps the list of actions when you click the button could be :

- Remove the field from the template tiddler,
- clone the template tiddler
- add back the field to the template tiddler.

Regards

FrD

Le vendredi 3 août 2018 04:46:30 UTC+2, TonyM a écrit :
>
> Folks/Team,
>
> I am creating a tool to create tiddlers from template tiddlers and will 
> share today (if I resolve this).
>
> However to do so I am using the following to clone the tiddler to a new 
> tiddler name eg "task 1" and open for edit (which the user then modifies)
>
> \whitespace trim
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=< toolbar-class>> >
> <$action-setfield $field=template-source $value=<>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> 
>
>
>- I identify which tiddlers are templates by the existence of the 
>field *tiddler-template-caption*
>- During the clone which works perfectly the tiddler-template-caption also 
>gets cloned
>- Unfortunately this means the new tiddlers now appear in the list of 
>tiddler templates
>- In the above code *<$action-deletefield 
>$field=tiddler-template-caption/*> deletes the field from the template 
>tiddler not the new one.
>- How can I delete this field from the new tiddler with the yet to be 
>determined name?
>
> I believe I need to use message="tm-new-tiddler" param=<> 
> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
> use the $savetitle.
> I want the clone to work regardless of the fields and their content so I 
> do not want to explicitly create the fields, I just want them to come from 
> the template tiddler except for *tiddler-template-caption.*
>
> Note: <$action-setfield $field=template-source 
> $value=<>/> updates the template tiddler before the clone, 
> this saves the user doing it.
>
> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
> on the new tiddler after it is named/created without an additional 
> "trigger"*
>
> Thanks
> 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/97046571-f787-4423-bf17-c1e7fd6bb565%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[tw5] Re: Delete a field on a newly "cloned" tiddler

2018-08-02 Thread TonyM
Folks,

It would be good to answer this, especially if it was a "clean" and 
uncomplicated solution, however I have decided to flag template tiddlers 
using a method that does not get cloned ie no field, text or tag. In this 
case I am creating a subtiddler currenttiddler/template to indicate 
template tiddlers.

Regards
Tony

On Friday, August 3, 2018 at 12:46:30 PM UTC+10, TonyM wrote:
>
> Folks/Team,
>
> I am creating a tool to create tiddlers from template tiddlers and will 
> share today (if I resolve this).
>
> However to do so I am using the following to clone the tiddler to a new 
> tiddler name eg "task 1" and open for edit (which the user then modifies)
>
> \whitespace trim
> <$button message="tm-new-tiddler" param=<> tooltip="Clone 
> this 'template'" aria-label="Clone this 'template'" class=< toolbar-class>> >
> <$action-setfield $field=template-source $value=<>/>
> *<$action-deletefield $field=tiddler-template-caption/**>*
> {{$:/core/images/clone-button}}
> 
>
>
>- I identify which tiddlers are templates by the existence of the 
>field *tiddler-template-caption*
>- During the clone which works perfectly the tiddler-template-caption also 
>gets cloned
>- Unfortunately this means the new tiddlers now appear in the list of 
>tiddler templates
>- In the above code *<$action-deletefield 
>$field=tiddler-template-caption/*> deletes the field from the template 
>tiddler not the new one.
>- How can I delete this field from the new tiddler with the yet to be 
>determined name?
>
> I believe I need to use message="tm-new-tiddler" param=<> 
> rather than ActionCreateTiddlerWidget to clone the tiddler, where I would 
> use the $savetitle.
> I want the clone to work regardless of the fields and their content so I 
> do not want to explicitly create the fields, I just want them to come from 
> the template tiddler except for *tiddler-template-caption.*
>
> Note: <$action-setfield $field=template-source 
> $value=<>/> updates the template tiddler before the clone, 
> this saves the user doing it.
>
> How can I trigger *<$action-deletefield $field=tiddler-template-caption/**> 
> on the new tiddler after it is named/created without an additional 
> "trigger"*
>
> Thanks
> 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/4be10e51-a477-4af0-bf0c-bb13a010de5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.