Longhorn has no WindowsForms ?

  • Thread starter Thread starter ncaHammer
  • Start date Start date
N

ncaHammer

http://www.geocities.com/basslagter/longhorn.html

look at the last picture (the error with the stack trace)
seems that all controls belong to the System.Windows namespace
(ElementCollection), nowhere System.Windows.Forms !
has anybody the beta of LongHorn to confirm it ?

btw has anybody a xaml file to post it ?
i am *very* curious to see its schema (to compare it with XUL)
 
Hello,

ncaHammer said:
http://www.geocities.com/basslagter/longhorn.html

look at the last picture (the error with the stack trace)
seems that all controls belong to the System.Windows namespace
(ElementCollection), nowhere System.Windows.Forms !
has anybody the beta of LongHorn to confirm it ?

btw has anybody a xaml file to post it ?
i am *very* curious to see its schema (to compare it with XUL)
Click to expand...

I don't know if Windows Forms are included, but it will include the
Avalon forms package.

HTH,
Herfried K. Wagner
 
Hi Herfried,
I don't know if Windows Forms are included, but it will include the
Avalon forms package.
Click to expand...

Thanks,
I thought that Avalon was a new GDI+ only, and that System.Drawing and
Windows forms will remain as is with small changes

anyway, googling I found this

http://www.devsearch.com/codemag/Article/11489/0/page/5

<quote>
By then the Win32 API will be gone forever. Microsoft is working on a new
user interface API (codenamed Avalon) to be used in the Windows shell as
well as in the next generation of desktop applications. Putting more effort
in the Windows Forms of today is a lost investment.
</quote>

if I want *today* to create a new toolbar control what should I do ?

1) Write it from scratch using GDI+ (more code, hoping that porting it
to Avalon will be easy)
2) Use the existing toolbar (or subclass toolbar common control) and make a
ton of Interop calls (faster and you are sure that your code will be
obsolete<g>)
3) Don't do anything, just use the out-of-the-box toolbar (and probably
leave the competition to eat you)

Advise ?
Any chance that MS will give some guidelines on this subject ?

PS. toolbar control is just an example, IMO writing from scratch a GDI+
toolbar is easier than subclass it
 
Hello,

ncaHammer said:
I thought that Avalon was a new GDI+ only, and that System
.Drawing and Windows forms will remain as is with small changes
Click to expand...

AFAIK avalon forms are an alternative GUI package (used by Windows
Longhorn). I think/hope that Windows Forms and Win32 Controls will
still work.

HTH,
Herfried K. Wagner
 
AFAIK avalon forms are an alternative GUI package (used by Windows
Longhorn). I think/hope that Windows Forms and Win32 Controls will
still work.
Click to expand...

I can't imagine that they won't, after all Microsoft's biggest
strength is the huge range of software available for Windows... and
most of it is written for the Win32 API! (including MFC/VC/Delphi...)
 
Back
Top