Ticket #8170 (new enhancement)

Opened 6 years ago

Last modified 5 years ago

Put core activity actions in the same place across activities

Reported by: sj Owned by: Eben
Priority: normal Milestone: 9.1.0-cancelled
Component: not assigned Version: not specified
Keywords: Cc: mikus@…
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking: #6932

Description

From teacher feedback

* Core activity features should always show up in the same place in an activity... ==> being able to launch without the core "activity-tab" buttons available is repeatedly confusing.

This means, among other things : have certain features (closing an activity, changing sharing status) always available with the same set of keystrokes/movements, not requiring opening a special tab. This is made worse by activities choosing different default tabs.

Change History

Changed 6 years ago by kimquirk

  • milestone changed from Not Triaged to 9.1.0

Changed 6 years ago by kimquirk

  • type changed from defect to enhancement

Changed 5 years ago by mikus

  • cc mikus@… added
  • spec_stage set to unknown
  • spec_reviewed set to 0

Changed 5 years ago by Eben

This is a tough one. The choice to omit a static, persistent toolbar for meta actions (keep, stop, etc.) was made to preserve space, as well as to give the activity the top edge of the screen (for easier buttons to hit, along the edge. With this decision, many found it confusing, for instance, to open Browse and not have an address bar immediately presented; or paint and not see the painting tools. For this reason, we recommended that the default toolbar be chosen by the activity, which I still think is the right choice.

There are two improvements to the system that I think are relevant to this issue:

  1. We're going to add "encouragement" for naming/tagging of activities in an upcoming release, which should reduce the need to have input focus on the title entry. This doesn't solve the problem for things like stop and keep, though keep at least should be 99% automatic.
  1. The new toolbar proposal (http://wiki.laptop.org/go/Designs/Toolbars) can provide a great way to handle this problem, since the activity toolbar would become a toolbar button in the new paradigm, and could be shown in addition to the default activity toolbar. This makes the meta actions persistently available for as long as the kid wishes them to be, though they may hide them as desired.
Note: See TracTickets for help on using tickets.