On Jun 18, 2008, at 12:57 PM, Brian Goetz wrote:
I think that's Java-think talking; we're used to the way you have to
do it in Java. Binding makes 90% of the MVC code just go away,
which means that your model and view classes are much simpler, and
putting them together is often more natural.
I don't think that's right.
Having all your classes in the same file is a convenience for trivial
apps.
But supporting separation of concerns is required (and of hiding
implementation details)
Proper support for separating code into multiple source files and
multiple directories (packages) is required, for larger scale
applications and for code that's developed independently or
collaboratively by multiple developers. In my opinion the java package
scope is inconvenient as it forces grouping by access control (usually
implementation detail) rather than allowing logical grouping. In
addition, there's a desire to have platform specific profiles for the
javafx script runtime libs, which involves re-grouping subsets and
supersets of classes and packages by "profile", which we should take
into consideration.
Chris
15 messages in net.java.dev.openjfx-compiler.devRe: accessibility proposal
