On Documents an Views
rodda at kde.org
Thu Jun 19 00:03:05 UTC 2008
On Thursday 19 June 2008 08:08:26 Andreas Pakulat wrote:
> I'm working on providing a xmlgui client as widget for the Qt designer
> documents and was wondering when one should create a new Sublime::View
> subclass? I mean what are the possible benefits of that?
As of yesterday, you can now show some status in the status bar if you have a
custom Sublime::View subclass. But you also need it if you want to save some
state when KDevelop saves its areas.
> Other questions coming to my mind:
> - why is there so much code-duplication for the "ask-for-save-on-close"
> code, I see the same code in qtdesignerdocument and TextDocument and
> PartDocument (isn't the latter read-only?) Can't this just move to
I moved it from TextDocument to PartDocument but then realised that the
designer document was not even a PartDocument, and didn't go any further.
Moving to IDocument would be ok if it can access all of the required api.
> - Same goes for the cleanup code at the end of PartDocument::close, this
> should IMHO move to a common base class, so I don't need to do this
> myself in QtDesignerDocument if I use a Sublime::View subclass.
Haven't looked into that.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel