Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WPF is WOW
Message
From
25/05/2010 09:08:59
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
 
 
To
25/05/2010 08:57:36
General information
Forum:
ASP.NET
Category:
Windows Presentation Foundation (WPF)
Title:
Miscellaneous
Thread ID:
01464256
Message ID:
01465858
Views:
100
There is some value in exactly what you say is not needed. I have an application that is touch screen and fills the entire monitor as it needs the real estate. I spent lots of time getting all the objects to be able to scale to the monitor size of 8", 10" or 12" depending. With WPF that would have been a no brainer. I hate what windows forms look like when the user resizes them and all the controls don't resize with the form.

WPF fixes most of those issues quite easily and they don't have to be hand coded. It isn't just the ability to do fancy stuff that makes WPF appealing. I do realize not every business has the needs of WPF, but it is more flexible allowing one to create what they need more readily than ancient technology of windows forms. Plus Brian, it is XAML not AXML.

Just another opinion.
Tim

>That’s a pretty broad statement with very little meat to back it up.
>WPF s an attempt to fill a need that simply doesn’t exist in line of business applications. We have no need of a platform that allows graphic designers to paint up forms or controls . Most line of business applications I’ve worked on since win 3.0 don’t even stray from the standard controls. A typical Business form is pretty straight forward. You have a list of some type or search criteria and a details section or page. The details will have some validations and maybe some custom formatting. If you work in a team or have been coding for a while you probably already have base class forms to handle some or most of the query and crud logic on your business objects. So that just leaves dropping controls on the form wiring up the data binding. The majority of the data binding is usually a simple matter of putting the field name in a binding property, pretty fast and straight forward. Any validation are equally fast and straight forward. Go to the property sheet click the events button choose the valid event and dbl click to get your stub. Call your business rule or write your valid code. Again Fast and straight forward
>The users will be presented with exactly what they need exactly how they need it. And guess what else none of it will require a 3D graphics card. That’s fairly improtant in an organization with thousands of workstations.
>We don’t need yet another MS markup wana b language (AXML) for that . Just the fact that you have to go into the axml file and hand code things precludes it be more productive than WInforms.
>
>Now I’ve pointed out why I don’t see value in wpf in a line of business application. Can you show me where there is a value?
Timothy Bryan
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform