About the foot print; we could break the EditMapWIthPalette out into a separate
plugin if needed; but I am trying to make less plugins rather than more of
them. If you feel there would be a good benefit then perhaps we could do the
work together?
> After some tests with the GEF palette I stumbled over some issues:
> - Some actions are still in the toolbar (Zoom Selection, Commit, Rollback)
>
>
>
Yes all actions are still in the toolbar; this was part of the initial proposal.
Only the "modal tools" are in the palette (indeed that is what the palette is
for).
> - Palette can attached on the left or on the right side, not on top or button.
>
>
>
Correct; the super class defines this. You can also open the palette view in
order to reposition the palette else where in your user interface.
> - Having no resources in map and adding some the palette refreshes and
> Edit-Actions are added. Having a map with resources and the user removes all
> layers, the palette doesn't refresh (Edit-Actions are still in palette till
> reopening the Map)
>
>
>
Can you make a bug report for this; and we can try and look at it next week.
> - In general I think its a bit tricky to find an action, especially for
> "first time users". IMHO all actions should be visible and disabled if not
> available (context relevant action, eg. selection avaliable, Layer selected,
> etc).
>
>
>
That was our intention however I found I was unable to implement the "disabled
state" directly using the GEF facilities. This was not something we knew about
going into this work.
The only hint that this can be done is contained here:
http://www.eclipsezone.com/eclipse/forums/t47375.html
If this can be figured out then I would prefer to use disabled as you say.
Cheers!
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
