Lots of changes here... Added a CRUD web service front end and a query web service front end. There are now 7 projects in the sources:
- BlogCmd - command line radio to blogx converter
- BlogXRuntime - data model, shared by all
- BlogXServiceProxy - hand tweaked web service proxy
- WeblogX - ASP.NET front end & web services
- WinBlogX - WinForms front end (talks to web services)
- WinBlogXControls - Shared controls between WinBlogX and WoodBlog
- WoodBlog - "Legacy" WinForms front end
WoodBlog was done to directly whack on the XML files. This was more effiecient but it introduced the problem of two places you can edit (through the web and client). I decided to just go with a single data store, on the server, and then rewrite the client to talk through web services.
BlogXServiceProxy was needed because I wanted the objects seen on the client to be from BlogXRuntime. Since all the data model is XML Serializable, I just removed the XSD generated data classes and viola!
The WinBlogXControls currently contains an HTML editor and viewer. Both are actually the same control, and require VS.NET to be installed to use. I'm going to search around for the write code to do these correctly, but for now it works for me.
I have two web services exposed now - BlogXEditing and BlogXBrowsing. The browsing service is basically all the entry points you would need to write a browsing application. Including categories, etc. Right now it is still missing a "post a comment" on the browsing service. The editing service is a simple CRUD api set for manipulating the blog entries. Today it is secured with a crappy password argument on all the methods. I'll work on real security later.
Once I can get reliable FTP working for uploading new versions, I am ready to switch from Radio. My plan will be to keep the existing Radio HTML files up on the server so that permalinks work, but all new content will be on the BlogX version. However, I still can't make the switch because I'm having difficulties uploading my software.