[wp-hackers] XMLRPC Patches

[Emmanuel Frécon]

I have had a look at the README file, which gave me enought insights 
into how you have coded that. It all makes sense and I am tempted to say 
that the XMLRPC interface would not make sense. Read further...

It seems to me that building dependencies on some plugins in the XMLRPC 
API is a bad idea. This remark does not only apply to the TFS, it also 
applies to my current patch that is now floating around and attempts to 
be smart about markdown (a plugin that has to be activated) and textile 
(another plugin). The whole idea does seems awkward. Plugins are for 
making extensions that leave as less "tracks" as possible behind them in 
the main system. If you start building dependencies on existing plugins 
in the main system, you have broken the whole idea.

I understand that I am not very constructive here. Please understand me, 
I am not trying to start a flame, I am just trying to start the discussion.


Dougal Campbell wrote:
> Emmanuel Frécon wrote:
> 
>  > [...]
> 
>>    5. It sets correctly the mt_convert_breaks field to reflect 
>> textile, markdown or nothing.
> 
>  >
>  > [...]
> 
>>
>> item 5 is interesting. I did not really know what to do there and 
>> built further upon the Ecto patch. MT allows you to use different text 
>> input filters depending on the entry. To my knowledge (stop me if I am 
>> wrong), WP does not allow you to do that. Since most of these text 
>> input filters also allow you to write raw HTML, the Ecto solution (a 
>> further mine) is to look for active plugins and if one of those is 
>> activated, to return relevant information.
> 
> 
> Correct, by default, WP doesn't have a way to set content filters on a 
> per-post filters.
> 
> But my new Text Filter Suite plugin[1] can do it. I'm hoping that 
> eventually, we might such a capability a standard WP feature. It would 
> be particularly useful for multi-author sites, where certain authors 
> prefer a particular markup style, e.g. Textile or Markdown.
> 
> My current TFS filters are mostly "entertaining". But I'm planning to 
> add "tfs-textile" and "tfs-markdown" sometime soon, which will make it 
> much more useful to a wider audience.
> 
> Anyhow, I didn't know if you might be interested in looking at my 
> implementation for handling per-post formatting on the server end.
> 
> [1] http://dougal.gunters.org/blog/2004/08/30/text-filter-suite
> 


-- 
New book: "Inhabited Information Spaces"
	  Book site: http://www.iisbook.com/
	  Publisher's site: http://www.springeronline.com/1-85233-728-1

Emmanuel Frécon              Tel:         +46 8 633 1534
SICS                         Fax:         +46 8 751 7230
Box 1263                     Email:       emmanuel at sics.se
Isafjordsgatan 22            Static Web:  http://www.sics.se/~emmanuel/
SE-164 29 Kista              Dynamic Web: http://embrof.sics.se/

I filter all incoming Emails through several Spam filters. They
occasionally crunch real letters though.