[Gvsig_english] Menu refactoring (was Re: gvSIG 1.9.1)

[Jorge Gaspar Sanz Salinas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29/03/10 15:48, Benjamin Ducke wrote:
> 
> Yes, of course!
> 
> As I proposed before, a good compromise may be for
> me to first feed all my changes that relate to bug fixes into SVN. Those
> are not too many and they are well tested (by me, at least).
> 
> Then there is a much bigger set of changes that relate to GUI changes
> and other "matters of taste" (e.g. a large patch to unify filetype
> names in all gvSIG file selector windows, some additional items for
> the context menu, etc.). 
> How about you merge these (they really don't affect that much code and are 
> completely documented) yourself if you like them? That would leave me with 
> some time for additional bug fixing.
> 
> As regards the changes in menu structure (you know, all those config.xml)
> files: those can be regarded a form of "skinning". We will provide them
> in a separate download archive on oadigital.net. Then people can install
> them seperately on top of any version of gvSIG they like.

Ben,

We're not going to accept to change the GUI menus for 1.9.1, as we
said, because we have an usability work on gvSIG GUI planned for 2.0
or the next release.

BUT, as you say, we can help you to create and extension to implement
those changes, in order to avoid to "fork" or change official gvSIG
code but maintaining the functionality you want to add for your
distribution.

This is the typical approach we seek to maximize modularity: "if you
want to change something and gvSIG is not extensible in that way, we
will try to add the mechanisms in gvSIG that enable modularity on your
needs to let you override the default gvSIG behaviour".

Technically speaking there's a mechanism called ExclusiveUIExtension
to let one extension to decide how the other behave. The documentation
is in Spanish[1] but we can help you on the process and eventually
translate it.

This approach requires some coding and more work than just paste all
the config.xml files, but we think is a more sustainable way to
interact with the GUI.

So, don't hesitate to ask for help if you think it's worth.

Cheers

[1]
http://www.gvsig.org/web/docdev/reference/gvsig/andami/plugins-extensiones/extensiones/uiextension/



> 
> Best,
> 
> Ben
> 
- -- 
Jorge Gaspar Sanz Salinas
gvSIG Team
Technical Steering Committee Manager
http://www.gvsig.org
http://www.gvsig.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLsg+cAAoJEAOYD75lvHdBJ+8H/29/qavcVoaED5AgbNIPOzJe
vpYhlLnjHGoQUknG6IP9aJCdbjHrSp45z8oqpobV4wiYsS2rfQjdYoPseQ5x58As
2R8D8zwdUCMiAZuF6blar4y5P+QspKXYe6F4NUpU9bkZQqAdEPkaygIJXDuDzzUm
f6mr7LJMDvByhfaOPKyAq90cMKqJY9ROOpZU9NzAhPMVpXW88bz/YsOMKTcVCprS
6/sP51Tiam9N2Wp4dXmkXPyR0eL/l1KDXSvDux8/2KRRCitm+wH53k3rfApXSjdM
hikQRNnA94fJavxim++p/LfvWmF3GoTtNYofOV1GHWya5Hzo2ti+O7jE7EYvvk4=
=sBZ5
-----END PGP SIGNATURE-----