'Obsolete' may be overstating the case. But not by that much. After
all, MVC dates back to Smalltalk days! You would HOPE that someone
would have come up with a better design pattern by now.
But what in fact happened was different. Two big things happened: 1)
since everyone knew MVC was
Yours is a very good point, but it leaves unanswered the crucial
question: when IS it advantageous to use the declarative approach
instead? I am not convinced that Google's choice of which declarations
to offer makes this decision straightforward, far less obvious.
On Jan 17, 11:40 am, Bob Kerns
MVC is yet another good concept gone buzzword. The idea of
separation of concerns and modularity is critical to the design of
complex programming systems -- by splitting an application along the
RIGHT boundaries you can vastly reduce its effective complexity,
improve maintainability, and
Fwiw, I don't think there is anything we attempt to describe in Android as
MVC. Any such words being applied to Android are coming from elsewhere. :)
On Wed, Jan 19, 2011 at 7:38 PM, DanH danhi...@ieee.org wrote:
MVC is yet another good concept gone buzzword. The idea of
separation of
doesn't matter how you implement your view. the key is keeping M V and C
separate.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send
Doesn't matter how you implement the view in your MVC.
If you keep the concerns seperate (in MVC), you will get the benifits
regardles of your implementation of the view part.
XML is a little more declarative, but otherwise doesn't matter.
On Jan 13, 7:04 pm, Toby t...@tobiah.org wrote:
Ok,
MVC separation of View and Controller -- Obsolete? That is
something I have never heard of. Could you elucidate? What replaces
it? The separation in MVC exists for very specific benefits. If you
view it as obsolete, you must have a New Idea -- MVC started as a New
Idea, and I like New
Android's XML layouts are built to be easily manipulated from code. For
instance, it is very common for applications to selectively inflate bits of
a View hierarchy by using a LayoutInflater. Other APIs, like ViewStub and
findViewById(), help bridge the gap.
One of the most important reasons why
I think this the XML layout is introduced mostly in order to facilitate GUI
generators, like
http://droiddraw.org/
If they generate Java, which is editable for the developers, switching
between code and modeling becomes rather error-prone.
The good thing is that you are not bound to it, you can
Well, I would not have anything against programmatic layouts per se. Indeed,
I've written a couple of layout managers for custom layouts that the
standard layout managers were not designed for. However, one of them was
driven by an XML configuration file,
--
You received this message because you
On Jan 13, 7:04 pm, Toby t...@tobiah.org wrote:
Ok, we've thought about MVC paradigms for our company,
but unless you really need to hide the code from some
Designer I can't see the benefits.
You must not have created a somewhat deeply nested view hierarchy yet,
nor have you tried to reuse
It is much easier to maintain XML layouts. XML layout is less wordy
than Java, too (amount of text in XML file versus amount of text in
Java file accomplishing the same).
This is especially true if you have different layouts for one
activity, depending on the phone's orientation, screen size,
12 matches
Mail list logo
