If you hadn't noticed

Geoff and gang,

I did some bug fixing. We keep moving foward. The biggest issues on
the list are now two big bugs, the Ctrl-C when in messages and then
optimization. Othere than that I think we should go ahead and make a
release, decide what engines / tools / extensions will go and then just
release 0.2.0 then start working on new features. Once those bugs get
fixed i’ll make a fork. Actually i guess I can make it now.

You have the mac package done right? I have yet to make the Windows
package for the newest stuff so that still needs to be done :frowning:

Will get on it ASAP.


Donald

Am Montag, 17. September 2007 08:13:34 schrieb Donald Ephraim Curtis:

The biggest issues on
the list are now two big bugs, the Ctrl-C when in messages and then
optimization.

There is one issue which is very important: Translation. I will try to add
i18n support today. I showed Avo to a friend (also a chemistry teacher) and
he was very impressed. He said he could easily imagine using Avo in school
and for homework (as it is free and ligthweight).

BUT only if the GUI is available in german. I hope i18n-support is easy to do
in Qt 4, but I am sure it is.

Carsten

On Monday 17 September 2007 08:13:34 Donald Ephraim Curtis wrote:

I did some bug fixing.

I noticed, and was impressed :slight_smile:

optimization.

This is what worries me the most – that current svn has framerates much lower
than back in may-june. Probably at this point, either some of us has a
precise idea of what changes brought slowdowns (painter abstraction?
threading?) or we need to resort to using a profiler (which would be useful
anyway).

Anyway, I don’t really hope this to be easily fixed, so it might be a good
idea to release 0.2 before.

I admit that I’m not really entitled to talk about problems as I don’t
currently have the time to contribute to fixing them.

Cheers,
Benoit

Am Montag, 17. September 2007 08:19:13 schrieb Carsten Niehaus:

Am Montag, 17. September 2007 08:13:34 schrieb Donald Ephraim Curtis:

The biggest issues on
the list are now two big bugs, the Ctrl-C when in messages and then
optimization.

There is one issue which is very important: Translation. I will try to add
i18n support today.

BUT only if the GUI is available in german. I hope i18n-support is easy to
do in Qt 4, but I am sure it is.

It if, if you have .pro files which we don’t… Ok, I found out that QGis is
also using cmake. They wrote a shellscript which generates
temporary .profiles which are then used to generate .ts-files (we want .ts
files).

http://wiki.qgis.org/qgiswiki/TranslatorsCorner

Later today, I will try to figure out if that concept works for us as well.

Carsten

Am Montag, 17. September 2007 15:26:32 schrieb Carsten Niehaus:

Am Montag, 17. September 2007 08:19:13 schrieb Carsten Niehaus:

Am Montag, 17. September 2007 08:13:34 schrieb Donald Ephraim Curtis:

The biggest issues on
the list are now two big bugs, the Ctrl-C when in messages and then
optimization.

There is one issue which is very important: Translation. I will try to
add i18n support today.

BUT only if the GUI is available in german. I hope i18n-support is easy
to do in Qt 4, but I am sure it is.

It if, if you have .pro files which we don’t… Ok, I found out that QGis
is also using cmake. They wrote a shellscript which generates
temporary .profiles which are then used to generate .ts-files (we want .ts
files).

http://wiki.qgis.org/qgiswiki/TranslatorsCorner

Later today, I will try to figure out if that concept works for us as well.

It does but there is an issue in our code:

/home/carsten/svn/avogadro/trunk/avogadro/src/elementcombobox.cpp:29:
Unbalanced braces in C++ code (or abuse of the C++ preprocessor)

That lines is simply

namespace Avogadro {

No clue why this breaks lupdate…

Carsten

Hey Carsten duder,

Check out the translation stuff i did.

(Mon, Sep 17, 2007 at 05:42:17PM +0200) Carsten Niehaus cniehaus@gmx.de:

Am Montag, 17. September 2007 15:26:32 schrieb Carsten Niehaus:

Am Montag, 17. September 2007 08:19:13 schrieb Carsten Niehaus:

Am Montag, 17. September 2007 08:13:34 schrieb Donald Ephraim Curtis:

The biggest issues on
the list are now two big bugs, the Ctrl-C when in messages and then
optimization.

There is one issue which is very important: Translation. I will try to
add i18n support today.

BUT only if the GUI is available in german. I hope i18n-support is easy
to do in Qt 4, but I am sure it is.

It if, if you have .pro files which we don’t… Ok, I found out that QGis
is also using cmake. They wrote a shellscript which generates
temporary .profiles which are then used to generate .ts-files (we want .ts
files).

http://wiki.qgis.org/qgiswiki/TranslatorsCorner

Later today, I will try to figure out if that concept works for us as well.

It does but there is an issue in our code:

/home/carsten/svn/avogadro/trunk/avogadro/src/elementcombobox.cpp:29:
Unbalanced braces in C++ code (or abuse of the C++ preprocessor)

That lines is simply

namespace Avogadro {

No clue why this breaks lupdate…

Carsten


This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Am Montag, 17. September 2007 20:03:07 schrieben Sie:

Hey Carsten duder,

Check out the translation stuff i did.

Moin moin folks…

I just fixed i18n for Avogadro, it works.

BUT: I need to install the files somewhere. Currently it only works if the .qm
files (generated my ‘lrelease’) are in /home/kde4/kde/ which is not exactly
perfect…

Ok, so where shall I put the files?

Carsten

On Sep 18, 2007, at 9:53 AM, Carsten Niehaus wrote:

BUT: I need to install the files somewhere. Currently it only works
if the .qm
files (generated my ‘lrelease’) are in /home/kde4/kde/ which is not
exactly
perfect…

That’s really strange. Isn’t there some standardized location like /
usr/share or /usr/local/share?

Surely the KDE project and/or Open SUSE lists must have some ideas
about these paths. Let’s make sure it’s the right place first.

Thanks,
-Geoff