I love the code folding, syntax highlighting, and code suggestion/auto-completion features. Beyond that, any other feature is just icing on the cake.

The only suggestion I'd have for future improvement on these features is to allow customization of the syntax highlighting so that users can create their own coloring schemes (background and foreground color, active line, elements, values, etc.)

I just hope all these added features don't slow the app down.

I really want to be able to use CSSVista as my CSS editor, and the above mentioned features really make me believe this can be a reality. All I want to be able to do is edit CSS files for local and external HTML pages. If this can be done stably with CSSVista, then I think I'm home.

As far as the saving of CSS files go, if it were me I wouldn't worry about FTP right now. It's (hopefully!) way more usual to develop a site locally and upload. FTP would be nice, but I've got a slew of tools that already do that - Dreamweaver mostly, and SmartFTP when I need to do something non-basic. Plus, dealing with the dialogs for that sort of thing would be a fair bit more complex than a straight SaveDialog.

Custom plug-in support, while supremely interesting to me as a C# developer, is as naught compared to getting my filthy paws on all the other features you've already got :D

As long as it reliably works with the Mozilla Control I'm fine with whatever may come else.
The 0.1 always showed pages with the IE preview but no (very seldom, never knew why) with the Mozilla preview. Hope that gets a polish since CSS Vista is a wonderful tool.

Sol:
Nice idea for custom syntax colouring, this is actually quite easy to do, I'll look into adding it to the settings box. I thought a nice idea would be to have preset styles to what people are used to, eg: "Dreamweaver Style", "Visual Studio Style" etc.

As for CSSVista slowing down, this is one of the biggest problems right now. Hopefully, by 0.2, CSSVista will be completely multi-threaded, that is, processing the CSS will take place in a background thread, so it won't interfere with the browsers rendering and CSSVista's general UI.

Russell:
Thanks for that, it's very interesting to hear. I've had my doubts from the beginning about FTP, so I'll wait to hear what others think, but I'm leaning towards leaving it out of 0.2.

However, version saving is a real life-saver, so I'd love to leave that in.

The custom plug-in/add-on support means plug-ins (or add-ons) for Internet Explorer / Firefox. Sorry, I was a little unclear on that. I meant things like QuickTime plug-in, Flash etc. Custom ones will mean you won't have to wait 'til we add support for something, like, for example, if you use an SVG viewer, you could just add it to IE and FF in CSSVista yourself - although this isn't the case yet.

Gnak:

Yes, sorry, one of the largest problems with 0.1 was the mozilla control would not load properly on some machines. This is almost entirely fixed now, except that (as you can see in the pictures here) mozilla keeps losing its vertical scroll bar. This will all need to be fixed by 0.2.

Yes, you're right about versioning. I should have mentioned that it'd have saved me hours just recently...

While all these features sound very nice, it does sound like you could be making a lot of work for yourself. I think the primary thing for me is stability. At the moment 0.1 is (relatively) simple and the few problems it does have are easy to work around. The benefit it provides far outweighs the cost of remembering what these workarounds are.

If lots and lots of new features were added, I think it would be a lot of work for one guy to keep it stable. Well, I know I'd find it a lot of work anyway ;)

I think I might comment on your other new thread re: code completion, even if it's kind of related :)

Just another vote for losing FTP. I for one would never use it. I don't use the FTP features in any of my IDE's either. For FTP, I'd rather use a dedicated FTP program such as FileZilla.

Russell, you're right (again) - stability is #1 priority.

The next big change to be made is moving a lot more processing to background threads.

Once IE7 is out of beta, we'll be advising users to upgrade to that (although it's not required at all) - IE7 has much better support for changes to the DOM at run-time via mshtml. I've had to implement many a crazy workaround to stop IE6 throwing access violations.
I intend to code CSSVista to bypass these workarounds if IE7 is detected, therefore users experiencing problems with stability can try upgrading to IE7 to fix the problem.

Sol, thanks for your comments, it's looking less and less likely FTP will be seen in the next few versions.

While we're on the subject of new features, have you given any thought to a feature that would provide a tree-view of all the classes, IDs, and other elements in the currently loaded HTML file?

This is sort of related to your other post regarding auto-complete for user-specific elements, as it would be another way to boost productivity when I want to target different page elements. This way, the designer could just double-click the element in the tree-view, rather than having to sift through the source to find the different element names. It would be a boon for CSS designers that didn't do the HTML themselves.

Again, just a thought, not a necessary feature at all.

Sounds great! Good work.

Honestly, the only thing I'm really looking forward to is the "Accessing Authenticated Pages" option, since all the projects need it. Looking forward to use cssvista 0.2

Keep up the good work.

Come on baby! Release it. I can't wait any more.

What about unleashing the beast?

any ETA on this version?

What I wouldn't mind seeing is something similar to FireBug where you can click an element to find it's CSS, and see what styles it is using/inheriting. I know Firebug has this built in, but IE doesn't have anything of the sort. Of course there's IE Web Developer Toolbar, but it still falls short compared to Firebug. And since IE is usually the culprit when it comes to style faults, this functionality would be a godsend.