GnomeDoPolishedSymbolInterface

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2007-09-26 18:12:33 →
Size: 2895
Editor: c-76-99-54-167
Comment:
← Revision 2 as of 2007-09-26 18:22:28 → ⇥
Size: 2168
Editor: c-76-99-54-167
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * '''Launchpad Entry''': UbuntuSpec:foo
 * '''Packages affected''': 		 * '''Launchpad Entry''': [https://blueprints.launchpad.net/gc/+spec/polished-symbol-interface Polished Symbol Interface]
# * '''Packages affected''':
Line 10: Line 10:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. Add some spit and polish to the GNOME Do symbol interface by adding some shadows, curves, and glossiness.
Line 14: Line 14:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.		 This interface is essential for our first release.
Line 20: Line 18:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. The current symbol interface is bland and looks flat, especially when drawn on screens without transparency. By making some small stylistic changes (or large ones) we can dramatically improve the friendliness and sexiness of the symbol interface.
Line 23: Line 21:

  * John starts GNOME Do for the first time and begins searching. He sees a sleek interface with bodacious curves and larger-than-life icons. John thinks GNOME Do looks so fantastic that he is encouraged to use it as his primary means of interacting with his GNOME desktop environment, and because of this encouragement he becomes a master at using the symbol interface and learns the real advantage to using GNOME Do.
Line 36: Line 36:
Line 39: Line 38:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: Either modify existing interface code with new drawing code, or create a new window class.
Line 43: Line 42:
Should cover changes required to the UI, or specific UI that is required to implement this See above.
Line 47: Line 46:
Code changes should include an overview of what needs to change, and in some cases even the specific details. See implementation.
Line 51: Line 50:
Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.		 N/A.
Line 58: Line 54:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.		 New interface should be 100% feature compatible with existing symbol interface.
Line 64: Line 58:
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. N/A.
Line 68: Line 62:
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. ...

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

# * Packages affected:

Summary

Add some spit and polish to the GNOME Do symbol interface by adding some shadows, curves, and glossiness.

Release Note

This interface is essential for our first release.

Rationale

The current symbol interface is bland and looks flat, especially when drawn on screens without transparency. By making some small stylistic changes (or large ones) we can dramatically improve the friendliness and sexiness of the symbol interface.

Use Cases

  • John starts GNOME Do for the first time and begins searching. He sees a sleek interface with bodacious curves and larger-than-life icons. John thinks GNOME Do looks so fantastic that he is encouraged to use it as his primary means of interacting with his GNOME desktop environment, and because of this encouragement he becomes a master at using the symbol interface and learns the real advantage to using GNOME Do.

Assumptions

Design

First, see Apple's [http://www.thinksecret.com/archives/leopard9a559/image/finder12.jpg high-resolution 'Spaces' icon].

Second, see GNOME Do's [http://davebsd.com/do/images/symbol-interface-09-26-2007.jpg symbol interface as of 09/26/2007].

Thirdly, see the [http://davebsd.com/do/images/gnome-do-spaces-mockup.jpg Spaces icon/Do symbol interface mockup].

Finally, implement this interface.

Implementation

Either modify existing interface code with new drawing code, or create a new window class.

UI Changes

See above.

Code Changes

See implementation.

Migration

N/A.

Test/Demo Plan

New interface should be 100% feature compatible with existing symbol interface.

Outstanding Issues

N/A.

BoF agenda and discussion

...

CategorySpec

GnomeDoPolishedSymbolInterface (last edited 2008-08-06 16:18:51 by localhost)