Hi Yakov
> I'm trying to adapt TW5 to certain limited needs while exploring its
capabilities and here are several notes/questions:
Great, I'm glad to hear you're looking at TW5. I'll be interested in your
thoughts and feedback.
1. I'd like to take advantage of TW5 encryption. Does it still encrypt only
> the whole TW or there's a possibility to encrypt single tiddlers?
>
As you've heard, single tiddler encryption is available via a plugin. It's
not something I'm planning for the core in the immediate future because I
think I'd like to learn more about the use cases and the desired
features/UI.
> 2. Double click doesn't open a tiddler for editing. Will this behaviour be
> implemented in TW5?
>
I don't plan to introduce double click to edit by default, for the reason
given by Stephan: it breaks double-clicking to select text. But I would
like to include it as an option.
> 3. I haven't found a way to add DOM classes inline (like {{myClass{text}}}
> in TWc), only inline styles and block styles/classes [1]. Will there be
> some syntax to do this?
>
The TW5 equivalent is @@.myClass text@@. See:
http://tiddlywiki.com/#Styles%20and%20Classes%20in%20WikiText
The documentation only covers the block mode form, but it also works as
inline syntax:
@@.myClass This is some text with a class@@
@@background-color:red;This is some text with a background colour@@
@@width:100px;.myClass This is some text with a class and a width@@
4. In TiddlyWiki.com, permalink/permaview are now shown in the toolbars.
> Of'course, I can unhide them each time, but it would be more convenient if
> they are shown (mostly permalink on tiddlers).
>
I want to keep tiddlywiki.com simple, and so don't intend to have more than
three tiddler toolbar buttons shown by default. Hopefully it's easy enough
to use the tiddler info panel to access other toolbar buttons.
5. In default theme, the EditTemplate (or how it is called in TW5) doesn't
> look simple at all (while Jeremy wrote that simplicity is of importance for
> attracting new users a while ago). Also, the edit area itself occupies very
> part of the tiddler area. I'd propose some adjustments:
> -- move "show preview" to the toolbar
> -- hide the "Use wiki text <http://tiddlywiki.com/static/WikiText.html>
> to add formatting, images, and dynamic features" tip to some sort of
> "info section" which is to be toggled by a button in the toolbar (just like
> the info button in the view mode toggles info)
> -- put the content type chooser and the field adder in the same line
> (added fields are displayed in separate lines anyway)
> -- probably reduce margine of the edit area at least by third
>
As others have noted, there has been a lot of discussion about how best to
improve the edit template:
https://github.com/Jermolene/TiddlyWiki5/issues/506
https://github.com/Jermolene/TiddlyWiki5/issues/170
I'm keen to improve it.
6. Are there sections, slices or stuff like that in TW5? Some means of
> usage TW in a "database-like" style (like using ForEachTiddlerPlugin or
> GridPlugin [2]) -- with the content shown inside the tiddler text? May be
> even some tools to aggregate such tables within the core?
>
No, there's no support for sections or slices. DataTiddlers are supported
which are somewhat similar to slices:
http://tiddlywiki.com/#DataTiddlers
There are many reasons that I've chosen not to support sections as part of
the core at the moment. One practical issue is that section parsing is
brittle and error prone if done with a simple regexp as in TWC, and
expensive if done with a full parse of the tiddler content
The bigger philosophical issue is that TiddlyWiki embodies the idea that
the smallest fundamental unit of information is a tiddler. The operations
that TiddlyWiki supports are inter-tiddler operations, that combine and
link individual, discrete tiddlers. Sections imply an algebra for
intra-tiddler operations, potentially duplicating the inter-tiddler
operations.
The purest expression of TiddlyWikis philosophy would be to break a tiddler
with sections into separate tiddlers, and transclude the sections back
together when you need to view them as a single unit.
None of that precludes adding section support, whether in the core or via a
plugin.
There are two approaches to consider:
* The TWC-like approach of referring to sections via a text reference (eg
title::section). Currently, text references give us a title, and optionally
either a field name or an index name (for data tiddlers). The knock-on
effects of extending that include a section name would impact an awful lot
of core code
* Supporting transcluding a fragment of a tiddler. This would just be an
extension to the transclude widget, and feels much more do-able
Best wishes
Jeremy
>
> Best regards,
> Yakov.
>
> [1] http://tiddlywiki.com/#Styles%20and%20Classes%20in%20WikiText
> [2] tiddlytools.com/#GridPluginInfo
>
> --
> 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 [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/tiddlywiki.
> For more options, visit https://groups.google.com/d/optout.
>
--
Jeremy Ruston
mailto:[email protected]
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
