Skip to content

Commit

Permalink
GSoC21: idea for Human Interface Guidelines Redesign
Browse files Browse the repository at this point in the history
  • Loading branch information
srevinsaju committed Feb 6, 2021
1 parent c356429 commit 8b544dd
Showing 1 changed file with 74 additions and 0 deletions.
74 changes: 74 additions & 0 deletions Ideas-2021.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@

* [Port Sugar and core activities to Python 3](#port-sugar-and-core-activities-to-python-3)
* [Improve and maintain 15 Sugar activities](#improve-and-maintain-15-sugar-activities)
* [Human Interface Guidelines Redesign for Sugar](#human-interface-guidelines-redesign-for-sugar)
* [Music Blocks 2.0 Block Graphics Refactoring](#music-blocks-2.0-block-graphics-refactoring)
* [Music Blocks 2.0 Menus and Palettes](#music-blocks-2.0-menus-and-palettes)

Expand Down Expand Up @@ -96,6 +97,79 @@ will help you to gain experience
**Assisting Mentors**<br>
To be added.

--------------

## Human Interface Guidelines Redesign for Sugar

**Selected**<br>
Nobody.

**Prerequisites**<br>
- Experience with UX design
- Extensive experience with Python and GTK3
- Experience with Sugar activities/toolkit
- Experience with user interface and graphics design (and SVG)

**Description**<br>
Sugar’s use of color and icons (described in detail here [HIG
color](https://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Sugar_Interface/Colors)
and [HIG
icons](https://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Sugar_Interface/Icons))
is functional but a bit tired when compared to modern desktops and
mobile systems.

This project is about redesigning the use of color in Sugar in order
to enable full-color icons for both the desktop itself and activities.
This would require rewriting the [Human Interface Guidelines](https://wiki.sugarlabs.org/go/Human_Interface_Guidelines).

The primary role of color in the current icon design is to;
- Indicate whether or not an activity has been used
- Indicate whether or not an activity is being shared with another
Sugar user (the colors of the person who launches the activity show
up on the desktops of the people who join the activity.)

Fortunately, Sugar also support a mechanism for putting badges on
icons. An example is in the neighborhood view, where badges are used
to indicate which access points are active (See
[networkviews.py](https://github.com/sugarlabs/sugar/blob/master/src/jarabe/desktop/networkviews.py)).

We could use badges (See
[icon.py](https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/graphics/icon.py#L49))
to replace the functionality of color described above: for example, an
XO badge to indicate an activity has been used. And the color of that
badge could indicate collaboration. This would free up the icon itself
to take on any colors deemed suitable by the activity designer.

**Project Task:**<br>
- [ ] Rewrite the Human Interface Guidelines. Design a new idea for
the Sugar UX and UI.
- [ ] Add color functionality to the badges;
- [ ] Add badges in every instance where we currently use color: the
desktop, the journal, the neighborhood view and the activity
toolbar;
- [ ] Work with the design team to come up with new color icons for
all of the core Sugar toolbars, activities and activity toolbars

**Optional Tasks:**<br>
- [ ] Improve the Sugar Shell desktop UI, such as adding Animations
- [ ] Port Sugar Toolkit to GTK4 (GTK4 has extensive support for animations)
- [ ] Complete the [Corner Layout Feature](https://github.com/sugarlabs/sugar/pull/740)
which is an open pull request, not finished yet.
- [ ] Complete adding the [Screenshot Popup](https://github.com/sugarlabs/sugar/pull/675)
feature, which also remains as an open pull request.

**Suggested issues to work on:**<br>
- There are not any issues specific to this project, but working on
some open bugs would be a good place to start in understanding the
code base.

**Coding Mentors**<br>
None

**Assisting Mentors**<br>
None


------------

## Music Blocks 2.0 Block Graphics Refactoring
Expand Down

0 comments on commit 8b544dd

Please sign in to comment.