Ubuntu Wiki

• Launchpad Entry: spec:new-images-plymouth-lightdm-wallpaper

• Created: ScottLavender

• Contributors:

• Packages affected: ubuntustudio-default-settings, ubuntustudio-artwork

Summary

Create the following new thematically linked images to give Ubuntu Studio a more polished and consistent look.

• plymouth theme concept image
• lightdm greeter theme concept image
• desktop wallpaper image

'concept image' is listed for the plymouth and lightdm greeter themes because it is not a static image that will be used. Unless you are able and willing to help with the coding please do not get too crazy with the concepts

Release Note

The users will be presented with a new consistently thematic images throughout the starting, logging in, and using Ubuntu Studio. It will give a more polished and engineered look and feel to Ubuntu Studio.

Rationale

The current images are either disparate or crudely ugly (default lidghtdm theme currently used).

Assumptions

It is suggested that there are two large assumptions for this specification:

• # The first assumption is that the person(s) responsible for art will NOT be explicitly responsible for implementation or code. If you want to help in these regards, please do so. But they are not required as other's already involved can do these things but not create the artistic images desired. # The creation of the images will be an iterative process. Filtering the minimalistic (and perhaps abstract) directions though the artists interpretation most likely will require further discussions.

Design

Overall Concept

Here are some simple guidelines about the overarching concept:

• make sure there are consistent thematic elements in all images (e.g. colors, images, possibly positions)
• not every element or thematic concept needs to be included in every image (e.g. CoF might be located differently or even excluded)
• KISS - simplicity is beauty (plus it should make implementation easier)

Suggested Colors

Below are the suggested colors. Previously we used lots of blacks and blues, but more grays might align better with the new xubuntu based theme.

Here is a list suggested colors. You don't have to use all of them

You might have noticed the crazily-lacking-continuity orange in there. It was inspired by this page which will feature later on.

CoF

Here is a .svg for the base CoF file. new-precise-images-logo.svg

It looks like the image from the developer.ubuntu.com website, but this is the only image that can currently be found that has the Ubuntu Studio CoF as separate parts to be manipulated.

Feel free to play around with the CoF. In the .svg linked above it was changed to orange and dotted lines. Of course, you don't have to include the CoF in the concepts or images, but it might be nice to include it in at least one of them.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

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.

Test/Demo Plan

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 testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

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.

BoF agenda and discussion

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.

CategorySpec