I think that would be nice. Using the yzis kpart in kate is somehow not 
different from using it inside KDevelop or Quanta.

If we start to work together closely, we should also take the 
opportunity to make the syntax highlighting engine of kate reusable, so 
that we do not have to merge it manually in yzis.

Mickael, what would be required to make the syntax highlighting code of 
kate reusable, as opposed to the current solution ?

	Philippe

Christoph Cullmann wrote:
> Hi,
> I understand that kate part and yzis part target different userbases, but I guess we could cooperate at
> the KDE app level ;=) Just looking at the Kate port to KDE 4, and Kate really does only need some methodes in addition to
> KTextEditor Interface from the part to use it. I think it should be no problem to come up with 1-2 texteditor interfaces which cover
> them and than nothing would harm Kate to switch from Kate::Document/View to KTextEditor::Document/View without loosing any
> functionality. Is there interest in merging the efforts of Kyzis and Kate development? I think the Kate GUI still provides lots of more
> stuff than Kyzis, not to mention better mdi, splitting and more, and given we switch over to KTextEditor, Kate could provide a
> unique GUI to the both kde texteditor parts, which than could join forces and not building 2 guis in parallel.
> it's like the current efforts to merge quanta and kdevelop together under a common framework, Kate could provide such a framework
> for our texteditor parts, for users not interested in complete IDE environments ;)
> 
> this is just a idea, if no interest on both side, hey, we let it like it is ;)
> 
> cu
> Christoph
> 
> cu
> Christoph
> 

Send instant messages to your online friends http://asia.messenger.yahoo.com 
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel