The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Prior to my forced retirement, I was working in a mental health care setting with a very limited budget. Third-party controls were out of the question, unless they were free and available with source code. This meant that, if I wanted a nonstandard control, I usually had to create it. With WinForms, this was a continuing pain.
With WPF, much of the needed functionality was built in via data bindings. I could often do things with an existing control using a data binding and a few lines of code in a backend module that would have required a whole separate project to create a new control in WinForms.
My boss at the time did not favor my approach, but as the sole programmer and an ever increasing list of new code to be written and older code to maintain, coding speed was important.
same boat here; was a single developer with no budget for 3rd party controls. but I'm going to guess you had mostly database work that made data binding your go to. so yes WPF does make that easier than winform's data binding.
the stuff i dealt with in industrial control had no databases what so ever, and had no need for binding; it was mostly generic tags that the live IO was converted from; temperatures, pressures, on/off values... each tag had a unique id.
Winforms was extremely efficient for what i used it for, it's a bit of a different world than most software development.
I'm not saying the way you did it is wrong, quite the opposite; you worked with a technology stack that worked best for you.
winforms worked best for me. now I'm at a place that uses WPF as it's main product because binding makes more sense here. when ever I go back to dealing with non-database applications, I usually default back to winforms, because I have direct ability to draw what i need directly to the surface of a control; UWP also let's me do this, but I really don't like the store-app model for distributing my software.
I would have said semantics, but you said that's not the one you're looking for, so:
If it's how words are used in everyday speech that may be different from "official" definitions - colloquial.
If it's how words take on additional meaning especially within certain phrases - connotation.
That's all that's coming to mind at the moment.
As words are used by influential people (unfortunately today, this is no longer great statesmen or scientists but instead, a bunch of brain-dead reality stars or "pop-icons") they are used by others until they become commonplace and accepted with whatever new meaning they now are lumbered with.
- I would love to change the world, but they won’t give me the source code.
...till 20 years since the little sister died. Kicked me in the nuts and upset many wanna be child molesters here, eat a bag of dicks.
Manfred Santa's Reindeeir C**k and Hide Behind Sherlock knob jockey can suck my dick.
Got any opinions about expressing emotions about my little sister, wander down and have a chat with me face to face c**k knockets.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
There is a thing called professional help. It will not bring you back the lost person, but it can help you better manage the loss! I did it and it helped at least a Little bit. And I'm sure you will know that a Little help on such matters are then and when a big help.
It does not solve my Problem, but it answers my question
I was reading The Guardian today and ran across a striking article[^] about women in computer science. It takes me back to the 1980s, when I worked for Interdata, a company that used to build minicomputers.
In the computer center, most of the operators were women. One of the women complained to me about one of the utility programs she had to frequently use. When she asked for modifications, she was belittled and denied. She asked me for help, but I was behind schedule on my project at the time. Instead, I had been helping her with her computer science homework, I suggested that she modify the source code. She did and logged it into the library. I countersigned as the "supervising engineer." The new version began shipping with all new computers and was included in the software maintenance update.
Then the problems began. Customers complemented Interdata on the improvement. Only then did management realize that the utility had been updated. Because of government contracts, all software updates had to be signed by the "responsible engineer", that is, the engineer who actually did the work. She did not have the title of "engineer". I, as "supervising engineer", refused to modify the release document, citing the IEEE Code of Ethics which the company officially supported.
This went on for several weeks. There was a government delivery approaching, which would include a software library audit. I suggested that, since she had the skills and would soon receive her bachelor's degree, that she be promoted. I was told that the idea would never fly. Guess what? Just before the delivery, senior management promoted her to Junior Engineer.
Guess what also happened.... I was in deep political hot water. I did stay with the company through several name changes for the next six years.
From the article, however, nothing much has changed in the past forty years!
Guess a better name for InterData would have been InterDit
At my company things were quite (or maybe too) relaxed, until we had to certify for the ISO 9001, we expect to finish it in the next couple of weeks.
My favorite Interdata/Perkin-Elmer memory is when for several months a coworker and I managed to keep the documentation and software folks working at cross-purposes. We found a slight difference between a program and the documentation for that program, and kept sending in requests; his asked that the software be changed to match the documentation, mine that the documentation be changed to match the software. For six months, each was changed to match what the other said or did, which meant they no longer matched again. Apparently after that stretch, either one of the groups failed to change it, or the two groups finally talked to each other. I do have fond memories of the day when we got our first 8/32, and thinking that we'd never fill up 256K of RAM!