Object Manager - Revision history

Moini at 13:07, 13 May 2024

2024-05-13T13:07:55Z

← Older revision		Revision as of 13:07, 13 May 2024
Line 1:		Line 1:
	= ~~'''~~This ~~is obsolete information this~~ feature ~~is implmented in to~~ [[Release notes/1.2#Layers and Objects dialog\|Layers Dialog]]~~''' =~~		{{Outdated\|message=This feature has been incorporated into the [[Release notes/1.2#Layers and Objects dialog\|Layers Dialog]].}}

	'''The Inkscape Object Manager'''		'''The Inkscape Object Manager'''

Adambelis at 15:57, 12 May 2024

2024-05-12T15:57:24Z

← Older revision		Revision as of 15:57, 12 May 2024
Line 1:		Line 1:
			= '''This is obsolete information this feature is implmented in to [[Release notes/1.2#Layers and Objects dialog\|Layers Dialog]]''' =
	'''The Inkscape Object Manager'''		'''The Inkscape Object Manager'''

Frigory: Frigory moved page ObjectManager to Object Manager: Separated words

2016-07-13T05:50:04Z

Frigory moved page ObjectManager to Object Manager: Separated words

← Older revision	Revision as of 05:50, 13 July 2016
(No difference)

Kiirala at 17:17, 7 October 2009

2009-10-07T17:17:55Z

← Older revision		Revision as of 17:17, 7 October 2009
Line 1:		Line 1:
	~~<h1>~~The Inkscape Object Manager~~</h1>~~		'''The Inkscape Object Manager'''

	~~<strong>~~A hybrid of the XML Editor and Item Properties dialog.. mixed in with a bit of love.~~</strong>~~		'''A hybrid of the XML Editor and Item Properties dialog.. mixed in with a bit of love.'''


Line 8:		Line 8:


	~~<h2>~~Brief~~</h2>~~		== Brief ==
	~~<ul>~~		* An expandable list of the groups and objects within your SVG. Previews of what is within that group is handy but not essential ( like in the XML editor: when groups are selected , the relative items on the canvas are selected )
	~~<li>~~An expandable list of the groups and objects within your SVG.~~<br />~~		* Groups can be expanded down to object level and each list item can be renamed.
			* Each list item has a visibility and sensitive check button.
			* Objects can be dragged from the list to the canvas. This will initiate a Use function to duplicate that group ( can we do this ? it would do wonders for economising file-size and graphics! )
			** Should be able to. cloning objects does that now, and we are able to clone groups

	~~Previews of what is within that group is handy but not essential ( like in the XML editor: when groups are selected , the relative items on the canvas are selected )</li>~~		== Better for Semantics ==

	~~<li>Groups can be expanded down to object level and each list item can be renamed~~.~~</li>~~		Many Users will identify this manager as a type of 'Object Library' for their SVG documents.

	~~<li>Each list item has a visibility and sensitive check button~~.~~<br /></li>~~		The benefit here lies in the content. As users rename the objects they see in the manager they will be in-fact renaming the ID's in the XML.

	~~<li>objects can be dragged from~~ the ~~list to~~ the ~~canvas~~. ~~<br />~~		This means the more semantic their documents, the more the user is rewarded with a logical 'object manager'.

	~~This will initiate a Use function~~ to ~~duplicate that group ( can we do this ?~~ it ~~would do wonders for economising file-size and graphics! )<br/>~~		Because it's as simple as double clicking your object in the manager to rename it, users will be not only encouraged too name objects for
	~~--Should~~ be ~~able to. cloning~~ objects ~~does that now, and we are able to clone groups</li>~~

	~~</ul>~~		== Better for Users ==

			When making objects sensitive and insensitive, users shouldn't have to go deep into the dark pits of the XML editor to make objects sensitive again. Same goes for objects with completely transparent fill and stroke.

			When importing SVG from other applications - or even Inkscape-generated plain SVG - layers are lost. "Promote group to layer" would then be a great thing to do. Probably it'd be useful in other ways, too.

			Clipping, masking and filter effects can be used on layers, too. Currently it's just hard to do, as it's not simple to select a layer.

			== The Gradient Manager ==

	~~<h2>Better for Semantics<~~/~~h2>~~		Currently when an object uses an existing [http://grin-optics.org gradient], inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.

	~~<p>Many Users will identify this manager as~~ a type ~~of 'Object Library'~~ for ~~their SVG documents.<br />~~		The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.
			What also makes for a nice feature is you can re-use the reference gradients for exact-gradient positioning based off other objects :)

	~~The benefit here lies in the content. As users rename the objects they see in the manager they will be in-fact renaming the ID's in the XML.<br />~~		=== Things that happen as you interact with the gradient manager ===
			* Draging and dropping objects above and below eachother changes their order in the xml
	~~This means the more semantic their documents, the more the user is rewarded with a logical 'object manager'.<br />~~		* Clicking on an object after it is selected allows the user to rename the id of that def
			* Selecting a gradient after selecting an object applies that gradient
	~~Because it's as simple as double clicking your object in the manager to rename it, users will be not only encouraged too name objects for </p>~~





	~~<h2>Better for Users</h2>~~

	~~<p>When making objects sensetive and insensetive, users shouldn't have to go deep into the dark pits of the XML editor to make objects sensetive again. </p>~~


	~~<h2>The Gradient Manager</h2>~~
	<p>currently when an object uses an existing [http://grin-optics.org gradient], inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. <br />This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.</p>

	~~<p>The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.<br />~~
	~~What also makes for a nice feature is you can re-use the reference gradients for exact-gradient positioning based off other objects :)</p>~~

	~~<h3>~~Things that happen as you interact with the gradient manager~~</h3>~~
	~~<p>~~
	~~<ul>~~

	~~<li>~~Draging and dropping objects above and below eachother changes their order in the xml~~</li>~~

	~~<li>clicking~~ on an object after it is selected allows the user to rename the id of that def~~</li>~~

	~~<li>selecting~~ a gradient after selecting an object applies that gradient~~</li>~~
	~~</ul>~~

	~~</p>~~

	=== Gradient Dialog Design Ideas ===		=== Gradient Dialog Design Ideas ===

Turnip at 19:42, 17 October 2006

2006-10-17T19:42:57Z

← Older revision		Revision as of 19:42, 17 October 2006
Line 82:		Line 82:
	* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png

	* http://turnipspatch.com/~~misc~~/inkscape/gradients.html		* http://turnipspatch.com/demos/inkscape/freehand-gradients/gradients.html

	* http://jozmak.heydo.com/wallpapers/screensavers.htm		* http://jozmak.heydo.com/wallpapers/screensavers.htm

Shmel at 18:34, 3 October 2006

2006-10-03T18:34:43Z

← Older revision		Revision as of 18:34, 3 October 2006
Line 49:		Line 49:

	<h2>The Gradient Manager</h2>		<h2>The Gradient Manager</h2>
	<p>currently when an object uses an existing gradient, inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. <br />This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.</p>		<p>currently when an object uses an existing [http://grin-optics.org gradient], inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. <br />This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.</p>

	<p>The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.<br />		<p>The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.<br />

Daiwai: /* Gradient Dialog Design Ideas */ fixed www.netsoc.tcd.ie images

2006-03-02T17:23:58Z

Gradient Dialog Design Ideas: fixed www.netsoc.tcd.ie images

← Older revision		Revision as of 17:23, 2 March 2006
Line 71:		Line 71:
	* http://www.macromedia.com/software/freehand/productinfo/features/static_tour/07effects.html#3		* http://www.macromedia.com/software/freehand/productinfo/features/static_tour/07effects.html#3

	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-001.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-001.png
	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-002-noise-gradient.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-002-noise-gradient.png
	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-003-menu.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-003-menu.png
	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-004.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-004.png
	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-005.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-005.png
	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-007.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-007.png

	And a screenshot of just the tool options bar for gradients:		And a screenshot of just the tool options bar for gradients:

	* http://~~matrix~~.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png		* http://www.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png

	* http://turnipspatch.com/misc/inkscape/gradients.html		* http://turnipspatch.com/misc/inkscape/gradients.html

Conversion script: link fix

2006-01-22T02:33:25Z

link fix

New page

<h1>The Inkscape Object Manager</h1>

<strong>A hybrid of the XML Editor and Item Properties dialog.. mixed in with a bit of love.</strong>

upload:obman2.png upload:gradients.png

<h2>Brief</h2>
<ul>
<li>An expandable list of the groups and objects within your SVG.<br />

Previews of what is within that group is handy but not essential ( like in the XML editor: when groups are selected , the relative items on the canvas are selected )</li>

<li>Groups can be expanded down to object level and each list item can be renamed.</li>

<li>Each list item has a visibility and sensitive check button.<br /></li>

<li>objects can be dragged from the list to the canvas. <br />

This will initiate a Use function to duplicate that group ( can we do this ? it would do wonders for economising file-size and graphics! )<br/>
--Should be able to. cloning objects does that now, and we are able to clone groups</li>

</ul>

<h2>Better for Semantics</h2>

<p>Many Users will identify this manager as a type of 'Object Library' for their SVG documents.<br />

The benefit here lies in the content. As users rename the objects they see in the manager they will be in-fact renaming the ID's in the XML.<br />

This means the more semantic their documents, the more the user is rewarded with a logical 'object manager'.<br />

Because it's as simple as double clicking your object in the manager to rename it, users will be not only encouraged too name objects for </p>

<h2>Better for Users</h2>

<p>When making objects sensetive and insensetive, users shouldn't have to go deep into the dark pits of the XML editor to make objects sensetive again. </p>

<h2>The Gradient Manager</h2>
<p>currently when an object uses an existing gradient, inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. <br />This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.</p>

<p>The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.<br />
What also makes for a nice feature is you can re-use the reference gradients for exact-gradient positioning based off other objects :)</p>

<h3>Things that happen as you interact with the gradient manager</h3>
<p>
<ul>

<li>Draging and dropping objects above and below eachother changes their order in the xml</li>

<li>clicking on an object after it is selected allows the user to rename the id of that def</li>

<li>selecting a gradient after selecting an object applies that gradient</li>
</ul>

</p>

=== Gradient Dialog Design Ideas ===

* http://www.macromedia.com/software/freehand/productinfo/features/static_tour/07effects.html#3

* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-001.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-002-noise-gradient.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-003-menu.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-004.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-005.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-007.png

And a screenshot of just the tool options bar for gradients:

* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png

* http://turnipspatch.com/misc/inkscape/gradients.html

* http://jozmak.heydo.com/wallpapers/screensavers.htm

If we want a solution that will scale beyond a few dozen gradients I'm
convinced the task of creating or editing new gradients should be seperated
out from the task of selecting and applying a gradient.
Part of the reasion I created a set of gradients for [[OpenClipart]].org was
to have a sample set that made it clear to anyone redesigining the dialog
that it would need to accomodate a whole lot of gradients. -- Alan

The way Xara does it:
http://www.xara.com/products/xarax/flash/fill.htm

BryceHarrington: *

2005-01-30T06:36:33Z

New page

<h1>The Inkscape Object Manager</h1>

<strong>A hybrid of the XML Editor and Item Properties dialog.. mixed in with a bit of love.</strong>

upload:obman2.png upload:gradients.png

<h2>Brief</h2>
<ul>
<li>An expandable list of the groups and objects within your SVG.<br />

Previews of what is within that group is handy but not essential ( like in the XML editor: when groups are selected , the relative items on the canvas are selected )</li>

<li>Groups can be expanded down to object level and each list item can be renamed.</li>

<li>Each list item has a visibility and sensitive check button.<br /></li>

<li>objects can be dragged from the list to the canvas. <br />

This will initiate a Use function to duplicate that group ( can we do this ? it would do wonders for economising file-size and graphics! )<br/>
--Should be able to. cloning objects does that now, and we are able to clone groups</li>

</ul>

<h2>Better for Semantics</h2>

<p>Many Users will identify this manager as a type of 'Object Library' for their SVG documents.<br />

The benefit here lies in the content. As users rename the objects they see in the manager they will be in-fact renaming the ID's in the XML.<br />

This means the more semantic their documents, the more the user is rewarded with a logical 'object manager'.<br />

Because it's as simple as double clicking your object in the manager to rename it, users will be not only encouraged too name objects for </p>

<h2>Better for Users</h2>

<p>When making objects sensetive and insensetive, users shouldn't have to go deep into the dark pits of the XML editor to make objects sensetive again. </p>

<h2>The Gradient Manager</h2>
<p>currently when an object uses an existing gradient, inkscape will create a new lineargradientXXXX def id so that the x1y1 x2y2 coords can be changed. <br />This def will then xlink:href to the existing gradient so that it can assume the colours and stops as the users.</p>

<p>The Gradient Manager provides a way to manage the names of both reference type gradient defs and also the gradient defs that contrain colour stop information.<br />
What also makes for a nice feature is you can re-use the reference gradients for exact-gradient positioning based off other objects :)</p>

<h3>Things that happen as you interact with the gradient manager</h3>
<p>
<ul>

<li>Draging and dropping objects above and below eachother changes their order in the xml</li>

<li>clicking on an object after it is selected allows the user to rename the id of that def</li>

<li>selecting a gradient after selecting an object applies that gradient</li>
</ul>

</p>

=== Gradient Dialog Design Ideas ===

* http://www.macromedia.com/software/freehand/productinfo/features/static_tour/07effects.html#3

* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-001.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-002-noise-gradient.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-003-menu.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-004.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-005.png
* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-editor-007.png

And a screenshot of just the tool options bar for gradients:

* http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/inkscape/screenshots/references/photoshop/adobephotoshop7_gradient-tooloptions-001.png

* http://turnipspatch.com/misc/inkscape/gradients.html

* http://jozmak.heydo.com/wallpapers/screensavers.htm

If we want a solution that will scale beyond a few dozen gradients I'm
convinced the task of creating or editing new gradients should be seperated
out from the task of selecting and applying a gradient.
Part of the reasion I created a set of gradients for OpenClipart.org was
to have a sample set that made it clear to anyone redesigining the dialog
that it would need to accomodate a whole lot of gradients. -- Alan

195.177.212.225: Removed spam

2004-09-24T08:00:37Z

Removed spam

New page