Re: [ANNOUNCE] libchamplain 0.6

---------- Forwarded message ----------
From: Jiří Techet <techet gmail com>
Date: Tue, May 25, 2010 at 21:25
Subject: Re: [ANNOUNCE] libchamplain 0.6
To: Tomaž Vajngerl <quikee gmail com>

On Tue, May 25, 2010 at 18:42, Tomaž Vajngerl <quikee gmail com> wrote:
> Hi,
> I have ported Vala bindigns from latest 0.4 to 0.6. Because I am
> unsure in what way you prefer that we send you the patches I will send
> it here. Please include it in the next 0.6 branch release. I will
> prepare patches also for 0.7 development but I would like to
> experiment first how to make automatic bindings building.

Thanks, will have a look at your patches.

Regarding submitting patches, it's best to create your own branch of
libchamplain at gitorious

and request a merge. The mailing list has a 40KB limit for attachments
and your patch was over this limit so I received some warnings.

The trunk is currently identical to the 0.6 branch so I'll apply it
there as well. I think for bindings it's not worth investing much time
to 0.7 until the API is frozen.



> regards, Tomaž
> On Tue, May 25, 2010 at 1:46 AM, Jiří Techet <techet gmail com> wrote:
>> Hello everyone,
>> libchamplain 0.6 is out. There hasn't been much exciting since 0.5.2;
>> here's a brief list of changes:
>> * Add dummy ChangeLog file (Łukasz Jernaś)
>> * Fix a problem on some machines when tiles are being destroyed (Jiří Techet)
>> * Add minimal demos (Jiří Techet)
>> * Some other minor fixes (Jiří Techet)
>> For more details refer to git log.
>> This is probably the right place to point out several
>> incompatibilities with the 0.4 branch. There have been many changes in
>> the API so it's possible you encounter some errors while compiling
>> your program, but these should be easy to fix. However, there are two
>> gotchas if you are upgrading from the previous stable release mainly
>> because your sources will compile just fine, but when running it,
>> unexpected things happen:
>> 1. ChamplainMapSource and ChamplainPolygon inherit from
>> GInitiallyUnowned now and g_object_ref_sink() is called on them. The
>> practical consequence is that you MUST NOT call g_object_unref() once
>> you insert them to ChamplainView, otherwise your application will
>> crash. libchamplain takes ownership of them so you don't have to care
>> about their deallocation any more.
>> 2. If you want to create a cached map source, call
>> champlain_map_source_factory_create_cached_source() instead of
>> champlain_map_source_factory_create(). The latter function will just
>> create the bare map source without any caching. So if it seems to you
>> the tiles don't get cached, this is probably the cause.
>> We're late with this release but I'll do my best to follow the gnome
>> schedule for the following release. In a few days I'll send a few
>> ideas what I'd like to have implemented for 0.8.
>> Cheers,
>> Jiri
>> _______________________________________________
>> libchamplain-list mailing list
>> libchamplain-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]