|
Kornfeld Eliyahu Peter wrote: plus add some buttons to each row Ah thinking like a web developer, I cannot remember when I last had buttons on each row. My VM knows precisely what row is selected so all I need is the action directive, also double click is your friend.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Yes, the default look isn't very nice - it takes a bit of effort to style the app, but webpages are like that as well. You can get WPF themes or third part controls that look nice out of the box.
|
|
|
|
|
Jacquers wrote: you can make some really nice looking apps.
...if you're willing to allocate the resources to do it. Otherwise WPF apps can be made to look every bit as ugly as WinForms-based apps.
If your focus is not on the UI, then WPF adds a lot of cost (in terms of learning overhead) with very little return, IMO.
|
|
|
|
|
Yes, the default look isn't very nice - it takes a bit of effort to style the app, but webpages are like that as well. You can get WPF themes or third part controls that look nice out of the box.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: Why's that WPF, that came to life to replace the ugly WinForms, is so ugly?
Because they decided instead to focus on an inane XML syntax instead that requires, among other things, custom instantiators instead of a simple parser and is almost (if not completely) impossible to express and correctly render in a designer, requiring you to hand code the XML, which when I wrote my articles on MyXaml, everyone screeched about how nobody would want to hand-code XML to design a UI, but when Microsoft put out WPF, that's what everyone was forced to do and even seemed to enjoy doing. Um.. end rant?
Oh, and because Microsoft likes to leave the professional UI design to third parties.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: professional UI design
Don't go that far...
I would like - for start - that vertical alignment in DataGrid of the content would be logical (bottom for all RTL and LTR languages)...
It is not that professional level request...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
I am an old fossil — when I started there was no such thing as a graphics interface. Input was either punched cards, magnetic tape or an IBM Selectric or ASR 33 console. I definitely prefer XAML to drag-and-drop. It is much easier to write parameters to modify a control than to have to open a property window. Extending a WinForms property window? Not trivial. Adding a parameter to an XAML control, by way of contrast, is almost effortless!
I LIKE WPF!! I just wish it had better error detection at coding time.
__________________
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|
|
Why do you need to write an extension in the first place? . There are third party grid components like xceed that can make life easier...anyway..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
A Visual Studio Extension...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
To do what..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Metadata management for our development...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
so got custom "metadata" in your code and you need a to develop a gui that will display the "metadata" in a datagrid in visual studio when a dev click a button in vs..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
modified 14-Oct-18 13:16pm.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: ugly WinForms I imagine the original design goals to include things like functionality, accessability, discoverabilty and consistency.
Not "look sexy".
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
The (wpf) UI designer is definitely horrible.
And wpf does have a steeeep learning curve (trust me, 'been there). The funny thing is, to fully appreciate it, you need to use it (and actually compare it to Winforms) - and while at the beginning, you'll curse a lot (I did ), when you start to "get" it, you'll use it for any non-trivial UI.
The more you'll delve into it, the more you'll love it (granted, you'll still hate the UI designer ).
Two easy examples: animations, pixel shaders (i.e., Effects). When you actually start understanding how layout works in wpf, you'll be able to create controls that can simply blow your mind (which would be really really hard to implement in Winforms)!
Best,
John
P.S. If (just if ) you want to learn WPF, I recommend "WPF 4.5 Unleashed" - a lot of things don't seem to make any sense in WPF, until explained. Again, been there
-- Phot-Awe - Find the Photos you Love - FAST!
|
|
|
|
|
Agreed, on all counts. I've been using WPF for ten years for UI on our products. Once you 'get it', you can do wonderfully useful things in your UI that would be next to impossible without it.
And yes, the WPF designer is worthless. Between constant crashes and its incessant need to insert absolute constants everywhere, it's far easier to hand-code XAML.
Software Zen: delete this;
|
|
|
|
|
Agree
__________________
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|
|
I agree that the learning curve is quite steep and there still are things that you cannot do in the designer or XAML (or at least not intuitively). I have, from time to time, built entire controls with children in the code so I don't have XAML documents 1000+ lines long and nested enough to require a lot of horizontal scrolling. However, I still prefer it to WinForms.
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
I'm sure it's Very true. Because all the experienced WPF developers say the same.
Full Reset
|
|
|
|
|
Winforms isn't ugly in my opinion. WPF is, though!
Anything that is unrelated to elephants is irrelephant Anonymous
- The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944
- Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
|
|
|
|
|
I concur. I tried, really tried, to use WPF but it produced such an ugly and clunky UI that i implemented what I wanted in WinForms - quickly and easily with very smooth and beautiful results - and a few fancy effects while I was at it - also easily implemented and debugged as necessary.
Bring back Winforms! I was about to say "All is Forgiven!" but there is nothing really to forgive.
I think the "Winforms is Ugly" came from Microsoft Marketing Bozos to enable adoption of the terrible WPF!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Maybe you should be using this[^] for your UI work.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I've been looking for something like this!
|
|
|
|
|
Thanks to all for not mentioning 'MVVM' ... wow ... rare.
|
|
|
|
|
WPF compared to winforms feels half baked and inconsistent; documentation is, poor and I spend more time searching the web on how to do something so simple in winforms (like a checked listbox) that I'm not enjoying development anymore.
UWP you can at least use win2d and get a graphics object like the GDI+ in winforms and draw natively when you need.
I'm not saying winforms is perfect, and not everything in WPF is bad, I can just do way more work in a single day with winforms than WPF.
It feels like the ones who created xaml looked at the web and tried to copy how that worked, to bring web devs to the desktop.
|
|
|
|
|
Only if you are doing something relatively simple.
Any form that requires execution-time reconfiguration gets real messy in WinForms, while in WPF, all it requires in changing bound parameter values. Before I was retired, I did this all the time.
__________________
Lord, grant me the serenity to accept that there are some things I just can’t keep up with, the determination to keep up with the things I must keep up with, and the wisdom to find a good RSS feed from someone who keeps up with what I’d like to, but just don’t have the damn bandwidth to handle right now.
© 2009, Rex Hammock
|
|
|
|