I just had a small heart attack after reading this. I think the currect ClamWin UI is next to perfect: it's clean, simple, functional, no annoying bells and whistles, responsive and fast. It's everything .NET apps are not. And above all, I do not want any .NET stuff on my servers.

What's next? Skins?

I really hope the currect light-weight UI will indeed be maintained, as you write. But I'm afraid I'm going to be left very disappointed in 1 or 2 years from now. 'Cool' and 'sexy' normally mean the end to good technology...

Cheers, Bob

My opinion (for what it's worth): ClamWin does need to provide some additional functionality/user options and this can only be done democratically by making some changes to the existing User Interface. I also think the average user doesn't care whether it's done via .Net or .whatever. I've seen a copy of the current state of the new GUI, and it appears to be on the right track--it's still clean/simple/functional.

Regards,

I agree with you that the avarage user probably doesn't care what the underlying technology used is, but I do care. Though I am in no position to judge what is necessary, I really doubt that this can only be achieved by using .NET. But, as long as there is going to be a seperate installer for the 'classic' UI without any .NET stuff, I think I have no reason to complain. I'm just a bit worried...

I don't mind changes to the UI however. Who knows, perhaps I'll be pleasantly surprised.

Cheers

Why must every personal firewall and virus scanner have its own style? Why can't they just follow the design guidelines of the underlying operating system? I never understood this. Colors, fonts, themes are system-wide settings and I expect them to be system-wide. I hate it if apps ignore system-wide settings just because a programmer thinks he has a better design.
An attractive design and attending system-wide settings aren't mutual exclusive things!

If ClamWin ever gets a GUI that ignores system-wide settings, I hope GUI code and scan engine code are separated enough so that I can write my own GUI.

Your GUI appears similar to be very similar to the peek of the version 1.0 GUI we recently saw in these forums.

The makers of most products, including computer software, try to distinguish themselves from the competition. "Packaging" is one way to do this. The problem is that the packaging often becomes more important than the product in the mind of the manufacturer. The package of some products costs more than what it contains!

Regards,

I hope that the classic UI will offer the same functions as the "other" GUI. I'm not pleased to hear that ClamWin use going the way of .NET .

I'm looking forward to the classic UI to see how it turns out.I can't believe how nice ClamWin has turned out to be I remember when it was barely known I even remember when it was just starting and all that existed was ClamAV for email. Yes those were the good old days