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)

Has the number of abstract interactions grown in recent years? I dread the day Sun will stop producing it's keyboards. It has the following keys on the left: Stop, Again, Props, Undo, Front, Copy, OPen, Paste, Find, Cut. Are there really that many more abstract actions? REST does with 4 :-) I work with debuggers and they have very little use for abstract actions but I spend a _lot_ of time with MVC details. DCI doesn't solve any of the problems I have to deal with. I think that is because DCI deals with the C->M interaction while I'm more concerned with M->V interactions. See my mini-variations of MVC in IZ 172694.

-- ivan soleimanipour 09:24, 24 September 2009 (CEST)

You are right that my presentation about Actions and DCI deals more with C->M than M->V. I am not sure if this this can be said about the DCI itself, maybe I am misinterpreting it slightly. As the amount of interactions goes: it is increasing in two directions. First of all we have general actions oriented contexts like compile, execute, save with various data being morphed into them. Then there are data oriented contexts like DBTable, DBColumn with various actions recognizing them and providing unlimited number of operations on them.

--JaroslavTulach 20:17, 24 September 2009 (UTC)

Is in DCI still a need for dependency injection?

--Andreas St. 11:25, 25 September 2009 (CEST)

My take on DCI and the NetBeans Platform:

http://www.antonioshome.net/kitchen/nbdci/

--Antonio 12:30, 1 October 2009 (CEST)

Nice documentation Antonio. For comments:

1. Don't stress that methodless roles need to be Java interfaces. For example methodless role to control palette is a Java class. The real difference between methodless roles and methodful roles is that methodless roles don't have any connection to data. Whether it is class or Java interface does not matter.
2. interaction deal and know only about methodless roles. This is written, but the interaction element is missing in your pictures.

--JaroslavTulach 15:02, 1 October 2009 (UTC)

nice, i came here from hackernews

--rofrol 22:16, 29 November 2009 (CET)