Why It Sucks To Be Me Today
-
I've been plodding along, writing our WPF app, and thinking I've got stuff pretty much ironed out regarding code organization. I put our custom templates and styles into a AppResources project, and user controls and minor windows into the AppControls project. Everything was fine until I decided I needed a custom
TabItemclass. So I implement that class, compile and run the app. All of a sudden, the tab items don't have borders - at all. Everything else seems to be there, but not the borders, unless the mouse is hovering over the tab. After a brief inspection, I thought that theTargetTypeproperty on my customTabItemtemplate should be changed fromTabItemtoMyTabItem(the customTabItemclass' name). Well, I can't do that because it will create a circular assembly reference, which is verboten in .Net. Now I have to go through ALL of my code to change crap around. Specifically, I have to move all the custom XAML code into the AppControls assembly, and change all of the control/window XAML that uses it to make sure all the references are correct. And I don't even know if this is going to fix the fraklking problem until I try it! One step forward, two steps back. What a royal frakking pain in the anal pore..."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Hi John, I hope you don't mind if I consider you a "WPF" equivalent of a turkey baking thermometer : my sense is when you start praising it, or finding it tolerably suckless, will be about the right time for me to start using it and studying it ... and/or ... SilverLight. For some strange reason I got an e-mail from ComponentOne Singapore today (I've never bought a product or signed up for anything from them that I can remember) that mentioned a new product called an XAP[^] optimizer for SilverLight : out of curiousity I looked at the web page. From my point of view anything that can reduce applications' size (including those produced using none of ComponentOne's controls) "30-70%" means that what is producing those applications is writing out a lot of bloat. best, Bill
"Many : not conversant with mathematical studies, imagine that because it [the Analytical Engine] is to give results in numerical notation, its processes must consequently be arithmetical, numerical, rather than algebraical and analytical. This is an error. The engine can arrange and combine numerical quantities as if they were letters or any other general symbols; and it fact it might bring out its results in algebraical notation, were provisions made accordingly." Ada, Countess Lovelace, 1844
-
I've been plodding along, writing our WPF app, and thinking I've got stuff pretty much ironed out regarding code organization. I put our custom templates and styles into a AppResources project, and user controls and minor windows into the AppControls project. Everything was fine until I decided I needed a custom
TabItemclass. So I implement that class, compile and run the app. All of a sudden, the tab items don't have borders - at all. Everything else seems to be there, but not the borders, unless the mouse is hovering over the tab. After a brief inspection, I thought that theTargetTypeproperty on my customTabItemtemplate should be changed fromTabItemtoMyTabItem(the customTabItemclass' name). Well, I can't do that because it will create a circular assembly reference, which is verboten in .Net. Now I have to go through ALL of my code to change crap around. Specifically, I have to move all the custom XAML code into the AppControls assembly, and change all of the control/window XAML that uses it to make sure all the references are correct. And I don't even know if this is going to fix the fraklking problem until I try it! One step forward, two steps back. What a royal frakking pain in the anal pore..."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John, I think you need a :beer: I am sure that WPF was a Friday afternoon project. You know when you just get from the pub and don't want to work but have to be seen to be doing something. Someone had a 'great idea' and as there were no harpoons to hand the world got WPF!
Panic, Chaos, Destruction. My work here is done.
-
I've been plodding along, writing our WPF app, and thinking I've got stuff pretty much ironed out regarding code organization. I put our custom templates and styles into a AppResources project, and user controls and minor windows into the AppControls project. Everything was fine until I decided I needed a custom
TabItemclass. So I implement that class, compile and run the app. All of a sudden, the tab items don't have borders - at all. Everything else seems to be there, but not the borders, unless the mouse is hovering over the tab. After a brief inspection, I thought that theTargetTypeproperty on my customTabItemtemplate should be changed fromTabItemtoMyTabItem(the customTabItemclass' name). Well, I can't do that because it will create a circular assembly reference, which is verboten in .Net. Now I have to go through ALL of my code to change crap around. Specifically, I have to move all the custom XAML code into the AppControls assembly, and change all of the control/window XAML that uses it to make sure all the references are correct. And I don't even know if this is going to fix the fraklking problem until I try it! One step forward, two steps back. What a royal frakking pain in the anal pore..."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001I just gotta ask. Besides just letting the app look more shiny and pretty, does WPF bring any functionality to the party? Specifically, is there something a WPF app can do that I can't accomplish with Winforms? This stuff sounds like the polar opposite of "best bang for the buck."
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
-
I've been plodding along, writing our WPF app, and thinking I've got stuff pretty much ironed out regarding code organization. I put our custom templates and styles into a AppResources project, and user controls and minor windows into the AppControls project. Everything was fine until I decided I needed a custom
TabItemclass. So I implement that class, compile and run the app. All of a sudden, the tab items don't have borders - at all. Everything else seems to be there, but not the borders, unless the mouse is hovering over the tab. After a brief inspection, I thought that theTargetTypeproperty on my customTabItemtemplate should be changed fromTabItemtoMyTabItem(the customTabItemclass' name). Well, I can't do that because it will create a circular assembly reference, which is verboten in .Net. Now I have to go through ALL of my code to change crap around. Specifically, I have to move all the custom XAML code into the AppControls assembly, and change all of the control/window XAML that uses it to make sure all the references are correct. And I don't even know if this is going to fix the fraklking problem until I try it! One step forward, two steps back. What a royal frakking pain in the anal pore..."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001John, may I point you here http://www.viz.co.uk/profanisaurus.html[^] for some light entertainment. Dalek Dave, may appriciate this as well.
Software Kinetics (requires SL3 beta) - Moving software
-
John, may I point you here http://www.viz.co.uk/profanisaurus.html[^] for some light entertainment. Dalek Dave, may appriciate this as well.
Software Kinetics (requires SL3 beta) - Moving software
The URL is: http://www.viz.co.uk/profanisaurus.html
The category of this URL is: Adult/Mature ContentPlease email Technical Services if you have a legitimate reason to access this site.
I didn't find it that entertaining. ;)
Panic, Chaos, Destruction. My work here is done.
-
John, may I point you here http://www.viz.co.uk/profanisaurus.html[^] for some light entertainment. Dalek Dave, may appriciate this as well.
Software Kinetics (requires SL3 beta) - Moving software
I managed to access it. I love Viz. Been going for years now, and still totally offensive.
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
-
The URL is: http://www.viz.co.uk/profanisaurus.html
The category of this URL is: Adult/Mature ContentPlease email Technical Services if you have a legitimate reason to access this site.
I didn't find it that entertaining. ;)
Panic, Chaos, Destruction. My work here is done.
Jeez, you obviously never read Viz. :^)
Software Kinetics (requires SL3 beta) - Moving software
-
I managed to access it. I love Viz. Been going for years now, and still totally offensive.
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
Good giggle, I've spent many an afternoon reading some of the entries and added my own as well.
Software Kinetics (requires SL3 beta) - Moving software
-
Jeez, you obviously never read Viz. :^)
Software Kinetics (requires SL3 beta) - Moving software
He Means he can't access it. Censorship!
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
-
He Means he can't access it. Censorship!
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
He should change jobs, perhaps?
Software Kinetics (requires SL3 beta) - Moving software
-
He should change jobs, perhaps?
Software Kinetics (requires SL3 beta) - Moving software
Or access his filters!
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
-
I managed to access it. I love Viz. Been going for years now, and still totally offensive.
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
Sweary Mary on the fromt cover always cheered me up in the days I used to read.
Panic, Chaos, Destruction. My work here is done.
-
I just gotta ask. Besides just letting the app look more shiny and pretty, does WPF bring any functionality to the party? Specifically, is there something a WPF app can do that I can't accomplish with Winforms? This stuff sounds like the polar opposite of "best bang for the buck."
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Christopher Duncan wrote:
letting the app look more shiny and pretty
Sadly, that can make the difference for the client...
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Photos/CP Flickr Group - ScrewTurn Wiki
-
Or access his filters!
------------------------------------ "When Belly Full, Chin Hit Chest" Confucius 502BC
O' er missus, I rather not touch his filters
Software Kinetics (requires SL3 beta) - Moving software
-
I just gotta ask. Besides just letting the app look more shiny and pretty, does WPF bring any functionality to the party? Specifically, is there something a WPF app can do that I can't accomplish with Winforms? This stuff sounds like the polar opposite of "best bang for the buck."
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
Christopher Duncan wrote:
s there something a WPF app can do that I can't accomplish with Winforms?
Is there something Winforms can do which MFC can not? No Is there something MFC can do which Win32 API can not? No But:- Can something be done better in MFC over raw Win32? -> Yes Can something be done better in WinForms over raw MFC? Yes Can something be done better in WPF over WinForms? Yes. Specifically, data binding, highly flexible UI model. Some kind of applications can be developed easily with WPF which will take enormously long time to develop with WinForms especially graphical/data visualization applications.
-
I just gotta ask. Besides just letting the app look more shiny and pretty, does WPF bring any functionality to the party? Specifically, is there something a WPF app can do that I can't accomplish with Winforms? This stuff sounds like the polar opposite of "best bang for the buck."
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
From what I understand of things, the data binding in WPF is pretty damn cool. While there's no logical/technical reason this couldn't have been a standalone library, it's not, and WinForms has no equivalent. Other than that, most of the rest is just eye-candy, especially for LOB apps.
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
-
Christopher Duncan wrote:
s there something a WPF app can do that I can't accomplish with Winforms?
Is there something Winforms can do which MFC can not? No Is there something MFC can do which Win32 API can not? No But:- Can something be done better in MFC over raw Win32? -> Yes Can something be done better in WinForms over raw MFC? Yes Can something be done better in WPF over WinForms? Yes. Specifically, data binding, highly flexible UI model. Some kind of applications can be developed easily with WPF which will take enormously long time to develop with WinForms especially graphical/data visualization applications.
Maybe the question should have been. "Specifically, is there something a WPF app can do that I can't accomplish with Winforms with less hassle ?"
Cheers Garth I don't really care whether or not i really care or not.
-
John, may I point you here http://www.viz.co.uk/profanisaurus.html[^] for some light entertainment. Dalek Dave, may appriciate this as well.
Software Kinetics (requires SL3 beta) - Moving software
Very cool! Going to have to bookmark that!
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
-
I just gotta ask. Besides just letting the app look more shiny and pretty, does WPF bring any functionality to the party? Specifically, is there something a WPF app can do that I can't accomplish with Winforms? This stuff sounds like the polar opposite of "best bang for the buck."
Christopher Duncan www.PracticalUSA.com Author of The Career Programmer and Unite the Tribes Got a career question? Ask the Attack Chihuahua!
It's easier to do some of the flashy stuff, but as far as adding functional value to the application, no.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I've been plodding along, writing our WPF app, and thinking I've got stuff pretty much ironed out regarding code organization. I put our custom templates and styles into a AppResources project, and user controls and minor windows into the AppControls project. Everything was fine until I decided I needed a custom
TabItemclass. So I implement that class, compile and run the app. All of a sudden, the tab items don't have borders - at all. Everything else seems to be there, but not the borders, unless the mouse is hovering over the tab. After a brief inspection, I thought that theTargetTypeproperty on my customTabItemtemplate should be changed fromTabItemtoMyTabItem(the customTabItemclass' name). Well, I can't do that because it will create a circular assembly reference, which is verboten in .Net. Now I have to go through ALL of my code to change crap around. Specifically, I have to move all the custom XAML code into the AppControls assembly, and change all of the control/window XAML that uses it to make sure all the references are correct. And I don't even know if this is going to fix the fraklking problem until I try it! One step forward, two steps back. What a royal frakking pain in the anal pore..."Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001"WPF" seems to be turning into "WTF" with a mouthful of doughnut.
I wanna be a eunuchs developer! Pass me a bread knife!