3 ms·
In my expirience the the mix of XML and code quickly grows into a worse situation than just having a decent programming API in first place. In Flex, which also
by moe 17y ago
In my expirience the the mix of XML and code quickly grows into a worse situation than just having a decent programming API in first place.
In Flex, which also sports a declarative layer, most seasoned developers seem to try to avoid it as much as possible - because it gets in the way when complexity grows.
Same story with XUL, which perhaps would feel a little less like broken glass if they had omitted the "X" from the name.
But well, I have never coded a win32 GUI, so quite possible XAML really is a step up from what they had before.
- StrawberryFrog 17y agoIn my expirience the the mix of XML and code quickly grows into a worse situation It depends on how you do it. In any environment, there are ways that scale and ways that don't. We've had very good results (seperation of concerns, plugability, extensiblity, blendability) using the ViewModel pattern, an IOC Container and Command objects. The good part of WPF is that you can do all this, or other things, if you want. The same is not true of Windows forms. WPF enables some nifty ways to scale that are just not there in Windows forms.
- joubert 17y agoI'm doing all my current work in Flex and think it is great; If you apply some Cocoa-style discipline to structure, you can achieve stunning results while remaining nimble.