I Had Forgotten...
-
... how enjoyable desktop app development is. I've spent the last couple of weekends implementing a WPF version of our web app as a POC. There is no hope in hell of this code actually going anywhere, but I can exercise various aspects of our web app. I've got the following stuff implemented: 0) The user can use Ctrl+/Ctrl- to grow/shrink the app's font (like a web browser) for Section 508 compliance 1) Most of the forms in the app have a listview, so I'm using my AutomaticListView component ()[^]), and have derived a ne version that automatically increases column widths to keep up with the MainWindow's font size increase/decrease. 2) I'm using my Customizable WPF MessageBox[^], with changes that include extended icons, and border colors that are aligned with the icons (green=success, blue=info, etc). This kind of mimics your typical web-based message indicators. 3) The app acts like an old-school SDI app, with each form being a UserControl and the app managing display/disposal 4) The base form class provides support for app-specific function keys, as well as the ability to augment these function keys on a form-by-form basis with pre/post event handlers, as well as the ability to override the common functionality of the function key itself. 5) We have a weird date control in the web app with "peculiar" behavior, and I've been able to succesfully duplicate it in the form of a custom control. It includes a lot of fail-gracefully code, as well as a tooltip that includes error info in the event the user does something stupid. (We don't present a calendar on our date controls because the web app has to support complete keyboard-driven input. Overall, it's been a blast working on the desktop again. I sure miss the old days... The last time I did a desktop app for a paycheck was 2015...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or -
... how enjoyable desktop app development is. I've spent the last couple of weekends implementing a WPF version of our web app as a POC. There is no hope in hell of this code actually going anywhere, but I can exercise various aspects of our web app. I've got the following stuff implemented: 0) The user can use Ctrl+/Ctrl- to grow/shrink the app's font (like a web browser) for Section 508 compliance 1) Most of the forms in the app have a listview, so I'm using my AutomaticListView component ()[^]), and have derived a ne version that automatically increases column widths to keep up with the MainWindow's font size increase/decrease. 2) I'm using my Customizable WPF MessageBox[^], with changes that include extended icons, and border colors that are aligned with the icons (green=success, blue=info, etc). This kind of mimics your typical web-based message indicators. 3) The app acts like an old-school SDI app, with each form being a UserControl and the app managing display/disposal 4) The base form class provides support for app-specific function keys, as well as the ability to augment these function keys on a form-by-form basis with pre/post event handlers, as well as the ability to override the common functionality of the function key itself. 5) We have a weird date control in the web app with "peculiar" behavior, and I've been able to succesfully duplicate it in the form of a custom control. It includes a lot of fail-gracefully code, as well as a tooltip that includes error info in the event the user does something stupid. (We don't present a calendar on our date controls because the web app has to support complete keyboard-driven input. Overall, it's been a blast working on the desktop again. I sure miss the old days... The last time I did a desktop app for a paycheck was 2015...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or#realJSOP wrote:
has to support complete keyboard-driven input
So it is still a gov't oriented project. They're the main ones that look for that "operators will be reading forms and entering data so make it such that they don't have to look at the screen much." motif.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
#realJSOP wrote:
has to support complete keyboard-driven input
So it is still a gov't oriented project. They're the main ones that look for that "operators will be reading forms and entering data so make it such that they don't have to look at the screen much." motif.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
Any data entry system should support keyboard field movement. It doesn't matter if it's a desktop or web application.
Should and DOES are two different things.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
-
... how enjoyable desktop app development is. I've spent the last couple of weekends implementing a WPF version of our web app as a POC. There is no hope in hell of this code actually going anywhere, but I can exercise various aspects of our web app. I've got the following stuff implemented: 0) The user can use Ctrl+/Ctrl- to grow/shrink the app's font (like a web browser) for Section 508 compliance 1) Most of the forms in the app have a listview, so I'm using my AutomaticListView component ()[^]), and have derived a ne version that automatically increases column widths to keep up with the MainWindow's font size increase/decrease. 2) I'm using my Customizable WPF MessageBox[^], with changes that include extended icons, and border colors that are aligned with the icons (green=success, blue=info, etc). This kind of mimics your typical web-based message indicators. 3) The app acts like an old-school SDI app, with each form being a UserControl and the app managing display/disposal 4) The base form class provides support for app-specific function keys, as well as the ability to augment these function keys on a form-by-form basis with pre/post event handlers, as well as the ability to override the common functionality of the function key itself. 5) We have a weird date control in the web app with "peculiar" behavior, and I've been able to succesfully duplicate it in the form of a custom control. It includes a lot of fail-gracefully code, as well as a tooltip that includes error info in the event the user does something stupid. (We don't present a calendar on our date controls because the web app has to support complete keyboard-driven input. Overall, it's been a blast working on the desktop again. I sure miss the old days... The last time I did a desktop app for a paycheck was 2015...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or#realJSOP wrote:
Forum:The Lounge ... how enjoyable desktop app development is.
My current ratio of desktop/web development is about 50/50 trending toward more web development. IMHO desktop is just easier/quicker for a POC for a lot of reasons...no back button, session state, richer controls are a few that come to mind. I can't say I prefer one or the other, but for a POC or testing, it sure is quicker to design/test/debug a desktop app. I can't tell you how many minutes a day I wait for the VS IIS Express to spin up just to test a minor edit :zzz: ...enough that I got a bigger hammer (new system with more of everything) waiting in the wings. :) Another weekend and I'll make the move.
"Go forth into the source" - Neal Morse "Hope is contagious"
-
#realJSOP wrote:
has to support complete keyboard-driven input
So it is still a gov't oriented project. They're the main ones that look for that "operators will be reading forms and entering data so make it such that they don't have to look at the screen much." motif.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated. I’m begging you for the benefit of everyone, don’t be STUPID.
It's a forensic drug testing application, and the folks in the labs use barcode scanners and keyboard input. They rarely (if ever) need to use a mouse for anything other than selecting the form they want to use. I think this app is the most complex I've ever worked on, even more so than the tax/charitable giving software I used to do... The complexity isn't a problem - the fact that it's a web app is what I have issues with.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013