Re: Windows.Forms crippled by Microsoft

#1

Quote:

Why part of .NET Windows Forms potential is hidden? Why there are
libraries
like MagicLibrary and similar, that support dockable windows, runtime
visuals styles and so on. Why are not a standard part of Windows.Forms?

Yes, this is a very interesting question for me, too!
I don't understand why MS does not include the well known
UI techniques which are state-of-the-art.

Roger

#2

You have to ask yourself who the WinForms library is aimed at. In terms of
windows development the overwhelming group are VB. VB developers have
always been used to forms and manually linking toolbar buttons with menu
items and status bars - exactly the stuff that MFC developers have taken for
granted for years and are now sorely missing in VS.NET. If VB developers did
not need those extra features, why spend the resources to add them?

Richard
--
my email evpuneqt (AT) zicf (DOT) bet is encrypted with ROT13 (www.rot13.org)

Roger Meyers wrote:

Quote:

Why part of .NET Windows Forms potential is hidden? Why there are
libraries like MagicLibrary and similar, that support dockable
windows, runtime visuals styles and so on. Why are not a standard
part of Windows.Forms?

Yes, this is a very interesting question for me, too!
I don't understand why MS does not include the well known
UI techniques which are state-of-the-art.

Roger

#3

Mitja Semolic wrote:

Quote:

Then I have misunderstood the goals of the .NET Framework. I thought
that Microsoft wanted to replace the outdated Windows API libraries,
with a modern and efficient API. A framework that would not have only

Yes, that is the reason for the .NET framework, and if you look at what the
..NET runtime does I think you'll agree with me that it has fulfilled its
goal.

Quote:

a common interface for all Windows platforms, but as much shared
code, to promote consistency and interoperability.

Again, yes, it has done that.

Quote:

But as you say .NET is meant to please only VB developers, other
shout use MFC and Windows API?

No, you have to read again what I said:

Quote:

You have to ask yourself who the WinForms library is aimed at.

My very cynical point of view is that Windows Forms is aimed squarely at
Visual Basic developers. I would even argue (with no evidence other than
looking at the classes in the library and what they do) that the Windows
Forms code base has its origin in the VB Forms code base.

Quote:

Which GUI library will use Windows Longhorn applications, because all
this new features would be easier to use and to implement in a brand
new library?

The big question is what GUI library will Longhjorn use? Its rumoured to
have a totally different GUI library called Avalon (search www.winnetmag.com
for the rumours, for example
http://www.wininformant.com/Articles...ticleID=39390).

Richard

--
my email evpuneqt (AT) zicf (DOT) bet is encrypted with ROT13 (www.rot13.org)

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Windows.Forms crippled by Microsoft

Dotnet FAQs microsoft.public.dotnet.faqs

Re: Windows.Forms crippled by Microsoft - 06-29-2003 , 09:44 AM

Re: Windows.Forms crippled by Microsoft - 07-01-2003 , 05:19 AM

Re: Windows.Forms crippled by Microsoft - 07-02-2003 , 10:11 AM