michal.humpula at seznam.cz
Sun Dec 22 15:46:31 UTC 2013
On Sunday 22 of December 2013 16:26:41 Sven Brauch wrote:
> On Sunday 22 December 2013 16:19:00 Christoph Cullmann wrote:
> > e.g. the current Kate application interfaces would make a good starting
> > point, guess needs to be just shrinked down.
> Yes, quite possible. We should sit together at the sprint and discuss what
> kinds of things we want to have in the interface and which of those both
> applications can easily provide.
> > Btw., does KDevelop support multiple main windows or is this then again a
> > new process?
> No. We have discussed this before, currently we don't support it at all. I
> think launching a new process it not a solution for KDevelop, because unlike
> kate we keep a large amount of language data in memory, and launching a new
> process would need to duplicate all this data.
Please don't take me too much seriously, but what about doing it with shared
memory (shm, mmap)?
> Additionally, our current
> architecture allows each session (which is bound to a language data
> repository) to be opened only once, because the underlying database system
> does not support concurrent access by multiple processes.
> > I was about thinking to go for Kate to the "each main window is an own
> > process" scheme, too. This would make the interfaces A LOT less complex,
> > as
> > each plugin would have only one view, even the plugin/view split could be
> > removed.
> I'm still not sure I understand this: If you want to keep split view (which
> I would really not remove), plugins always have to deal with multiple views
> anyways. The "two windows" doesn't really introduce any additional
> complexity over split view, or does it?
> KWrite-Devel mailing list
> KWrite-Devel at kde.org
More information about the KDevelop-devel