Current Status?

Hi everyone,

I know it’s been a while since we’ve used the list for communication,
but I wanted to get a feel for the current status. I think we’d all
like to get a 0.2 release out pretty soon, even if it doesn’t make
the next release of your favorite distribution.

So a few quick questions:

  • Marcus: I noticed a “ribbon” engine. Is this general purpose yet?

  • Benoit: For the OB bug, should we set the LC_NUMERIC as a workaround?

  • Donald: The Mac package is great, perhaps we should set a release
    target date?

  • Me: Try to get some Mac code to fix close/quit bugs.

Just trying to jump-start discussion again…

Cheers,
-Geoff

On Tuesday 04 September 2007 03:50:41 Geoffrey Hutchison wrote:

  • Benoit: For the OB bug, should we set the LC_NUMERIC as a workaround?

I investigated that today, and it turns out, Qt already does that for us. In
QCoreApplication, there is the following code:

void QCoreApplication::init()
{
Q_D(QCoreApplication);

#ifdef Q_OS_UNIX
setlocale(LC_ALL, “”); // use correct char set mapping
setlocale(LC_NUMERIC, “C”); // make sprintf()/scanf() work
#endif

This explains why avogadro works no matter what the LC_NUMERIC is. Doing
LC_NUMERIC="" ./avogadro
works. The same thing with Kalzium failed, until I committed a fix there. The
probable reason why Kalzium failed, is that some KDE class overrid the
behavior of QCoreApplication to set the locale according to KDE settings, and
the KDE settings in my KDE4 environment had LC_NUMERIC="".

The above code snippet is also interesting in that it shows that Trolltech has
decided that this fix is only needed for Unix platforms. Initially I was
worried about the portability of setlocale(), but this shows that we don’t
even need it on other platforms.

Cheers,
Benoit

On Tuesday 04 September 2007 02:50:41 Geoffrey Hutchison wrote:

Hi everyone,

I know it’s been a while since we’ve used the list for communication,
but I wanted to get a feel for the current status. I think we’d all
like to get a 0.2 release out pretty soon, even if it doesn’t make
the next release of your favorite distribution.

I agree it would be good to get a release out. I will see if I can finish off
some of the painter API improvements too, they won’t really change anything -
just the way it is done through the generalised API rather than using OpenGL
directly.

So a few quick questions:

  • Marcus: I noticed a “ribbon” engine. Is this general purpose yet?

No - if we do a release it should probably be removed for the release. I was
hoping I would get more time to finish it off but there are still a number of
things I need to implement before it will be even vaguely useful :frowning:

  • Benoit: For the OB bug, should we set the LC_NUMERIC as a workaround?

  • Donald: The Mac package is great, perhaps we should set a release
    target date?

  • Me: Try to get some Mac code to fix close/quit bugs.

Just trying to jump-start discussion again…

I have been less available due to my impending viva and the trans-Atlantic
move coming up very soon… I will do what I can to clean up the code ready
for release though.

Can we start to fill in the TODO for v2.0

I don’t have time to do it right now as i just took a sleep aid and i’m
feelig the effects already. Anyways, something in here about what you
want to see and that can be done (ie. is resonable to do). I’ll take a
look through the bug reports as the problem carsten is having with
libX11 and XCB is a BIG problem and i’m afraid it hasn’t been fixed yet.
I’m recompiling as we speak to test it out.


Donaldzzzzzz

(Mon, Sep 03, 2007 at 09:50:41PM -0400) Geoffrey Hutchison geoff.hutchison@gmail.com:

Hi everyone,

I know it’s been a while since we’ve used the list for communication,
but I wanted to get a feel for the current status. I think we’d all
like to get a 0.2 release out pretty soon, even if it doesn’t make
the next release of your favorite distribution.

So a few quick questions:

  • Marcus: I noticed a “ribbon” engine. Is this general purpose yet?

  • Benoit: For the OB bug, should we set the LC_NUMERIC as a workaround?

  • Donald: The Mac package is great, perhaps we should set a release
    target date?

  • Me: Try to get some Mac code to fix close/quit bugs.