Re: Backgrounder needed. Why WPF
- From: "Patrice" <http://www.chez.com/scribe/>
- Date: Fri, 23 May 2008 13:57:22 +0200
WPF is redesigned while Windows Forms still builds on the good old concepts
introduced years ago...
Examples of things allowed by this redesign in WPF are :
- rendering is "standardized" so that an item rendered in a list box can be
whatever you want from text to images or even videos. It was previously more
complicated to create listboxes with custom elements
- the rendering tree doesn't stop at the control level, i.e. by customizing
the template for a control you can customize its appearance much more easily
than previously. For example if you have first a listbox of video names you
could customize the listbox to render it as a "video carrousel" but
technically speaking this is still a listbox
- improvements in layout capabilities, styling, sizing and countless others
(vector graphics, animations, transformations allowing to render non axis
aligned UIs etc...)
---
Patrice
<Just_a_fan@xxxxxxxx> a écrit dans le message de groupe de discussion :
3tgc34hb91353hv35rp74k9ielllic0jd8@xxxxxxxxxx
I have been through two books where they talk about the (almost)
parallel control set for WPF and VB. They go through the small
difference and talk about everything going on a form but what they don't
say is...
WHY WPF?
What did we get by having a (almost) parallel design palette. If the
features were so good, why not just fold them into the parallel controls
in VB?
This makes for another set of hundreds of things to remember and I can't
see the overriding benefit.
Possibly there is a White Paper on this somewhere or someone in the know
can say why. Wrox book talk about the what but not why this duality
came about.
Thanks for any help with this. I can't help but think that two
competing groups of designers got to load their almost identical but
incompatible stuff into the same IDE. Just seems odd to me. Anyone
else?
Mike
-----------------------------------------------------------
There are a variety of enhancements to the WPF Designer that are not
available in the Windows Forms Designer. These enhancements include:
Margin lines and stubs: Margin lines around each control indicate that a
margin has been set for that control. A margin stub indicates that no
margin has been set for that control edge.
Zoom control: The Zoom control appears in the upper-left corner of
Design view and allows the developer to zoom in or out on the design
surface to perform exact adjustments.
Snaplines: While snaplines appear in both the WPF Designer and the
Windows Forms Designer, in the WPF Designer they also display exact
values. In addition to displaying control alignment, snaplines also show
text alignment for text-based controls. For more information, see How
to: Align to Both Text Baselines and Margins.
.
- References:
- Backgrounder needed. Why WPF
- From: Just_a_fan
- Backgrounder needed. Why WPF
- Prev by Date: Re: How to minimize command mode window in console program?
- Next by Date: Re: How to minimize command mode window in console program?
- Previous by thread: Backgrounder needed. Why WPF
- Next by thread: Re: How to minimize command mode window in console program?
- Index(es):
Relevant Pages
|
