| September 2002 | ||||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | |||||
| Aug Oct | ||||||
This site is no longer maintained.
My current weblog.
Wednesday, September 04, 2002Pocket Blog Direction
The port of Pocket Blog to the .NET Compact Framework is mostly on hold at this point. I find myself working around too many of the CF's bugs and limitations, which is very frustrating. I don't want the CF version of PB to degrade into an ugly mess of difficult-to-maintain work-arounds... I already have that with the eVB version.
When a new Beta is released I will re-examine the problems I am having and decide if it is worth continuing. If not, I'll wait for the full release.
In the mean time I am thinking about how to better integrate Pocket Blog with various weblog software and APIs. The Blogger API and MetaWeblog API are established standards. Pyra has been extending Blogger, Movable Type has several extensions and does not implement the full MetaWeblog API. On the Radio Userland front, I wonder how PB could work with liveTopics.
Rather than shoe-horn all of this stuff into PB itself, I'm thinking of switching to a plug-ins architecture. Using the object-oriented capabilities that .NET offers, PB would provide base objects that represent a weblog post and the editor interface. Individual plug-ins would inherit and extend these objects to account for metadata required by a particular API. They would also manage communications with the server. Ideally, plug-ins would allow themselves to be extended by other plug-ins: a plug-in for Movable Type would only implement functionality specific to MT, the rest would be inherited from the MetaWeblog API plug-in.
I like this concept because it allows Pocket Blog to grow incrementally: new APIs will not require a new release of PB and could be supported by others (particularly in areas that don't interest me, like the LiveJournal API).
