There IS a lot to absorb, and it was all "grown organically". I think the
specific macros you are finding odd are actually defined in the "tw5.com
edition", and is part of a set of macros called "documentation macros".
These macros use leading punctuation (.operator-example, .warning, .tip,
etc). These can be considered "user created" macros (with the user being
Jeremy and everyone on the GitHub repository), and the leading period is to
separate these into a different "name-space". Granted, this is never called
out, and you need to use the Advanced Search's System tab to find the
tiddlers that contain these definitions:
\define .icon(_) <span class="doc-icon">{{$_$}}</span>
\define .tip(_) <div class="doc-icon-block"><div
class="doc-block-icon">{{$:/core/images/tip}}</div> $_$</div>
\define .warning(_) <div class="doc-icon-block"><div
class="doc-block-icon">{{$:/core/images/warning}}</div> $_$</div>
Welcome to the community!
Best,
Joshua Fontany
On Wednesday, September 30, 2020 at 3:54:21 PM UTC-7 [email protected] wrote:
> Mario,
>
> to see what I mean about examples, open the TW wiki and search for .oper.
> You will get 24 retrieved. All the examples use this format.
>
> I can't remember other examples I found....I have 'found' many things and
> most of them have now been 'lost' :-)
>
> bobj
>
> On Thursday, 1 October 2020 at 04:13:10 UTC+10 Cade Roux wrote:
>
>> I sympathize.
>>
>> It's very hard for me to switch gears into TiddlyWiki filter and widget
>> syntax. I generate my tiddlers with a combination of SQL and PowerShell
>> within and around a source template TW. So I am dealing with two
>> completely different declarative models (TW - plus HTML/CSS - and SQL
>> queries) and four different imperative models (C#, Javascript, PowerShell,
>> SQL procedures) on a daily basis.
>>
>> I am trying to let each be the best at what it does. So in cases where I
>> might have previously generated an HTML table to put in a tiddler, I am
>> instead replacing that with a macro based on a list(s) of elements put into
>> a field(s) in the tiddler, and generating more of the raw data into the
>> fields of the tiddlers and let them render more things based on their
>> attached data.
>>
>> I find the filters are really hard to deal with finding which one you
>> need. The names are so generic and terse and they are so varied. I mean
>> we have tag, tags and tagged which all have to do different things. And
>> ones like each, get, has, is, contains - all needed obviously for their
>> different input and semantics, but it's hard to keep them all in your head
>> there are so many compared to other languages.
>>
>> I use a macro to do edit/transclusion extensively, to allow the medical
>> informaticist to edit tiddlers which annotate things in various places
>> which need handwritten narratives - so he gets quick feedback since
>> everything is transcluded, he can see the results immediately as if he was
>> building the manual in Word or some other documentation tool without having
>> to cut and paste in new lists of things generated from the datamart. He
>> just transcludes them and when they are regenerated, they are updated.
>>
>> Because we have a combination of edited manual tiddlers and generated
>> tiddlers, and also need source control for our work simultaneously, I tend
>> to relegate all control over the template to the medical informaticist and
>> put anything I want in through the build process - all tiddlers are either
>> in the template or they are generated, there is no mixing. Once we
>> established that separation (generated tiddlers are marked in a field and
>> are all deleted and recreated during the build process), it has worked very
>> well. Generated tiddlers can transclude manual tiddlers and vice versa,
>> which truly is wonderful. It's somehow hard to tell whether the system is
>> filling out a template we have created or we are filling out a template the
>> build process has created - that is very liberating from the point of view
>> of generating a rapidly growing data dictionary for our data mart. It's a
>> continual learning process and a lot of refactoring and refinement, but I
>> think the process is a lot smoother and less labor intensive than if we had
>> a system that was more biased one way or the other towards whether the main
>> point of view was the generated documentation from manual parts or the
>> manual documentation from generated parts.
>>
>> Best of luck,
>>
>> Cade
>> On Wednesday, September 30, 2020 at 12:46:41 PM UTC-5 [email protected]
>> wrote:
>>
>>> Hi All,
>>>
>>> Read with interest all the comments. I am trying to help and it is
>>> warming to read that you seem to agree. Other lists I have been on are less
>>> welcoming.
>>>
>>> Imtaz's comments are right but I would go further and argue for a
>>> rewrite of all the filter docs. The one thing I have learned is the central
>>> and crucial role of filters to the extent that I believe they need a 'Book'
>>> on their own. Filters drive just about everything and understanding them,
>>> their role and how to code them is most crucial.
>>>
>>> Secondly, how to address stuff needs a rewrite, what
>>> bracket/brace/underscore configuration drives me crazy and every time I get
>>> my problem fixed and then apply that to the next wiki text statement to
>>> have it fail makes things worse. I don't believe the problem is because TW
>>> is a declarative language. I have used other such languages and they don't
>>> suffer from this. It sounds as if the scope of today's browsers contributes
>>> and maybe that needs to be looked at. Looking at HTML/CSS though, the early
>>> days of hard coding have been replaced by IDE's. Maybe TW needs to change
>>> to something like an IDE with sound foundation in language grammar and
>>> possibly restrict what can be done through the IDE but with a hook to let
>>> the experienced programmer do what they want with appropriate
>>> responsibilities on results of course.
>>>
>>> Mario, the examples I mentioned used code like '.operator parameter'.
>>> I'll find some and mail them to this list.
>>>
>>> BobJ
>>>
>>> ---------------
>>>
>>> Dr Bob Jansen
>>>
>>> The Cultural Conversations project
>>>
>>> Turtle Lane Studios Pty Ltd trading as the Australian Centre for Oral
>>> History
>>>
>>> 122 Cameron St, Rockdale NSW 2216, Australia
>>>
>>> Ph (Korea): +82 10-4494-0328 <+82%2010-4494-0328>
>>>
>>> Ph (Australia) +61 414 297 448 <+61%20414%20297%20448>
>>>
>>> Resume: http://au.linkedin.com/in/bobjan
>>>
>>> Skype: bobjtls
>>>
>>> KakaoTalk: bobjtls
>>>
>>> http://www.cultconv.com
>>>
>>>
>>> In line with the Australian anti-spam legislation, if you wish to receive
>>> no further email from me, please send me an email with the subject "No Spam"
>>>
>>>
>>> On 1 Oct 2020, at 02:46, Saq Imtiaz <[email protected]> wrote:
>>>
>>> Perhaps adding a note in the String concatenation documentation, about
>>> using filter operators if concatenating within filters, would be helpful.I
>>> suspect that documentation hasn't been updated since the filter operators
>>> were extended with addsuffix, addprefix etc.
>>>
>>> On Wednesday, September 30, 2020 at 6:13:11 PM UTC+2, PMario wrote:
>>>>
>>>> Hi
>>>>
>>>> @Bob, The PR is active at:
>>>> https://github.com/Jermolene/TiddlyWiki5/pull/4870 If you find more
>>>> inconsistencies, that drove you crazy, let me know and we will see, how we
>>>> can approve.
>>>>
>>>> The best way it can work is, if you directly write down, what would
>>>> have helped you, in your words. .. I'll check if and how it can be
>>>> implemented.
>>>>
>>>> have fun!
>>>> mario
>>>>
>>>>
>>>> --
>>> 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/jQpUdgQQQWc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/fc76e5e6-c223-4fa8-95d0-2e3a0fb47222o%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/tiddlywiki/fc76e5e6-c223-4fa8-95d0-2e3a0fb47222o%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/1220393b-1676-490c-8e3d-2e8937c8a7a5n%40googlegroups.com.
