2,354
edits
Changes
Jump to navigation
Jump to search
Line 22:
Line 22: + + + Line 35:
Line 38: − + + + +
Design Team/Proposals/Welcome First Boot Intro (view source)
Revision as of 09:10, 12 May 2012
, 09:10, 12 May 2012→Sugar Home View
[[File:First boot welcome proposal2.png|thumb|centre|640px|Layout example with go-previous and go-next content navigation buttons on opposite sides of the view.]]
[[File:First boot welcome proposal2.png|thumb|centre|640px|Layout example with go-previous and go-next content navigation buttons on opposite sides of the view.]]
==== Naming View ====
==== Naming View ====
[[File:First boot name intro welcome proposal.png|thumb|centre|640px|Naming view, user types their name. The next button is initially inactive until the user starts to type a name. Note the addition of the Back button on the bottom left, this should return the user to the welcome content.]]
[[File:First boot name intro welcome proposal.png|thumb|centre|640px|Naming view, user types their name. The next button is initially inactive until the user starts to type a name. Note the addition of the Back button on the bottom left, this should return the user to the welcome content.]]
==== Colour Picker View ====
==== Colour Picker View ====
[[File:First_boot_colour_picker_intro_blue.png|thumb|centre|640px|Colour picker, user chooses their fill and stroke colours. No change needed to this view.]]
[[File:First_boot_colour_picker_intro_blue.png|thumb|centre|640px|Colour picker, user chooses their fill and stroke colours. No change needed to this view.]]
==== Sugar Home View ====
==== Sugar Home View ====
First boot process leads to the Sugar Home view, where the user can choose to review the welcome content by starting the Welcome activity. Once at the Sugar home view a Welcome Activity is available if the user wants to review the welcome content at a later time. The Activity should have a standard Sugar toolbar with buttons for back and next that render the content, centred, onto a plain white canvas (same colour as first boot background) with no borders. This allows for content imagers with no visible edge boundaries, or a seamless style of the content authors choosing (e.g. drop shadows, traditional frame, texture). Content images can be in varying width and height, up to some recommended maximum, always presented centred on the canvas.
First boot process leads to the Sugar Home view, where the user can choose to review the welcome content by starting the Welcome activity. Once at the Sugar home view a Welcome Activity is available if the user wants to review the welcome content at a later time. The Activity should have a standard Sugar toolbar with buttons for back and next that render the content, centred, onto a plain white canvas (same colour as first boot background) with no borders. This allows for content imagers with no visible edge boundaries, or a seamless style of the content authors choosing (e.g. drop shadows, traditional frame, texture). Content images can be in varying width and height, up to some recommended maximum, always presented centred on the canvas.
* TODO: Design Welcome Activity svg icon
* TODO: Design new Welcome Activity svg icon
[[File:Welcome activity mockup.png|thumb|centre|640px|Simple viewer activity for welcome content after first boot. Ideally the image content should be shared between both first boot and activity implementations to reduce disk space usage and stay consistent. Should the first boot implementation check and look inside the Welcome activity bundle, or should the Activity look for content somewhere in the system? Using the Activity as the content source would allow for easy upgrading and modifying of the content using existing tools and infrastructure, but might become an issue as different deployment start to provide different sets of localised welcome content (local Welcome activity version number will begin to conflict due to multiple maintainers, or become large in size if many sets of localised image based content are included in one officially maintained release).]]