On 2/1/2015 3:24 PM, Tobias Beer wrote:
Why? We know what fields we use in the docs, no prefix needed. We
can't use @ as that is invalid in html attributes... an I don't see
why we should.
I see that as simply a marker that would be stripped by the parser. I
mean, we're not going to leave the trailing colons in the names either,
true? :) To me, it is a way for a parser to quickly rip through a file
looking for just the strings it cares about, and something like
/@([a-z]+):/i (I haven't tested that regex :) ), where we're looking for
strings starting with alpha between an @ and a : and capturing just the
string itself and not the delimiters seems like a viable approach (and
note the case insensitive flag, so people wouldn't have to worry about
/@title: /vs./@TITLE: /vs./@Title:/).
My concern here was around the fields in comments already in use (and I
believe relied upon by TW) in modules. I can see where modules would
need some "documentation" fields as well as normal "TiddlyWiki" fields,
and was trying to namespace the documentation fields basically, so that
we could have a something like:
title: $:/boot/boot.js // This is already in use by TW
@title: boot.js // or "Boot module" or "Das Boot" (joke)
// or whatever
That is possibly true, but then I would have a global setting for the
repo to define what format to use, which you could overwrite for a
single tiddler by setting the *type* field accordingly.
Probably a good approach, although I was thinking default would be TW
syntax and we make the Markdown people work harder. :) Just kidding!
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
For more options, visit https://groups.google.com/d/optout.
