Hi Jeremy, Here are my long due returns on this plugin.
First, I'll present my use-case. I've some PDF files, containing text with chapters, subsections, paragraphs, lists, inserts, icons, images, etc., that I want to turn into a TW. I want to present all these elements in a way that allows easy navigation in the table of content, and with some respect to the original layout. Here is an example of these PDF files (in French): http://issuu.com/lesombresdesteren/docs/esteren_livre_0_prologue/1. My first attempt, before the text-slicer plugin, satisfied me, but was quite complex. I used fields to store a reference for each tiddler (in a way that an alphanumeric sort gives the orer I want), and the parent reference, which were used to build a recursive representation inspired by the toc-macro. I also used a lot of macros for styling the inserts or some paragraphs that come with icons. I liked the result, but building the structure (references, ...) was quite time-consuming, and I made my test on the shorter of the PDF I want to transform... So, my hope for the text-slicer plugin is that it can make this building process faster, and I can focus on the presentation layer. And it seems very promising. With the two means (manually or with text-slicer), I must first transform the PDF into a text file (I'll manage images later, as they need some work). Then I insert some Wikitext formatting (mainly headings and the various sorts of lists). Here are some of my thought about the text-slicer plugin. *I need a lot of CSS styling.* And not tags for "How to apply custom styles by tag", because it only applies to tiddlers, not to transclusions (or I need more CSS-magic). So I modify the js code of each slicer by replacing the "tags" field by a "class" field to be valuated with the classes extracted from the DOM nodes (sorry if I don't have the appropriate vocabulary, I'm neither english-native nor web programmer). this.addToList(parentTitle,this.addTiddler({ "toc-type": "paragraph", title: title, text: "", class: tags })); I also modify each (interactive, the only ones that I have interest in) template to add a class attribute with the value of this "class" field, for example the list interactive template : \define body(type:"ul") <$type$ class={{!!class}}> <$list filter="""[all[current]] $(tv-exclude-filter)$ +[limit[1]]""" variable="item"> <$list filter={{!!toc-list-filter}} template= "$:/plugins/tiddlywiki/text-slicer/templates/interactive/tiddler"/> </$list> </$type$> \end <$macrocall $name="body" type={{!!toc-list-type}}/> Note that I could use the "tags" field for that... but I will end with a lot of CSS classes, and I want to reserve tags for thematic tags. Later. It would be extremely usefull to be able to *easily modify the order of children* in a tiddler list. And also to modify the parent of a tiddler (for example, if I have a "conclusion" paragraph of a h2 section which also contains h3 sections, it must be a child of the h2 tiddler, not of the last h3 tiddler). The new listops widget from matabele recently merged on github could be useful here. I will need a *prefix for tiddlers titles*. I can modify each js slicer to add it, but as you mentionned that the choice of a prefix was in your list of future enhancement, I would be glad to see it. There are *too much margins the way lists are displayed*. So I remove the block mode from the item transclusion in $:/plugins/tiddlywiki/text-slicer/templates/interactive/tiddler and I remove the double linebreaks in $:/plugins/tiddlywiki/text-slicer/templates/interactive/item. *I don't want duplicated text* when I open a tiddler created by the slicing, only its recursive content. So I add to all these tiddlers the field "hide-body" to "yes" (modification in each js slicer; this could maybe be an built-in option?), and I remove in $:/plugins/tiddlywiki/text-slicer/ui/view-template-segment this part: <div class="tc-view-template-document-tiddler-heading"> //This tiddler is part of a document. The content as it appears in the document appears below.// </div> I will certainly need at least a support for *<cite> elements*, and maybe also <blockquote>. I've already done a test to add a js slicer for that, it seems to work. Finally, as I need to have some styling (background color and border) over several headings (for example 2 headings of a total a 4, with all the descendance), I think I will need support for *<div> elements*. I may forget some other things... but I think these are the main points that I've found the need to modify for my first test of text-slicer usage. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/aa5e96c2-a99c-43ae-8a6b-fac041f47141%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
