Moved the edit_infos stuff from CKDevelop to DocViewMan

[Falk Brettschneider]

Falk Brettschneider wrote:

> Might as well just add an currentViewUndo() to m_docViewManager and then

> > connect appropriately. Then all these forwarding methods just disappear from
> > ckdevelop and you don't have to expose the internal widget (kwritedoc?) to
> > the outside.
> Hmm...hmm...the DocViewMan was actually thought as helper class for
> CKDevelop, as MDI manager so to speak.
> Now you propose to move functionality of the application framework to
> that class - I'm not that happy with it, this is more than DocViewMan
> should be. My feeling is DocViewMan has the task to compute the current
> views and documents but not much more. Slots connected to Mainframe
> window actions should belong to the framework class.

Maybe we can create an EditorManager which is owned by CKDevelop, uses the DocViewMan and where we can move
the CEditWidget-concerned slots of CKDevelop to. This may easy that huge CKDevelop class. What do you think?

Ciao,
F at lk



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«