Talk:DCI

In the MVC that I know controls are strongly associated with the view. I po that NB's need for context arises from having global tool/menubars ... a rut we're stuck in from the days of weak HW and weak OSes (Mac, Win3.1) Machines with better capability naturally evolved to a multi-window multi-control style. In the early days of NB it became clear that If you have focus-follows-mouse you cannot establish context and cannot have SDI. I believe that keeping controls "in" the view establishes context by visual proximity and visual proximity is an excellent way of establishing context.

--ivan soleimanipour 00:29, 23 September 2009 (CEST)

SDI vs. MDI is not really important for having one global menu and toolbar bar (e.g. a single interactions). NetBeans used to have SDI (only or by default) till ~2003. Still there was just one menu and toolbar. So your nostalgia for focus-follows-mouse cannot be used to decide the MVC vs. DCI evolution fight. The modular applications just naturally lead to definition of more abstract interactions. Actions in NetBeans are natural, easy to spot example.

--JaroslavTulach 06:57, 23 September 2009 (UTC)

Very good video! Please bring us some more ;) I like the intro - on why MVC is not part of the future...

--Ido Green 01:00, 23 September 2009 (CEST)

It is not that easy to find such generally interesting topic. But we will try.

--JaroslavTulach 06:57, 23 September 2009 (UTC)

Thanks for this article and presentation. The DCI pattern definitely make sense for me, as a large modular application architect.

The article can also be completed by http://folk.uio.no/trygver/2008/commonsense.pdf

--Mathieu Bastian 15:10, 23 September 2009 (CEST)