Tobias Beer於 2013年9月12日星期四UTC+8下午5時47分02秒寫道：
>
> Some more things...
>
> *(a) *I see your space ships with these simplistic grahpics.
>
> I don't think you need those and so I think you should get rid of them. All
> you need is a bordera simplistic *Base64 *encoded 1x1 pixel held by a
> section or slice or variable in your plugin... which you then stretch
> either horizontally or vertically to the desired size. No resources
> external to the plugin are needed. You simply render this as...
>
> <img
> src="data:image/gif;base64,R0lGODlhAQABALMAAICAgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAEAABAALAAAAAABAAEAAAgEAAEEBAA7"
>
> style:"height:1px;width:100px:"/>
>
> ...or the appropriate background image.
>
> background-image: url([[TreeDiagramFormatterPlugin::pixel]]);
>
> As before, this could be defined by the user to whatever he likes using css.
> Your ts:before would then need some defined width or height.
>
>
> *(b)* what on earth are *<tp>*, *<tl>*, *<ts>* elements
>
> ?!?
>
Ha, there are actually:
- <tl> = tree lists, just like "ol" "ul" "dl"
- <ti> = tree items, just like "li"
- <tp> = tree parent nodes
- <ts> = tree separators/spacers
I thought of using table cells and borders to make such a tree diagram in
the first place, but I knew this would take too many markups. After
searching on Stackoverflow, I found someone sharing about "display:
table-row/table-cell", so I decided to combine this CSS trick with the
TiddlyWiki list markup mechanism, creating new elements without using CSS
classes, because I don't want to use {{css{wrappers}}} per item.
Fortunately it worked with acceptable layouts (only that the bars were very
ugly before v0.4).
>
> *(c)* a tree should by default be wrapped into some span with a class *
> .treedg*
>
In the first place I did design to use a class to wrap the whole tree, that
was when I was still thinking of table markups and using CSS rules like
".treedg td/tr/th". But later when I changed to list model and new
elements, I abandoned the overall class wrapper. It seems that we can do
without it, how do you think?
>
> *(d) *right now I am playing with getting rid of images entirely and
> putting nothing but borders
>
It's a pity that CSS does not offer "border: upper-half/lower half" :-p
MediaWiki cladograms use borders, but based on nested tables. The output is
very clean, but I found it too hard and too complicated to implement with
TiddlyWiki markups... (perhaps have to write another plugin like
MediaWikiTableFormatterPlugin)
>
> *(e)* Seeing how you have included @White now, you should definetely
> create a plugin space outside of the treedg space or create a treedg-info
> space and then use the theme there.
>
> Best wishes, Tobias.
>
--
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 tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.
