[Digikam-devel] OpenGL support?

[Andi Clemens]

The question is do we really need those side bars in the lighttable? If I open 
both of them, I can't even see my images with a 1024x768 resolution anymore. 
The sidebars are wasting too much space.
Second question: If the sidebars are really necessary, can't we use the marble 
widgets from the main window somehow?
They should already be initialized. So when switching windows (main window, 
light table) the instances of the marble widgets are refreshed by the current 
view and current selected image.
Or wouldn't it be even possible to initialize the light table on startup (and 
the two other marble widgets), so that using it for the first time will start 
it faster?
The light table window is kept when used once, so we could also initialize it 
anyway when digiKam is starting up?

Andi

On Saturday 26 July 2008 16:43:51 Marcel Wiesweg wrote:
> > Hi,
> >
> > somehow Marble is broken, always pushing ASSERT messages to the console,
> > so I'm not able to start digiKam 0.10 anymore. So I started ccmake and
> > disabled the marble support and also openGL, because my laptop is not
> > working with 3D acceleration.
> > Now I noticed that the light table starts 5 times faster (before it took
> > nearly 5 seconds, now it starts in less than 1 second). I guess this has
> > nothing to do with marble so the only option left is the openGL support.
>
> I think at the bottom of the thread there is a conclusion that Marble is
> the culprit here. The lighttable has two sidebars, and each sidebar hosts a
> Marble widget. You cannot test, but when I start digikam (currently with an
> old version of Marble) I can see by debug statements that initializing
> Marble takes considerable time (a few secs). I expect initialization time
> for Marble, that's ok. There are two fields how we / the Marble team can
> work on this:
> - Find out if we can delay the initialization of Marble until the relevant
> sidebar is opened by the user. This can depend on Marble moving
> initialization tasks to a thread
> - Find out if Marble is optimized for using more than one widget instance
> in an application (we easily use several), or if perhaps more data sharing
> is possible
>
> Of course, all this is work secondary to having a stable and maintained
> Marble.
>
> Marcel
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel