Responses to some VisualBlogger Feedback

Josh, thanks for the feedback. I'll address them point by point.

1. Right now we're only pushing data. There is no real way to get posts to be able to do anything with them. The web services that allow you to get posts have been depricated, but they are still accessible. I'm working on ways to make that happen. remember, it is primarily a tool to keep you from losing posts you're working on. Anything beyond that is a value-added thing. Remember, we're currently limited by what .Text can/can't do.
2. Had a few comments about the sideways thing. Right now, the text is just a placeholder until I can get a UI guy to do some graphics work for me. I need icons for each of those options, and I wasn't going to even try to make one on my own, since I suck at it.
3. Not sure why the Config UI is not working. Ping me offline and we'll troubleshoot.
4. There are no default categories, so that's not a problem. In regards to which blog you're posting too by default, I'll look into it. The problem with adding a menu item is screen real-estate.
5. VS.NET Add-In Mode is not available in Beta 1. Should be enabled by Beta 2.
6. Spell check is not available in Beta 1. See my beef with ComponentOne for more details on why.
7. Ping me and we'll troubleshoot your feedback problems.
8. The next build will have a mechanism for saving who you are. Didn't have time to enable it in this build.
9. Status bars will be available in the final release, once I make the UI multi-threaded. There is a lot of work that has to go into the tool before that can happen. I will have at minimum a mechanism to tell you that the post got saved successfully.
10. Josh, I gotta tell you man, you're pie in the sky on this one. I have NO experience with shell programming, and I don't have the foggiest idea how to BEGIN adding that feature. I'll be flat out honest... you'll be lucky if you even get it in IE.
11. .Text has been having issues with categories lately. I keep getting SQL errors on the return, meaning that there are back end issues with the web service. I need to do some more troubleshooting to see if VisualBlogger or .Text is the source of the problem.
12. Timing is a known issue. It's a problem with the .Text web service. I'm still experimenting to see if I can correctly fix it in code. I believe the web service is adding in it's own datetime info, not using what is submitted. The web service is also not scrubbing that time based on your local timezone, so that is one of the reasons why the timing is off. I'll see if I can compensate for it, but no promises. Rest assured that it aggregates normally.

Ping me tonight and we'll troubleshoot your setup.