Tobias Beer於 2013年9月20日星期五UTC+8上午2時30分27秒寫道:
>
> Hi GJRobert,
>
> Looks interesting, again. ;-)
> I quite like those plugins playing with formatters.
>
> Since I actually overlooked your examples behind that sidebar and was 
> about to ask you for some side-by-side examples, I created...
> http://plock.tiddlyspace.com
>

Haha, that space is doing a great demo job... Thanks a lot! Pardon that I 
haven't completely expressed all the features (as you did) in my doc. I 
should have split and organized the contents in your fashion.
 

>
> Two things...
>
> 1) the syntax for custom css wrappers might have looked nicer as 
> ={myMlass{plain block}= or -{myClass{inline block}- ...was there something 
> forcing you to use so many instead or is it rather that your block and a 
> custom css wrapper can be nested? Otherwise, perhaps extend your syntax?
>

Yes, ={ }= and -{ }- can nest CSS wrappers without problem. But extending 
the syntax is indeed feasible.

All the problem was that I just borrowed the code from 
LegacyStrikeThroughPlugin in the beginning of my journey, to adapt into 
different formatters. Since most of the inline wrapping markups of 
TiddlyWiki are involved with "some characters ahead"...(text)..."some 
characters behind" to create semantic elements like <strong>, <em>, <u>, 
<strike> etc., and I did not take time to understand the handlers behind 
them, so all I thought was just creating new elements in the same way to 
achieve what I wanted.

But now that after seeing how you have modify NodeTreePlugin to use 
standard <div> with classes by changing the parameters in 
createTiddlyElement(), I now know that my old PlockPlugin should get some 
surgeries too. I still threw my current version however, to receive 
suggestions earlier.

I hope to achieve your suggestion soon. I also guess that the handler of 
@@...@@ can be studied too, because it takes custom styles and generate 
spans. Or, maybe looking at the handlers of {{CSS{wrappers}}} will do...
 

>
> 2) it may be desireable to define a default class to a <p> rendered by 
> your plugin. That way, one could use your markup for dedicated purposes 
> without fearing that other <p>'s wherever they may originate from interfere.
>

Sounds good! How about the class "p.plock"? Is it short enough?
 

>
> 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 [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/groups/opt_out.

Reply via email to