Thanks for the response... Tiddly and JavaScript are totally new to
me.
I'm a programmer developing C, Fortran and associated documentation.
I'm hoping that TiddlyWiki can help pull it all together.
How best to integrate them is what I'm exploring...
ExternalTiddlersPlugin
almost does enough (perhaps unintentionally), perhaps I need
TiddlyWeb,
perhaps something else.
Goals:
* Maintain Tiddly markup in plain text files (no HTML encoding).
* Leverage TiddlyWiki to present pages (Wiki-editing is optional)
I want to use TiddlyWiki to display pages, while doing most of the
authoring and maintenance of pages in Vim (where I'm highly
productive).
Vim allows me to approximate the Wiki experience, i.e. syntax/markup
highlights and follow links with "gf" and/or "gu" (goto file under
cursor and/or
Utl universal text links). This helps with authoring but is not good
enough
for published documentation.
Vim allows me to refactor code and documentation both easily and
globally.
Ctags allow the raw Tiddler source to magically link to C and Fortran
source.
The "gf" tricks allow the code to magically link to the Tiddler
documentation.
Both are useful, especially during initial development of a large
project
when there are 2 gazillion details to cross-reference and get right.
My Vim syntax file uses Tiddly highlights in C and Fortran comments
(which enhances readability in my opinion), while retaining language
highlights for the executable portions of the source code.
Question: would a TiddlyCtags plugin make any sense?
i.e. have a plugin that uses ctags information to find and display
relevant
source code, without explicitly using link markups. Ctags is like a
glossary of terms and where their definition can be found.
If the user clicks on a naked phrase that is not defined, then they
might be given the opportunity to define it (glossary entry or source
code).
On Sep 21, 1:41 pm, Eric Shulman wrote:
> > Any help getting "Pretty Links" (i.e. "|link-text") to work with
> > ExternalTiddlersPlugin would be greatly appreciated.
>
> You can't use a TW *macro* inside the PrettyLink syntax.
>
> Macro don't work that way. They don't generate *text* that is
> inserted into the source and then parsed. Rather, they render their
> own output (if any) by directly generating browser DOM elements.
> Thus, you can't combine output from a macro with some surrounding
> syntax and then have that combination parsed as if it had been entered
> as text.
>
> [[text to show|<>]]
> is *not* valid TW syntax, and I'm actually surprised that it rendered
> at all, and even more astonished it appears to do anything even
> remotely similar to what you intended.
>
> Perhaps if you describe your objectives (in regular prose, not pseudo-
> code), I can suggest a suitable syntax that *is* valid and will
> achieve the results you want.
>
> -e
> Eric Shulman
> TiddlyTools / ELS Design Studios
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en
-~--~~~~--~~--~--~---
