Did the brave OO language research guys give (the better part of) their lives in vain; their graves to be desecrated by the vile 1970s SGML nincompoops?
From this sample, the only funciton of XAML seems to be to put the foul-tasting XML syntactic sugar around a very ordinary presentation paradigm.
How, for example, would I reuse this presentation when it's calling directly into code? How could I switch out a different processing engine? How would I even change the language? Of course, all this is the domain of the application design, not the technologies used to implement it; however I am singularly failing to see how XAML helps us to achieve anything more than what we have at present.
... did I just rant then? Bugger.
Bryan
Wednesday, February 10, 2010
Hi, I just finished a VB.Net version of your program written with VS 2008. I made some minor additions adding clear and reset buttons as well as the ability to edit the grid. Another feature I'd like to add is the ability to add/remove rows to the grid by resizing the form. As it stands now, resizing the form resizes the cells leaving the number of cells unchanged. I'm having a hard time figuring out how to dynamically add/remove columns or rows to a gridpanel. Any suggestions?
Comments
Oh, I really can't be bothered to rant....
Did the brave OO language research guys give (the better part of) their lives in vain; their graves to be desecrated by the vile 1970s SGML nincompoops?
From this sample, the only funciton of XAML seems to be to put the foul-tasting XML syntactic sugar around a very ordinary presentation paradigm.
How, for example, would I reuse this presentation when it's calling directly into code? How could I switch out a different processing engine? How would I even change the language? Of course, all this is the domain of the application design, not the technologies used to implement it; however I am singularly failing to see how XAML helps us to achieve anything more than what we have at present.
... did I just rant then? Bugger.