Design Team/Proposals/Welcome First Boot Intro - Revision history

Garycmartin: /* Sugar Home View */

2012-05-12T13:10:40Z

Sugar Home View

← Older revision		Revision as of 09:10, 12 May 2012
Line 41:		Line 41:


	[[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.]]		[[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).]]

Garycmartin at 12:57, 12 May 2012

2012-05-12T12:57:08Z

← Older revision		Revision as of 08:57, 12 May 2012
Line 38:		Line 38:
	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
	* TODO: ~~Add screenshot of~~ Welcome activity mockup

			[[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.]]

Garycmartin: /* Sugar Home View */

2012-05-11T16:06:49Z

Sugar Home View

← Older revision		Revision as of 12:06, 11 May 2012
Line 39:		Line 39:

	* TODO: Design Welcome Activity svg icon		* TODO: Design Welcome Activity svg icon
			* TODO: Add screenshot of Welcome activity mockup

Garycmartin at 16:06, 11 May 2012

2012-05-11T16:06:05Z

← Older revision		Revision as of 12:06, 11 May 2012
Line 22:		Line 22:

	[[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 ====

Garycmartin: /* Welcome View */

2012-05-11T16:05:39Z

Welcome View

← Older revision		Revision as of 12:05, 11 May 2012
Line 17:		Line 17:

	For future efforts we should consider providing animated feedback to the interaction (and swipe touch gestures), where the content images quickly animate as translations left and right when navigated through (a carousel like effect). And ultimately a left right full screen transition animation stepping through the Intro views pages.		For future efforts we should consider providing animated feedback to the interaction (and swipe touch gestures), where the content images quickly animate as translations left and right when navigated through (a carousel like effect). And ultimately a left right full screen transition animation stepping through the Intro views pages.


	[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]		[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]

Garycmartin: /* Welcome View */

2012-05-11T16:05:13Z

Welcome View

← Older revision		Revision as of 12:05, 11 May 2012
Line 16:		Line 16:
	A timer could allow for auto flipping through the content card deck if no interaction is made after a set period, though care should be taken not to take control away from a user who may just bee looking closely at one of the content images (timer should be stopped if the user is interacting, touching keys, moving cursor). For keyboard accelerators, the Enter/Return key should be used to move onto the Naming view, with Space bar navigating through the content slide deck (and or cursor left, cursor right, game pad left, game pad right).		A timer could allow for auto flipping through the content card deck if no interaction is made after a set period, though care should be taken not to take control away from a user who may just bee looking closely at one of the content images (timer should be stopped if the user is interacting, touching keys, moving cursor). For keyboard accelerators, the Enter/Return key should be used to move onto the Naming view, with Space bar navigating through the content slide deck (and or cursor left, cursor right, game pad left, game pad right).

	For future efforts we should consider providing animated feedback to the interaction, where the content images quickly animate left and right ~~translations as~~ navigated through (a carousel like effect). And ultimately a left right full screen transition animation stepping through the Intro views.		For future efforts we should consider providing animated feedback to the interaction (and swipe touch gestures), where the content images quickly animate as translations left and right when navigated through (a carousel like effect). And ultimately a left right full screen transition animation stepping through the Intro views pages.

	[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]		[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]

Garycmartin: /* Welcome View */

2012-05-11T14:08:23Z

Welcome View

← Older revision		Revision as of 10:08, 11 May 2012
Line 15:		Line 15:

	A timer could allow for auto flipping through the content card deck if no interaction is made after a set period, though care should be taken not to take control away from a user who may just bee looking closely at one of the content images (timer should be stopped if the user is interacting, touching keys, moving cursor). For keyboard accelerators, the Enter/Return key should be used to move onto the Naming view, with Space bar navigating through the content slide deck (and or cursor left, cursor right, game pad left, game pad right).		A timer could allow for auto flipping through the content card deck if no interaction is made after a set period, though care should be taken not to take control away from a user who may just bee looking closely at one of the content images (timer should be stopped if the user is interacting, touching keys, moving cursor). For keyboard accelerators, the Enter/Return key should be used to move onto the Naming view, with Space bar navigating through the content slide deck (and or cursor left, cursor right, game pad left, game pad right).

			For future efforts we should consider providing animated feedback to the interaction, where the content images quickly animate left and right translations as navigated through (a carousel like effect). And ultimately a left right full screen transition animation stepping through the Intro views.

	[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]		[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]

Garycmartin: /* First Boot Welcome Feature */

2012-05-11T13:56:23Z

First Boot Welcome Feature

← Older revision		Revision as of 09:56, 11 May 2012
Line 8:		Line 8:
	# Coloir picker view		# Coloir picker view
	# Sugar home view		# Sugar home view


	==== Welcome View ====		==== Welcome View ====
Line 13:		Line 14:
	In the welcome view, the user can step through, or skip, welcome content with a goal of providing initial XO and Sugar orientation. The content should be centred, onto a plain white canvas (same colour as first boot intro 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. Note that the content image below has been given a subtle coloured glow/shadow in post production as one possible example of seamless styling content in a frameless view.		In the welcome view, the user can step through, or skip, welcome content with a goal of providing initial XO and Sugar orientation. The content should be centred, onto a plain white canvas (same colour as first boot intro 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. Note that the content image below has been given a subtle coloured glow/shadow in post production as one possible example of seamless styling content in a frameless 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.]]		A timer could allow for auto flipping through the content card deck if no interaction is made after a set period, though care should be taken not to take control away from a user who may just bee looking closely at one of the content images (timer should be stopped if the user is interacting, touching keys, moving cursor). For keyboard accelerators, the Enter/Return key should be used to move onto the Naming view, with Space bar navigating through the content slide deck (and or cursor left, cursor right, game pad left, game pad right).

	[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]		[[File:First boot welcome proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]

			[[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 ====

Garycmartin at 03:59, 11 May 2012

2012-05-11T03:59:12Z

← Older revision		Revision as of 23:59, 10 May 2012
Line 11:		Line 11:
	==== Welcome View ====		==== Welcome View ====

	In the welcome view, the user can step through, or skip, welcome content with a goal of providing initial XO and Sugar orientation. The content should be centred, onto a plain white canvas (same colour as first boot intro 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.		In the welcome view, the user can step through, or skip, welcome content with a goal of providing initial XO and Sugar orientation. The content should be centred, onto a plain white canvas (same colour as first boot intro 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. Note that the content image below has been given a subtle coloured glow/shadow in post production as one possible example of seamless styling content in a frameless 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 proposal1.png\|thumb\|centre\|640px\|Layout example with centred go-previous-paired and go-next-paired content navigation buttons.]]

Garycmartin: /* First Boot Welcome Feature */

2012-05-11T03:25:30Z

First Boot Welcome Feature

← Older revision		Revision as of 23:25, 10 May 2012
Line 8:		Line 8:
	# Coloir picker view		# Coloir picker view
	# Sugar home view		# Sugar home view

	Once at the sugar desktop a Welcome Activity is available if the users 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. The allows for content imagers with no visible edge boundaries. Content images can be of varying width and height, up to some recommended maximum, always presented centred on the canvas.

	==== Welcome View ====		==== Welcome View ====

	* Welcome view, user can step through or skip welcome content providing initial XO and Sugar orientation.		In the welcome view, the user can step through, or skip, welcome content with a goal of providing initial XO and Sugar orientation. The content should be centred, onto a plain white canvas (same colour as first boot intro 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.


Line 26:		Line 24:
	==== 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.		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 Welcome Activity svg icon