I should have made it clearer that these are three unrelated ideas

> I have been thinking about this for a while now. It seems like we should
> have some way of being able to transclude tiddlers from other wikis. And we
> should have a syntax that makes this easy. This one might be better done as
> a plugin.


I'm thinking that the NodeJS server command would be useful as the
server-side component for this one. I know federation has also done this,
but it involves loading the client wiki into an iframe. I guess that could
work fine in some cases, but it is definitely more data to transfer. The
TiddlyWeb spec looks daunting to implement in some ways. You're right,
TiddlyWeb is probably the way to go on this one. I was thinking more in
terms of transcluding individual tiddlers, so recipes and filters might be
overkill.

Another thing I have been thinking is that we need a simple way to group
> pages [should be tiddlers] according to "folders". Maybe all this entails
> is a macro like TOC that lists all the folders under a prefix. It seems
> like a filter of some sort should work.
>

For this one, I am talking about tiddlers within one wiki. I'm thinking of
the way the Mediawiki software gives you the option to treat slashes in the
page title like a folder path. When you enable this option, as Wikipedia
does, it will treat page titles with slashes as a subpage. So in our case,
we would write a macro that looks like the TOC macro, but groups the
tiddlers using the title field instead of tags. For instance, the shadow
tiddlers of the core plugin would look like this:

$:/core

   - modules
   - macros
      - parsers
      - startup
      - utils
      - widgets
      - templates
   - ui
   - Buttons
      - ControlPanel
      - EditorToolbar


Another thing that would be nice is the ability to add preset fields to the
> edit template between the title and the body. That way I could specify that
> I always want the caption field available, for instance, even if nothing
> has been specified for that field yet.


I mean, we could just give this the same functionality as the field editor
below the body, where it would have the field name preset, but you would
still need to click create before it would actually save the value. Or
require the user to click create before it will show the value edit box.
Would that work? This is something I run into quite a bit with some of my
wikis, and I usually figure I'm not the only one.

Thoughts?
Arlen

-- 
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 https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAJ1vdSSY6ksOAMy3QTtA%2Bhs%2ByEFetXXyFDx3RfEmwZMpncYfYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to