kate part

[Roland Krause]

Sandy,
I like the idea. We can either rewrite the existing kwrite-part to
adhere to the KTextEditor interface or use Kate as the implementation.
I will look into the option to use kate then. 

The existing kwrite-part could be consolidated and made to implement
the KTextEditor interface also, but I think if someone wanted to to
that the person should base upon the KDevelop-2 branch version because
there were quite a few bugfixes that didnt make it into the gideon
branch. 

About 2): I dont think we need to use QDickWidget, lets also use
QExtMDI for that. 

About 3): we need a somewhat generic view manager for that, could
implement that as a part to get started and then follow Richard's
earier suggestion on having two interfaces to choose from. 

Roland


 
--- Sandy Meier <smeier at kdevelop.org> wrote:
 
> 1) droping the KEditor interface in Gideon (as suggested by Matthias)
> and 
> using KTextEditor::Document (and the subinterfaces) and
> KTextEditor::View 
> from the kdelibs.The nedit plugin and the simple editor (for testing)
> need a 
> new implementation, but I think this isn't on the top of the priority
> list.
> 
> 2) using QDockWindow for docking the treeview and outputview area
> (docking 
> support is already available in QMainWindow so this shoudn't be a
> problem)
> 
> 3) using QExtMDI for the document/view managing
> (editor,docbrowser,custom 
> plugin views). 
> 
> Can we agree on this?
> 
> Ciao!
> Sandy
> 
> _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com