[Amelia-development] Weekend Progress

[Karol K. <kk...@gm...>]

Hi Joao,

Just an update on what I did over the weekend on AMELIA.

1) I've noticed that you've added two new UI's to AMELIA, both
displaying a webpage. I've been thinking about doing that too, but
I've run into some problems while doing that, but I've managed to fix
them over the weekend. The first problem was that AMELIA crashed when
I've added a QWebView with http://amelia.sf.net . This was due to the
JPEG files embedded in the webpage. Since irrlicht becomes linked with
it's own version of LibJPEG, the symbols from it conflict with the
ones from the system's LibJPEG, which is used by Qt. The solution is
to remove LibJPEG from irrlicht and set it to link against the system
libs. How to do it is outline here:
http://irrlicht.sourceforge.net/phpBB2/viewtopic.php?t=30734

The second problem was that the web page was not loaded when we take
the screenshot for the ABase menu. I've had to come up with some
system to add conditions to update the screenshots on specific
signals. What you can now do is add hooks for specific signals to
ABase, and if one is called, it updates the pixmap. Pretty cool, eh?
For QWebView I hook the loadProgress() signal, which gets called when
another part is loaded. Thus we see the webpage loading in the menu...

Initially, taking a screenshot of a widget with QPixmap::grabWidget()
kept graying out the main window from time to time. This was solved by
making sure of the widget that we are taking a screenshot is not in
the QLayout when it is hidden. I dunno why this was, but I'm guessing
that painting a hidden widget to a pixmap disabled the painting for
any of it's parents that are layed out and yeah....

2) I've just comited a small change to the event manager, which makes
it store user generated data about events (ei: tags, date last
anaylized) in a separate file from the metadata file. This is
something we've discussed some time ago on Skype, but I did not have
time to do it. Anyways, the tags and other cool stuff is now stored in
a .logbook file.

3) I've found 3 things that are broken in the tour player. Two of
which ("actions" are not run and the tour keeps looking) I believe are
due to the fact that I removed the QIrrWidget::repainted() signal
which called a function in the ATourManager that updated the actions
and stopped the tour at the end. I will replace this function with a
timer for now, but in the future I want to use a QTimeLine, because it
allows us to do much cooler stuff. (Actually, I already have tours
"working" with a QTimeLine, and it was very easy for me to run the
camera animators forward OR backward or speed the whole thing up. Cool
stuff ;) However I'm not 100% sure that I understand how the structure
of the tours works (ei: what is the importance of blocks?), so I would
like to talk to you on Skype before I commit anything. However that
should wait until after release. ) Anyways, I'm going to see if I can
fix the tours tonight.

4) I saw this in the morning:
http://labs.trolltech.com/blogs/2008/11/03/parallax-sliding and I
though it would be quite cool to use something similar in the initial
menu.

Cheers,
Karol Krizka

PS: Would it be possible to schedule a Skype meeting for Friday or
Wednesday afternoon?