UI-less kdevplatform

[Aleix]

Ok, so what you think about that patch now?

I think it is much more simpler and similar to what you were asking for
before.

I've tested and it is working for me (a bit slower maybe, but not really
important since the most of the time is spent while parsing)

Thanks,
Aleix

PS: still with ::addProject()

On Sun, Aug 10, 2008 at 5:17 PM, Alexander Dymo <alexander.dymo at gmail.com>wrote:

> On Sun, Aug 10, 2008 at 11:49 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 10.08.08 01:44:34, Aleix wrote:
> > Uhm, didn't we just agree that it would be sufficient to just not create
> > the mainwindow and at try to not load any projects that are not using
> > defaultMainWindow()?
> I still think we need to use the same controller but do not try to
> have "ui/uiless" state distinction, even in the plugins. After all,
> the plugin usually has UI functionality called from either toolviews
> or menu items or config pages. And if we don't create a window,
> there's a 99% chance that plugin will never try to do something
> ui-wise. So it should be safe to assume that it's ok to load all
> plugins.
>
> > So the part about creating Core without ui is ok from me, but the new
> > controller still seems to be a bit too much as we can easily do it with
> > the existing controller.
> I second that.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20080815/6ba20299/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uiless3_kdevplatform.patch
Type: text/x-patch
Size: 5311 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20080815/6ba20299/attachment.patch>