Over the weekend I started on the .NETCF v2.0 version of my Pocket PC blogging application, using Beta 2 of Visual Studio 2005.
I had a lot of trouble getting Visual Studio to talk to the emulator, and unfortunately while the errors I was getting were the kind a lot of people have had, none of the solutions quite worked. I think this may be because I also have the WinFX SDK installed on the same machine, but who knows. I also had trouble getting the loopback adapter to work: it couldn't get an address, which has never happened to me before, so I gave it one manually. Then I installed ActiveSync 4 and managed to get the emulator cradled, after which Visual Studio happily talks to it as if it were a device (neat trick, and also an easy way to get files onto the emulator...and it will be handy when I get to testing CAB installation).
Soooo anyway, there are obvious things I'll be doing such as replacing my held-together-with-string interop code for Clipboard access, and I'll probably be using XML serialisation for storing configuration options (I was disappointed that there's still no configuration support in .NETCF 2).
I plan to replace the Blogger API with Atom for Blogger blogs - I hope that works for everybody. The main driver there is the desirability of using proper titles with Blogger, since that's a big minus for a lot of people.
I'm also thinking of simplifying things by dropping BlogX support, since it requires a fair bit of code to support and I suspect the intersection of BlogX users with people who use Diarist is something not unlike “Zero”. But let me know if I should leave it in, it's no big deal.
Generally I'd like to hear what people would like to see or what they'd like to be different (I'd quite like to revisit the whole blog setup/configuration thing quite drastically). You can use the Contact link to email me since I've had to switch comments off after being overwhelmed by [expletive regretfully deleted] spammers.
Addendum
I forgot to mention: Yesterday I was experimenting with a weak sort of “Blog this” feature - with this option in place, then whenever the application is activated it will check whether a) the content area is currently empty, and b) there is text in the clipboard.
If both of these conditions are satisfied the text contents of the clipboard will be copied to the content area for posting. In one possible scenario you could assign a hardware button to Diarist, and whenever you found an interesting piece somewhere you could select it and hit the aforementioned hardware button. Diarist would then open or come to the foreground with the selected text pasted and ready for posting (I doubt most people would waste a hardware button on it, but I suppose it depends what you spend most time doing).
I'd very much like to know whether or not anyone would actually find that to be a useful feature (I'd make it a tickable configuration option, since it would be very annoying to have it happen if you didn't want it to).