S
Silvio
On 03/29/2011 12:06 PM, Alessio Stalla wrote:
[snip]
I could not disagree more. There is no "one ultimate OO way" of doing
things. Nor is it clear cut whether any program fragment is "OO" or not.
Neither does OO mean you have to have an object model that is separate
from the UI (or any other part of the system). Why would coupling an
object model to the UI be any worse than coupling it to the database? In
most cases I would strive to decouple it from both.
OO is a programming methodology, just like functional programming and
even procedural programming. Neither methodology prescribes a single
solution for any problem.
And I am not using Java (which I consider only a weakly Object Oriented
language). I program in Scala but I am using the JVM and my share of
Java libraries.
[snip]
If you skip the domain model part, and pretend the GUI is the model of
your application, then you're simply not doing Object-Oriented
Programming. That is not a crime, mind you, but then I don't
understand why you're using Java in the first place.
Alessio
I could not disagree more. There is no "one ultimate OO way" of doing
things. Nor is it clear cut whether any program fragment is "OO" or not.
Neither does OO mean you have to have an object model that is separate
from the UI (or any other part of the system). Why would coupling an
object model to the UI be any worse than coupling it to the database? In
most cases I would strive to decouple it from both.
OO is a programming methodology, just like functional programming and
even procedural programming. Neither methodology prescribes a single
solution for any problem.
And I am not using Java (which I consider only a weakly Object Oriented
language). I program in Scala but I am using the JVM and my share of
Java libraries.