Color Entry Widget - Revision history

Romain2Boss: /* Deal with full SVG 1.1 colors */

2013-01-05T16:10:06Z

Deal with full SVG 1.1 colors

← Older revision		Revision as of 16:10, 5 January 2013
Line 58:		Line 58:
	FF00AADD		FF00AADD
	\| \|		\| \|
	No**		No*
	\| \|		\| \|

Romain2Boss: /* Deal with full SVG 1.1 colors */

2013-01-05T16:09:17Z

Deal with full SVG 1.1 colors

← Older revision		Revision as of 16:09, 5 January 2013
Line 22:		Line 22:
	\| \|		\| \|
	<nowiki>#FF00AA</nowiki>		<nowiki>#FF00AA</nowiki>
			\| \|
			Yes
			\| \|

			\|-
			\| \|
			<nowiki>#F0A</nowiki>
	\| \|		\| \|
	Yes		Yes
Line 35:		Line 42:
	\|-		\|-
	\| \|		\| \|
	~~<nowiki>#FF00AADD</nowiki>~~		F0A
	\| \|		\| \|
	No*		No*
Line 42:		Line 49:
	\|-		\|-
	\| \|		\| \|
	FF00AADD		<nowiki>#FF00AADD</nowiki>
	\| \|		\| \|
	No*		No**
	\| \|		\| \|

	\|-		\|-
	\| \|		\| \|
	~~rgb(255, 0, 170)~~		FF00AADD
	\| \|		\| \|
	~~Yes~~		No**
	\| \|		\| \|

	\|-		\|-
	\| \|		\| \|
	rgb(~~100%~~, 0%, ~~66%~~)		rgb(255, 0, 170)
	\| \|		\| \|
	Yes		Yes
Line 63:		Line 70:
	\|-		\|-
	\| \|		\| \|
	~~inherit~~		rgb(100%, 0%, 66%)
	\| \|		\| \|
	Yes		Yes
Line 77:		Line 84:
	\|}		\|}
	<nowiki>* Kept for historycal reasons</nowiki>		<nowiki>* Kept for historycal reasons</nowiki>
			<nowiki>** Kept for historycal reasons and as an hypotetical SVG 2 valid color format</nowiki>

	== Prepare SVG 2 ==		== Prepare SVG 2 ==

Romain2Boss: /* Deal with full SVG 1.1 colors */ Add a SVG 1.1 compliance matrix

2013-01-05T12:18:08Z

Deal with full SVG 1.1 colors: Add a SVG 1.1 compliance matrix

← Older revision		Revision as of 12:18, 5 January 2013
Line 12:		Line 12:

	The third case is proposed.		The third case is proposed.

			{\| class="wikitable centre" width="80%"
			\|+ SVG 1.1 compliance matrix
			\|-
			! scope=col \| Input/Loaded color
			! scope=col \| SVG 1.1
			! scope=col \| Saved as
			\|-
			\| \|
			<nowiki>#FF00AA</nowiki>
			\| \|
			Yes
			\| \|

			\|-
			\| \|
			FF00AA
			\| \|
			No*
			\| \|

			\|-
			\| \|
			<nowiki>#FF00AADD</nowiki>
			\| \|
			No*
			\| \|

			\|-
			\| \|
			FF00AADD
			\| \|
			No*
			\| \|

			\|-
			\| \|
			rgb(255, 0, 170)
			\| \|
			Yes
			\| \|

			\|-
			\| \|
			rgb(100%, 0%, 66%)
			\| \|
			Yes
			\| \|

			\|-
			\| \|
			inherit
			\| \|
			Yes
			\| \|

			\|-
			\| \|
			red
			\| \|
			Yes
			\| \|

			\|}
			<nowiki>* Kept for historycal reasons</nowiki>

	== Prepare SVG 2 ==		== Prepare SVG 2 ==

Romain2Boss: Add Summary and Prepare SVG2

2012-12-26T14:21:28Z

Add Summary and Prepare SVG2

← Older revision		Revision as of 14:21, 26 December 2012
Line 1:		Line 1:
	The entry accepts colors as defined by the [http://www.w3.org/TR/SVG/color.html SVG 1.1 Specifications]. ~~Those~~ colors are stored in the SVG file as specified by the user (i.e. no more forced conversions to ~~RRGGBBAA~~). However, for internal purposes, the colors can be stored and handled differently.		Here are the aims of this blueprint.

			== Deal with full SVG 1.1 colors ==

			The entry accepts colors as defined by the [http://www.w3.org/TR/SVG/color.html SVG 1.1 Specifications].

			SVG 1.1 colors do not handle alpha (it's stored in a separate attribute). We have three options:

			# Change nothing and keep displaying the alpha value with the color value by extanding the SVG specification (#RRGGBB => RRGGBBAA, rgb(255, 255, 255) => rgba(255, 255, 255, alpha)...).
			# Do like many softwares and display the color in the entry without the alpha (which is displayed in it's own entry). This would probably need a widget rearrangement.
			# Allow both: implement the SVG 1.1 specification (case 2) and keep case 1 as a preparation for SVG 2. This will allow inputs but, because Inkscape files are SVG 1.1, any loaded file will be displayed using case 2.

			The third case is proposed.

			== Prepare SVG 2 ==

			Based on [http://www.w3.org/TR/SVG2/color.html SVG2]. The idea is to be more ''SVG 2 ready''.

			=== sRGB colors ===

			The HSL format is closed to RGB: no issue.

			Some color named are added: no issue.

			=== sRGB colors with alpha ===

			RGBA and HSLA are added: no issue.

			=== ICC and LAB colors ===

			To be implemented?

			== Keep the user value ==

			Colors are stored in the SVG file as specified by the user (i.e. no more forced conversions to hex values). However, for internal purposes, the colors can be stored and handled differently. This would mean having an internal color value (as now) and a display value.

	The color sets in the entry is (chronologically):		The color sets in the entry is (chronologically):
Line 6:		Line 40:
	# Then, if modified by the user (pasted or typed), the user value		# Then, if modified by the user (pasted or typed), the user value
	# Then, if modified by the software (in case of multiple input widgets), the software value		# Then, if modified by the software (in case of multiple input widgets), the software value

			If the alpha is not part of the user input, Inkscape keep the previous one and will not append it in the entry.

			== Help the user ==

	If the text in the entry cannot be converted to a valid color, the entry changes it's appearance (red border?).		If the text in the entry cannot be converted to a valid color, the entry changes it's appearance (red border?).

	If a color from the palette is dragged and dropped on the entry, it takes the color value.		If a color from the palette is dragged and dropped on the entry, it takes the color value.

	The SVG specification split colors and opacity in two different properties. However, the Inkscape Color Entry propose the user to merge them in the same entry. We would extend the SVG specifications to allow Alpha (ie RRGGBB => RRGGBBAA) but, if not set, Inkscape append the previous alpha.

	[[Category:Proposals]]		[[Category:Proposals]]
	[[Category:Widgets]]		[[Category:Widgets]]

Romain2Boss at 23:14, 11 December 2012

2012-12-11T23:14:30Z

← Older revision		Revision as of 23:14, 11 December 2012
Line 11:		Line 11:
	If a color from the palette is dragged and dropped on the entry, it takes the color value.		If a color from the palette is dragged and dropped on the entry, it takes the color value.

	~~== To be defined ==~~		The SVG specification split colors and opacity in two different properties. However, the Inkscape Color Entry propose the user to merge them in the same entry. We would extend the SVG specifications to allow Alpha (ie RRGGBB => RRGGBBAA) but, if not set, Inkscape append the previous alpha.

	~~For the alpha value associated to the color~~, ~~following options:~~

	~~# We keep~~ the ~~default behaviour (~~the ~~alpha is part of the entry)~~
	~~# We goes~~ to ~~a more compliant SVG philosophy where alpha is not part of~~ the entry ~~anymore~~
	# We ~~have an half way where we~~ extend the SVG specifications to allow Alpha (ie RRGGBB => RRGGBBAA) but, if not set, Inkscape append the previous alpha

	[[Category:Proposals]]		[[Category:Proposals]]
	[[Category:Widgets]]		[[Category:Widgets]]

Romain2Boss: Created page with "The entry accepts colors as defined by the [http://www.w3.org/TR/SVG/color.html SVG 1.1 Specifications]. Those colors are stored in the SVG file as specified by the user (i.e...."

2012-12-11T23:09:22Z

Created page with "The entry accepts colors as defined by the [http://www.w3.org/TR/SVG/color.html SVG 1.1 Specifications]. Those colors are stored in the SVG file as specified by the user (i.e...."

New page

The entry accepts colors as defined by the [http://www.w3.org/TR/SVG/color.html SVG 1.1 Specifications]. Those colors are stored in the SVG file as specified by the user (i.e. no more forced conversions to RRGGBBAA). However, for internal purposes, the colors can be stored and handled differently.

The color sets in the entry is (chronologically):

# First, the color as written in the SVG file (if any)
# Then, if modified by the user (pasted or typed), the user value
# Then, if modified by the software (in case of multiple input widgets), the software value

If the text in the entry cannot be converted to a valid color, the entry changes it's appearance (red border?).

If a color from the palette is dragged and dropped on the entry, it takes the color value.

== To be defined ==

For the alpha value associated to the color, following options:

# We keep the default behaviour (the alpha is part of the entry)
# We goes to a more compliant SVG philosophy where alpha is not part of the entry anymore
# We have an half way where we extend the SVG specifications to allow Alpha (ie RRGGBB => RRGGBBAA) but, if not set, Inkscape append the previous alpha

[[Category:Proposals]]
[[Category:Widgets]]