4 Replies - 385 Views - Last Post: 11 December 2018 - 04:46 PM

#1 Skydiver   User is offline

  • Code herder
  • member icon

Reputation: 6988
  • View blog
  • Posts: 23,760
  • Joined: 05-May 12

WPF, WinForms, and WinUI going open source

Posted 04 December 2018 - 04:43 PM

WPF, WinForms, and WinUI are going open source

I love that WPF will go open source so that customizing out-of-the-box controls will be easier to customize, but I cringe at the thought of WinForms going open source. It's going to extend the life of WinForms which was at end of life, the same way XNA continues to live via Monogame. But what really makes me worry is that I foresee somebody re-skinning the WinForms controls to look just like iOS UI controls, or Android UI controls. I hoping that someone will not re-skin it to look like the old Borland/Delphi controls.

Looking at the bright side, somebody may actually fix the tab control idiosyncrasies, or make a truly usable masked edit control.

Is This A Good Question/Topic? 1
  • +

Replies To: WPF, WinForms, and WinUI going open source

#2 modi123_1   User is online

  • Suitor #2
  • member icon



Reputation: 15170
  • View blog
  • Posts: 60,720
  • Joined: 12-June 08

Re: WPF, WinForms, and WinUI going open source

Posted 04 December 2018 - 05:53 PM

Yeah I caught that in the keynote. Spiffy!
Was This Post Helpful? 0
  • +
  • -

#3 hexagod   User is offline

  • 😂😂😂
  • member icon

Reputation: 31
  • View blog
  • Posts: 577
  • Joined: 29-October 16

Re: WPF, WinForms, and WinUI going open source

Posted 11 December 2018 - 09:40 AM

View PostSkydiver, on 04 December 2018 - 04:43 PM, said:

WPF, WinForms, and WinUI are going open source
but I cringe at the thought of WinForms going open source. It's going to extend the life of WinForms which was at end of life, the same way XNA continues to live via Monogame. But what really makes me worry is that I foresee somebody re-skinning the WinForms controls to look just like iOS UI controls, or Android UI controls. I hoping that someone will not re-skin it to look like the old Borland/Delphi controls.


I use WPF but Winforms is that classic look... there's something fun about the older GUI for super simple projects.

winforms nevar dyeee muahahahhahahahahhaha :baaa:

but srsly tho Glad MS is open sourcing these technologies
Was This Post Helpful? 0
  • +
  • -

#4 hexagod   User is offline

  • 😂😂😂
  • member icon

Reputation: 31
  • View blog
  • Posts: 577
  • Joined: 29-October 16

Re: WPF, WinForms, and WinUI going open source

Posted 11 December 2018 - 02:52 PM

Skydiver's version of a nightmare is probably all WinForms hardcoded push to UI and no databinding allowed... dev has to go through and manually change all interfaces at the slightest change to model. He wakes up in cold sweats when he sees thousands of lines like this:

                    foreach (DataRow _row in dt.Rows)
                    {
                        // nameValues.Add((string)row["Name"]);
                        nameValues.Add(_row["Name"].ToString());
                        driverValues.Add(_row["DriverName"].ToString());
                        portValues.Add(_row["PortName"].ToString());
                    }
                    namesListBox.ItemsSource = nameValues;
                    namesListBox.Items.Refresh();
                    driversListBox.ItemsSource = driverValues;
                    driversListBox.Items.Refresh();
                    portsListBox.ItemsSource = portValues;
                    portsListBox.Items.Refresh();


:sweatdrop:
Was This Post Helpful? 0
  • +
  • -

#5 Skydiver   User is offline

  • Code herder
  • member icon

Reputation: 6988
  • View blog
  • Posts: 23,760
  • Joined: 05-May 12

Re: WPF, WinForms, and WinUI going open source

Posted 11 December 2018 - 04:46 PM

Actually, no since I used to write that kind of code all throughout my Win32 and WinForms days. My nightmare is that a PM or Exec wants yet "just one more minor UI tweak" which involves a lot of pixel counting, or finding the right sized font such that US version looks like what they want, but still keeps all the other 20-40 localized versions working, as well as still comply with Section 508 accessibility laws.

All of that and your co-workers resist hand coding the forms, but would rather keep on using the buggy WinForms Designer. Yes, that same WinForms Designer that crashes 50% of the time they next time you rebuild even if nothing was changed between builds.
Was This Post Helpful? 2
  • +
  • -

Page 1 of 1