Talha,
In relation to your syntax question, jeremy explained it well, but we need
to help new people learn this early. The reason <<>> is used as in
<<macro>> and <<variable>> is used in wikitext is to not compete with
<htmltags></htmltags> so when you are inside a widget we need not keep up
this << >> and we fall back to < > and since these are delimiters as well
we can abandon [ ] when we place a <macro> or <variable> in widgets, that
we may have been tempted to use by the filter operators definition.
My use of tiddlywiki recently matured and it is this kind of knowledge I
wish I understood at the outset.
and includes
- The use, or not, of the variable= in lists widgets to let the current
tiddler change or not
- I now write most macros to
- change the currentTiddler if they are listing other tiddlers
- not change the current tiddler if they are returning a value I
want to use (now or further in)
- The use of <$macrocall for any macro, or widget when wanting to
include a <<macro>> or<<variable>> in the parameters
- Using {{!!fieldname}} in wiki text {!!fieldname} in filters (to
replace it with the content) or field-name in operators.
- Using the emptyMessage (in list) and emptyValue (in Set) to great
effect
- Using logical type test like has[fieldname] in filters or when
generating multiple items limit[1]
- empty message allows you to return a "false"
There is plenty of material like this to share, we just need an interactive
and easy to contribute repository. I plan to work on one soon.
Regards
Tony
On Tuesday, July 17, 2018 at 8:03:13 AM UTC+10, talha131 wrote:
>
> Stobot has put into words very clearly what I had in the back of my mind.
> Name
>
> Name is definitely an issue. A long time ago I mentioned TiddlyWiki
> Classic to my coworkers and all I get laughs. In those days when JS wasn’t
> as ubiquitous as it is today, a whole wiki system enclosed in a single file
> was nothing less than revolutionary. But they didn’t take it seriously.
>
> Of course, anyone seriously looking for versatile todo and wiki app should
> have an open mind and mustn’t be put off by the name. Moreover, tiddly is
> not alone. There are other equally hard to pronounce and funny sounding
> apps with considerable user base like
>
> 1. Anki
> 2. Vim
> 3. Mnemosyne
>
> Nonetheless, a friendlier name would not have hurt.
> Documentation
>
> TW site and this forum has plethora of information. Seasoned users here
> are very active and helpful.
>
> As a new user when I am trying to understand TW and its idioms, the site
> seems hard to navigate. Don’t get me wrong. It’s a good idea that TW hosts
> its documentation using itself. It showcases the features and strength. But
> it’s hard to navigate in the beginning, when you don’t know what a tiddler
> is or how tiddlers are linked together, or what a tag is. So a novice faces
> two problems
>
> 1. Get familiar with TW, and at the same time,
> 2. Learn from an unfamiliar UI
>
> I don’t mean TW documentation should be moved to some other static site
> generator like Hugo or Pelican or Gatsby. Perhaps, a friendlier and
> familiar theme like the material-ui Stobot suggested would be easier on
> beginners.
>
> A Gitbook like software is very useful for documentation. Writer can
> arrange the content in an order he deems suitable for the reader. Reader
> will know he is supposed to read from chapter and onward. Checkout these
> two examples
>
> 1. https://basarat.gitbooks.io/typescript/docs/quick/nodejs.html
> 2. https://redux.js.org/
>
> May be it’s just me, but their order is very clear. TW on the other hand
> is more like a mind map. You create different tiddlers and then link them
> together using tags and transclusion. TW homepage can do with a overhaul to
> make it more friendly.
> Syntax
>
> What bugs me most is that TW syntax has d/f variants and all work the same
> with littler differences. For example, macro parameter can be defined using
> : or =.
>
> \define example(p:'default')
> \define example(p='default')
>
> Variable can be access using <<__var__>> or <<var>>. But inside a filter
> using single angle bracket [tag<MyTag>]. I always second guessing myself
> the my syntax is correct.
> Programming Tutrial
>
> A tutorial on programming TW would be nice, like we have for so many other
> languages. TonyM has a book in the yammer group which is a good start.
> Plugin library is incomplete
>
> The option of installing TW plugin and themes without leaving TW is nice.
> But the default plugin library is almost barren. You will find more options
> in this Dynalist <https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM> then in
> the plugin library.
>
> JD has create a very useful revision plugin
> <https://groups.google.com/forum/#!topic/tiddlywiki/EZhMkt0BDn0> but you
> will never know about it unless you visit the forum regularly.
> Community
>
> A StackOverflow like site is better suitable for QA then this forum
> because it offers better search. I think even Discourse
> <http://www.discourse.org/> has better search and navigation then Google
> groups which is archaic. Don’t remember when was the last time Google
> updated it.
>
> A monthly newsletter would be nice too.
>
> All in all TW is a fantastic piece of software. I am sure the community it
> has will make any other software users envious. But it has a leaning curve
> which can be flattened.
>
>
--
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/e484446a-4855-443f-8cef-6771acff44fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
