Looks as if the Blog 7.1 did the trick – or at least so it seems from what Dominion tells me :p He says things are working fine for him and so I hope that the mysterious slowdown bug is laid to rest at last because I’d hate for it to be carried on to Blog 8.0 since some people might not want to migrate to 8.0 if it turns out to be too bloated :p This is something Phil mentioned in a comment – that if I merged Blog and BlogMan, people can always decide not to upgrade but I worry about bugs since all bug fixes usually go into the newer version and I’d hate anybody determined to stick to 7.0 to be stuck with any bugs. Hopefully, the 7.1 release will take care of all bugs and we can start off 8.0 with a clean slate.
Incidentally, I’d be interested in your response to the new UI changes in 7.1 but I guess I’ll have to wait till 7.1 is release and everybody has had a chance to test it out for themselves. Personally, I like the new UI but that’s only because I use the bare minimum of Blog features :p I’m more interested in the comments of somebody who uses the Preview feature a lot and/or the built-in Blog comments. Since the Preview pane is in a tab by itself, you might find it a bit awkward and if so, I’d like to try to do something to make the user experience a better one.
Since I’d switched over to Delphi 7.0 at work yesterday (I uninstalled all the old Delphi 6.0 and 7.0 stuff and reinstalled Delphi 7.0 :p), I had messed up and put in the demo version of PlusMemo. So the users who got the pre-release version of Blog 7.1 get a PlusMemo nag screen. This will be rectified as soon as I can find my copy of the registered version and you should have a nag-free release when I do do the public release. I’m also playing with a few internal components to see if I can try to reduce the application file size since the switch to Delphi 7.0 meant a sudden jump in the final executable size. Granted, it’s not even 100kb (more like half that) but I still hate executable size increases and am trying to see if I can somehow cut down on that by using a different component to do the same job.