Could CWT be an empty bundle that re-exports underlying bundles:

o.e.n.cwt.animation
o.e.n.cwt.panning
etc

This way the maintenance would be much easier.

Regards,

Wim


On Fri, May 25, 2012 at 9:50 AM, Nicolas Richeton <
[email protected]> wrote:

> Hi Wim, Hallvard,
>
> Code sharing is the idea behind CWT, so it makes sense to move common code
> there.
>
> Animation is already part of it, but Gallery currently has its own copy
> since it does not depend on cwt yet. (actually it comes with a newer
> version, cwt has to be updated).
>
> The only issue on cwt is that we probably need a clear process for
> API/behavior changes since they may affect several widgets. This is yet to
> be done.
>
> On async image provisioning, gallery does not have this since it uses the
> same API as Tree or Table. Image management has to be made by the user.
>
> Regards,
> --
> Nicolas
>
> Le 22 mai 2012 à 10:37, Wim Jongman <[email protected]> a écrit :
>
> This is a good idea. I think the Animation is not part of CWT (Common
> Widget Toolkit) but it was the idea to put it there, AFIAK. Nicholas isn't
> that correct?
>
> Regards
>
> Wim
>
> On Tue, May 22, 2012 at 9:24 AM, Hallvard Trætteberg <[email protected]>wrote:
>
>> Hi,
>>
>> I was considering the structure of GeoMap yesterday and concluded it
>> consisted of three main parts:
>> - canvas tiled with images
>> - async provision/downloading of images
>> - view management including coordinates and zooming levels
>>
>> Only the third of these is really specific for GeoMap. A tiled canvas
>> with panning and zooming is useful for many applications, particularly
>> grid-based games like sokoban. Async provision/downloading of images is
>> useful to improve performance. (I can imaging the gallery widget needs/has
>> something similar).
>>
>> Does it make sense to factor out generic code? Does the Nebula project
>> consider cross-component refactoring and code sharing?
>>
>> Hallvard
>> ______________________________**_________________
>> nebula-dev mailing list
>> [email protected]
>> https://dev.eclipse.org/**mailman/listinfo/nebula-dev<https://dev.eclipse.org/mailman/listinfo/nebula-dev>
>>
>
> _______________________________________________
> nebula-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
> _______________________________________________
> nebula-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
>
>
_______________________________________________
nebula-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Reply via email to