Modify

Opened 16 months ago

Last modified 14 months ago

#7299 new enhancement

Move features to expert mode

Reported by: bastiK Owned by: team
Priority: normal Component: Core
Version: Keywords: expert mode
Cc: joshdoe, akks

Description

Let's discuss which features should be hidden in non-expert mode.

The idea is, that a new user can focus on the important stuff first. When they have mastered the basics and feel comfortable, expert mode can be turned on (and stay on).

Attachments (0)

Change History (19)

comment:1 Changed 16 months ago by joshdoe

  • Cc joshdoe added

comment:2 Changed 16 months ago by akks

  • Cc akks added

comment:3 follow-up: Changed 16 months ago by akks

New checkbox for expert mode looks and works really good.

My ideas:

  • move half of DisplaySettings-GPS points options to expert mode (Circle from HDOP, Force lines, custom Waypoint labeling, etc.)
  • move more importang settings for starters upwards - the first should be "Connection Settings", then "Plugins" and "WMS/TMS", then "Map Settings" and "Toolbar". "Audio" , "Validator", "Remote control" on the bottom. [to be discussed]
  • (offtopic) Links to configuration tabs in context menus can be very helpful (like existing Configure toolbar).
Last edited 16 months ago by akks (previous) (diff)

comment:4 Changed 16 months ago by bastiK

In [4843/josm]:

see #7299 - Move features to expert mode

comment:5 Changed 16 months ago by bastiK

I've added a few menu items that seem like clear cases to me:

  • File > Export to GPX...
  • File > Close open changesets
  • Edit > Copy Coordinates
  • Edit > Purge...
  • View > Viewport Following
  • Tools > Mirror
  • Tools > Follow Line
  • Tools > Add Node...
  • Tools > Move Node...

comment:6 follow-up: Changed 16 months ago by bastiK

What about toggle dialog buttons? My choice would be

  • User list
  • History
  • Filter
  • Changesets
  • Map paint styles

Maybe also command list, but it could be helpful to understand how JOSM works.

comment:7 Changed 16 months ago by bastiK

In [4844/josm]:

made most of the GPS display settings expert. (see #7299)

comment:8 in reply to: ↑ 3 ; follow-up: Changed 16 months ago by bastiK

Replying to akks:

New checkbox for expert mode looks and works really good.

My ideas:

  • move half of DisplaySettings-GPS points options to expert mode (Circle from HDOP, Force lines, custom Waypoint labeling, etc.)

Done.

  • move more importang settings for starters upwards - the first should be "Connection Settings", then "Plugins" and "WMS/TMS", then "Map Settings" and "Toolbar". "Audio" , "Validator", "Remote control" on the bottom. [to be discussed]

IMO this should be a general reordering (both normal and expert mode). Otherwise it is too confusing for both users and devs.

  • (offtopic) Links to configuration tabs in context menus can be very helpful (like existing Configure toolbar).

True.

comment:9 in reply to: ↑ 6 ; follow-up: Changed 16 months ago by stoecker

Replying to bastiK:

What about toggle dialog buttons? My choice would be

  • User list
  • History
  • Filter
  • Changesets
  • Map paint styles

Maybe also command list, but it could be helpful to understand how JOSM works.

Not the filters I would say. They should be prominent, as they are a very important feature nowadays.

comment:10 Changed 16 months ago by skyper

Speaking for myself, I used the "user list" quite often right from the beginning and I still do.

You quickly get an overview on other users in your region and it offers an easy way to get into contact with them.

comment:11 in reply to: ↑ 9 Changed 16 months ago by akks

Replying to stoecker:

Replying to bastiK:

What about toggle dialog buttons? My choice would be

  • User list
  • History
  • Filter
  • Changesets
  • Map paint styles

Maybe also command list, but it could be helpful to understand how JOSM works.

Not the filters I would say. They should be prominent, as they are a very important feature nowadays.

And I also like "Map paint styles". It can be used to turn on "Potlatch style", which can be convenient for beginners :)

Last edited 16 months ago by akks (previous) (diff)

comment:12 in reply to: ↑ 8 ; follow-up: Changed 16 months ago by akks

Replying to bastiK:

Replying to akks:

  • move more importang settings for starters upwards - the first should be "Connection Settings", then "Plugins" and "WMS/TMS", then "Map Settings" and "Toolbar". "Audio" , "Validator", "Remote control" on the bottom. [to be discussed]

IMO this should be a general reordering (both normal and expert mode). Otherwise it is too confusing for both users and devs.

Yes, I mean general reordering to put essential things upwards in both simple and expert modes. What do you think about it?

Last edited 16 months ago by akks (previous) (diff)

comment:13 Changed 16 months ago by bastiK

In [4849/josm]:

make History- & Changeset-Toggle dialog expert (see #7299)

comment:14 in reply to: ↑ 12 Changed 16 months ago by bastiK

Replying to akks:

Replying to bastiK:

Replying to akks:

  • move more importang settings for starters upwards - the first should be "Connection Settings", then "Plugins" and "WMS/TMS", then "Map Settings" and "Toolbar". "Audio" , "Validator", "Remote control" on the bottom. [to be discussed]

IMO this should be a general reordering (both normal and expert mode). Otherwise it is too confusing for both users and devs.

Yes, I mean general reordering to put essential things upwards in both simple and expert modes. What do you think about it?

Yes, maybe. In tutorials, it is sometimes hard to name the top level tab ("second from the top, looks like a globe"). Maybe we can add text labels, so this gets easier. I think the structure of the preference dialog could be improved in general.

comment:15 Changed 14 months ago by simon04

From #4561: Is the command stack toggle dialog necessary for the non-expert mode? Such a list of undo-able commands is rarely available in other applications and may not be needed.

comment:16 follow-up: Changed 14 months ago by akks

Maybe, but on the other hand it is human-readable and let novices understand better what they do - for example, notice movements done by mistake, etc.

comment:17 in reply to: ↑ 16 Changed 14 months ago by skyper

Replying to akks:

Maybe, but on the other hand it is human-readable and let novices understand better what they do - for example, notice movements done by mistake, etc.

+1

comment:18 follow-up: Changed 14 months ago by bastiK

But we can have the command stack closed on first start and relation list opened instead.

comment:19 in reply to: ↑ 18 Changed 14 months ago by skyper

Replying to bastiK:

But we can have the command stack closed on first start and relation list opened instead.

This is what #4561 is about. Where does you opinion change come from ?

I prefere the command stack to be minimized but open but that is just my use and I haven't looked over newbies' shoulders lately.

Last edited 14 months ago by skyper (previous) (diff)

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as new .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team. Next status will be 'new'.
Next status will be 'needinfo'.The owner will change to bastiK
as duplicate The resolution will be set to duplicate. Next status will be 'closed'.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous. Next status will be 'assigned'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.