[tw] Re: set story width in a stylesheet tiddler
Your code works fine when I put it in a new tiddler on tiddlywiki.com. Has your screen width perhaps dropped below 1440px? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Illness
Hi Jeremy, Wishing you a rapid recovery! – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: List field values as links?
To get unique values only, use *each*: $list filter=[each[topic1]get[topic1]] [each[topic2]get[topic2]] [each[topic3]get[topic3]] +[sort[title]]/ Most filter operators remove duplicates automatically, but *get* doesn't. Duplicates are automatically removed from a sequence of filter runs, such as: [each[topic1]get[topic1]] [each[topic2]get[topic2]] So even if the same item crops up in both topic1 and topic2, it will only appear once in the filtered output. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: How do I retrieve a list field list like: [[item one]] [[item two]] as a list without [[]] (item one item two)?
Hi Måns,
I suspect the only way to achieve this at present is to use a JavaScript
macro.
You can generate the desired string via *$list
filter=[list[ThisTiddler!!listfield]]{{!!title}} /$list*. And if you
define a macro *m* with that as its value, you can then say *$macrocall
$name=m $output=text/plain/* to obtain the string as plain text.
But you can't pass a macrocall widget as an argument to a macro, i.e. you
*can't* say:
*$macrocall $name=sentences category=All items sentences=$macrocall
$name=m $output=text/plain//*
This is because you can't pass one widget as an attribute to another.
It would be brilliant if the macrocall widget provided a way to assign its
result to a specified variable. You'd then be able say things like this:
*$macrocall $name=m $output=text/plain $variable=sentences*
*$macrocall $name=sentences category=All items
sentences=sentences/*
*/$macrocall*
I can think of lots of places where that would be extremely useful.
The set widget has a filter option which almost does what you want:
*$set name=sentences filter=*
*[list[ThisTiddler!!listfield]]*
*$macrocall $name=sentences category=All items
sentences=sentences/*
*/$set*
But it has the side effect of wrapping double square brackets round any
items that contain spaces, which rather defeats the point here.
It would be nice if there was a *join* filter operator for performing
concatenation (with a separator as its parameter), so you could say this:
*$set name=sentences filter=**[list[ThisTiddler!!listfield]join[ ]]*
*$macrocall $name=sentences category=All items
sentences=sentences/*
*/$set*
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: How do I retrieve a list field list like: [[item one]] [[item two]] as a list without [[]] (item one item two)?
This is a fascinating topic. I've raised issue 1538 https://github.com/Jermolene/TiddlyWiki5/issues/1538 for it on GitHub. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: How do I retrieve a list field list like: [[item one]] [[item two]] as a list without [[]] (item one item two)?
Hi Måns,
It's all a question of what's parsed when. Macros are just a simple text
substitution system. They know nothing about WikiText: the only special
notation they know about is *$param$* and *$(var)$*. And their results are
not parsed as WikiText either, unless they happen to be returned to a
parsed context, such as the surface level of a tiddler. So if you write
*$widget
attribute=m/*, the result of the call to *m* will *not* be treated as
WikiText.
In your case, you're passing the value *[[item one with
{{!!see_fieldvalue}}]] [[item two]]* as a parameter to your *appendButton*
macro, and therefore *that exact string* will be appended to the text of
*SomeTiddler*. The string then finds itself at the surface of a tiddler,
and so it duly gets parsed as WikiText, but by then it's too late: the
*!!field* notation will refer to a field of *SomeTiddler* rather than
*ThisTiddler*.
Setting *tv-wikilinks* to *no* doesn't suppress the *{{…}}* functionality,
but as you say, the string you're dealing with has *{{…}}* inside *[[…]]*,
and the WikiText parser always treats the contents of *[[…]]* literally,
doing no further analysis on it, other than looking for the optional *|*
suffix.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Display PDF inside tiddler
Hi Bill,
Use the technique shown at http://tiddlywiki.com/#ExternalImages.
You need a special tiddler to represent the PDF within your wiki. Let's say
this tiddler is called *CoolPDF*. Set its type to *application/pdf*, and
add a field called *_canonical_uri* (with an initial underscore) with
*Cool.pdf* or whatever the file's called as its value. Both
*[img[MyCoolPDF]]* and *{{MyCoolPDF}}* should then work.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Using Macro Substitution as a filter parameter
Hi Alan,
Macro parameters are *not* parsed as WikiText until they are returned to a
WikiText context. They're just inert strings of characters. This means your
JavaScript is receiving strings that start with *{{* and end with *}}*.
Only once the macro call has returned will its result be parsed as WikiText
and the transclusions detected and acted upon.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
Re: [tw] TW5: A tiddler that is a list of tagged tiddlers
Hi Henry, Filters can indeed be used in the Advanced Search tiddler, but only on its Filter tab. That tab is an excellent way to learn about filters. (The Standard tab, System tab and Shadows tab of Advanced Search simply search for text in those three categories of tiddlers.) You may like to read the improved filter documentation in the preview of the upcoming version 5.1.8: http://tiddlywiki.com/prerelease/#Filters – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Bug: hard linebreaks plus angle brackets plus code block
Very true, although it's then harder to make the address be a link. And you wouldn't need the angle brackets – they're really only there to delimit the address in ordinary prose. The typographical styling of the code element would be a sufficient delimiter. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Bug: hard linebreaks plus angle brackets plus code block
The hard line breaks are not actually relevant: you can get the same
effect without them.
When a sequence of letters and digits (and hyphens and dollar signs)
immediately follows a left angle bracket, TiddlyWiki treats this as the
start of an opening tag.
*michaelabcde/michael* thus gets passed straight through to the HTML of
the rendered tiddler. You could in fact style the text (*abcde*) using CSS:
*michael { color: red; font-size: 200%; }*
So basically angle brackets are part of TiddlyWiki's fundamental syntax,
and to escape them you have to use standard HTML techniques such as *lt;*
or *#60;*. For quoting email addresses, I suggest using a macro:
*\define email(user,domain) lt;$user$@$domain$gt;*
*email michael microsoft.com*
In a published wiki, splitting the address into two pieces like that may
help to conceal it from harvesters.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TW Community Search
Hi Erwan, Feel free to index http://ae-railroad.tiddlyspot.com/ if you wish, although there may be little point, as that plugin will be directly documented on tiddlywiki.com in a few days' time when 5.1.8 is released. The other tiddlyspots I've published are temporary and not worth indexing. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Next stop on the railroad
Hi Michael, Is there a way to make the text in a single box (single railroad car?) multi-line? I'd asked myself the same question, but the answer is: not without rewriting most of the underlying library https://github.com/tabatkins/railroad-diagrams. What you *can* do is break a large diagram into smaller diagrams, and have a master diagram that merely contains links to the smaller ones. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Automattically adding date created to title of tiddler
Hi Dmitry,
There's a *new journal* button in the Tools tab of the sidebar. It creates
a new tiddler with today's date as its title. The Control Panel lets you adjust
the exact format http://tiddlywiki.com/#Creating%20journal%20tiddlers of
the title.
Putting *{{!!created}}* in the title doesn't work, because tiddler titles
can't contain WikiText. Or more accurately, WikiText syntax isn't processed
in tiddler titles. Tiddler titles have to be fixed strings of characters.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
Are you sure about that? Positive. If you don't believe me, look at the code in filters/list.js. It starts by retrieving an array of titles from the list field. *list* without an exclamation mark simply returns that array. But negated *list* iterates over its input titles, i.e. *tag[foo]* in my example, and it outputs only those input titles that are *not* in the array. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Changing an Image from Embedded to _canonical_uri
A very interesting link – thank you, Mario. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
I guess it was not intended to operate on a list of tiddlers. It's implemented like any other filter operator, taking an input list and producing an output list. I think it should rather be *[has[type]each[type]get[type]*... not returning blanks. But *get* never returns blanks, although *each* does return tiddlers in which the field in question is blank. So on tiddlywiki.com at present, *[each[color]]* returns six titles, whereas *[get[color]]* and *[each[get[color]]* return five. But perhaps there is a case where you do want specifically declared blanks, rather than undefined. In exploring the *title* operator today, I've discovered that it supports negation (previously undocumented). *title[x]* is absolute, ignoring its input. But *!title[x]* is relative, and serves to filter out *x* from the input. Oddly, though, it doesn't filter out *x* if *x* doesn't exist as a tiddler. So we can't use *!title[]* to filter out blanks from other lists. I was about to extend *each*, so it does handle list fields So that, given one tiddler with list *A B C* and another with list *A C E G*, it would return *A B C E G*? That sounds like a relative form of the *list* operator: *[tag[foo]list:relative[]]*. Or an absolute form of it that somehow took a *list* of text references as its parameter. Perhaps it should rather be: *[tag[foo]get:list[]]* or *[**tag[foo]* *get:list[my-list-field]]* with the behaviour you describe That would also be logical. In fact, the concept of unpacking a list into an array is so useful that maybe it deserves its own unsuffixed operator. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
One othe related oddity of the *list* operator is that it behaves very differently when negated: * *[list[t!!f]]* is absolute, and outputs the titles listed in field *f* of tiddler *t* * *[tag[foo]!list[t!!f]]* is relative, and outputs any foo-tagged titles that are not listed in field *f* of tiddler *t* – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
In fact, the concept of unpacking a list into an array is so useful that maybe it deserves its own unsuffixed operator. And come to think of it, that operator already exists: it's *list[tiddler!!field]*. What's needed is the reverse of that, so that the parameter (*tiddler!!field*) can be specified as the input instead. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
Hi Alan, It's interesting you mention this, because I was on the verge of posting something to the Dev group about this yesterday. The *get* operator will output a list of the values in a specified field in its input tiddlers: *[tag[Example]get[my-field]]*. But the output can contain duplicates. This is odd, because every other filter operator takes care to avoid outputting duplicates. I wonder if *get* is *intended* to be different. Or is this an oversight that ought to be fixed? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is it possible to get a list of unique values of a single field?
Interesting. Why is *get* special, such that *[get[type]]* doesn't mean *[each[type]get[type]*? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Changing an Image from Embedded to _canonical_uri
*addTiddler* appears to also update existing tiddlers, and only those fields handed down in the fields object. When a field is explicitly declared as *undefined* or *null*, it is deleted. *addTiddler* either just accepts its parameter as a tiddler, or it constructs a new tiddler using its parameter as a definition of the fields. The tiddler constructor accepts *multiple* parameters, and therefore it has to handle the possibility of a particular field being defined by more than one of the parameters. A value found in a later parameter will override a value found in an earlier one. The special case is that overriding with a value of *undefined* or *null* will actually delete the field altogether. So you're right that the tiddler constructor can delete fields, but it's deleting them from the tiddler that's under construction. And that's fine, because the fields of that tiddler don't get frozen until the *end* of the constructor. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Changing an Image from Embedded to _canonical_uri
I couldn't quite decipher how *addTiddler *circumvents this. I don't think it does. The tiddler constructor function freezes the tiddler's map of fields and the value of each field. *addTiddler* constructs an entirely new tiddler and slots it into the wiki's map of tiddlers, replacing the reference to the old tiddler of that title. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Changing an Image from Embedded to _canonical_uri
Anyhow, updating a tiddler essentially means deleting the old one and overwriting it with another. Yes. The *setText* method of the wiki object is perhaps the simplest case of this. Would be good if there were some instructions on how to handle *getCreationFields *and *getModificationFields *in the context of the execution and when to write / update which. It's certainly confusing. As an example, when *setText* encounters a data tiddler, it calls *setTiddlerData*, which passes *getCreationFields()* to *addTiddler*. However, it passes other parameters, too, and these will normally *override* the *created* field, setting it back to its pre-existing value (including deleting it again if it didn't previously have such a field). That sort of complexity deserves at least a small explanatory comment in the code :) Presumably the reason for freezing the fields is to force all modifications to go through a single point – namely *addTiddler* – to guarantee that the display gets refreshed in response. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: Free JavaScripts site! - how install?
There are coding conventions in TW which to the beginner JS programmer may find puzzling. For example in Tobias' example plugin we have a line which says tid = tid The actual line is: *tid = tid || GettingStarted* That's conceptually similar to the less puzzling line: *tid = tid + 1* which causes *tid* to be set to its own previous value + 1. In Tobias's example, the *||* symbol means or else, and the line causes *tid* to be set to either its current value, or else (if *tid* isn't currently set to anything) to *GettingStarted*. This is a common idiom for supplying a default value for a parameter in JavaScript. Tobias's example doesn't actually need to use the word *var* (which introduces a new variable), because *tid* has already been declared (as a parameter). – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] css and transclusion
Hi Jon,
You could enclose {{mytiddler}} in a div and then style that.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Which plugin to see Motovun Jack.pdf ?
Hi Mat, I think Jeremy talked about JSONP in one of the three or four most recent hangouts. I recall him describing it as really horrible or words to that effect :) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Lists, Filters and Orphans - thoughts
Hi Mat, If it hadn't been for the space between } } which I initially assumed was a typo, I wouldn't have figured out what is happening. Yes, it's cryptic stuff. I agree that any documentation that uses this example should explain it a bit more. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
Hi Tobias, I'd be inclined to make the same suggestion as I have to Danielo... I was trying to follow the instructions at http://tiddlywiki.com/#PluginMechanism: *Plugin authors are encouraged to provide special information and documentation tiddlers that TiddlyWiki can include as plugin information tabs in the control panel.* If you think that's bad practice, I recommend you propose a change to the instructions. Please consider shipping the plugin with one mater example that shows it all. That's what the example in the Example tab was trying to do, but maybe it can be improved. See below :) Also, I think it would be better to just see the example code, not the output with some pseudo-code that is hard to read... and get to. I've changed that example so that it directly shows the notation above the diagram. Finally, that example tab in the current documentation shows an error. Oops. That's because I hadn't updated http://ae-railroad.tiddlyspot.com http://www.google.com/url?q=http%3A%2F%2Fae-railroad.tiddlyspot.com%2Fsa=Dsntz=1usg=AFQjCNHj2jp2vPJwXyS-pRLcIdBsQkfC8g to the latest prerelease core. Thanks – now fixed. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
Also, this is TW5, not TWC. Sorry, how stupid of me! All I can say is: it was late at night when I posted. I'll start a new TW5 thread for any further discussion that would have appeared in this one. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] [TW5] Next stop on the railroad
You may not have seen this thread: https://groups.google.com/forum/#!topic/TiddlyWiki/b57cfTZoI5w … because I goofed and typed [TWC] instead of [TW5] in the title. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Context Search plugin updated
Picking up on Tobias's comment at https://groups.google.com/forum/#!topic/TiddlyWiki/b57cfTZoI5w: Maybe the documentation for plugins in Jermolene's repository (i.e. plugins that are version-linked to the core, such as KaTeX and railroad) should be held centrally on tiddlywiki.com. In the current thread, Tobias said: I pretty much create a new TiddlySpot (or other individual wiki) for every little thing. To document and showcase individually. I find that helps with the focus. I can see both sides of this. Certainly it's good to avoid mixing things up into a muddly mess. On the other hand, you then have to spend more time maintaining everything when (say) a new version of the core is released. Personally, I also wouldn't ship js comments with the core. Perhaps plugins should offer an alternative compact version of themselves, in which the JavaScript would be minified and the documentation removed. Then the user could choose which they want. But this would mean more work for the plugin developer. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Context Search plugin updated
Out of interest, I've just tried minifying a couple of large JS files from the core (boot.js and wiki,js) and a couple of small ones (addprefix.js and textparser.js). The result in each case was just under half the size of the original file. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
By the way, this discussion should really be in the TW5 thread I created after it was pointed out that I'd labelled this one TWC… https://groups.google.com/forum/#!topic/tiddlywiki/p-xfq5Jxq4I I suggest we move over there. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Lists, Filters and Orphans - thoughts
An even better example would be something like:
*\define concat(1 2 3 4 5) $1$$2$$3$$4$$5$*
*concat abc{{ Getting Started } }def*
making it clearer that there's nothing special about *{{* and *}}* being
first and last in the macro's result string.
A counterexample would also be good:
*\define itself(x) $x$*
*itself {{GettingStarted}}*
That one *doesn't* transclude anything, because the return value of the
macro call is parsed in isolation, so it can't see the closing *}}* and so
doesn't match the syntax for a transclusion.
Pushing the edge cases still further:
*{{itself GettingStarted}}*
results in nothing at all. The macro call returns the string
*GettingStarted*, which the parser then recognises as a link – and this
link then makes no sense within the transclusion brackets.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
Hi Mario, Thank you for filling in some gaps in my knowledge of the *vnd.* and *x-* prefixes. Do you think, the railroad grammar should be a tiddlywiki mime type, or should it have its own mime type. eg: text/x-railroad .. as long as it is experimental. I don't mind. An x- type would be fine. Does the grammar you use have its own mime type? Or did you design it for TW? I designed it for TW, basing it on EBNF http://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form. Note that it contains syntax for linking to and transcluding tiddlers, so it really is very TW-specific. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
So x-types will definitely break some user content, when it's changed to
vnd. later on.
There's no technical reason why we couldn't support both. More than one
MIME type can be attached to the same TiddlyWiki parser module.
As it is based on EBNF, imo it should be a real subset of EBNF.
EBNF is great for formal grammar analysis, but it wasn't designed for ease
of producing railroad diagrams. For example, as far as I know, EBNF has no
compact way to express the separator in a list. But that's a specific
component of railroad diagrams, and is represented in my notation as *{
item +separator }*.
So one could take tiddler content and convert it to full EBNF with a
simple converter.
That's a very interesting idea. But you'd need a formalism for how the rest
of the tiddler should be laid out. Bear in mind that a railroad diagram
represents just one rule of a grammar, whereas EBNF is a list of rules.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TWC] Next stop on the railroad
So one could take tiddler content and convert it to full EBNF with a simple converter. More on this! While converting EBNF to a railroad diagram is non-trivial, it would be pretty easy to go the other way. It would just need an additional pragma for specifying the name of the rule (i.e. the nonterminal) being defined in the diagram. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Lists, Filters and Orphans - thoughts
Hi Matthew, The problem (if you can call it that) is that if the only time a tiddler is referenced is as part of a filtered list, then it shows up as an orphan. Coincidentally, I'm currently revising the documentation of all the filter operators, and I've noticed a very similar problem. The system for detecting links (and hence also backlinks, orphans and missing tiddlers) doesn't detect links that are: * contained in text trancluded from elsewhere * supplied via a macro or variable * generated by a link widget whose *to* attribute is a transclusion, macro or variable In order to make the documentation clear and accurate, I've actually given this phenomenon a name: not all links are observable. However, in your case, the only link is in fact a mention in a filter, which I wouldn't expect to count as a link by any definition. A simple solution for you might be to ignore the standard Orphans tab, and instead create your own list with a more specialised filter, e.g. *[all[orphans]!tag[Journal]]* – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Lists, Filters and Orphans - thoughts
$:/core/Filters/Orphans
http://www.google.com/url?q=http%3A%2F%2Ftiddlywiki.com%2F%23%2524%253A%252Fcore%252FFilters%252FOrphanssa=Dsntz=1usg=AFQjCNGUYLEDQgIE5-fIbWEROK-8Q5M98A
That tiddler is only used for populating the dropdown list on the Filter
tab of Advanced Search.
Variable Parameter Defaults @tb5
http://www.google.com/url?q=http%3A%2F%2Ftb5.tiddlyspot.com%2F%23Variable%2520Parameter%2520Defaultssa=Dsntz=1usg=AFQjCNFBCFXY-PnxZEMCynbMeyDFyM9niw
Those work because macro parameters are dumb. They're just simple strings
of characters, and not parsed at all. This is true both of the default
values specified on the *\define* line, and of the values passed when a
macro is called.
A macro call returns a string that is the value/definition of the
underlying variable/macro, with any *$parameter$* placeholders filled in
via trivial textual replacement. Only once the string has been returned
does it finally get parsed.
For the same reason, the following weirdness also works:
*\define concat(1 2 3 4 5) $1$$2$$3$$4$$5$concat {{ Hello There } }*
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] [TWC] Next stop on the railroad
I've done some more work on the railroad plugin. You can now store a diagram's notation in a dedicated tiddler of type *text/vnd.tiddlywiki.railroad*, and simply transclude that tiddler to wherever you want the diagram to show up. The explicit *$railroad* widget is still supported, of course, and won't ever be removed. I've added widget attributes for controlling the style of the diagram's start and end points – the double vertical line looked too bulky. The default is now a single line. These options can also be specified via pragmas such as *\arrow yes*, *\start double* and *\end none* in the diagram notation itself. Demo: http://ae-railroad.tiddlyspot.com/ – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: TW5 beginners question: template to render link+content?
Hi Joerg,
You can do this either way. The template could say:
*! {{!!title}}{{!!text}}*
(The template itself then displays a recursive transclusion error, but
that's normal in such cases: the template's text is including itself, ad
infinitum.)
Or you could use a macro:
*\define chapter(tiddler)! {{$tiddler$!!title}}{{$tiddler$}}\end*
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TW5 beginners question: template to render link+content?
Hi Jörg,
$transclude/
Or, as I suggested, *{{!!text}}*, which avoids the need for an explicit
widget, and is very slightly shorter :)
Is there a way to avoid the 'Recursive transclusion error in transclude
widget' error message in the template itself?
Not really, because when you view the template itself, the current tiddler
– i.e. the context against which *$transclude/* or *{{!!text}}* operate –
is the template itself. The result is that the tiddler attempts to
transclude a copy of itself, which would lead to a bottomless pit of
recursion.
You could always use CSS to hide the error:
*.tc-error { display: none; }*
But then you won't see other more important errors that may turn up.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: TW5 beginners question: template to render link+content?
Tobias's method is the most idiomatic, because it uses a filter to select the chapters. Furthermore, you could wrap it up in a macro and pass any desired chapter filter as a parameter. Very nice. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Conditional table rows
Thanks, Tobias. That seems like an elegant solution. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: The Concept of Tags and Tagging
Hi Mat, There will be tiddlers that are difficult to find, as exemplified by the tiddler Tagging http://tiddlywiki.com/#Tagging and someone curious about how to use tags and therefore searches tags. Part of the difficulty is the word-stemming issue that Mario has mentioned. At present, the search system looks for *exact* matches only, so a search for *tags* will not find *tagging*. At least the search system is case-insensitive :) But there's also the issue of synonyms and controlled vocabularies. The user might search for *labels* or *categories*, unaware that TiddlyWiki terminology uses the word *tag*. Perhaps it would be nice if the search system made it clear which of the results were found as *tags*, just as it currently indicates which of the results were found in *titles*. One can imagine a dedicated mechanism for searching* only* the tags, perhaps as a filter at the top of the Tags tab in the sidebar. Perhaps the Tags tab should be promoted to the top level of the sidebar, as at http://tb5.tiddlyspot.com/, where users would discover it more easily. Note that this is an example of a carefully designed and tagged tiddler. But *has* the *Tagging* tiddler been sufficiently carefully designed and tagged? In my opinion, it contains too much information – too many sections that really belong in tiddlers of their own. And I think the *Tagging* tiddler should be called *Tags*, as that's a more likely thing for people to search for. (Tags are concrete things; tagging is an action – more abstract and complicated-seeming.) The *Tagging*/*Tags* tiddler currently carries the *Concepts* tag. In other words, it's been filed (correctly) under *Concepts*. Likewise, other tiddlers that discuss how to use tags should be filed under (i.e. tagged with) *Tags*. Tags are such an important concept in TiddlyWiki that it's slightly surprising that tiddlywiki.com doesn't yet have a *Tags* tag. If we delegate ad hoc tags to be part of the text, we have a problem when the tiddler is not really common text. I'm not fully understanding the difference between an ad hoc tag and any other tag. A tag X is just a way of saying I want to file this tiddler under X. The neat thing about tags, of course, is that – unlike folder-based filing systems – you can file the same tiddler under *several* tags. The table of contents (TOC) can then present your filing system *as if* it was folder-based, and you can choose which tags participate in the TOC. Perhaps an ad hoc tag is merely a tag that isn't attached to the TOC, i.e. a tag whose tiddler isn't tagged *TableOfContents* or whatever. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: The Concept of Tags and Tagging
Hi Mario, Adding a tag to a tiddler *means* filing the tiddler under that tag, as a child to a parent, a many-to-one link. This is true even for tags that are just temporary markers or spur-of-the-moment annotations. Whether a user chooses to make any further use of that filing mechanism is up to them, but it's inherently there in TiddlyWiki's design. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Tip: Fresh TW5 on TiddlySpot - how to set it up quickly
Hi Birthe, Error:NS_ERROR_DOM_BAD_URI: Access to restricted URI denied. Same here. In fact this seems to be normal – the error is mentioned at http://tiddlywiki.com/#Saving%20on%20TiddlySpot. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Glitch importing lists from Classic
The rationale can be found in a thread from mid-2013 here: https://groups.google.com/forum/#!topic/tiddlywikidev/dLn04Z4Vl5w – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] [TW5] Conditional table rows
Here is a table with an optional middle row. (Change *text=y* to *text=x* to reveal it.) table trtdJanuary/tdtd2015/td/tr *$reveal default=x type=match text=ytrtdFebruary/tdtd2016/td/tr/$reveal* trtdMarch/tdtd2017/td/tr /table But if you try this, you'll find that it generates *span class=tc-reveal* around the middle row, and this ruins the table's layout. The reveal widget will generate *div class=tc-reveal* instead if it believes it's being parsed in block mode. But if I add blank lines, a p element gets generated, and this ruins the layout in a different way. Is it possible to make a row of a table conditional, and if so, how? Incidentally, I think my use case for this would be satisfied by a new \ifdef pragma, as discussed here: https://groups.google.com/forum/#!topic/tiddlywiki/VX1qnNb48PI – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: The Concept of Tags and Tagging
Regarding the parent–child relationship, notice how the core table-of-contents macro assumes that tags are pointers to parent tiddlers. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Problem With Variable Text Reference In Filter
this magick-voodoo-wikitext-kungfu It's staggeringly powerful, but it also comes close to being a write-only language. The necessary mechanisms have to be created using the existing mechanisms every time, which leads to a low signal-to-noise ratio. Have you considered spending some time putting together a plugin offering widgets and macros to simplify the task of writing program-like tiddlers? There are plenty of recurring patterns, such as *$set name=x value=$x$* to copy a macro parameter into a variable, and the use of *$list filter=...* to mean *if*. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Ordering the table of contents
Hi Danielo, Add the list field to the tiddler that represents the parent level in the contents. A good example is http://tiddlywiki.com/#Reference. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Problem With Variable Text Reference In Filter
Hi Felix, That's the sort of thing: a system that would offer more readable syntax for higher-level programming operations (for, if, concat, etc) that are needed over and over again. TiddlyWiki itself is already a kind of templating system, by virtue of its variables and transclusions. In my mind, I hadn't gone as far as envisaging an MVC system, but that would be a good way to organise these sorts of code tiddlers. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: The Concept of Tags and Tagging
Hi Mat, there are simply different ways of thinking And people have different requirements as to what they want to be able to extract from a wiki. Now, how should I tag this tiddler? A key decision is whether you want people other than yourself to be able to find the tiddler. There's a world of difference between searching for a particular tiddler you know exists (because you put it there) and searching to see *whether* any relevant tiddlers exist. Preparing a wiki to support the latter is like writing an index. I really like Douglas Hofstadter's comment at the start of the index to his book *Le Ton beau de Marot*: Doing an index is a lesson to end all lessons in the vagueness and subjectivity of human categories. For this reason it is desirable to be able to hide tags from view mode(!) on command. Yes. But the techniques to support this already exist. Tags can be classified in various ways (at least three have been suggested), and the view template can then filter based on that classification – and a simple UI can allow the user to change the filter as desired. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] The Concept of Tags and Tagging
Hi Andrew, Your replies are showing up as separate threads from the messages you're replying to. Or at least they are in the Google Groups web interface. Something at your end is adding a *[tw]* prefix to the subject lines. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] The Concept of Tags and Tagging
Hi Andrew, My humble apologies, then. It's not a big problem :) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Edit tags from multiple tiddlers
Hi Terenor, I think this falls into the category of global search and replace, which is a feature that's on the roadmap. But Stephan Hradek has an example called RenameTags at http://tw5magick.tiddlyspot.com/. developing plugins is daunting. Is there a step by step guide with pointers to prerequisites for those with no prior experience? I don't think there is, but there ought to be. I think that http://www.tiddlywiki.com/dev ought to contain a reasonably detailed explanation of how the code actually works – not to the level of individual lines, but documenting the main classes and functions and principles of use, i.e. the API. These can be deduced by reading the code, but that's time-consuming. I recently wrote a plugin containing a widget for generating railroad diagrams. This was my first experience at writing a TiddlyWiki plugin, although I was undoubtedly helped by the fact that I work as a developer and have tinkered with JavaScript before. The railroad plugin is a wrapper around an independent JavaScript library, so I started by finding another plugin that's like that. I chose the KaTeX plugin, took a copy of it, and stripped out all the KaTeX-specific stuff, and this left me with the bare bones of a plugin that did nothing. I then began to add simple things to the skeleton to see what would work and what wouldn't, and what ought to go where. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Problem With Variable Text Reference In Filter
Hi Tobias,
To figure this out, I added *$text text=items* just before *$list
filter=items/*. This revealed that *items* contains strings like
*[field:type[{{$:/library/sjcl.js!!type}}]sort[]]*, which are invalid
filters.
So the problem is that the *currentGroup* variable stores the syntax of a
transclusion rather than the result of performing that transclusion.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Semantic fieldnames
Hi Mat, Like Andrew, I'm not sure I entirely understand your list. hidepill:foo A field is a name–value pair. I believe you're suggesting a field whose *name* is *hidepill:foo*. What would the *value* of this field be? And what would the placeholder *foo* be replaced by in practice? I think the basic idea here is a way of *classifying* tags semantically, so that a filter could select (let's say) all of the tiddlers carrying a tag of a particular semantic class, such as *author* or *publication* or *language*. For example, a tiddler might have the tag *Shakespeare*, and *Shakespeare* would be classed as an author. This can be achieved via fields, as Jeremy points out in the first of the two GitHub discussions you linked to. I guess it can also be achieved by adding an *author* tag to the *Shakespeare* tiddler. Are you looking for a way to make a field show up as something like a tag pill when you view a tiddler that carries that field? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Problem With Variable Text Reference In Filter
Hi BJ,
Yes, that seems to be the solution, i.e. simplifying the invalid
*[…[{{…}}]]* to the correct *[…{…}]* syntax for a filter sep.
– æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Search
Hi Alan, Yes, I sometimes find that a bit frustrating, too. The underlying search function in the TiddlyWiki code has an option to treat the entire search term literally. However, the search filter operator (as used by the sidebar search system) provides no way to set this option. In the absence of this option, the search function splits the search term into several pieces, using a sequence of one or more spaces as the separator. Any tiddler that contains any of the pieces (either as a whole word or not) is then considered to be a match. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Install from GitHub - how?
Hi Felix, A drag and drop from the demo site would certainly be much easier. I should have read to the end of your GitHub readme :) At least the Node.js info I've given may help someone else with a similar question some day. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
Hi Branimir, You're very welcome. Note, if it's not already obvious, that the diagrams' colours, line thicknesses, etc can be adjusted via CSS. The plugin contains a default CSS tiddler. Do people like the default colour scheme? It's simply what came with the underlying diagram library, but could be modified if desired. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
Hi Tobias, Thanks for those CSS suggestions. They're great improvements, that make the diagrams feel much less heavy and clunky. It's a bit of a bummer that the text is actually controlled via stroke and stroke-width Eh? It's an SVG text element, controlled by normal CSS font properties. I've removed the bold setting. The result can be seen at http://ae-railroad.tiddlyspot.com/ – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Table of Content generate from tags
Hi Tobias, You've got /styles instead of /style at the end of in the catlist macro. I'm impressed by the speed with which you create these complicated macros. You write them in far less time than it takes me to understand what you've written! Do you find these sort of macros easy to read if you come back to them a week later? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] I asked a question a long time ago and it is still relevant today
The federation techniques that Jeremy discussed in a recent hangout are probably the only plausible way to allow a collection of TiddlyWikis to function as a forum. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Install from GitHub - how?
Hi Mat, I think the easiest way to do this is to use Node.js. (If there's an easier way, I'm sure someone else will soon let us know :) Download a copy of Jeremy's repository by clicking Download ZIP at https://github.com/Jermolene/TiddlyWiki5/tree/master and unzip it. Then do the same for Felix's repository. His zip file contains a *dist* folder with a *felixhayashi* subfolder. Copy the *felixhayashi* folder so that it becomes a subfolder of the *TiddlyWiki5/plugins* folder in your unzipped copy of Jeremy's repository, i.e. so that it sits alongside the existing *tiddlywiki* folder there. Then go to one of the subfolders of *editions*, e.g. *empty* or (to get some content to play with) *tw5.com*. In there you'll find a text file called *tiddlywiki.info*, which contains (among other things) a list of plugins. Add Felix's plugin to the end of the list, with a comma separating it from the previous item, like this: plugins: [ tiddlywiki/googleanalytics, ... tiddlywiki/railroad *,felixhayashi/topstoryview* ], Now all you need do is: - go to a terminal window or command prompt, - change directory to the TiddlyWiki5 folder of your copy of Jeremy's repository (where a file called *tiddlywiki.js* resides), - run *node tiddlywiki.js editions/empty --server* (changing *empty* to whichever edition you chose to add the plugin to), - and in your browser go to *http://127.0.01:8080/* (or whatever address Node.js tells you it's serving the wiki on). Good luck! – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
Awesome, Jeremy. Many thanks. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
Further to my previous comment, I've just discovered that `[backlinks[]]` and `[all[orphans]]` don't take account of most automated links. For instance, if I have a tiddler whose text is my-macro [[Target]] then the Target tiddler has an empty References list and shows up on the Orphans tab. And if the Target tiddler doesn't exist, it doesn't show up on the Missing tab. It's much the same situation if I have a tiddler whose text is $list filter=[title[Target]] $linkclick here/$link /$list As a result of this, the tiddlywiki.com site shows almost half of its tiddlers as orphans, even though most of them aren't. Interestingly, things *do* work correctly if I have a tiddler whose text is $link to=Targetclick here/$link Apologies if this has been discussed before, but it's a difficult thing to search the group for. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
Hi Tobias, Your alink macro would be really handy for use in the TiddlyWiki documentation. It would significantly reduce the file size, because we have lots of links of the form `[[…|…]]` (and we will be acquiring more over time). The main drawback is that it's not understood by important filters such as `[backlinks[]]` and `[all[orphans]]`, which means that the sidebar Orphans tab can show false positives and the info References tab can incorrectly show nothing. A comment about the implementation: The regexp doesn't check for a trailing pipe sign, so `a: tab` will match `|table`. The fact that your example shows `|alias|aliases` suggests this isn't what you intended. It would be problematic if one tiddler had an alias of `|tab` and another had an alias of `|table` – it wouldn't be clear which one `a: tab` (or indeed `a: ta`) would link to. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
I've just added a feature that I think greatly improves the readability of the railroad diagrams. Where the diagram loops back on itself, it now has an arrow to make it clear that the track runs from right to left at that point. http://ae-railroad.tiddlyspot.com/ The arrow can be turned off by setting the $railroad widget's arrow attribute to no. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Add to top of ViewTemplate
Give your tiddler a list-before field, but leave its value empty. The techniques available are the same as described for tag ordering at http://tiddlywiki.com/#Tagging – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
Hi Tobias, that looks like poor use of double square brackets to me... Let me suggest a less abstract example, then. Your tb5 site offers a macro for colouring text http://tb5.tiddlyspot.com/#Colored%20Text. One can easily imagine passing a whole sentence, e.g. a warning message, to this macro, and that sentence could contain a link. That link would not be detected by the link-tracking system that drives the References and Orphans tabs. There could well be a recommendation to always use single or double quotes or triple double quotes for strings and reserve double square brackets for tiddler titles only. But that still wouldn't solve the general case in which a quote-delimited parameter can contain a double-square-bracketed link as *part* of its content. Perhaps tiddler-links, or TiddlyLinks but not static links. I agree that static isn't the right word, but the alternatives you suggest could apply equally well to links generated on the fly by macros and widgets and whatnot. Perhaps we could speak of a literal link – a link that is literally present in the text field of a tiddler. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Add to top of ViewTemplate
Agreed. In fact I almost mentioned that in my initial reply. TemplateOrder sounds almost mystical :) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
Indeed. But the author of the JavaScript library underlying the widget was aiming to reproduce the appearance of the railroad diagrams on the JSON site http://www.json.org/, and those lack arrows. So the widget makes the arrows optional. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
Hi Tobias, They could even be shorter, if that's feasible. Good idea – done. The shorter arrow also means I no longer need to artificially increase the height of the backward arc to avoid a cramped appearance. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
Hi Tobias, Sorry if I misunderstood. I got the impression we were talking slightly at cross-purposes, so felt the need to clarify further. But we're in agreement. Manual link isn't bad. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
On further reflection, the problem of backlinks and orphans is not as important as I initially thought. Links that are automatically generated by a filter-based widget will normally always be links to *existing* tiddlers, otherwise the filter wouldn't have selected them. So these links can be filed under things the system takes care of so you don't have to. But it's potentially problematic that the system doesn't keep track of links within macro parameters. If TiddlerOne passes a sentence of ordinary text to a simple macro that just returns its parameter in bold with a red background, and if that sentence contains a link to TiddlerTwo, then it would be nice if TiddlerTwo recognised TiddlerOne on its info References tab. I suppose the difficulty is that the system can't easily detect whether the macro returns its parameter intact. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Plugin for the-insensitive links?
Hi Tobias, So long as (part of?) a macro parameter is declared via double square brackets, that may be achieved. How so? While it's possible to use double square brackets to delimit a macro parameter, these are merely an alternative for quotes. They have no link semantics. For example, given `\define emphasis(_) //$_$//`, the call `emphasis [[Target Tiddler]]` returns `//Target Tiddler//` rather than any kind of link to Target Tiddler. I believe a macro parameter is *always* a mere string of characters, no matter how it's passed. Even if you use the $macrocall widget, $macrocall $name=emphasis _=[[Target Tiddler]]/ the parameter remains a string, in this case `[[Target Tiddler]]`. The issue is that macros are dynamic, so they're not really suitable candidates for the rapid indexing relied on by things like [backlinks[]] and [all[orphans]]. I wonder if the message No tiddlers link to this one on the References tab ought to say No tiddlers contain static links to this one? – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Prerelease of 5.1.8
there are many, many updates to the documentation And be aware that further changes* to the documentation of filter syntax are in the pipeline – including a thorough overhaul of the step-by-step introduction – but my incompetence with the Git command line meant that these narrowly missed making it into the new prerelease. * https://github.com/Jermolene/TiddlyWiki5/pull/1360 Git is rightly named :) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] YoutubePlugin (tentative)
Hi Tobias, That is utterly brilliant. My own contribution was pathetic in comparison :) What you've done there also serves as a great practical example for intermediate users of how to use some of the more advanced TiddlyWiki techniques. I'm sure I will learn a lot from it. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] YoutubePlugin (tentative)
Hi Rich, On your videos the start point on all videos is actually 00:00:00 and you are Jumping Playback to specific point. If you play a Tiddler once it starts at the correct spot and stops correctly if you hit the Replay button it starts at 00:00:00. Interestingly, I get that effect on Chrome, but not on Firefox. Hitting Replay on Firefox plays the correct segment of the video again. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
Hi Rich, Sorry for the delay in replying, but pleased you figured things out. Switching the order of parameters to a macro is merely a matter of switching their order within the parentheses on the \define line. If you need to include the (double quote) character when you pass a value to a macro, there's an easy solution: enclose the value in (triple double quotes). There's an example under Multiline Parameters at http://tiddlywiki.com/#Macros%20in%20WikiText – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] [TW5] Default colour palettes
According to http://tiddlywiki.com/#ColourPalettes: By convention, each [[theme|Themes]] provides a default colour palette in the tiddler [[$:/config/DefaultPalette]]. Thus, setting the tiddler [[$:/theme]] to the string `$:/config/DefaultPalette` will revert to the palette packaged with the current theme (as long as it hasn't been redefined, since it is a shadow tiddler). Is this still true? I can't find any trace of $:/config/DefaultPalette, and following the instruction in the second sentence above seems to have no effect. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
Jed has produced a superb interface there. I am flumoxed and think there is a simple space issue in the code. Could you expand on that thought? I've had another look at the JavaScript of the youtube-embed macro, and can't see anything wrong with it. I've added some comments to it (on http://aelocson-test-1.tiddlyspot.com) that may help you better understand how it works. But I did spot a mistake I'd made in the definition of the topiclink macro. It was using the value of hangoutprefix as the prefix of the target of its generated link, where it should have been using the string TwHo# plus the value of hangout - which should be a simple number, like this: \define hangout() 73 Apologies for that: it's now corrected. The trap I fell into when I first experimented with JavaScript macro modules was that I expected my changes to the macro's cde to immediately show up in the tiddlers that called the macro. But they don't. You have to refresh the page first, so that TiddlyWiki gets a chance to re-execute the module definition. This can be bewildering if you don't realise what's going on. Additional confusion may have arisen from the fact that I've published these macros to you in several steps, and later steps have modified some of my work in earlier steps. I adjusted some of the parameter names, for example. I'll reply to your Dev posting with some thoughts on debugging. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
But on further investigation… You were right, Rich. There was a mistake in the embed macro. I'd missed off the closing dollar sign of $start$ and $end$. This was causing the youtube-embed JavaScript macro to receive the strings $start and $end as its parameters, wreaking havoc. Bizarrely, embed was still embedding a YouTube video that played the expected section when clicked. At least, it was for me. I don't claim to understand that. I've uploaded a corrected version to TiddlySpot. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
Well, I've put together a working example at http://aelocson-test-1.tiddlyspot.com. This contains a new macro for embedding the hangout videos. Hopefully it's not too hard to follow. Things are less messy now. You no longer need to define youtubeid at the start of each hangout tiddler. Instead, the IDs live in a data tiddler called $:/.rich/data/videos, where the various macros look up the hangout number using text references (http://tiddlywiki.com/#TextReference). It occurs to me that your entire spreadsheet could be converted into a set of data tiddlers, and the entire content of each hangout tiddler could be generated automatically from that information. In fact, it would be possible to generate the entire hangouts wiki from a separate source, such as your spreadsheet or even another TiddlyWiki. But I'm not going to bite off more than I can chew :) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] Nested $macrocall?
Hi Stephan, That's a brilliant suggestion. For anyone interested in the future, here's a tested example: \define m1(x) 1($x$) \define m2(y) 2($y$) \define m3(z) 3($z$) $set name=m2result value=m3 abc m2result and $macrocall $name=m1 x=abc/ and $macrocall $name=m1 x=m2result/ /$set … which returns: 3(abc) and 1(abc) and 1(3(abc)) – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
Hi Rich, Glad to help. A good next step would be to macro-ify the remaining markup for each topic in a hangout. Add a tiddler called $:/.rich/macros/topic with the $:/tags/Macro tag and the following content: \define topic(description, time, minSec) yt $time$ $minSec$ ''---'' $description$ \end \define topiclink(description, time, minSec) yt $time$ $minSec$ ''---'' [[$description$|$(hangoutprefix)$ - $description$]] \end with a linefeed at the end of the content, as before. Then each of your hangout tiddlers can start with something like this: \define hangoutprefix() TwHo#73 \define youtubeid() EU-H0xhga08 and can contain things like this: topic Q A Start 00:01:25 001m25s topiclink Eric Discusses how he creates the Wiki Way 02:08:08 128m08s The topic macro simply states the description. The topiclink macro turns the description into a link to a tiddler with that same name but prefixed with TwHo#73 or whatever. — æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
I couldn't resist the temptation to put a JavaScript macro together, so
I've er… put a JavaScript macro together :)
This simplifies usage of the topic and topiclink macros, described in
my previous post, to just this:
topic Q A Start 00:01:25
topiclink Eric Discusses how he creates the Wiki Way 02:08:08
If you want to try it out, create a tiddler called
$:/.rich/macros/youtime.js. This one doesn't need a tag, but at the
bottom of the tiddler edit area, you'll need to set its type to
application/javascript, plus add a field called module-type whose value
is macro. Paste the tiddler's content from the attached file,
youtime.txt.
You can then change the content of $:/.rich/macros/topic to this:
\define topic(description, timecode)
youtime $(youtubeid)$ $timecode$ ''---'' $description$
\end
\define topiclink(description, timecode)
youtime $(youtubeid)$ $timecode$ ''---''
[[$description$|$(hangoutprefix)$ - $description$]]
\end
This causes topic and topiclink to use the youtime macro defined in
$:/.rich/macros/youtime.js. The youtime macro generates a timed YouTube
link and can be used on its own, like this:
youtime EU-H0xhga08 00:01:25
If this works for you, you can delete the $:/.rich/macros/youtube tiddler
I offered yesterday :)
— æ
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
/*\
title: $:/.rich/macros/youtime.js
type: application/javascript
module-type: macro
\*/
(function(){
use strict;
exports.name = youtime;
exports.params = [
{ name: youtubeid },
{ name: timecode }
];
exports.run = function(youtubeid, timecode) {
youtubeid = youtubeid || no-video-specified;
var hms = timecode || 00:00:00;
var bits = hms.split(:);
var h = bits[0], m = bits[1], s = bits[2], m = h*60 + m*1;
var output = [[[, hms, |http://www.youtube.com/watch?v=;, youtubeid];
if(timecode) {
output.push(t=, m + m, s + s);
}
output.push(]]);
return output.join();
};
})();
--
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: How can I view the changes from each version of TW5
Go to https://github.com/Jermolene/TiddlyWiki5 and click 34 releases near the centre of the top of the page. That gives you a list of all the releases. Click on a particular version number, and you'll find a link labelled n releases to master since this tag. Click that link to get a nice list of all the changes in that version. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
In the previous Tiddlers Macro Example I would define the youtubeid at the start of the Tiddler and it would be used in only that Tiddler. Do I still do that? Yes, you do. Each hangout tiddler needs to start with \define hangoutprefix() TwHo#73 \define youtubeid() EU-H0xhga08 to set up its environment. The topiclink macro then picks these up as $(youtubeid)$ and $(hangoutprefix)$: \define topiclink(description, timecode) youtime $(youtubeid)$ $timecode$ ''---'' [[$description$|$(hangoutprefix)$ - $description$]] \end By the way, the reason why $description$ and $timecode$ don't have parentheses inside their dollar signs is that they're the immediate parameters of the topiclink macro itself. The $(blah)$ syntax, by contrast, looks for blah as something defined further out. Will I have to eliminate the original macro as I have done some work with it and would like to keep it? I was kinda assuming you would delete it. I changed the definitions of topic and topiclink to use the youtime macro, and your wiki can't contain both definitions at the same time. If you try to do so, they will fight each other as you say, and one or the other will win in a pretty arbitrary fashion. Sorry I wasn't able to supply you with everything at once! I'm on the TW5 learning curve, too… Can you not search and replace to adjust your earlier work to the new pattern? How do you put a 'Created by X or Y in a Macro.js file?' The top section of the text, between /*\ and \*/, is a JavaScript comment. TiddlyWiki expects this comment to start with lines giving name: value information about the macro, but it gives up at the first blank line of the comment. So feel free to write anything you like after a blank line, but before the \*/: /*\ title: $:/.rich/macros/youtime.js type: application/javascript module-type: macro blah blah blah and some more blah \*/ Time code in a consistent format that is 'future proof' That makes sense, and is why I gave preference to that format as the parameter to youtime. no 2m3sec for Embedding Ah. How annoying. I didn't know that. I think you'll need a second macro, similar to youtime, that takes the same two parameters (youtubeid and timecode) and generates whatever's needed for an embed. I think you've already realised this yourself. I use a real Tiddler Name of TwHo#72 - Eric IndieGogo Update as Eric Might Update us in more than one hangout ;) Indeed! But that's what hangoutprefix is for. The revised topiclink macro in my third post in this thread generates just such a link: [[$description$|$(hangoutprefix)$ - $description$]] can I hack your code to create a 'timecode' macro? Go ahead. It should be a question of changing var h = bits[0], m = bits[1], s = bits[2], m = h*60 + m*1; to var h = bits[0], m = bits[1], s = bits[2], s = h*60*60 + m*60 + s; and then using s (rather than both m and s) in the output. The output might as well be the whole iframe embedding guff. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: [TW5] Idea for a Hangouts TiddlyWiki
Hi Rich, There's an example of a YouTube macro here: http://tiddlywiki.com/#Formatting%20text%20in%20TiddlyWiki But you might like to try this as an experiment: Create a new system tiddler on your Hangouts wiki. Call it something like $:/.rich/macros/youtube - the dot before rich will keep this tiddler floating conveniently at the top of the list in the sidebar's System tab. Store the following three lines as the tiddler's content: \define yt(time, minSec) [[$time$|http://www.youtube.com/watch?v=$(youtubeid)$t=$minSec$]] \end Make sure there's a linefeed at the end of the third line, i.e. check your typing cursor can go onto a fourth (empty) line below the word \end. Give this tiddler the special tag $:/tags/Macro. This makes the macro it defines available to all tiddlers. The macro it defines is called yt (a nice short name, because you may be using it a lot :) When you subsequently use the macro, you will have to supply two values, known here as time and minSec. When you subsequently use the macro, time will be the time you want to display, e.g. 00:01:25, and minSec will be the time in YouTube's format, e.g. 001m25s. The values you supply will appear in the places where the macro's definition says $time$ and $minSec$. So… at the very start of each hangout tiddler, add a line like the following. Change the video ID to match the hangout in question, and place a blank line between this and the rest of the tiddler. \define youtubeid() EU-H0xhga08 This also defines a macro, but this macro is only available within this tiddler. Each hangout tiddler can define its own private youtubeid macro in this way, to save you having to repeat it for every scene of the hangout. Then… throughout the rest of the tiddler, you can replace things like this [[00:01:25|http://www.youtube.com/watch?v=EU-H0xhga08t=001m25s]] with less bulky things like this: yt 00:01:25 001m25s Ideally, you'd want to say just yt 00:01:25 or yt 001m25s but I don't think TiddlyWiki itself provides the necessary conversion mechanism. (I hope someone will prove me wrong.) The conversion could be done with a power macro written in pure JavaScript, but that's a different can of worms. – æ -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
