[Psc] Last PSC meeting

[Eric Lemoine]

On Sun, Apr 19, 2009 at 1:33 PM, Andreas Hocevar <ahocevar at opengeo.org> wrote:
> After thinking again, I think I understand the decision now. The aim
> here is to depend on nothing but OpenLayers and Ext. Adding ux
> components in their native namespace could become a problem in
> applications that use a different version of the same ux. So pulling
> these ux components into a GeoExt namespace makes sense. And if we
> apply the same rule to ux components that we create or modify, then it
> makes a lot of sense to put them in a GeoExt namespace.

Here's the case I was concerned with: we create Ext.ux components,
host them in some dir at the root of our SVN, and create GeoExt
components based on those Ext.ux components. If we do that without
doing versioning for our Ext.ux stuff, we will have to make sure what
every modification made to our Ext.ux does not break any of the GeoExt
releases. Example: the 1.0 release of GeoExt includes GeoExt.Styler
that depends on Ext.ux.ColorPicker, to improve GeoExt.Styler for
GeoExt 1.1 someone needs to modify Ext.ux.ColorPicker, the
modifications made to Ext.ux.ColorPicker must not break GeoExt.Style
shipped with GeoExt 1.0. And doing versioning for our Ext.ux stuff
will force us to do specific releases of our Ext.ux, we don't want I
guess, this is too much burden.

-- 
Eric Lemoine

Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac, Cedex

Tel : 00 33 4 79 44 44 96
Mail : eric.lemoine at camptocamp.com
http://www.camptocamp.com