[i]Often proof-of-concept programs are helpful, but all too often management sees a demo that appears 80% feature complete and thinks the project is almost done. It leads to unrealistic expectations.[/i]
Nobody would look at at architects model of a bridge and say "that looks good, go toss it in the river and we'll use it", but we seem to do it all the time in software
>I personally believe that global warming exists however I still don't know how much humans are involved in the process.
Well if it is cyclical and natural hten we may or may not be contributing to it and, more crucially, we may or may not be able to do anything about itto *stop* it, in which case we're better of putting our money into finding a way to live through it rather than futilely fighting somehting beyond out power
>Cincom Smalltalk, which is the descendant of VisualWorks, still uses MVC. Dolphin
Sort of. It uses a secondary layer on top, "VisualWorks", the manages the interations between the models and the controllers and views. Then the UIBuilder builds to this structure. It makes it a lot easier to use. Technicaly it's down there but you don't have to worry about it much
MVP is a pretty good improvement over MVC
It's been awhile since I used VisualAge and they use something else, with a Bridge pattern thrown in the middle to manage crossplatform access to native widgets
Slashdot Mirror
did each haird have it's own AI and fighting style?
[i]Often proof-of-concept programs are helpful, but all too often management sees a demo that appears 80% feature complete and thinks the project is almost done. It leads to unrealistic expectations.[/i]
Nobody would look at at architects model of a bridge and say "that looks good, go toss it in the river and we'll use it", but we seem to do it all the time in software
Sheesh, with X you can cut and paste between machines
Well...it stays current... :)
In which case are we better of trying to stop something we can't? Or trying to learn how to live through it?
>I personally believe that global warming exists however I still don't know how much humans are involved in the process.
Well if it is cyclical and natural hten we may or may not be contributing to it and, more crucially, we may or may not be able to do anything about itto *stop* it, in which case we're better of putting our money into finding a way to live through it rather than futilely fighting somehting beyond out power
I think Wine and Bristol both do that.
...take a decade off and come back refreshed
>Xerox Park.
That's PARC, for Palo Alto Research Center
>Cincom Smalltalk, which is the descendant of VisualWorks, still uses MVC. Dolphin
Sort of. It uses a secondary layer on top, "VisualWorks", the manages the interations between the models and the controllers and views. Then the UIBuilder builds to this structure. It makes it a lot easier to use. Technicaly it's down there but you don't have to worry about it much
MVP is a pretty good improvement over MVC
It's been awhile since I used VisualAge and they use something else, with a Bridge pattern thrown in the middle to manage crossplatform access to native widgets