Thanks, Thomas, for the thorough review. 

Let me comment some issues:

   1. TOC based on drag-and-drop feature makes of use the *list* field (or 
   other assigned for this field). That frees *tag* field from unnecessary 
   load and makes possible to build easily several TOCs associating them to 
   different list fields.
   2. Heading autonumeration. I see as applicable and useful numbering the 
   tiddler titles only according to their numbering in the TOC. This numbering 
   could be used for displaying in the whole text, in the TOC and for 
   referencing to a particular section (means - tiddler).
   3. Regarding your question: *What do you mean, Olegh, when you say: "The 
   object description is stored in field caption."?* I mean that a caption 
   (or a description) of an object is to be stored in *caption* field. It 
   is acceptable practice to append lists of figures, tables, etc.
   4. I support completely inclusion of *citations* to the list of the 
   referable objects.

Olegh

пʼятниця, 4 січня 2019 р. 00:37:05 UTC+2 користувач Thomas Elmiger написав:
>
> Dear Olegh, happy 2019 to you too!
>
> Just some loose thoughts as I have been working on a related concept 
> lately ...
>
> *1. TOC/Story lists*
>
>    - I am working on a solution to save and load storylists related to 
>    the TOC. Basically you can choose a "chapter" from the first TOC level and 
>    save a story list under it (tagged with it).
>       - This will be ready rather sooner than later, so you could have a 
>       first look at it.
>    - Drag and Drop to reorder the TOC would be great, but I guess it 
>    could become complicated when dragging into another (deeper or higher) 
>    level.
>
>
> *2. Heading autonumeration*
>
>    - Tiddler titles are always rendered as H2 in existing story views. 
>    This would make it difficult, if not impossible to use them semantically 
> on 
>    different levels of a structure like
>    1. Main title (H1)
>    1.1 Subtitle (H2)
>    1.1.1 Paragraph title (H3)
>    - Icons as numbers? My experience suggests that it would be a 
>    dangerous hack to mix images and text together to resemble an entity 
>    (printing, accessibility issues, ...).
>
>
>
> *3. Headings: an alternative*
>
>    - I think of headings as text, that should be stored in the text field 
>    of a tiddler. There we – as authors – have easy access to all levels: ! = 
>    H1, !! = H2, ...
>    - A number could be stored in a field and prepended using a 
>    view-template like {{!!myNumber}} {{!!title}}
>    - Maybe the renumbering script could count exclamation points (!) at 
>    the beginning of tiddlers to decide about numbering levels.
>    - Ideally only a single title should be stored in a title tiddler.
>
>
> *4. What about tiddler titles then?*
>
>    - I made a plugin to hide everyting not absolutely necessary for 
>    readers, primarily tiddler titles, but also tags, author, date 
>    (configurable)
>    see 
>    https://tid.li/tw5/plugins.html#%24%3A%2Fplugins%2Ftelmiger%2FReaderMode
>     
>
>
> *5. Should authors bother about tiddler titles?*
>
>    - Not necessarily. Tiddler titles could be generated automagically, if 
>    they were mostly IDs. The problem is: They are used for other stuff. 
> Links, 
>    tags, ...
>    - The TOC uses *caption *if present, else *title *– so I thought about 
>    using this as a name for tiddlers ...
>
>
> *6. Captions*
>
> *What do you mean, Olegh, when you say: "The object description is stored 
> in field caption."?*
>
> Image captions can be quite long AND language specific while images could 
> be language independent. A caption like 
>
>> Furuyama Moromasa. *Portrait of Ichikawa Danjuro II as Kamakura no 
>> Gongorô,* 1736. The Art Institute of Chicago. 
>>
> would not be ideal to display in a TOC. But it is the official, required, 
> caption for an artwork. (Image link 
> <https://www.artic.edu/artworks/123402/portrait-of-ichikawa-danjuro-ii-as-kamakura-no-gongoro>
> )
>
>
> *7. Images*
>
> Your image example does not use the figure + figcaption HTML structure I 
> suggested im my examples 
> <https://tid.li/tw5/hacks.html#%24%3A%2Fplugins%2Ftelmiger%2Ffigures%2Fui%2Frenumber-story:%24%3A%2Fplugins%2Ftelmiger%2Ffigures%2Fui%2Frenumber-story%20%24%3A%2Fplugins%2Ftelmiger%2Ffigures%2Freadme%20%24%3A%2Fplugins%2Ftelmiger%2Ffigure%2Fexample-image2%20%5B%5BFig.%20Cat%20Jack%5D%5D%20%24%3A%2Fplugins%2Ftelmiger%2Ffigure%2Fexample-image%20%5B%5BFig.%20Cat%20Sleep%5D%5D%20%5B%5BList%20of%20Figures%5D%5D%20%24%3A%2Fplugins%2Ftelmiger%2Ffigures%2Ffigure-macros>.
>  
> I know it is too complicated to create, but it should be the goal to have 
> semantical code output wherever possible.
>
>
> *8. Citations*
>
> Maybe add an example for citations 
> <https://tiddlywiki.com/#Block%20Quotes%20in%20WikiText> too? Would be 
> interesting with source/author references.
>
>
> That’s it for today. All the best,
> Thomas
>
> Am Donnerstag, 3. Januar 2019 18:25:55 UTC+1 schrieb oleghbond:
>>
>> Dear colleagues, Happy New Year!
>>
>> Please find my comprehensive vision of how the autonumbering system looks 
>> like - https://protw.github.io/autonum/. 
>>
>> Actually it is a hybrid of the code working with tiddler files directly 
>> and the TW macro code. A complete description of the system as well as 
>> further development requests one can find inside this site. However, the 
>> project is not complete yet and needs input from the TW Community.
>>
>> The idea of ​​adapting TW to create books looks promising for both 
>> potential authors and in terms of expanding the application of the TW 
>> platform.
>>
>> So, it would be great to have your input to develop this idea.
>>
>> Olegh
>>
>>

-- 
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 https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/a0e5bf3a-d6f2-4ffb-a39b-737ec0a56510%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to