Hi BJ,
Sure, it would do.
What I am trying to do is to generate the name of a new tiddler (created
from info captured by TC) and record it into the list field of an
"umbrella" tiddler. Currently I am using the @date/time information of the
web page, which is available in the Rule entries for both tiddlers
("umbrella" and new one). But passing information across the Rule entries
would allow me to use sequence numbers.
The link I posted earlier points to the TW I am working on. I will upload a
working version in the next few days.
Thank you!
Julio
El sáb., 26 mar. 2016 a las 10:06, BJ (<[email protected]>) escribió:
>
> Hi Julio,
> your usecase sounds very interesting. I don't think I can change how the #
> variables work without things breaking. An alternative would be to
> introduce a new type of variable, maybe ':' so that (eg) ':myvar' would
> keep it value across applications of rules. Do you thing that would work
> for you usage?
>
> all the best
> BJ
>
>
> On Friday, March 25, 2016 at 10:45:52 PM UTC, Julio Cantarero wrote:
>>
>> Hi BJ,
>>
>> While defining new rules for TiddlyClip, and I have bumped into a
>> characteristic of TiddlyClip's #variables: the scope of a #variable is
>> limited to the operations run inside the tiddler referenced in the 'Fields
>> modifiers' column.
>> Would it be possible to extend the scope of #variables so that their
>> values can be passed across Rules in the same operation?
>>
>> If so, I would be able to reuse values across different Tiddlers that I
>> create with a single TC click (category). I think this would make the rules
>> syntax more flexible. I do not know if extending the scope could cause
>> other problems/risks to TC itself.
>>
>> I must confess that I have tried to do this myself in your code
>> (commenting out //table['#']={}; in all instances in tidpaste.js
>> <https://github.com/buggyj/tiddlyclip-plugin/blob/master/common/tidpaste.js>
>> but the first one), but I did not manage to reuse #variables across Rule
>> tiddlers with just these changes.
>> Thank you,
>>
>> Julio
>>
>> El lunes, 1 de febrero de 2016, 12:16:03 (UTC+1), BJ escribió:
>>>
>>> hi Julio,
>>> thanks for the feedback, it's nice to know that people use tiddlyclip.
>>> Feedback like this is invaluable as it enables me to see what needs to be
>>> improved/added. - I have added comments below.
>>>
>>> On Sunday, January 31, 2016 at 11:07:01 PM UTC, Julio Cantarero wrote:
>>>>
>>>> Hi BJ,
>>>>
>>>> Thank you very much for the TiddlyClip TW5 plugin and FF addon. I use
>>>> them very often to capture news to my TW when browsing around.
>>>>
>>>> Since you were also asking about particular uses, I also tried a few
>>>> months ago to use TW5 + TiddlyClip to create a web notebook for studying
>>>> vocabulary of foreign languages. The goal was to easily create new
>>>> vocabulary entries in a TW5 thanks to TiddlyClip, and then use other TW5
>>>> features to treat these entries as flashcards to support studying them. I
>>>> didn't get to finish it, but I found TiddlyClip was very flexible. I was
>>>> even capable of creating new tiddlers and renaming them, as well as create
>>>> and delete tiddler fields (I have uploaded a copy of the latest status
>>>> here: http://juliocantarero.github.io/TW5-LanguageStudyNotebook/ . It
>>>> is not fully working though)
>>>>
>>>> Regarding suggestions, I would have never dared, but since you asked :-)
>>>>
>>>> - In the documentation, it took me a while to realize that there
>>>> are tags and modes settings (table columns) both at Category (operation)
>>>> and Rule level. Modes at Category level are BrowserConfigModes, which is
>>>> different than Rule modes.
>>>>
>>>> As I wrote tiddlyclip I fully understand how it works, so I really need
>>> feedback on what is not clear - I will make this more clear in the
>>> documentation.
>>>
>>>>
>>>> -
>>>> - I tried to transclude a tiddler in the tags column at Category
>>>> level, using {{TiddlerName}} but it did not work. I think I read
>>>> somewhere
>>>> in the plugin documentation that the {{ }} option should work. It works
>>>> in
>>>> the body column. The purpose of this was to be able to tag clips from
>>>> different sessions with different identifiers, like lesson N or
>>>> subjects,
>>>> etc.
>>>>
>>>> There is only this type of flexibility in the rules (I need to add this
>>> to the documentation ) so you would have to use the tag entry there for
>>> this function.
>>>
>>>>
>>>> - And if I may: I guess there is a reason for it, but I found that
>>>> the syntax of the substitution expressions and macros was complex and
>>>> rigid. I guess I was stretching the use of TiddlyClip, or missed an
>>>> easiest
>>>> way to collect information in multiple passes from a web page. The only
>>>> option I could think of to pass structured information to TW5 (I mean a
>>>> vocabulary entry with term, definition, examples, pronuntiation, etc.)
>>>> was
>>>> tiddler fields.
>>>>
>>>> Your language study application is very interesting. Like you say the
>>> basic tiddlyclip operation is to select some text and clip the selection
>>> into tiddler(s) fields. It is also possible to clip the contents of the
>>> clipboard using the @clip variable, so one can copy some text to the
>>> clipboard, then highlight some text and clip both to tiddlers. To clip more
>>> selections on the page (other than using multiple clip actions as you have
>>> done) either requires using regular expressions or writing macros. It is
>>> possible to highlight multiple selections on a page (using the highlight
>>> rule), then select all of the page's text and clip that through selection
>>> macros (that would need to written - this is not difficult), eg
>>> @Selected#1(@web), @Selected#2(@web) etc.
>>>
>>> For the next release I may expand macro to take multiple arguments to
>>> support functions like @Selected(#1,@web).
>>>
>>> My choice of syntax for Tiddlyclip was constrained to be usable with
>>> wikitext, which restricted the syntax that could be used for its template
>>> braces (of the syntax compatible with wikitext I thought that '((*' '*))'
>>> would standout in the middle the wikitext. All tiddlyclip logic had to be
>>> put inside these braces. I will try and add some literal numbers and
>>> strings to the future release).
>>>
>>>>
>>>> -
>>>>
>>>> Regards,
>>>>
>>>> Julio
>>>>
>>>> El martes, 26 de enero de 2016, 16:19:16 (UTC+1), BJ escribió:
>>>>>
>>>>> Hi all,
>>>>> I am working on necessary changes to tiddlyclip in order support
>>>>> future versions of firefox. As I am current focused on tiddlyclip, this
>>>>> would be a good time to let me know of anything that you think could be
>>>>> improved or added to tiddlyclip or its documentation, or maybe you have a
>>>>> particular use or setup to share that could be added to tiddlyclip's
>>>>> website?
>>>>>
>>>>> all the best
>>>>>
>>>>> BJ
>>>>>
>>>> --
> 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/RWACKEmd9BA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> 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/50684637-281d-475f-beef-9c6bb465132b%40googlegroups.com
> <https://groups.google.com/d/msgid/tiddlywiki/50684637-281d-475f-beef-9c6bb465132b%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/CAG0O%3DG5P1K_xUgT86qgJajVjizPtG0jW8cauS4ZCB4KThEdLeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
