> * multilangual use. As for now, I've heard of tweaking with themes
> some other concepts ([1]), but this is of concern afterall, the idea
> of inter-personal web notebook implies some internatianality) By
> multilangual use I mean some fields architecture in the first place -
> like, say one title which is an id of a tiddler and titles and
> textareas with some language suffixes in names.. anyway, Tobias
> figured some things in [1]
I agree entirely. My goal is to devise a better mechanism for
translators to create new translations of TiddlyWiki, and for that
same mechanism to be usable by creators of TiddlyWiki to manage the
translation of their content.
> * export mechanism. TW is too standalone and if I need to pick some
> items and send them to other people I need either use something like
> Eric's plugin which allows to "print" tiddlers into html or make one
> more TW and import the tiddlers into it (and install some plugins if
> needed); and some devices like e-ink Books restrict this even worse
> since they can't do JavaScript. Also, more interaction with file
> system can allow syncronize with already written things some more
> ([2]); however, I understand that the latter thing is not about
> "restrictions" but rather about "extention".
I think this is indeed another question about "what functionality goes
in the core". There's been a lot of discussion in the group over this,
and people often argue that particularly useful plugins should "go in
the core" because they are so useful.
I have come to the conclusion that it is unhelpful trying to define
the core in terms of how extensive its functionality should be, and
instead we should look to engineering considerations of minimality to
drive the shape of what belongs in the core. The questions about
usefulness should guide the scope of particular vertical editions of
TiddlyWiki.
> * input of formulae. This is also not exactly a restriction, and there
> are some plugins [3] for that; but renewing TW means loss of the
> plugins on the one hand and a question about possibility to visualize
> a formula when editing on the other. The latter thing I'm talking
> about is not WYSIWYG itself, but rather a hybrid which is used in
> codecogs-based plugins ([4]) and Open Office: it is always faster to
> write a formula in some markup (not clicking buttons with mouse) but
> see what it will look like in some other "window".
I agree. I'd like the wikification to be seamlessly extensible, so
that users can reach up for mathematical formulae, choreographic
symbols, musical symbols etc.
> * "massive operation manager". The gem of TW is that we can organize
> things very precisely but once someone gets to reorganize things, say
> change one tag to another, or delete many tiddlers, he/she needs some
> sort of plugin (and sometimes this requires also manual piloting, when
> shaping the list of tiddlers to delete for instance). Something like
> that is required when importing tiddlers (checking tiddlers by tags,
> authors etc). The latter is implemented in plugin(s)
> (ImportTiddlersPlugin by Eric and others, perhaps).
Yes, my goal in the core is to make it easy for peoplt to create
plugins to support specific refactoring scenarios.
> And one more feature that's not about "restrictions" at all:
>
> * link rebinding. TW is "enclosed" space of hypertext, so this seems
> proper not to get links within it broken after renaming a tiddler. I
> mean, if tiddler B has a link/{tiddler/..} macro referencing tiddler
> A, it would be nice to get a "would you like to rebind all the links
> to this tiddler" dialog when renaming A (which has references).
Yes, this one keeps eating away at me. There are powerful attractions
for keeping tiddlers in working storage in a more structured tree
format that makes it easier to do this kind of thing. (Another example
of something that's hard to do with the current architecture is a
checkbox that is typed [ ] and gets changed dynamically to [X] when it
is clicked).
> I know, I sound so demanding, but afterall it's interesting to hear
> what do you think of this matters and what to expect in future.
Many thanks for the interesting observations,
Best wishes
Jeremy
> Many thanks, Yakov.
>
> [1]
> http://groups.google.com/group/tiddlywiki/browse_thread/thread/d38df1e51d3e4d54/a54f42d375850eab
> [2]
> https://groups.google.com/group/tiddlywiki/browse_thread/thread/4c9744205f64a415
> [3]
> https://groups.google.com/group/tiddlywiki/browse_thread/thread/72a1d4bdc6f0742e/7a33f8783b51572b
> [4] http://twmath.tiddlyspot.com/
>
> --
> You received this message because you are subscribed to the Google Groups
> "TiddlyWikiDev" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/tiddlywikidev?hl=en.
>
>
--
Jeremy Ruston
mailto:[email protected]
http://www.tiddlywiki.com
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywikidev?hl=en.
