[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: KTextEditor Plugins
From:       Christoph Cullmann <cullmann () absint ! com>
Date:       2013-12-22 20:52:51
Message-ID: 665314330.658376.1387745571593.JavaMail.root () absint ! com
[Download RAW message or body]

> > On Sunday 22 December 2013 16:46:31 Michal Humpula wrote:
> > At least the multi-screen thing is what comes up from time to time for
> > kdevelop, as a feature request.
> Yeah,
> 
> thats the question, how it is used and how often.
> 
> my 2 cents. everything below is my personal practice and opinion ;)
Thanks for the feedback, that is very valuable!

> --
> 
> I don't use multiple windows cuz its usefulness to me close to zero. I have a
> lot of kate sessions for all my projects. Sometimes, if project is a big
> enough, I can have few sessions for one single project w/ different plugins
> and settings in it. Sessions used to hold a preopened files as well. For
> example for kate development I've got 4 sessions:
> * generic (for C++ development or source code investigation)
> * python plugins
> * js plugins
> * syntax files
> (and one more I've made recently for `pate` plugin development, cuz it have
> some special settings for my C++ plugin differ from a generic one)
> 
> I don't need other main window for same session: quick switch is quite enough
> to me. If I need another kate window it is always some other session w/ a
> bunch of files in it...
Yeah, and Joseph brought up, that we need some more clever handling to avoid having \
sessions opened in multiple Kate instances, to avoid random data-loss, perhaps the \
Kate applications should sync themself via DBus.

> 
> so personally I +1 for remove main windows from kate cuz they are too complex
> to handle them properly in plugins...
Yeah, I think that, too.

> 
> but, I agreed w/ Sven, we should not remove KTE plugins... despite it is 4 of
> them ever exists for last decade...
> and yes, it would be harder to develop some new (and bring more dependencies
> to kate) optional functionality...
> so I fully agreed w/ Sven: plz do not remove them!
I would then really like to have some more generalized "application plugins" \
interfaces, that allow to have shared Kate / KDevelop plugins (and perhaps other apps \
can follow, if the interface is lightweight).

I would propose some shrinked kate application interface for that, given we would \
drop multi-mainwindow support, it should be fairly small and easy.

Greetings
Christoph

-- 
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH      Email: cullmann@AbsInt.com
Science Park 1                         Tel:   +49-681-38360-22
66123 Saarbrücken                      Fax:   +49-681-38360-20
GERMANY                                WWW:   http://www.AbsInt.com
--------------------------------------------------------------------
Geschäftsführung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


[prev in list] [next in list] [prev in thread] [next in thread]