Blog Clients
Blog posting editors can operate from the client-side in a browser like Firefox or Internet Explorer or from the server-side in the default posting editors that come with blogging software like Blogger, Movable Type, Wordpress, or Nucleus or with add-on editors like FCKeditor (please excuse the name which supposedly comes from the initials of the author).
Client-side editors have the advantage of a more seamless interface. You don't have to modify server-side software. The Metaweblog API is used to make postings to the weblog. The Metaweblog API in turn uses XML-RPC. The modifications [1,2,3]typically require some knowledge of computer programming, backups in case you need to restore the old system, and reapplication of the modifications after upgrades, which all complicate things. There's a well-written criticism of the Metweblog API basically arguing that there are more natural ways to do it like HTTP GET and POST or SOAP, that there are security issues, and also that more functionality like settings, search, and blogroll maintenance should be be included in the interface.
WYSIWYG editors for composing blog entries are important if you want to insert photos, illustrations, or diagrams. If you have a multi-blog scenario with many contributing bloggers, some are probably using Microsoft Word or Open Office, so you'll need to cut and paste from these documents. The normal server-side, html-based, post editors are not very convenient for cutting and pasting from other formats.
Blog clients are necessary if post editing is at all sophisticated like this. Unfortunately, finding the right fit can often be difficult and much of the software is commercial which is to be expected perhaps, since time and attention to producing high-quality software tuned to the specific needs of users takes time and money.
The Wikipedia policy of not allowing commercial links that you can see on the page linked to is a little unrealistic and doesn't reflect reality.
Client-side editors have the advantage of a more seamless interface. You don't have to modify server-side software. The Metaweblog API is used to make postings to the weblog. The Metaweblog API in turn uses XML-RPC. The modifications [1,2,3]typically require some knowledge of computer programming, backups in case you need to restore the old system, and reapplication of the modifications after upgrades, which all complicate things. There's a well-written criticism of the Metweblog API basically arguing that there are more natural ways to do it like HTTP GET and POST or SOAP, that there are security issues, and also that more functionality like settings, search, and blogroll maintenance should be be included in the interface.
WYSIWYG editors for composing blog entries are important if you want to insert photos, illustrations, or diagrams. If you have a multi-blog scenario with many contributing bloggers, some are probably using Microsoft Word or Open Office, so you'll need to cut and paste from these documents. The normal server-side, html-based, post editors are not very convenient for cutting and pasting from other formats.
Blog clients are necessary if post editing is at all sophisticated like this. Unfortunately, finding the right fit can often be difficult and much of the software is commercial which is to be expected perhaps, since time and attention to producing high-quality software tuned to the specific needs of users takes time and money.
The Wikipedia policy of not allowing commercial links that you can see on the page linked to is a little unrealistic and doesn't reflect reality.
posted by Jon Fernquest at 8:56 PM
0 Comments:
Post a Comment
<< Home