Hey, It seems that OJ users have different habits and it will be difficult to make everybody happy. Still hope we can make the menu a little bit lighter without penalizing users. We'll have to synthetize all answers before making a decision. > from my users side of view I can say that I use context menu, button and also > EZ-Buttons...it depends on the functions I want to use and what I can reach > faster. But this should be the difficult thing becuase every users works in a > different way as I realzied it from how my collegues work with OJ. So the > best solution should be a user adaptable (contex)menu/button toolbar...but > this should be a very difficult development. and I wonder it is worthwhile. I know from my own experience that when there are several ways to achieve a task, the one I use is not always the best. Just the option that I discovered first or that has been shown to me, keeping me away from looking for a better one ;-) > Independent from this I use also the ... > - copy/paste layer/features functions from the context menu (I believe it is > the fastest way, so I need it in the contect menu) Just wonder if paste features wouldn't be easier to use in viewPanel context menu (with a submenu item for each editable layer - don't know if it's easy to do however) > - But I use the change style options only from the toolbar (I do not need it > in the context menu) > - I never used the Add Objects function from the context menu (it can be > moved to the menu bar) > - I do not need Visibility function in the context menu (it faster to use the > checkbox in the layer list (it can be moved to the menu bar) I think the context menu is more confortable if you have to change the visibility for many layers.
Michaël > Kindly regards > Arnd > > >> Larrys& Michaels proposal would be fine with me too. >> >> I use the copy/paste style quite often, putting them in a submenu would >> be nice, but saves not much space. In opposite to Michael I rarely use >> buttons but rather the context menu to call "change style", " View / >> Edit Attributes", Select features from layer, ... >> >> my 2 cents >> stefan >> >> Larry Becker schrieb: >>> I agree with Michaël's priorities. >>> >>> I would move these to the Layer menu: >>> >>> Rename Selected Layer >>> Move Layer Up >>> Move Layer Down >>> >>> and remove these >>> >>> Add New Feature... maybe enough to have it in edit menu >>> Paste Feature : maybe enough to have it in edit menu >>> >>> my 2 cents, >>> >>> Larry >>> >>> 2010/10/27 Michaël Michaud<michael.mich...@free.fr >>> <mailto:michael.mich...@free.fr>> >>> >>> Le 27/10/2010 15:56, Larry Becker a écrit : >>>> Isn't there a way of breaking context menus up to several >>>> columns, like windows does? >>>> Maybe java already delivers this in some way? >>>> >>>> >>>> Sure. I did that to organize this menu in SkyJUMP. You need >>>> to move at least 3 to a submenu to make it worth while. It might >>>> be enough to move 4 items to the Layer menu, if there is room >> there. >>> I think that we can remove some menu item already in layer menu or >>> in edit menu. >>> Here is the way I use context munu. What about yours ? >>> >>> *Editable : very important >>> Selectable : **very important >>> **Layer properties : **very important* >>> Rename Selected Layer : can be removed (there is double click and >>> still the menu item in Layer menu) >>> *Zoom to Layer : very important* >>> *Style *: generally, I use the toolbar (copy/paste rarely used) >>> Change style... : good candidate for a submenu >>> Copy styles : good candidate for a submenu >>> Paste styles : good candidate for a submenu >>> View / Edit Attributes : I always use the toolbar) >>> View / Edit Schema : I'd like a button in the toolbar >>> *Save selected Datasets : very important* >>> *Refresh Layer... *: didn't know it : let it here (to be renamed >>> Refresh database layer... ?) >>> *Save Dataset as* : *very important* (I'd like a second plugin >>> Save Selected Dataset in...) >>> Move Layer Up : can remove it (not user friendly, can be added in >>> Layer menu) >>> Move Layer Down : can remove it (not user friendly, can be added >>> in Layer menu) >>> moving layer with drag and drop is more user friendly, but a >>> little bit buggy >>> *Cut Layer* : *important* (maybe enough to have it in Layer menu) >>> *Copy Layer* : *important *(maybe enough to have it in Layer menu) >>> *Remove layer* : *very important* (but can be put in a submenu) >>> Add New Feature... maybe enough to have it in edit menu >>> Paste Feature : maybe enough to have it in edit menu >>> Remove all features : could be added to edit menu >>> *Change visibility* : *very important* must be higher in the menu >>> (beside editable, selectable) >>> Select features from layer : maybe enough to have it in >>> edit>select submenu >>> >>> Michaël >>> >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North America >> contest >> Create new apps& games for the Nokia N8 for consumers in U.S. and Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
