After nearly 2 years, xml-weblog 1.1 is complete!
Although some (none, actually) of the features originally planned for version 1.1 didn't make the cut (non-admin user logon, custom views/settings for users, article submission), enough work has been done to merit a point release.
Some changes from 1.1 have already been previously announced, but the major changes can be summarized as: new object-based code structure, RSS support, and the most cool new feature, an XML-RPC interface to post/edit/delete articles using the Blogger and MetaWeblog APIs, which means you can use tools like NetNewsWire to edit your site!
You can download xml-weblog 1.1 from my ftp site, or Read More for a complete list of changes.
New in 1.1:
- Improved XHTML/CSS default style, now renders properly in all modern browsers and gracefully degrades with older clients.
- Images stored as regular files (big speed increase).
- Fully valid XHTML 1.0, CSS1/2, and RSS 2.0.
- Images converted from PNG to (now patent-free) GIF, to support some ancient browsers that don't like PNG.
- Non-administrator user login partially supported.
- New avantgo.php AvantGo/mobile XSLT style.
- RSS 2.0, implemented as an XSLT style.
- New object-based/library structure, which will significantly ease future development.
- New SSL+cookie-based login scheme, which uses a cookie to store only desired state (logged on or logged off), site still uses basic auth, now optionally requiring SSL encryption.
- Basic XML validation (for articles)
- XML-RPC support for site editing with NetNewsWire, using the Blogger and MetaWeblog APIs (partially implemented, see http://ranchero.com/netnewswire/developers/methods.php)
- Many bug fixes
Planned for 1.2 (from TODO):
- support conditional GET (news aggregators)
- add WAP + thin style, fix style/query string handling
- add user story submission - with XML-RPC support (?)
- add user signup/preferences screen
Finally, I'm really in need of a new logo and/or icon for xml-weblog, and also could really use a stable & secure http md5 digest authentication implementation (so I can mess with IE users ;) If anyone out there wants to take a shot at this, let me know!