headers
Piotr Cychowski | 4 Jul 2008 12:14
Picon
Favicon

String changes

I made a wiki page for translators to collate string changes planned for 
1.5 and done already since branching

>http://www.wesnoth.org/wiki/TextdomainStatus
>Things marked with 'no' have potential to get really fuzzy
>Things marked 'avoid' will most likely change altogether
>'wait for stringfreeze' means I've got absolutely no idea ;)

If anyone plans/knows of something big not listed there already it would 
be good if he made updates as needed. It will save translators some work 
(and keep Ivanovic happy ;) )

----------------------------------------------------
Która z gwiazd ma fajniejszy dekolt? Kto powinien zrezygnować z
mini? Oglądaj, oceniaj, baw się!
Wejdź na http://klik.wp.pl/?adr=http%3A%2F%2Fhityczykity.pl&sid=403
Permalink | Reply | 0 comments |
headers
Nils Kneuper | 6 Jul 2008 11:04
Picon

Release plans for 1.4.x and 1.5.x


Hi everyone!
Just to keep you informed, here are my plans for the next stable and dev releases:

* I plan to release 1.4.4 in about two weeks. At max I will wait for three
weeks. After this I want to have a stable release (if something changed) every
~6 weeks unless some major bugs appear. This is just to keep people supplied
with translation updates.

* I want to slowly get back to the three to four week cycle for dev releases.
That is I plan to roll 1.5.2 out next weekend.

Anyone speaking against this shedule? Some real blockers stopping me from doing
this?

Cheers,
Nils Kneuper aka Ivanovic
Permalink | Reply | 0 comments |
headers
Mark de Wever | 6 Jul 2008 14:28
Picon
Picon
Favicon

Re: [RFC] switching from SDL_TTF to SDL_Pango

On Fri, Jun 20, 2008 at 11:20:12PM +0200, Mark de Wever wrote:
> I want to change my work in progress widget library to use SDL_Pango
> instead of SDL_TTF that way we can test with it and see how it works.
> Any objections against adding SDL_Pango or are there better alternatives
> anybody is aware of?

Since there are no objections I added pango support to autotools in
commit 27775.

"Added the pango dependency. I'm not sure yet what will be the minimum
required version so I used 1.14.8 as shipped with Debian Etch as
minimum.  The library isn't used yet but will be soon. Only added
autotools support.
(Also some minor tab->spaces changes in the changelog.)"

Since SDL_Pango seems rather unmaintained, I will add it to the source
tree. Maybe later I might want to publish the changes separately but for
now this seems the easiest. Debian and Gentoo (and maybe other distros
as well) already use patched version.

Regards,
Mark de Wever aka Mordante/SkeletonCrew
Permalink | Reply | 1 comment |
headers
Greg Copeland | 7 Jul 2008 16:22
Picon
Favicon

boost::python?

As Wesnoth is already heavily tied to boost for many things, what's the
group's position on use of boost::python? Boost::python is pretty neat
as it makes it pretty easy to expose both C++ to python and python to C
++.

http://www.boost.org/doc/libs/1_35_0/libs/python/doc/index.html
Permalink | Reply | 1 comment |
headers
dave | 7 Jul 2008 17:41

Re: boost::python?

I think we'd be fine with using boost::python...

Quoting Greg Copeland <gtcopeland <at> earthlink.net>:

> As Wesnoth is already heavily tied to boost for many things, what's the
> group's position on use of boost::python? Boost::python is pretty neat
> as it makes it pretty easy to expose both C++ to python and python to C
> ++.
>
> http://www.boost.org/doc/libs/1_35_0/libs/python/doc/index.html
>
>
>
> _______________________________________________
> Wesnoth-dev mailing list
> Wesnoth-dev <at> gna.org
> https://mail.gna.org/listinfo/wesnoth-dev
>
Permalink | Reply | 0 comments |
headers
Mark de Wever | 10 Jul 2008 20:56
Picon
Picon
Favicon

Re: [RFC] switching from SDL_TTF to SDL_Pango

On Sun, Jul 06, 2008 at 02:28:58PM +0200, Mark de Wever wrote:
> On Fri, Jun 20, 2008 at 11:20:12PM +0200, Mark de Wever wrote:
> Since SDL_Pango seems rather unmaintained, I will add it to the source
> tree. Maybe later I might want to publish the changes separately but for
> now this seems the easiest. Debian and Gentoo (and maybe other distros
> as well) already use patched version.

After some experimenting with SDL_Pango it really seems to be too old
and unmaintained. Also in order to use it nicely I have to write a C++
library around the C library, so I decided to rewrite it in C++ from
scratch. After some testing the cairo backend seems to be the nicest so
I'm now using that backend. I added autotools support and loonycyborg
added scons support (commented out at the moment). It would be nice if
somebody can add cmake support. I intend to commit my initial library
code soon so it can be shipped with 1.5.2. Then we can see how much
trouble the new library gives to the packagers.

Regards,
Mark de Wever aka Mordante/SkeletonCrew
Permalink | Reply | 0 comments |
headers
Bruno Wolff III | 10 Jul 2008 23:14
Picon

OLPC sound samples

I saw an LWN article (http://lwn.net/Articles/287526/) that said that OLPC
has released a large number of sound samples. Perhaps this was discussed
in the forums, but in case not I figured I'd metion it here.
Permalink | Reply | 0 comments |
headers
Nils Kneuper | 19 Jul 2008 16:31
Picon

Release of 1.4.4


Hi everybody!
Just to keep you informed and make you commit any fixes you have left:

I plan to release 1.4.4 early next week. That is probably either Tuesday or
Wednesday. If you have anything that I should wait for, please ping me either
via mail or in irc. If there is anything beside translation updates to mention
in the announcement, please tell me.

Cheers,
Nils Kneuper aka Ivanovic
Permalink | Reply | 0 comments |
headers
Greg Copeland | 24 Jul 2008 16:06
Picon
Favicon

Wesnoth Packagers

If you are a Wesnoth packager for the 1.5.x series, I'm asking you to
please consider packaging Python 2.5.x, versus 2.4.x, in your next
build. This is NOT a requirement and is only a request.

The benefits of migrating to Python 2.5 (2.5.2 as of this writing) are
simple. Python 2.5 has both new language features and new optimizations.
Given that AIs tend to be CPU bound, performance boosts are certainly
appreciated. Beyond the performance gains, I am creating a new, higher
level module called Wesnoth AI Library, or wail for short, which sits on
top of the existing wesnoth module. This module makes use of new 2.5
language features.

In the event Python 2.5 is not packaged, existing AIs will continue to
run and compatibility is ensured. As I said before, this is not a
requirement. However, newer AIs which make use of the wail module, once
released, will not be compatible with any package built against Python
2.4. As such, it is to the advantage of the Wesnoth Python AI community
to include Python 2.5 where possible.

Thus far the developers and packagers I've spoken with have been very
receptive. Thanks to everyone for their support in this initiative. If
you have questions, comments, or concerns, please feel free to email me
or the list.

Cheers,

Greg
Oracle
BlindOracle
(Continue reading)

Permalink | Reply | 2 comments |
headers
Nicolas Grunbaum | 24 Jul 2008 22:33
Favicon

Profiling

I have been profiling Wesnoth with Shark and Instruments on OS 10.5,  
the results which still need a bit of mining and statistical analysis  
show that Wesnoth spends a majority of its time ( ~ 85% ) in the  
graphics and audio routines, a large amount of time blocking in the  
main loop ( between ~3% and ~7% ), and lastly about ( ~ 3% ) combined  
allocating std::string, copying std::strings and comparing  
std::strings in maps. Most other operations weigh in under 0.1%. These  
numbers, as I said need refining, and as I only have had time for a  
sample size of three runs ( they take quite some time ) they may change.

Before I do anymore runs, do these numbers line up roughly with  
expectations and previous analysis?

Is there a better testing scenario?

.-   .--
Permalink | Reply | 8 comments |

Gmane