XAML

[Ioannis Vranos]

Will XAML be mandatory in VS "Orcas"?

 

[Bjoern Hoehrmann]

* Ioannis Vranos wrote in microsoft.public.dotnet.languages.vc:

Will XAML be mandatory in VS "Orcas"?

"Mandatory" in which way?

 

[Ioannis Vranos]

"Mandatory" in which way?

For example when you create a new project, a Windows Form and drag and
drop components on it, or an Avalon GUI instead of creating the
underlying code in the language of choice (C++ for example) as it is
today, to create it in XAML only.

 

[Carl Daniel [VC++ MVP]]

For example when you create a new project, a Windows Form and drag and
drop components on it, or an Avalon GUI instead of creating the
underlying code in the language of choice (C++ for example) as it is
today, to create it in XAML only.

From what I've heard/seen/read, no - not at the Avalon level anyway. I
wouldn't be surprised though if all the VS project wizards use XAML for UI
construction.

-cd

 

[Ioannis Vranos]

From what I've heard/seen/read, no - not at the Avalon level anyway. I
wouldn't be surprised though if all the VS project wizards use XAML for UI
construction.

I asked because at http://channel9.msdn.com/ShowPost.aspx?PostID=34528
in the video it is shown that when he creates an Avalon project, it is
created in XAML.

 

[Tomas Restrepo \(MVP\)]

Ioannis,

I asked because at http://channel9.msdn.com/ShowPost.aspx?PostID=34528
in the video it is shown that when he creates an Avalon project, it is
created in XAML.

AFAIK (and I don't know much), Avalon and Winforms will coexist, so, that
seems about right... you'd use XAML for avalon projects (that's what is
for), and winforms if not...

 

[Ioannis Vranos]

AFAIK (and I don't know much), Avalon and Winforms will coexist, so, that
seems about right... you'd use XAML for avalon projects (that's what is
for), and winforms if not...

As far as I know, XAML is a simple compiled .NET language suitable for
GUI stuff (and not much else).


I had heard in the past that things will be like this. We will be making
the GUI stuff (Forms, Buttons etc) with XAML and the event handlers with
another language of our choice.

Since I have not much time to learn another VB-- just to make the GUI
stuff, and would like to use C++ to do the job in the first place,
making the designer of VC++ using XAML instead of C++, I think would
just enforce yet another language upon us, without any real benefit.

 

[David Lowndes]

Since I have not much time to learn another VB-- just to make the GUI

stuff, and would like to use C++ to do the job in the first place,
making the designer of VC++ using XAML instead of C++, I think would
just enforce yet another language upon us, without any real benefit.

I'd expect the XAML (if there is any) to be hidden from most users -
i.e. perhaps it'll be the output of the form designer?

Dave

 

[ben]

XAML is much like HTML, but more sophiticated, from the surface anyway. What
I think is

1) XAML is probably the most typing-saving and straight to the point
language for UI design. You can almost visualize the screen as you look at
the code. can you visualize the screen among a dozen C++ UI classes?

2) XAML is such an easy language compare to C++ anyway

 

[Ioannis Vranos]

XAML is much like HTML, but more sophiticated, from the surface anyway. What
I think is

1) XAML is probably the most typing-saving and straight to the point
language for UI design. You can almost visualize the screen as you look at
the code. can you visualize the screen among a dozen C++ UI classes?

2) XAML is such an easy language compare to C++ anyway

OK, but why should we be forced to learn it? One may be excited with
XAML, but would one like to be forced to learn any language I am excited
about?

 

[Steve McLellan]

OK, but why should we be forced to learn it? One may be excited with XAML,
but would one like to be forced to learn any language I am excited about?

If it's the language the UI designer outputs you won't be forced to learn
it. It makes much more sense than the development team writing UI designers
that output 3 different languages, IMHO. From what I've seen, XAML looks
really simple, and like David says, most of it will presumably be hidden
from users (like the 'InitializeComponent' call which in the majority of
cases you don't need to look at - most code is written in event handlers).
You could always pass the feedback on to Microsoft though, it's probably
still a good time for them to be getting ideas from developers.

Steve

 

[Ioannis Vranos]

If it's the language the UI designer outputs you won't be forced to learn
it. It makes much more sense than the development team writing UI designers
that output 3 different languages, IMHO. From what I've seen, XAML looks
really simple, and like David says, most of it will presumably be hidden
from users (like the 'InitializeComponent' call which in the majority of
cases you don't need to look at - most code is written in event handlers).
You could always pass the feedback on to Microsoft though, it's probably
still a good time for them to be getting ideas from developers.

Well, many times I add some things of my own in the form definition,
some boolean, some integer, a vector may be. How will I do that in an
XML language? I will have to learn it.

And as I saw in the video, probably XAML will be used only in an Avalon
project (Window), so I guess we will be forced to learn XAML to make
animated buttons, or we will be erasing everything and use C++ manually,
which is counter-productive.