ghost at cs.msu.su
Mon May 5 19:20:54 UTC 2008
On Monday 05 May 2008 22:50:41 Alexander Dymo wrote:
> Vladimir, thanks for the explanation (in this and your other mail). At least
> now I understand much better what areas are and how we want to use them. I
> didn't know that before I started implementing areas.
> The current implementation still bothers me a bit. We have two separate
> concepts - area types and areas which are implemented using the same Area
> class and distinguished by uicontroller as "default" area shown nowhere
> or "clone of the default" shown in the mainwindow. I'd like to try separating
> these two in the code as well into Area and AreaType classes. AreaType would
> be the default area added in the code or by plugins and Area class would be
> the same as it was before - just collection of views shown in the mainwindow.
How those two would be related? The joy of the current model is that visible
areas are indeed just clones of the default areas, and resetting areas to
default is a simple clone. In smart words, this is called "Prototype" pattern.
I'm not sure using two separate classes would keep this simplicity.
What personally bothers me right now is that we have this default/clone model,
but outside of it, you can set any random area to a window, thereby probably
breaking lots of things. I'd suggest making that impossible :-)
More information about the KDevelop-devel