On Wednesday, 2013-06-05, Jan Kundrát wrote: > On Wednesday, 5 June 2013 17:19:08 CEST, Thomas Lübking wrote:
> > For integration into kontakt you'll (likely) have to write a > > part plugin what (likely) means that trojitas functionality has > > to exist in a library and either be loaded from the part or the > > binary. > > Just converting the src/Gui/ to be a shared library (with a volatile > interface without any guarantess, of course) shall be doable, right? You'll basically needs a second build target. If it compiles the sources again or links to them in the form of a shared library doesn't matter, whatever you prefer :) > > Anyway, this (afaik) requires the mainwindow to derive from > > KParts::MainWindow, thus will probably not be doable w/o a > > compile time branch. (I would not konsider myself a huge kparts > > expert - quite ununixish concept ;-) > > What about a stub widget which is "set up" by KParts, but then simply > embeds the actual Trojita's main window? More like the central widget than the main window, the main window is provided by the Part shell, Kontact. A good example is KAddressBook, which has both a KPart for Kontact integration as well a stand-alone main window application version. Both use the same MainWidget class for the actual content. > > Have you already contacted kde-...@kde.org on this topic and to > > explore requirements and possibilities? > > FYI, Kevin Krammer (who reads us in Cc) promised to act as a backup mentor. > > Kevin, what is your idea on how to collaborate best? I'd suggest joining > this ML (via trojita+subscr...@lists.flaska.net) Subscribed. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
