Synfig Studio :: Documentation - User contributions [en]

Dev:Software roadmap

2006-05-14T05:31:32Z

SnapSilverlight: An undocumented todo discovered in a discussion on IRC. (Duckmatic/DuckMap)

A software roadmap is in the process of being developed. If you would like to lobby for specific functionality to be implemented sooner than what is stated, please discuss it in the [[Talk:Software roadmap|talk page]].

Since the roadmap isn't finished yet, here is an unsorted list of things that I plan to implement:
==Roadmap==
===Under-the-hood changes===
* Redesign the render target class
** current implementation doesn't handle large images very well
* migrate API to be more language agnostic
* Add support for arbitrary multiple color channels
* Add support for customizable mixing gamma per canvas
* Start migrating toward a script-friendly API
* Implement garbage collection of synfig nodes
* Re-write or replace the "Simple Text" layer for proper font support. Current implementation is gnarly.

===Optimizations===
* Change the way surfaces are stored in memory from chunky to planar. This alone should provide significant speed improvements, as well as pave the way for future hardware optimization. (like Apple's new [http://www.apple.com/macosx/tiger/coreimage.html CoreImage])
* Support for arbitrary [[color channels]]
* Support for customizable [[color mixing gamma]]

===User Interface===
* Re-write the canvas properties dialog, as it is currently too awkward and confusing
* Reimplement the [[draw tool]] so that it is actually useful
* Rewrite state_draw to handle simultaneous creation of region/bline/curve gradient, like state_region. ([[User:SnapSilverlight|Snap]])
** Since that's basically recopying code, try to refactor this functionality into its own module somewhere? ([[User:SnapSilverlight|Snap]])

==TO-DO==
'''''(Synfig-Studio)'''''

* Objectify Synfig-Studio's representation of Synfig-Core's types
** Build datatypes for Studio visualisations
*** Implement 'shell' datatypes for existing Synfig types.
**** Studio Layer datatype
***** Create initial definition of this datatype and add to project
***** Insert code into selection functions to store references to ducks on "studio layer" type when selected.
***** Add functions to "studio layer" type to select specific ducks on layer.
* Rework and extend layer-search system.
** "The layer should provide a virtual function for determining if the layer is clickable at the given point or not -- a bool. This will allow you to implement different types of traversals/filtering" -- darco, on IRC
** "Actually, I think there will still need to be a virtual function which handles the traversal case, and have it use the bool function... Things can get complicated if you had a layer that had two canvas parameters" -- darco, on IRC
* Build a public interface for DuckMap (duckmatic.cpp/208)
(From the code)
;'''src/gtkmm/cellrenderer_timetrack.cpp''' (161)
:Add in RangeGet so it's not so damn hard to click on points
;'''src/gtkmm/cellrenderer_timetrack.h''' (104)
:Make multiple... on both time and value select...
;'''src/gtkmm/duckmatick.h''' (208)
:need a public interface for DuckMap
;'''src/gtkmm/widget_timeslider.h''' (78)
:Fill out blue pill stuff
;'''src/synfigapp/blineconvert.cpp''' (496)
:Tolerance should be set based upon digitization resolution (length dependent index selection)
;'''src/synfigapp/blineconvert.cpp''' (584)
:Must be sure that the break points are 3 or more apart then must also store the breaks which are not smooth, etc. and figure out tangents between there

==Needs //Comment// Doc==
;'''src/gtkmm/app.h''' (file header brief)
;'''src/gtkmm/canvasview.h''' (546)
:rebuild_ducks()
;'''src/gtkmm/cellrenderer_timetrack.h''' (142)
:property_enable_timing_info_;
;'''src/gtkmm/duck.h''' (79)
:class Duck
;'''src/gtkmm/duck.h''' (155)
:set_tangent(bool x)
;'''src/gtkmm/duck.h''' (158)
:get_tangent()
;'''src/gtkmm/duck.h''' (175)
:set_type(Type x)
;'''src/gtkmm/duck.h''' (178)
:get_type()
;'''src/gtkmm/duckmatic.h''' (367)
:set_type_mask(Type x)
;'''src/gtkmm/duckmatic.h''' (370)
:get_type_mask()
;'''src/gtkmm/duckmatic.h''' (388)
:Duckmatic::Push
;'''src/gtkmm/duckmatic.h''' (407)
:Duckmatic::Bezier
;'''src/gtkmm/duckmatic.h''' (421)
:Duckmatic::Stroke
;'''src/gtkmm/instance.h''' (file header brief)

Dev:Software roadmap

2006-05-03T15:11:48Z

SnapSilverlight: Adding known missing comments.

A software roadmap is in the process of being developed. If you would like to lobby for specific functionality to be implemented sooner than what is stated, please discuss it in the [[Talk:Software roadmap|talk page]].

Since the roadmap isn't finished yet, here is an unsorted list of things that I plan to implement:
==Roadmap==
===Under-the-hood changes===
* Redesign the render target class
** current implementation doesn't handle large images very well
* migrate API to be more language agnostic
* Add support for arbitrary multiple color channels
* Add support for customizable mixing gamma per canvas
* Start migrating toward a script-friendly API
* Implement garbage collection of synfig nodes
* Re-write or replace the "Simple Text" layer for proper font support. Current implementation is gnarly.

===Optimizations===
* Change the way surfaces are stored in memory from chunky to planar. This alone should provide significant speed improvements, as well as pave the way for future hardware optimization. (like Apple's new [http://www.apple.com/macosx/tiger/coreimage.html CoreImage])
* Support for arbitrary [[color channels]]
* Support for customizable [[color mixing gamma]]

===User Interface===
* Re-write the canvas properties dialog, as it is currently too awkward and confusing
* Reimplement the [[draw tool]] so that it is actually useful
* Rewrite state_draw to handle simultaneous creation of region/bline/curve gradient, like state_region. ([[User:SnapSilverlight|Snap]])
** Since that's basically recopying code, try to refactor this functionality into its own module somewhere? ([[User:SnapSilverlight|Snap]])

==TO-DO==
'''''(Synfig-Studio)'''''

* Objectify Synfig-Studio's representation of Synfig-Core's types
** Build datatypes for Studio visualisations
*** Implement 'shell' datatypes for existing Synfig types.
**** Studio Layer datatype
***** Create initial definition of this datatype and add to project
***** Insert code into selection functions to store references to ducks on "studio layer" type when selected.
***** Add functions to "studio layer" type to select specific ducks on layer.
* Rework and extend layer-search system.
** "The layer should provide a virtual function for determining if the layer is clickable at the given point or not -- a bool. This will allow you to implement different types of traversals/filtering" -- darco, on IRC
** "Actually, I think there will still need to be a virtual function which handles the traversal case, and have it use the bool function... Things can get complicated if you had a layer that had two canvas parameters" -- darco, on IRC
(From the code)
;'''src/gtkmm/cellrenderer_timetrack.cpp''' (161)
:Add in RangeGet so it's not so damn hard to click on points
;'''src/gtkmm/cellrenderer_timetrack.h''' (104)
:Make multiple... on both time and value select...
;'''src/gtkmm/widget_timeslider.h''' (78)
:Fill out blue pill stuff
;'''src/synfigapp/blineconvert.cpp''' (496)
:Tolerance should be set based upon digitization resolution (length dependent index selection)
;'''src/synfigapp/blineconvert.cpp''' (584)
:Must be sure that the break points are 3 or more apart then must also store the breaks which are not smooth, etc. and figure out tangents between there

==Needs //Comment// Doc==
;'''src/gtkmm/app.h''' (file header brief)
;'''src/gtkmm/canvasview.h''' (546)
:rebuild_ducks()
;'''src/gtkmm/cellrenderer_timetrack.h''' (142)
:property_enable_timing_info_;
;'''src/gtkmm/duck.h''' (79)
:class Duck
;'''src/gtkmm/duck.h''' (155)
:set_tangent(bool x)
;'''src/gtkmm/duck.h''' (158)
:get_tangent()
;'''src/gtkmm/duck.h''' (175)
:set_type(Type x)
;'''src/gtkmm/duck.h''' (178)
:get_type()
;'''src/gtkmm/duckmatic.h''' (367)
:set_type_mask(Type x)
;'''src/gtkmm/duckmatic.h''' (370)
:get_type_mask()
;'''src/gtkmm/duckmatic.h''' (388)
:Duckmatic::Push
;'''src/gtkmm/duckmatic.h''' (407)
:Duckmatic::Bezier
;'''src/gtkmm/duckmatic.h''' (421)
:Duckmatic::Stroke
;'''src/gtkmm/instance.h''' (file header brief)

Dev:Software roadmap

2006-05-02T23:50:30Z

SnapSilverlight: Notes from IRC - hit_check should be bool, not iter?

A software roadmap is in the process of being developed. If you would like to lobby for specific functionality to be implemented sooner than what is stated, please discuss it in the [[Talk:Software roadmap|talk page]].

Since the roadmap isn't finished yet, here is an unsorted list of things that I plan to implement:

* '''Under-the-hood changes'''
** Redesign the render target class
*** current implementation doesn't handle large images very well
** migrate API to be more language agnostic
** Add support for arbitrary multiple color channels
** Add support for customizable mixing gamma per canvas
** Start migrating toward a script-friendly API
** Implement garbage collection of synfig nodes
** Re-write or replace the "Simple Text" layer for proper font support. Current implementation is gnarly.

* '''Optimizations'''
** Change the way surfaces are stored in memory from chunky to planar. This alone should provide significant speed improvements, as well as pave the way for future hardware optimization. (like Apple's new [http://www.apple.com/macosx/tiger/coreimage.html CoreImage])
** Support for arbitrary [[color channels]]
** Support for customizable [[color mixing gamma]]

* '''User Interface'''
** Re-write the canvas properties dialog, as it is currently too awkward and confusing
** Reimplement the [[draw tool]] so that it is actually useful
** Rewrite state_draw to handle simultaneous creation of region/bline/curve gradient, like state_region. ([[User:SnapSilverlight|Snap]])
*** Since that's basically recopying code, try to refactor this functionality into its own module somewhere? ([[User:SnapSilverlight|Snap]])

==TO-DO==
'''''(Synfig-Studio)'''''

* Objectify Synfig-Studio's representation of Synfig-Core's types
** Build datatypes for Studio visualisations
*** Implement 'shell' datatypes for existing Synfig types.
**** Studio Layer datatype
***** Create initial definition of this datatype and add to project
***** Insert code into selection functions to store references to ducks on "studio layer" type when selected.
***** Add functions to "studio layer" type to select specific ducks on layer.
* Rework and extend layer-search system.
** "The layer should provide a virtual function for determining if the layer is clickable at the given point or not -- a bool. This will allow you to implement different types of traversals/filtering" -- darco, on IRC
** "Actually, I think there will still need to be a virtual function which handles the traversal case, and have it use the bool function... Things can get complicated if you had a layer that had two canvas parameters" -- darco, on IRC
(From the code)
;'''src/gtkmm/cellrenderer_timetrack.cpp''' (161)
:Add in RangeGet so it's not so damn hard to click on points
;'''src/gtkmm/cellrenderer_timetrack.h''' (104)
:Make multiple... on both time and value select...
;'''src/gtkmm/widget_timeslider.h''' (78)
:Fill out blue pill stuff
;'''src/synfigapp/blineconvert.cpp''' (496)
:Tolerance should be set based upon digitization resolution (length dependent index selection)
;'''src/synfigapp/blineconvert.cpp''' (584)
:Must be sure that the break points are 3 or more apart then must also store the breaks which are not smooth, etc. and figure out tangents between there

Related Projects

2006-05-02T15:09:03Z

SnapSilverlight: Adding Ktoon, notes on Inkscape.

==Animation==
* [http://www.blender3d.org/ blender] - 3D modelling and animation
* [http://http://ktoon.toonka.com/ KToon] - Pixel-based 2D animation, similar layout to ToonBoom Studio

==Raster Image Manipulation==
* [http://www.gimp.org/ GIMP] - GNU image manipulation program
** the iwrap deformation tool can create (crude) animations
** layers can be saved as animated .gif
* [http://www.gimp.org/tutorials/Using_GAP/ GAP] - GIMP Animation Plugin
* [http://www.cinepaint.org/ cinepaint] - a GIMP fork used for motion picture frame-by-frame retouching

==Vector Image Manipulation==
* [http://www.inkscape.org/ inkscape] - SVG-based vector graphics, animation capability scheduled for Milestone 20 - Inkscape 0.54
* [http://www.xaraxtreme.org/about/ xaralx] - vector graphic program
* [http://cvs.cinelerra.org/ Cinelerra] - video editor and compositor

==Video editing==
* [http://www.jahshaka.org/ jahshaka] - video and film compositing, editing and special fx system

==TODO==
(Please verify URL, comment it, sort it)

*http://www.mdk.org.pl/articles/category/diva
*http://www.diva-project.org/wiki/Main_Page
*http://www.pitivi.org
*http://positron.sourceforge.net
*http://cuisine.bigasterisk.com
*http://lives.sourceforge.net
*http://www.kinodv.org/
*http://users.pandora.be/acp/kino/kinoplus.html
*http://dvbackup.sourceforge.net/
*http://mjpeg.sourceforge.net/
*http://ronald.bitfreak.net/lvs/
*http://www.robfisher.net/video/
*http://www.theora.org/
*http://effectv.sourceforge.net/
*http://freej.dyne.org/
*http://developer.skolelinux.no/info/studentgrupper/2005-hig-stopmotion
*http://www.allusion.net/bakasub/
*http://gsubedit.sourceforge.net/
*http://sourceforge.net/projects/ksubeditor/

*[http://freshmeat.net/browse/256/ Freshmeat Category: Non-Linear Video Editor]
* [http://dvr.sourceforge.net DVR], digital video recorder

Dev:Software roadmap

2006-05-02T05:36:29Z

SnapSilverlight: Missing functionality in Studio. Please edit this to make more sense.

Dev:Software roadmap

2006-04-27T17:07:56Z

SnapSilverlight: Todo's (grep'd from source!)

Dev:State stroke

2006-04-26T00:50:41Z

SnapSilverlight:

==Description==
state_stroke is an 'invisible' mode - that is, you can't select it from the [[Toolbox]]. You see it on the [[Draw Tool]] and the [[Sketch Tool]] between mouse-down and mouse up, it's what's actually drawing to the canvas and taking your data.

''NOTE: state_stroke does NOT handle mouse-down! This is to allow your tool to figure out if it needs to do anything different based on where the mouse is clicking, *before* state_stroke is entered!''

==Provides==
EventStroke(stroke_data,width_data,modifier)
: EventStroke is sent to the tool that calls state_stroke as soon as the state exits, along with the stroke data. Intercept this event to do something with the data.

==Internals==

===Events Caught===
*EVENT_STOP: event_stop_handler
*EVENT_REFRESH: event_refresh_handler
*EVENT_WORKAREA_MOUSE_BUTTON_UP: event_mouse_up_handler
*EVENT_WORKAREA_MOUSE_BUTTON_DRAG: event_mouse_draw_handler
*EVENT_REFRESH_TOOL_OPTIONS event_refresh_tool_options

===StateStroke_Context===
''State constructor''

===~StateStroke_Context===
''State destructor''

Restores the previous duck view, refreshes the toolbox, and raises EventStroke on the State Machine.

===event_refresh_tool_options===
Intercepts the event, and nothing further.

===event_stop_handler===
exits the state (pop-exception)

===event_refresh_handler===
Intercepts the event, and nothing further.

===event_mouse_up_handler====
''MouseUp Handler''

If this is the LMB, set 'modifier' for the destructor event from the mouse event's data, then exit the state (pop-exception)

If this is for the RMB, intercept the signal and end.

If this is for any other mouse button, pass it along.

===event_mouse_draw_handler===
''Mouse drag event handler''

If this is the LMB, accept the event, add the event's position to stroke_data, and the event's pressure to width_data, and call queue_draw (?).

If it's the RMB, accept the event to keep the context menu from appearing.

Any other button, pass the event along.

Dev:State stroke

2006-04-26T00:35:30Z

SnapSilverlight: Description of State Stroke

==Description==
state_stroke is an 'invisible' mode - that is, you can't select it from the [[Toolbox]]. You see it on the [[Draw Tool]] and the [[Sketch Tool]] between mouse-down and mouse up, it's what's actually drawing to the canvas and taking your data.

==Provides==
EventStroke(stroke_data,width_data,modifier)
: EventStroke is sent to the tool that calls state_stroke as soon as the state exits, along with the stroke data. Intercept this event to do something with the data.

==Internals==

===Events Caught===
*EVENT_STOP: event_stop_handler
*EVENT_REFRESH: event_refresh_handler
*EVENT_WORKAREA_MOUSE_BUTTON_UP: event_mouse_up_handler
*EVENT_WORKAREA_MOUSE_BUTTON_DRAG: event_mouse_draw_handler
*EVENT_REFRESH_TOOL_OPTIONS event_refresh_tool_options

===StateStroke_Context===
''State constructor''

===~StateStroke_Context===
''State destructor''

Restores the previous duck view, refreshes the toolbox, and raises EventStroke on the State Machine.

===event_refresh_tool_options===
Intercepts the event, and nothing further.

===event_stop_handler===
exits the state (pop-exception)

===event_refresh_handler===
Intercepts the event, and nothing further.

===event_mouse_up_handler====
''MouseUp Handler''

If this is the LMB, set 'modifier' for the destructor event from the mouse event's data, then exit the state (pop-exception)

If this is for the RMB, intercept the signal and end.

If this is for any other mouse button, pass it along.

===event_mouse_draw_handler===
''Mouse drag event handler''

If this is the LMB, accept the event, add the event's position to stroke_data, and the event's pressure to width_data, and call queue_draw (?).

If it's the RMB, accept the event to keep the context menu from appearing.

Any other button, pass the event along.

Dev:Source Outline

2006-04-25T23:48:16Z

SnapSilverlight: link-in

*template
*gtkmm
**about
**adjust_window
**app
**asyncrenderer
**audiocontainer
**autorecover
**canvasoptions
**canvasproperties
**canvastreestore
**canvasview
**cellrenderer_gradient
**cellrenderer_time
**cellrenderer_timetrack
**cellrenderer_value
**childrentree
**childrentreestore
**compview
**devicetracker
**dialog_color
**dialog_gradient
**dialog_keyframe
**dialog_preview
**dialogsettings
**dialog_setup
**dialog_soundselect
**dialog_tooloptions
**dialog_waypoint
**dockable
**dockbook
**dock_canvases
**dock_canvasspecific
**dock_children
**dock_curves
**dockdialog
**dock_history
**dock_info
**dock_keyframes
**dock_layergroups
**dock_layers
**dockmanager
**dock_metadata
**dock_navigator
**dock_params
**dock_timetrack
**duck
**duckmatic
**ducktransform_rotate
**ducktransform_scale
**ducktransform_translate
**eventkey
**event_layerclick
**event_mouse
**groupactionmanager
**historytreestore
**iconcontroler
**instance
**ipc
**keyframeactionmanager
**keyframetree
**keyframetreestore
**keymapsettings
**layeractionmanager
**layergrouptree
**layergrouptreestore
**layerparamtreestore
**layertree
**layertreestore
**metadatatreestore
**mod_mirror
***mod_mirror
***state_mirror
**mod_palette
***dock_palbrowse
***dock_paledit
***mod_palette
**module
**onemoment
**preview
**renddesc
**renderer_bbox
**renderer_canvas
**renderer_dragbox
**renderer_ducks
**renderer_grid
**renderer_guides
**renderer_timecode
**render
**smach
**state_bline
**state_circle
**state_draw
**state_eyedrop
**state_fill
**state_gradient
**statemanager
**state_normal
**state_polygon
**state_rectangle
**state_redraw
**state_rotate
**state_scale
**state_sketch
**state_smoothmove
**[[state_stroke]] - handles feedback and input for the drawing tools.
**state_width
**state_zoom
**toolbox
**valuelink
**widget_canvaschooser
**widget_coloredit
**widget_color
**widget_compselect
**widget_curves
**widget_defaults
**widget_distance
**widget_enum
**widget_filename
**widget_gradient
**widget_sound
**widget_time
**widget_timeslider
**widget_value
**widget_vector
**widget_waypoint
**widget_waypointmodel
**workarea
**workarearenderer
**zoomdial
*synfigapp
**action
**action_param
**action_system
**actions
***activepointadd
***activepointremove
***activepointset
***activepointsetoff
***activepointseton
***activepointsetsmart
***activepointsimpleadd
***blinepointtangentmerge
***blinepointtangentsplit
***canvasadd
***canvasremove
***canvasrenddescset
***colorset
***editmodeset
***gradientset
***groupaddlayers
***groupremove
***groupremovelayers
***grouprename
***keyframeadd
***keyframeduplicate
***keyframeremove
***keyframesetdelta
***keyframeset
***keyframewaypointset
***layeractivate
***layeradd
***layerduplicate
***layerencapsulate
***layerlower
***layermove
***layerparamconnect
***layerparamdisconnect
***layerparamset
***layerraise
***layerremove
***layersetdesc
***timepointscopy
***timepointsdelete
***timepointsmove
***valuedescconnect
***valuedescconvert
***valuedescdisconnect
***valuedescexport
***valuedesclink
***valuedescset
***valuenodeadd
***valuenodeconstset
***valuenodedynamiclistinsert
***valuenodedynamiclistinsertsmart
***valuenodedynamiclistloop
***valuenodedynamiclistremove
***valuenodedynamiclistremovesmart
***valuenodedynamiclistrotateorder
***valuenodedynamiclistunloop
***valuenodelinkconnect
***valuenodelinkdisconnect
***valuenoderemove
***valuenoderename
***valuenodereplace
***waypointadd
***waypointremove
***waypointset
***waypointsetsmart
***waypointsimpleadd
**blineconvert
**canvasinterface
**cvs
**editmode
**inputdevice
**instance
**main
**selectionmanager
**settings
**timegather
**uimanager
**value_desc

Dev:Source Glossary

2006-04-25T15:47:23Z

SnapSilverlight: Notes about stuff. Yeah.

===State===
Any tool in the toolbox, these define Synfig's [http://en.wikipedia.org/wiki/Mode_%28computer_interface%29 modes].

States can be transitory ( [[state stroke|state_stroke]] is responsible only for displaying/inputting the stroke as you draw it with another tool) or they can register themselves with the Toolbox and be 'sticky'.

===Action===
I don't know yet, but there's a lot of them! [[User:SnapSilverlight|Snap]]

===Events===
Synfig has an event system, using GTK's event system, I think. [[User:SnapSilverlight|Snap]]

Dev:Source Outline

2006-04-25T15:21:36Z

SnapSilverlight: Source files (compiled from a headers list)

*template
*gtkmm
**about
**adjust_window
**app
**asyncrenderer
**audiocontainer
**autorecover
**canvasoptions
**canvasproperties
**canvastreestore
**canvasview
**cellrenderer_gradient
**cellrenderer_time
**cellrenderer_timetrack
**cellrenderer_value
**childrentree
**childrentreestore
**compview
**devicetracker
**dialog_color
**dialog_gradient
**dialog_keyframe
**dialog_preview
**dialogsettings
**dialog_setup
**dialog_soundselect
**dialog_tooloptions
**dialog_waypoint
**dockable
**dockbook
**dock_canvases
**dock_canvasspecific
**dock_children
**dock_curves
**dockdialog
**dock_history
**dock_info
**dock_keyframes
**dock_layergroups
**dock_layers
**dockmanager
**dock_metadata
**dock_navigator
**dock_params
**dock_timetrack
**duck
**duckmatic
**ducktransform_rotate
**ducktransform_scale
**ducktransform_translate
**eventkey
**event_layerclick
**event_mouse
**groupactionmanager
**historytreestore
**iconcontroler
**instance
**ipc
**keyframeactionmanager
**keyframetree
**keyframetreestore
**keymapsettings
**layeractionmanager
**layergrouptree
**layergrouptreestore
**layerparamtreestore
**layertree
**layertreestore
**metadatatreestore
**mod_mirror
***mod_mirror
***state_mirror
**mod_palette
***dock_palbrowse
***dock_paledit
***mod_palette
**module
**onemoment
**preview
**renddesc
**renderer_bbox
**renderer_canvas
**renderer_dragbox
**renderer_ducks
**renderer_grid
**renderer_guides
**renderer_timecode
**render
**smach
**state_bline
**state_circle
**state_draw
**state_eyedrop
**state_fill
**state_gradient
**statemanager
**state_normal
**state_polygon
**state_rectangle
**state_redraw
**state_rotate
**state_scale
**state_sketch
**state_smoothmove
**state_stroke
**state_width
**state_zoom
**toolbox
**valuelink
**widget_canvaschooser
**widget_coloredit
**widget_color
**widget_compselect
**widget_curves
**widget_defaults
**widget_distance
**widget_enum
**widget_filename
**widget_gradient
**widget_sound
**widget_time
**widget_timeslider
**widget_value
**widget_vector
**widget_waypoint
**widget_waypointmodel
**workarea
**workarearenderer
**zoomdial
*synfigapp
**action
**action_param
**action_system
**actions
***activepointadd
***activepointremove
***activepointset
***activepointsetoff
***activepointseton
***activepointsetsmart
***activepointsimpleadd
***blinepointtangentmerge
***blinepointtangentsplit
***canvasadd
***canvasremove
***canvasrenddescset
***colorset
***editmodeset
***gradientset
***groupaddlayers
***groupremove
***groupremovelayers
***grouprename
***keyframeadd
***keyframeduplicate
***keyframeremove
***keyframesetdelta
***keyframeset
***keyframewaypointset
***layeractivate
***layeradd
***layerduplicate
***layerencapsulate
***layerlower
***layermove
***layerparamconnect
***layerparamdisconnect
***layerparamset
***layerraise
***layerremove
***layersetdesc
***timepointscopy
***timepointsdelete
***timepointsmove
***valuedescconnect
***valuedescconvert
***valuedescdisconnect
***valuedescexport
***valuedesclink
***valuedescset
***valuenodeadd
***valuenodeconstset
***valuenodedynamiclistinsert
***valuenodedynamiclistinsertsmart
***valuenodedynamiclistloop
***valuenodedynamiclistremove
***valuenodedynamiclistremovesmart
***valuenodedynamiclistrotateorder
***valuenodedynamiclistunloop
***valuenodelinkconnect
***valuenodelinkdisconnect
***valuenoderemove
***valuenoderename
***valuenodereplace
***waypointadd
***waypointremove
***waypointset
***waypointsetsmart
***waypointsimpleadd
**blineconvert
**canvasinterface
**cvs
**editmode
**inputdevice
**instance
**main
**selectionmanager
**settings
**timegather
**uimanager
**value_desc

Dev:Software roadmap

2006-04-25T05:59:07Z

SnapSilverlight: This is a specific source tweak rather than a feature request.

Dev:Wish list

2006-04-25T05:41:04Z

SnapSilverlight: AUto-link

Got a great idea for a new feature, just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&atid=757419 feature requests tracker].
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----
* '''Auto-link option in [[Draw tool]]''' so that you can draw a line, and have its endpoint automatically link to a duck - or if Auto-connect is off, you can get a line object linked to the end of another line object.

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]] (could be a bit of 3, and much more of 4)''' — the ability to save as/in the Free/Open MNG (.mng) format [http://libpng.org/pub/mng/]

* '''Layer Convert''' <strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)". See [[UI Reloaded]] for progress on this.

* '''Feedback for [[smooth move tool]]''' (3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

* '''Image filmstrip import''' (2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer.

* '''Bitmap Objects and Backgrounds''' <s>(5)</s>(0) — Simmilar to the above but for more than for just purely bitmap based animations. I feel that the to do production quality animations you need production quality backgrounds, foregrounds, and effects. Many of which are very difficult or even impossible to achieve with vector based graphics. I suggest support for alpha transparencies as well to make this truely useful. An example of how this could be used would be a bitmap background and a bitmap foreground that can be panned as the scene moves.
::''Static bitmaps with alpha are possible already, if that is what you mean. I have just documented it in [[How do I]]. [[User:Maxy|Maxy]] 06:35, 9 Apr 2006 (PDT)''

* '''Align function''' (3) — Align objects at a common border (as in Inkscape)

* '''Improved SVG import''' (4) — Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)

Dev:Gentoo Ebuilds

2006-03-08T02:21:49Z

SnapSilverlight: Updated Subversion ebuilds, took out the essentially-unwritten ebuilds for specific-versions.

We're working on ebuild files for the Gentoo operating system here. To use this page directly with Gentoo, you need to know how Portage works. Specifically:
* Create a Portage overlay so these ebuilds won't be clobbered by an emerge sync
* Cut out each ebuild and put it in the proper place in the overlay.
* Find mistakes in the ebuilds, and post fixes here

= Specific-version ebuilds in Gentoo's BugZilla =

'''synfig-studio''' (-> /overlay/media-gfx/synfig-studio)

http://bugs.gentoo.org/show_bug.cgi?id=111279

'''synfig''' (-> /overlay/media-gfx/synfig)

http://bugs.gentoo.org/show_bug.cgi?id=111278

'''ETL''' (-> /overlay/dev-cpp/ETL)

http://bugs.gentoo.org/show_bug.cgi?id=111277

= Short howto =
1. make digests in your '''overlay''' directory i.e.:
'''ebuild''' /overlay/media-gfx/synfig-studio/synfig-studio-0.61.01.ebuid '''digest'''
...

2. this goes in the '''/etc/portage/package.use'''
media-gfx/synfig ffmpeg freetype imagemagick libdv openexr
media-gfx/synfig-studio fmod

3. emerge -av synfig-studio
=SVN Ebuilds=
==dev-cpp/ETL-svn==
'''''Warning: incomplete ebuild!'''''
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=""

# svn co http://svn.voria.com/code/ETL/trunk/ ETL
# ./bootstrap
# ./configure
# sudo make install
</pre>

==media-gfx/synfig-svn==
<pre>
DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE="tiff jpeg png freetype fontconfig openexr ffmpeg"

DEPEND="dev-cpp/libxmlpp
dev-libs/libsigc++
sys-devel/libtool
png? ( >=media-libs/libpng )
tiff? ( >=media-libs/tiff )
jpeg? ( >=media-libs/jpeg )
imagemagick? ( >=media-gfx/imagemagick )
freetype? ( >=media-libs/freetype )
fontconfig? ( >=media-libs/fontconfig )
openexr? ( >=media-libs/openexr )
ffmpeg? ( >=media-video/ffmpeg )

virtual/ETL"

PROVIDE="virtual/synfig"

ESVN_REPO_URI="http://svn.voria.com/code/synfig-core/trunk"
ESVN_PROJECT="${PN}"

inherit subversion

src_compile() {
./bootstrap
econf \
$(use_enable ffmpeg) \
$(use_enable libdv) \
$(use_enable imagemagick) \
$(use_enable ffmpeg libavcodec) \
$(use_enable freetype) \
|| die
emake || die
}

src_install() {
make DESTDIR="${D}" install || die
}
</pre>

==media-gfx/synfig-studio-svn==
<pre>
DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/gtkmm-2.4
virtual/synfig
!media-gfx/synfig-studio"

ESVN_REPO_URI="http://svn.voria.com/code/synfig-studio/trunk"
ESVN_PROJECT="${PN}"

inherit subversion

src_compile() {
./bootstrap
econf || die
emake || die
}

src_install() {
make DESTDIR="${D}" install || die
}
</pre>

Dev:Wish list

2006-02-01T07:13:33Z

SnapSilverlight:

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' <strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Feedback for [[smooth move tool]]''' (3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

* '''Image filmstrip import''' (2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer.

* '''Align function''' (3) — Align objects at a common border (as in Inkscape)

Dev talk:Software roadmap

2006-01-30T04:47:06Z

SnapSilverlight: Linking HIG o/~

I'd like to work on improving the UI and making it comply to the [http://developer.gnome.org/projects/gup/hig/ HIG].

Progress so far:

* [http://i36.photobucket.com/albums/e27/droden/software/synfig/abb7847a.png] Canvas Properties Dialog
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/b25cdfb6.png] Canvas Properties Dialog, Tab 2
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/e504b02a.png] Canvas Properties Dialog, Tab 3
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/c1909071.png] Render Dialog
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/ac411a1c.png] Preview Options
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/724a0495.png] Waypoint Editor
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/7f0360d2.png] Canvas Options Dialog
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/a840f627.png] Canvas Options Dialog, Tab 2
* [http://i36.photobucket.com/albums/e27/droden/software/synfig/6bb96bb7.png] Canvas Options Dialog, Tab 3

Any suggestions or comments? --[[User:Bombe|Bombe]] 14:40, 29 Jan 2006 (PST)

Dev:Wish list

2006-01-27T17:04:15Z

SnapSilverlight: Update flock tool request description

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' <strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Feedback for [[smooth move tool]]''' (3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

* '''Image filmstrip import''' (2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:Snap|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Dev:Wish list

2006-01-24T21:02:54Z

SnapSilverlight:

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' <strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;) ''(This is covered by the [[smooth move tool]] but the interface for it really needs to be revamped.)'' [[User:SnapSilverlight|Snap]] 13:02, 24 Jan 2006 (PST)

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

* '''Image filmstrip import''' (2) — Allow import of a series of images (TGA, etc) as frames of an animation, on a layer.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:Snap|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Dev:Gentoo Ebuilds

2006-01-24T21:00:25Z

SnapSilverlight: Err, oops.

We're working on ebuild files for the Gentoo operating system here. To use this page directly with Gentoo, you need to know how Portage works. Specifically:
* Create a Portage overlay so these ebuilds won't be clobbered by an emerge sync
* Cut out each ebuild and put it in the proper place in the overlay.
* Find mistakes in the ebuilds, and post fixes here

'''''These ebuilds are not yet complete! Only use if you know what you're doing and are prepared to fix them!'''''

===dev-cpp/ETL-0.04.07==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

# ./bootstrap
# ./configure
# sudo make install
</pre>

===media-gfx/synfig-0.61.04==
<pre>
DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="dev-cpp/libxmlpp
dev-libs/libsigc++
>=dev-cpp/ETL-0.04.07"
</pre>

===media-gfx/synfig-studio-0.61.04==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/gtkmm-2.4
>=media-gfx/synfig-${PV}"
</pre>

==dev-cpp/ETL-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=""

# svn co http://svn.voria.com/code/ETL/trunk/ ETL
# ./bootstrap
# ./configure
# sudo make install
</pre>

==media-gfx/synfig-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="dev-cpp/libxmlpp
dev-libs/libsigc++
dev-cpp/ETL-svn
!dev-cpp/ETL"
</pre>

==media-gfx/synfig-studio-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/gtkmm-2.4
media-gfx/synfig-svn
!media-gfx/synfig"
</pre>

Dev:Gentoo Ebuilds

2006-01-24T18:59:59Z

SnapSilverlight: Adding listed deps.

We're working on ebuild files for the Gentoo operating system here. To use this page directly with Gentoo, you need to know how Portage works. Specifically:
* Create a Portage overlay so these ebuilds won't be clobbered by an emerge sync
* Cut out each ebuild and put it in the proper place in the overlay.
* Find mistakes in the ebuilds, and post fixes here

'''''These ebuilds are not yet complete! Only use if you know what you're doing and are prepared to fix them!'''''

===dev-cpp/ETL-0.04.07==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""
</pre>

===media-gfx/synfig-0.61.04==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="dev-cpp/libxmlpp
dev-libs/libsigc++
>=dev-cpp/ETL-0.04.07"
</pre>

===media-gfx/synfig-studio-0.61.04==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/gtkmm-2.4
>=media-gfx/synfig-${PV}"
</pre>

==dev-cpp/ETL-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=""
</pre>

==media-gfx/synfig-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="dev-cpp/libxmlpp
dev-libs/libsigc++
dev-cpp/ETL-svn
!dev-cpp/ETL"
</pre>

==media-gfx/synfig-studio-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/gtkmm-2.4
media-gfx/synfig-svn
!media-gfx/synfig"
</pre>

Dev:Gentoo Ebuilds

2006-01-24T18:52:32Z

SnapSilverlight: Let's make some ebuilds that people can use!

We're working on ebuild files for the Gentoo operating system here. To use this page directly with Gentoo, you need to know how Portage works. Specifically:
* Create a Portage overlay so these ebuilds won't be clobbered by an emerge sync
* Cut out each ebuild and put it in the proper place in the overlay.
* Find mistakes in the ebuilds, and post fixes here

'''''These ebuilds are not yet complete! Only use if you know what you're doing and are prepared to fix them!'''''

===dev-cpp/ETL-0.04.07==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""
</pre>

===media-gfx/synfig-0.61.04==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=dev-cpp/ETL-0.04.07"
</pre>

===media-gfx/synfig-studio-0.61.04==
<pre>
MY_P=${PN/-/}-${PV/_p/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=">=media-gfx/synfig-${PV}"
</pre>

==dev-cpp/ETL-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (support libraries, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND=""
</pre>

==media-gfx/synfig-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (core engine, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="dev-cpp/ETL-svn
!dev-cpp/ETL"
</pre>

==media-gfx/synfig-studio-svn==
<pre>
inherit subversion

DESCRIPTION="Synfig: Film-Quality Vector Animation (main UI, SVN-sources)"
HOMEPAGE="http://www.synfig.com/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~x86"
IUSE=""

DEPEND="media-gfx/synfig-svn
!media-gfx/synfig"
</pre>

Dev:Build Instructions

2006-01-24T18:13:12Z

SnapSilverlight: OS-specific links and such.

Hey you! Do you want access to bleeding-edge Synfig? Well, I have good news. Anonymous access to the Synfig subversion repository for Synfig is now enabled! Here are the URLs to the respective repositories:

* http://svn.voria.com/code/synfig-core/
* http://svn.voria.com/code/synfig-studio/
* http://svn.voria.com/code/ETL/

==System-Specific==
The later sections of this page can be used for any system, but the following links and wiki pages offer some system-specific help:
* Mac OSX
* Linux
** [[Gentoo Ebuilds|Gentoo]]
** RedHat
** Debian
* Windows
* Irix (SGI)

= ETL =
ETL is a template library, there is nothing to build really, it just needed to be installed.
# svn co http://svn.voria.com/code/ETL/trunk/ ETL
# ./bootstrap
# ./configure
# sudo make install

= synfig-core =
Requires the libraries
* libxml++
* libsigc++

# svn co http://svn.voria.com/code/synfig-core/trunk/ synfig-core
# ./bootstrap
# ./configure
# make
# sudo make install

= synfig-studio =
Requires the library:
* gtkmm >= 2.4

# svn co http://svn.voria.com/code/synfig-studio/trunk/ synfig-studio
# ./bootstrap
# ./configure
# make
# sudo make install

Doc:Getting Started

2006-01-18T03:50:22Z

SnapSilverlight: /* The user interface */

== Introduction ==

Synfig, like most every other competent graphics program, breaks down individual elements of a [[Canvas]] into [[Layers]]. However, it differs from other programs in two major ways:

# An individual layer in Synfig usually represents a single "Primitive". ie: A single region, an outline of a region, an imported JPEG, etc... This allows you to have a great deal of flexibility and control. It is not uncommon for a composition to have hundreds of layers(organized into a hierarchy for artist sanity of course).
# A layer can not only composite information on top of the image below it, but also distort and/or modify it in some other way. In this sense, Synfig Layers act much like filters do in Adobe Photoshop or the GIMP. For example, we have a [[Blur Layer]], [[Radial Blur Layer]], [[Spherical Distortion Layer]], [[color-correct layer]], [[bevel layer]], etc...

Each layer has a set of parameters which determine how it behaves. When you click on a layer (either in the canvas window, or in the [[Layer Dialog]]), you will see its parameters in the [[Params Dialog]].

Synfig Studio has an autorecover feature. If it crashes, even if the current file has not been saved, it will not lose more than 5 minutes of work. At restart it will automatically prompt the user to recover the unsaved changes. Unfortunately history isn't recovered yet. That feature comes later.

One thing you may notice is that Synfig Studio is SLOW, making it practically unusable on hardware that is over 3 years old. The biggest reason for this is that all of the color calculations are done in floating point--because Synfig Studio was built from the ground up with High-Dynamic-Range Imaging in mind. HOWEVER, this will not be the case forever.

I have some fairly major re-implementations and optimizations that I am about to implement that should quite dramatically improve the performance of Synfig on all platforms. My goal is not a 200% speed increase, my goal is at least a 2000% speed increase. With the optimizations that I plan to implement, I will be able to pipeline operations in such a way that this performance improvement can be realized. It should also pave the way to hardware acceleration using todays powerful graphics processors, which should yield further performance improvements measurable in orders of magnitude.

== The user interface ==

When you start Synfig Studio, it will display a splash graphic and boot itself up. After it finishes loading, you should see three windows. The window in the upper left is the [[toolbox]]. This is where you can open files, change [[tools]], etc. You'll notice that most of the buttons are greyed out--because there is no file open yet.

The other two windows (one on the bottom, and one to the right) are customizable [[dock dialogs]]. You can rearrange the contents of these however you wish by simply dragging the tab to where you want it. You can even create a new dock dialog by dragging a [[dock tab|tab]] out of the dock dialog it was inside of.

If you ever accidently close a [[dock tab]]s (by dragging it out of the dock dialog, and closing the new dock dialog that gets created), no worries. Simply goto the toolbox and goto "File->Dialogs", and then click on the name of the dialog you need.

There are a lot of [[dock tab]]s. If you have no idea what a dock tab does, simply hold your mouse over its icon and a tooltip will pop up describing the name of the tab.

Here are some of the more important ones:

* [[Layers Dialog]] - This tab shows you the layer hierarchy for the currently selected canvas. It also allows you to manipulate these layers.
* [[Params Dialog]] - This tab will show you the parameters of the currently selected layer, (OR, if multiple layers are selected, it shows you only the parameters that the selected layers have in common)
* [[Categorical Help#Synfig Dialogs|Tool Options Dialog]] - Shows you any options specific to the currently selected tool
* [[Navigator|Navigator]] - Shows you a thumbnail of what the currently selected Canvas looks like. You can also zoom in and move the focus around with this tab.
* [[History Dialog]] - Shows you the history stack for the current composition. You can also edit the actions in history.

If you click the "new composition" button in the toolbox, a new [[composition]] will be opened and the [[canvas properties dialog]] will appear.

The canvas properties dialog is a mess, I know. I'll have it re-designed into something much more comprehendible in the next few days. For now, ignore the "Image Area" and "Locks and Links" sections.

If you click OK, the canvas properties dialog will disappear and you will see the [[Canvas window]]. This window represents the [[Root Canvas]], not that that means much to you at the moment, but that's OK--I'm just trying to show you around.

In the upper left corner of the Canvas Window, you'll see a button with a [[Canvas Menu Caret|caret]] If you click on this button, the [[Canvas Menu Caret|canvas window menu]] will pop up. (As an aside, if you right click in the canvas area and there is not a [[layer]] under the mouse position, this menu will also appear) So now you know where the menu is in the Canvas Window. Good. Everything else should be pretty self-explanatory in the Canvas Window. (Explanations on the menu stuff is to come in a sec)

== First steps ==

Lets create something so that we can tweak with it. Now that you have a new composition open and the properties dialog is out of the way, go over to the toolbox and click on the [[circle tool]](If you don't know which one it is, just mouse over them until you find the one with the tooltip that says "circle").

The second you click on the circle tool, you should notice that the [[tool options tab]] changed. But we'll get to that later.

With the circle tool selected, you can now create circles in the [[canvas window]]. This pretty much works exactly as you might expect it to. Go ahead and create two (or more, if you fancy) circles.

Now go back to the toolbox and click on the [[normal tool]] (the blue circle with the arrow on it). After you do this, click on one of your circles. You will then see a [[bounding box]](which is kinda useless at this point in time, but I digress), a green dot at the center, and a cyan dot on the radius. Those dots are called ''[[duck]]s''. If you want to modify the circle, grab a duck and drag it around. Easy!

So you can select a [[layer]] by clicking on it. If you want to select more than one layer, hold down CONTROL while you are clicking--this works in both the [[canvas window]] and the [[layer tab]]. Try it!

You can also select multiple ducks. You can do this in several ways. First, you can hold down CONTROL and individually click the ducks that you want selected, but this can be tedious. However, there is a much faster method--just create a [[selection box]] by clicking the mouse and dragging it over the area of ducks that you want selected.

Go ahead and select two circles, and select all of their ducks. With several ducks selected, moving one duck will move all of the ducks. This behavior is dependent on the [[normal tool]]. Thus, a more descriptive name for this tool might have been the "move" or "translate" tool.

The [[rotate tool|Rotate]] and [[Scale tool]]s work much like the [[Normal tool]], except in the case where you have multiple ducks selected. It is much easier to just try it than read about it. Select a few circles, select all of their ducks, and try using the rotate and scale tools.

Note that, unlike the normal tool, the other duck manipulation tools DO have options associated with them. If a particular tool isn't doing what you want, take a look in the [[tool options tab]] to see if it is set up like you want it.

== Linking ==

Now lets try [[linking]]. Lets say we always want these two circles to be the same size. Select two circles, and then select both of their Radius ducks(the cyan dot). Then right click on either duck and a menu will pop up. Click on "Link". Boom. The parameters are linked together. You can prove it to yourself by selecting just one of the circles and changing its radius--the other one will change as well. Neat stuff, eh?

Linking is a fundamental concept in Synfig. You can create links not only between ducks, but also between parameters as well by selecting multiple layers, right clicking on the parameter in the param tab, and selecting "Link".

DIGRESSION: This is how [[outline layer|outlines]] are attached to their [[region layer|regions]]—but I'm getting ahead of myself. At the moment, the fundamental power and flexibility of linking in Synfig Core is beyond what Synfig Studio currently allows for. This will change in the future. Anyway, back on track...

Lets say you want one of the circles to be a different color. If you look in the toolbox below the tools, you'll see the foreground/background color selector, the outline width selector, and some other stuff like the default blend method and gradient. The foreground/background color widget works exactly as you might expect--you can click on the foreground color, and a modest color chooser will appear. Now to can change the color pretty easily.

But sometimes you just want to click on a color and go. This is where the palette editor tab comes in. It's functionality isn't quite 100% yet (ie: saving and loading custom palettes hasn't been implemented yet), but the default palette is pretty decent. Click on the Palette editor tab and have a look--it's the one with the palette-ish looking icon. Clicking on colors in here will immediately change the default foreground color.

That's all great, but we still haven't changed the color of the circle. There are two ways to do this. The first way is that you select the circle layer you want to modify, goto the params tab and double click on the color parameter--a color selector dialog shows up and you just tweak away. But lets say you already got the color you wanted selected as the default foreground color. Easy. Just click on the "Fill tool" from the toolbox, and then click on the circle in the canvas window. Boom. Circle changes color. This works with more than just circles, but we'll get to that in a sec.

Try playing around with the circles for a bit. Muck around with the parameters, and see what happens. To get you started, play around with feather a bit.

== Digging deeper ==

Of course, so far you just found out how to use the basic features of Synfig Studio but not how you animate a drawing. This is covered in the [[Animation_Basics|next tutorial]].

Doc:Getting Started

2006-01-18T03:44:50Z

SnapSilverlight: /* Introduction */

== Introduction ==

Synfig, like most every other competent graphics program, breaks down individual elements of a [[Canvas]] into [[Layers]]. However, it differs from other programs in two major ways:

# An individual layer in Synfig usually represents a single "Primitive". ie: A single region, an outline of a region, an imported JPEG, etc... This allows you to have a great deal of flexibility and control. It is not uncommon for a composition to have hundreds of layers(organized into a hierarchy for artist sanity of course).
# A layer can not only composite information on top of the image below it, but also distort and/or modify it in some other way. In this sense, Synfig Layers act much like filters do in Adobe Photoshop or the GIMP. For example, we have a [[Blur Layer]], [[Radial Blur Layer]], [[Spherical Distortion Layer]], [[color-correct layer]], [[bevel layer]], etc...

Each layer has a set of parameters which determine how it behaves. When you click on a layer (either in the canvas window, or in the [[Layer Dialog]]), you will see its parameters in the [[Params Dialog]].

Synfig Studio has an autorecover feature. If it crashes, even if the current file has not been saved, it will not lose more than 5 minutes of work. At restart it will automatically prompt the user to recover the unsaved changes. Unfortunately history isn't recovered yet. That feature comes later.

One thing you may notice is that Synfig Studio is SLOW, making it practically unusable on hardware that is over 3 years old. The biggest reason for this is that all of the color calculations are done in floating point--because Synfig Studio was built from the ground up with High-Dynamic-Range Imaging in mind. HOWEVER, this will not be the case forever.

I have some fairly major re-implementations and optimizations that I am about to implement that should quite dramatically improve the performance of Synfig on all platforms. My goal is not a 200% speed increase, my goal is at least a 2000% speed increase. With the optimizations that I plan to implement, I will be able to pipeline operations in such a way that this performance improvement can be realized. It should also pave the way to hardware acceleration using todays powerful graphics processors, which should yield further performance improvements measurable in orders of magnitude.

== The user interface ==

When you start Synfig Studio, it will display a splash graphic and boot itself up. After it finishes loading, you should see three windows. The window in the upper left is the [[toolbox]]. This is where you can open files, change [[tools]], etc. You'll notice that most of the buttons are greyed out--because there is no file open yet.

The other two windows (one on the bottom, and one to the right) are customizable [[dock dialogs]]. You can rearrange the contents of these however you wish by simply dragging the tab to where you want it. You can even create a new dock dialog by dragging a [[dock tab|tab]] out of the dock dialog it was inside of.

If you ever accidently close a [[dock tab]]s (by dragging it out of the dock dialog, and closing the new dock dialog that gets created), no worries. Simply goto the toolbox and goto "File->Dialogs", and then click on the name of the dialog you need.

There are a lot of [[dock tab]]s. If you have no idea what a dock tab does, simply hold your mouse over its icon and a tooltip will pop up describing the name of the tab.

Here are some of the more important ones:

* [[Layers Tab|Layers]] - This tab shows you the layer hierarchy for the currently selected canvas. It also allows you to manipulate these layers.
* [[Paramss Tab|Params]] - This tab will show you the parameters of the currently selected layer, (OR, if multiple layers are selected, it shows you only the parameters that the selected layers have in common)
* [[Tool Options Tab|Tool Options]] - Shows you any options specific to the currently selected tool
* [[Navigator Tab|Navigator]] - Shows you a thumbnail of what the currently selected Canvas looks like. You can also zoom in and move the focus around with this tab.
* [[History Tab||History]] - Shows you the history stack for the current composition. You can also edit the actions in history.

If you click the "new composition" button in the toolbox, a new [[composition]] will be opened and the [[canvas properties dialog]] will appear.

The canvas properties dialog is a mess, I know. I'll have it re-designed into something much more comprehendible in the next few days. For now, ignore the "Image Area" and "Locks and Links" sections.

If you click OK, the canvas properties dialog will disappear and you will see the [[Canvas window]]. This window represents the [[Root Canvas]], not that that means much to you at the moment, but that's OK--I'm just trying to show you around.

In the upper left corner of the Canvas Window, you'll see a button with an arrow. If you click on this button, the canvas window menu will pop up. (As an aside, if you right click in the canvas area and there is not a [[layer]] under the mouse position, this menu will also appear) So now you know where the menu is in the Canvas Window. Good. Everything else should be pretty self-explanatory in the Canvas Window. (Explanations on the menu stuff is to come in a sec)

== First steps ==

Lets create something so that we can tweak with it. Now that you have a new composition open and the properties dialog is out of the way, go over to the toolbox and click on the [[circle tool]](If you don't know which one it is, just mouse over them until you find the one with the tooltip that says "circle").

The second you click on the circle tool, you should notice that the [[tool options tab]] changed. But we'll get to that later.

With the circle tool selected, you can now create circles in the [[canvas window]]. This pretty much works exactly as you might expect it to. Go ahead and create two (or more, if you fancy) circles.

Now go back to the toolbox and click on the [[normal tool]] (the blue circle with the arrow on it). After you do this, click on one of your circles. You will then see a [[bounding box]](which is kinda useless at this point in time, but I digress), a green dot at the center, and a cyan dot on the radius. Those dots are called ''[[duck]]s''. If you want to modify the circle, grab a duck and drag it around. Easy!

So you can select a [[layer]] by clicking on it. If you want to select more than one layer, hold down CONTROL while you are clicking--this works in both the [[canvas window]] and the [[layer tab]]. Try it!

You can also select multiple ducks. You can do this in several ways. First, you can hold down CONTROL and individually click the ducks that you want selected, but this can be tedious. However, there is a much faster method--just create a [[selection box]] by clicking the mouse and dragging it over the area of ducks that you want selected.

Go ahead and select two circles, and select all of their ducks. With several ducks selected, moving one duck will move all of the ducks. This behavior is dependent on the [[normal tool]]. Thus, a more descriptive name for this tool might have been the "move" or "translate" tool.

The [[rotate tool|Rotate]] and [[Scale tool]]s work much like the [[Normal tool]], except in the case where you have multiple ducks selected. It is much easier to just try it than read about it. Select a few circles, select all of their ducks, and try using the rotate and scale tools.

Note that, unlike the normal tool, the other duck manipulation tools DO have options associated with them. If a particular tool isn't doing what you want, take a look in the [[tool options tab]] to see if it is set up like you want it.

== Linking ==

Now lets try [[linking]]. Lets say we always want these two circles to be the same size. Select two circles, and then select both of their Radius ducks(the cyan dot). Then right click on either duck and a menu will pop up. Click on "Link". Boom. The parameters are linked together. You can prove it to yourself by selecting just one of the circles and changing its radius--the other one will change as well. Neat stuff, eh?

Linking is a fundamental concept in Synfig. You can create links not only between ducks, but also between parameters as well by selecting multiple layers, right clicking on the parameter in the param tab, and selecting "Link".

DIGRESSION: This is how [[outline layer|outlines]] are attached to their [[region layer|regions]]—but I'm getting ahead of myself. At the moment, the fundamental power and flexibility of linking in Synfig Core is beyond what Synfig Studio currently allows for. This will change in the future. Anyway, back on track...

Lets say you want one of the circles to be a different color. If you look in the toolbox below the tools, you'll see the foreground/background color selector, the outline width selector, and some other stuff like the default blend method and gradient. The foreground/background color widget works exactly as you might expect--you can click on the foreground color, and a modest color chooser will appear. Now to can change the color pretty easily.

But sometimes you just want to click on a color and go. This is where the palette editor tab comes in. It's functionality isn't quite 100% yet (ie: saving and loading custom palettes hasn't been implemented yet), but the default palette is pretty decent. Click on the Palette editor tab and have a look--it's the one with the palette-ish looking icon. Clicking on colors in here will immediately change the default foreground color.

That's all great, but we still haven't changed the color of the circle. There are two ways to do this. The first way is that you select the circle layer you want to modify, goto the params tab and double click on the color parameter--a color selector dialog shows up and you just tweak away. But lets say you already got the color you wanted selected as the default foreground color. Easy. Just click on the "Fill tool" from the toolbox, and then click on the circle in the canvas window. Boom. Circle changes color. This works with more than just circles, but we'll get to that in a sec.

Try playing around with the circles for a bit. Muck around with the parameters, and see what happens. To get you started, play around with feather a bit.

== Digging deeper ==

Of course, so far you just found out how to use the basic features of Synfig Studio but not how you animate a drawing. This is covered in the [[Animation_Basics|next tutorial]].

Params Panel

2006-01-17T21:35:46Z

SnapSilverlight: Initial commit. Unfinished.

== Introduction ==

The Params Dialog is in many ways the heart of the Synfig interface. This is where all the parameters of the layers you create are edited, and in some less obvious ways,

The layout of the Params Dialog is quite simple - it is simply a two column list

The first column, named Param, simply is an expandable tree listing of the parameters of the selected layer. Most layers do not have many nested parameters, with the exception of the Vertex List on most [[Geometry Layer Category|Geometry layers]].

The second column, ValueBase, is where the data for each of the params are listed. Several different types of data can be shown here.

==Params and Layers==
An interesting feature of the Params Dialog is that - when you select two or more layers in the [[Layers Dialog]], the Params Dialog will only show the parameters that are *shared* between the layers. When the dialog is in this state, context-clicking on the parameters will allow parameters to be linked between the two layers.
''(write more)''

==Default Params==
There are three params that are shared between nearly every layer:
* [[Z Depth Parameter|Z Depth]]
* [[Amount Parameter|Amount]]
* [[Blend Method]]

Dev:Wish list

2006-01-17T20:32:52Z

SnapSilverlight: Comment for Layer Hide, revision of Layer Convert.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' <strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter. ''(This feature request is a refactoring of the [[Amount Parameter]])''

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:Snap|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Dev:Wish list

2006-01-17T20:19:34Z

SnapSilverlight: BBQ pulled duck.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter.

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Intuitive tangent modification''' (3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:Snap|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Doc:How Do I

2006-01-17T06:17:47Z

SnapSilverlight: I want a TOC now, not in another How Do I!

Feel free to add your own questions here. Or put them on the [[Wiki Wish List]].

__TOC__

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Dialog]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Dialog]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Inline Canvas]]. (and any other layers in that section).

==Show or hide a layer, or fade the effect of a blur?==
In the [[Params Dialog]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? == (Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Create the [[Outline Layer|outline]] you want to fill.
*# From the [[Layer Menu]] (either context-click on the [[Layers Dialog]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]]
*# Make '''sure''' that the [[Region Layer]] is above the [[Outline Layer]] in the [[Layers Dialog]] - this affects which layer's shape remains after the link.
*# Select both layers in the [[Layers Dialog]] This will display only the parameters shared by both layers in the [[Params Dialog]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[bline tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[bline tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.

Doc:How Do I

2006-01-17T06:15:38Z

SnapSilverlight: darco explained how to link layer shapes. Yay!

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Dialog]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Dialog]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Inline Canvas]]. (and any other layers in that section).

==Show or hide a layer, or fade the effect of a blur?==
In the [[Params Dialog]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? == (Requested by [[User:Karlb|Karlb]])

There are several options:
* The easiest way is to link a new region layer to the outline's shape.
*# Create the [[Outline Layer|outline]] you want to fill.
*# From the [[Layer Menu]] (either context-click on the [[Layers Dialog]] or use the [[Canvas Menu Caret]]) create a new [[Region Layer]]
*# Make '''sure''' that the [[Region Layer]] is above the [[Outline Layer]] in the [[Layers Dialog]] - this affects which layer's shape remains after the link.
*# Select both layers in the [[Layers Dialog]] This will display only the parameters shared by both layers in the [[Params Dialog]].
*# Context-click on the [[Vertices Parameter]], and select [[Linking|Link]].
*# The [[Region Layer]] will snap to the shape of the [[Outline Layer]].
* When you create an [[Outline Layer|outline]] with the [[bline tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[bline tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. If you want a region that depends on multiple outline layers, this is really your only choice for now.

Dev:Wish list

2006-01-14T03:57:46Z

SnapSilverlight: Still finding hidden stuff that negates wishlist items.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter.

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:Snap|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

User:SnapSilverlight/myskin.css

2006-01-12T21:44:07Z

SnapSilverlight: Testing user-space CSS skins.

.nothinghereyet {}

New Layer Defaults

2006-01-12T20:55:20Z

SnapSilverlight: Initial commit

==Brush Colors==
This section of the palette contains two large overlapping squares - the one in front is the Foreground Color, the one in back is the Background Color. When you are creating a layer of only one color, the foreground color is always used. When you create a [[Region Layer|region]] and an [[Outline Layer|outline]] simultaneously, the region is given the background color. The [[New Layer Defaults#Current Gradient|current gradient]] fill defaults to dynamically between these two colors. Clicking either will bring up the [[Colors Dialog]] to select a new color.

In addition to these two controls, there are two smaller controls located in the corners between them.

The '''arrows''' on the upper-right side swap the foreground and background colors.

The letter '''R''' on the lower left reverts the foreground and background colors to their default of black on white.
==Brush Size==
Sets the size of the line for new [[Outline Layers]]. If you are using the [[draw tool]], this sets the maximum size that the line will be based on pressure sensitivity.
==Default Blend Method==
Sets the [[Blend Method]] for new layers. Defaults to [[Blend Method#Composite|Composite]].
==Default Opacity==
Sets the [[Amount Parameter]] for new layers. Defaults to 1.00 (Completely opaque)
==Current Gradient==
Used by the [[bline tool]] when creating a new [[Curve Gradient]] layer. Also used by all [[Gradient Layer Category|Gradient layers]] as their fill. This defaults to a gradient between the foreground color and background color. Clicking this will bring up the [[Gradient Editor Dialog]]
==Default Interpolation==
Sets the default [[Interpolation]] of new keyframes. Initially this is set to [[Interpolation#TCB|TCB]].

Wiki Wish List

2006-01-12T20:21:30Z

SnapSilverlight: o/~ Sometimes you look like a wiki....sometimes you don't...o/~

If you've come here looking for help, and you've found its documentation hasn't been written yet, post it here. That way, we'll know what to work on documenting next!

If you're looking for something to write, and nothing here strikes your fancy, take a look at [[Special:Wantedpages|Wanted Pages]] in the [[Special:Specialpages|Special Pages]] section.

(If, however, you're looking for a feature that you need in Synfig but aren't sure exists, consider listing it on the [[Wish list]] instead.)

* '''Animation Namespace''' — Should be a seperate namespace for discussing animation terminology and technique, and such, independent from description of Synfig features. For example, the "Twelve Principles Of Animation" don't really have anything to do with how to use Synfig's interface, but have everything to do with things being created in Synfig.

* '''MediaWiki's TeX math rendering''' system isn't turned on. There've been a few times I've wanted to use it.

* '''MediaWiki Skin''' matched to www.synfig.com, or specific to this wiki. (See the variation used on [http://www.tango-project.org/ http://www.tango-project.org/] for an example of what can be done.)

Dev:Wish list

2006-01-12T20:15:28Z

SnapSilverlight: I want to use synfig with friends! Also rewriting the Interface wish, again.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter.

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''[http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance]''' — This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)"

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Networkability''' (2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option.

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. (added as this is a standard request/feature for a graphics or video app)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:SnapSilverlight|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:SnapSilverlight|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Doc:How Do I

2006-01-12T19:09:50Z

SnapSilverlight: Answering Karlb

== Apply a gradient to an object instead of the entire canvas? ==

# Create the region you want to fill with a gradient, and the gradient layer, if you haven't already.
# Make sure that the gradient layer is above the region layer in the [[Layers Dialog]].
# Select both layers, right click, and select [[Encapsulate]].
# Expand the new [[Inline Canvas]] layer if it's not already, and select your gradient layer.
# In the [[Params Dialog]] select the [[Blend Method]] parameter, and choose [[Blend Method#Onto|Onto]] from the drop-down menu.

The gradient will clip to the visible area of the region below it inside the [[Inline Canvas]]. (and any other layers in that section).

==Show or hide a layer, or fade the effect of a blur?==
In the [[Params Dialog]], look for an option labeled [[Amount Parameter|Amount]] - this controls how much of the blended result of the layer is composited with the blend of the layers beneath it.

In other words, for a typical layer, this will 'fade it out'. For a [[Blur Layer]] set to "[[Blend Method#Straight|Straight]]", this will fade ''between'' the blurred version and the unblurred version of the canvas. If you want it to become less blurry, adjust the [[Blur Layer#Size|Blur Layer's 'size' parameter]].

== Fill an outline? == (Requested by [[User:Karlb|Karlb]])

We hope there'll be an easy answer to this as Synfig is revised! There are a couple solutions on the [[Wish List]]. As for now:
* When you create an [[Outline Layer|outline]] with the [[bline tool]] that you intend to be a filled area as well, make sure you select the Fill checkbox in the [[bline tool#Options|tool options dialog]]. Obviously, this doesn't help much if you realise later that you needed a fill here.
* If you are using the [[draw tool]], there is a button at the bottom of the [[draw tool#Options|tool options dialog]] labeled "Fill Last Stroke", which creates a new [[Region Layer]] and links its shape to the previously drawn outline. Unfortunately, it doesn't work as of Synfig Studio v0.61.04
* There appear to be mechanisms in place for linking the shape of a new layer to that of another layer, by selecting the list of vertices, and using the context menu to reference them to the first layer. The interface for this is not complete yet either.
* Create a [[Region Layer|region]] with the same number of ducks, and manually link each duck. This is possible in the current version, but takes forever.

So in short, hang in there! Looks like there should be a few easy ways to fill an outline in upcoming releases. For now it's possible, just rather difficult.

Dev:Wish list

2006-01-12T08:00:16Z

SnapSilverlight: Rewording a wish....some of its functionality is already there, in two different forms, but not getting at what I want to refer to.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean parameter''' (3) — An animatable way to remove a layer from visibility and consideration in tools. And as an option, to hide the layer in the layer list while it is invisible. This crosses over functionality from the [[Amount Parameter]], the Show/Hide checkbox in the [[Layers Dialog]], and builds upon it as well, allowing the [[Layers Dialog]] to dynamically unclutter.

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''Alternate UI''' (2) — An MDI window would be nice on systems that don't support a fixed menu location (like Windows or Gnome/KDE) - or at the very least place the Canvas's context menus along the top of the Canvas window. [http://sourceforge.net/tracker/index.php?func=detail&aid=1401371&group_id=144022&atid=757419]

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. (added as this is a standard request/feature for a graphics or video app)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:SnapSilverlight|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:SnapSilverlight|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

Doc:Creating Shapes

2006-01-12T06:58:59Z

SnapSilverlight: Linking

(Draft) ''Note to the reader: This is still incomplete; please be patient.''

=== Introduction ===

Basic primitives such as circles or rectangles are all great, but they are pretty much geometrically inflexible. What about shapes? To do this, we use the [[bline tool]].

=== Headline ===

In Synfig, the construct for describing shapes is called a [[Bline]]. This is roughly analogous to a "path" in other programs, except that it is strictly a hermite spline.

When you click on the [[bline tool]], you will see that the ducks from your currently selected layer (if there was one) will disappear, but the layer(s) will still remain selected in the [[Layers Dialog]]. This is normal. Anything you create in the [[bline tool]] will be inserted above the currently selected layer. Keep in mind that if you want to insert a shape somewhere, you should select where you want to insert it before you go into the [[Bline tool]]—changing the selection afterward will automaticly swap you back to the normal tool.

If you take a look at the [[bline tool#Options|tool options]] dialog, you'll notice that the first things you see are three checkboxes. Make sure that only "Fill" AND "Outline" are checked.

First, go ahead and click on the "R" button in the lower left corner of the FG/BG color widget in the [[Toolbox|toolbox]]. This will reset us back to black and white. Also, go ahead and set the [[New Layer Defaults#Default Line Width|default line width]] (right next to the FG/BG widget) to something nice and thick -- 10pt should do the trick.

Clicking with your mouse in the canvas will place vertices. While you are placing a vertex, you can drag out its tangent by dragging the mouse. Do this over and over, and you construct a Bline.

Keep in mind, however, that during this construction, there is nothing stopping you from just moving it if you don't like where you placed a vertex or a tangent. Honest! If you want to remove a vertex, right click on it and delete it. Want to split the tangents? Right click on the tangent and hit "split tangents". Want to loop the bline? right click on the first vertex and select "loop".

So I assume you got your first Bline laid out like you want it. That's great. But we are still in construction mode -- the layers haven't been created yet. There are two ways to create the layers:
# just switch to another tool, or
# press the "create" button at the bottom of the [[bline tool#Options|tool options tab]] (it's the icon that looks like a gear).

For now, just go ahead and click on the [[normal tool]] because we are done with the [[bline tool]].

// Insert Figure about here

Ok, we now have a nice pretty white region with a thick black outline. Notice that there are two layers that we have created--the [[Outline Layer|Outline]] and the [[Region Layer|Region]]. Despite the fact that they are two separate layers, their vertices parameter has already been [[Linking|linked]]--so you can select either one and move its ducks around and the other one will also change.

If you want to manipulate the vertices after you have created the layers, it is very easy to do so. Just click on one of the layers and have at it. If you want to remove a vertex, right click on it and hit "Remove Item (smart)". Want to insert a point somewhere? Right click on the segment where you want to insert something and his "Insert item (smart)".

NOTE: The only major difference between this normal editing mode and the construction mode is in how you split the tangents--in construction mode you right click on the tangent itself. In normal duck editing mode, you must right click on the vertex that the tangents are attached to. This could be considered a usability bug, and it will be resolved at some point.

This may appear to be leading to a mess of layers. And yes, if you aren't using the software properly, that is exactly what you will get. But there is a way to make this more sane: Just study the [[Adding_Layers|previous tutorial]]

One quick thing to mention before I finish up. You can change the width of an outline at each vertex. You do this by selecting the outline layer (NOTE: you must select the [[Outline Layer]], the [[Region Layer]] has no width data) and tweaking with the width ducks. By default, these are masked. To show them, press Alt-5. Repeat to hide them again. You can also see other things to mask via the [[Canvas Menu Caret]] > [[View Menu]] > [[Mask Ducks Menu]].

That should give you enough of a grasp of the software to be able to figure out more stuff on your own.

Wiki Wish List

2006-01-12T06:41:07Z

SnapSilverlight:

If you've come here looking for help, and you've found its documentation hasn't been written yet, post it here. That way, we'll know what to work on documenting next!

If you're looking for something to write, and nothing here strikes your fancy, take a look at [[Special:Wantedpages|Wanted Pages]] in the [[Special:Specialpages|Special Pages]] section.

(If, however, you're looking for a feature that you need in Synfig but aren't sure exists, consider listing it on the [[Wish list]] instead.)

* '''Animation Namespace''' — Should be a seperate namespace for discussing animation terminology and technique, and such, independent from description of Synfig features. For example, the "Twelve Principles Of Animation" don't really have anything to do with how to use Synfig's interface, but have everything to do with things being created in Synfig.

* MediaWiki's TeX math rendering system isn't turned on. There've been a few times I've wanted to use it.

Canvas Menu Caret

2006-01-12T06:39:45Z

SnapSilverlight:

Whereas most graphics apps have a set of menus at the top of the screen, the top of the MDI window, or the top of the drawing window, Synfig has a caret. A sideways one. It is located in the upper left hand corner of the Canvas window, and looks like this:

>

Beneath this button are all the menus you'd expect, and where you can access most of Synfig Studio's features:

* [[File Menu]]
* [[Edit Menu]]
* [[View Menu]]
* [[Canvas Menu]]
* [[State Menu]]
* [[Group Menu]]
* [[Layer Menu]]
* [[Keyframe Menu]]

Canvas Menu Caret

2006-01-12T06:39:04Z

SnapSilverlight: Canvas Menu Caret. With any luck someday we'll be able to delete this page.

Whereas most graphics apps have a set of menus at the top of the screen, the top of the MDI window, or the top of the drawing window, Synfig has a caret. A sideways one. It looks like this:

>

Beneath this button are all the menus you'd expect, and where you can access most of Synfig Studio's features:

* [[File Menu]]
* [[Edit Menu]]
* [[View Menu]]
* [[Canvas Menu]]
* [[State Menu]]
* [[Group Menu]]
* [[Layer Menu]]
* [[Keyframe Menu]]

Wiki Wish List

2006-01-12T06:24:08Z

SnapSilverlight:

Draw Tool

2006-01-12T04:50:43Z

SnapSilverlight: Formatting

The draw tool is the one that most artists will be familiar with. This tool is best used with a drawing tablet, although it can be used with a mouse.

The draw tool generates either a region, or a [[Bline]] [[Outline Layer]] with pressure output from the tablet mapped to the line's width.

==Options==
;'''Pressure Width'''
:Whether or not to scale the width based on the pressure input. If this is unchecked, the layer will be drawn at the width indicated in the [[New Layer Defaults]] section of the [[Toolbox]]
;'''Auto Loop'''
:When the stroke of the draw tool ends near the beginning of the stroke, automatically connect the last duck to the first.
;'''Auto Connect'''
:When the stroke begins at or near an endpoint duck of another [[Outline Layer|outline]], the resulting [[Outline Layer|outline]] is simply appended to the existing [[Outline Layer]]
:When the stroke begins at or near a vertex duck in the middle of another [[Outline Layer|outline]], the first vertex of the resulting [[Outline Layer|outline]] is [[Linking|linked]] to the duck on the existing [[Outline Layer]].
;'''Create Region Only'''
:Rather than creating an [[Outline Layer]], the tool discards pressure information, and creates a [[Region Layer]] instead.
;'''Min Pressure'''
:The value of this option clamps the lower end of the Pressure sensitivity to a specific value, essentially determining how thin the thinnest possible segment is relative to the [[New Layer Defaults#Brush Size|Brush Size]] parameter in the [[Toolbox]].
;'''Feather'''
:''(revise me) Seems to have something to do with setting the [[Feather Parameter]] on the layer, but there doesn't seem to be a clear translation between the setting of this control, and the resulting parameters.''
;'''LocalError'''
:''This affects whether the Smooth option is in world coordinates or not. But I'm not sure what it measures when this is turned on.''
;'''Smooth'''
:Determines how much tablet jitter is removed, and as a result, how many vertices the resulting splines are composed of.

==Buttons==
;'''Fill Last Stroke'''
:Currently creates a [[Region Layer]], causes some errors, and then deletes the [[Region Layer|region layer]] again.

Draw Tool

2006-01-12T04:50:21Z

SnapSilverlight: initial commit

The draw tool is the one that most artists will be familiar with. This tool is best used with a drawing tablet, although it can be used with a mouse.

The draw tool generates either a region, or a [[Bline]] [[Outline Layer]] with pressure output from the tablet mapped to the line's width.

==Options==
;'''Pressure Width'''
:Whether or not to scale the width based on the pressure input. If this is unchecked, the layer will be drawn at the width indicated in the [[New Layer Defaults]] section of the [[Toolbox]]
;Auto Loop
:When the stroke of the draw tool ends near the beginning of the stroke, automatically connect the last duck to the first.
;Auto Connect
:When the stroke begins at or near an endpoint duck of another [[Outline Layer|outline]], the resulting [[Outline Layer|outline]] is simply appended to the existing [[Outline Layer]]
:When the stroke begins at or near a vertex duck in the middle of another [[Outline Layer|outline]], the first vertex of the resulting [[Outline Layer|outline]] is [[Linking|linked]] to the duck on the existing [[Outline Layer]].
;'''Create Region Only'''
:Rather than creating an [[Outline Layer]], the tool discards pressure information, and creates a [[Region Layer]] instead.
;'''Min Pressure'''
:The value of this option clamps the lower end of the Pressure sensitivity to a specific value, essentially determining how thin the thinnest possible segment is relative to the [[New Layer Defaults#Brush Size|Brush Size]] parameter in the [[Toolbox]].
;'''Feather'''
:''(revise me) Seems to have something to do with setting the [[Feather Parameter]] on the layer, but there doesn't seem to be a clear translation between the setting of this control, and the resulting parameters.''
;'''LocalError'''
:''This affects whether the Smooth option is in world coordinates or not. But I'm not sure what it measures when this is turned on.''
;'''Smooth'''
:Determines how much tablet jitter is removed, and as a result, how many vertices the resulting splines are composed of.

==Buttons==
;'''Fill Last Stroke'''
:Currently creates a [[Region Layer]], causes some errors, and then deletes the [[Region Layer|region layer]] again.

Categorical Help

2006-01-12T04:03:59Z

SnapSilverlight: Adding Canvas Menu Caret to the Main Canvas section.

==The Main Canvas==
[[Canvas Menu Caret]]
==Working With Layers==

* Layer Compositing - the [[Blend Method]] attribute.

==Animation==

==[[Synfig Dialogs]]==
These are the main ancilliary windows you'll use in Synfig to manage your project data outside of the canvas window.
* Tool Options Dialog - the options for each tool described in the [[Toolbox]]
* [[History Dialog]]
* [[Canvas Browser]]
* [[Keyframes Dialog]]
* [[Layers Dialog]]
* [[Params Dialog]]
* [[Canvas Metadata Dialog]]
* [[Children Dialog]]
* [[Info Dialog]]
* [[Navigator]]
* [[Timetrack]]
* [[Curves Dialog]]
* [[Groups Dialog]]
* [[Palette Editor]]
* [[Palette Browser]]

Group Layer

2006-01-12T04:02:18Z

SnapSilverlight: typo

The Inline Canvas layer is a special layer that can hold other layers. It is generated via the [[Encapsulate]] comand accessed via the context menu in the [[Layers Dialog]] or through the [[Layers Menu]] in the [[Canvas Menu Caret]].

Inline Canvas layers also are the only layer ''(revise if there's another)'' that cannot be created through the [[New Layer Menu]].

An Inline Canvas layer has the following parameters:
* [[Z Depth]]
* [[Amount Parameter]]
* [[Blend Method]]
* [[Origin]]
* '''Canvas''': This is "Inline Canvas" by default. It also lets you select another canvas. Currently, cancelling selecting another canvas from this menu induces a crash.
* [[Zoom Parameter]]
* [[Time Offset Parameter]]
* '''Children Lock''': (to be written)

Group Layer

2006-01-12T04:01:15Z

SnapSilverlight: Initial commit.

The Inline Canvas layer is a special layer that can hold other layers. It is generated via the [[Encapsulate]] comand accessed via the context menu in the [[Layers Dialog]] or through the [[Layers Menu]] in the [[Canvas Menu Caret]].

Inline Canvas layers also are the only layer '''(revise if there's another)'' that cannot be created through the [[New Layer Menu]].

An Inline Canvas layer has the following parameters:
* [[Z Depth]]
* [[Amount Parameter]]
* [[Blend Method]]
* [[Origin]]
* '''Canvas''': This is "Inline Canvas" by default. It also lets you select another canvas. Currently, cancelling selecting another canvas from this menu induces a crash.
* [[Zoom Parameter]]
* [[Time Offset Parameter]]
* '''Children Lock''': (to be written)

Layers Panel

2006-01-12T03:46:15Z

SnapSilverlight: Initial commit

==Summary==

The Layers Dialog allows you to view and manipulate the layer hierarchy in your scene. This is where you can determine which objects get drawn first, and create [[Inline Canvas|subsets of layers]] for the purpose of applying effects.

==Elements of the Layers Dialog==
The Layers Dialog contains a detailed list of the [[Layers]] in your scene. Each row represents a layer, and the columns are:
; '''Show/Hide checkbox'''
: Turns the layer on or off in the composition. This parameter is not keyable.
; '''Z''' (This column will likely be renamed in subsequent releases)
: The icon representing the layer type. For [[Region Layer|Regions]], [[Outline Layer|Outlines]], and [[Gradient Layer Category|Gradients]], the icons will be those of the [[bline tool]], the [[width tool]], and the [[gradient tool]], respectively.
; '''Layer Name'''
: The name of the layer you're currently working on.
; '''Z''' (does not always appear)
: The second Z column indicates the Z position of the layer, which can also affect layer compositing.

Below the layer list, are buttons (and a drop down menu containing any buttons that don't fit on the palette) for the basic layer commands. These are the same commands found in the [[Layer Menu]] in the [[Canvas Menu Caret]][http://en.wiktionary.org/wiki/caret], and in the context menu for the Layer Dialog.

Dev:Wish list

2006-01-12T02:44:38Z

SnapSilverlight: 'Nother couple of features that people would find useful, but I'm not particularly interested in.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean''' (3) — Removes a layer from consideration on frames when this is active. Tools that consider other layers should ignore layers that are currently set hidden. An option to turn off display of hidden layers in the [[Layers Dialog]] as well, when you don't need to worry about them (you can always show them again to get ahold of them).

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''Alternate UI''' (2) — An MDI window would be nice on systems that don't support a fixed menu location (like Windows or Gnome/KDE) - or at the very least place the Canvas's context menus along the top of the Canvas window. [http://sourceforge.net/tracker/index.php?func=detail&aid=1401371&group_id=144022&atid=757419]

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. (added as this is a standard request/feature for a graphics or video app)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:SnapSilverlight|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* '''mod_synfig''' (1) — For Apache. Render .sif to some format like png/mng on access.

* '''synfig nsplugin''' (1) — Let Mozilla and Mozilla-based view synfig files in-browser.

----

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:SnapSilverlight|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)

User:SnapSilverlight

2006-01-12T02:05:30Z

SnapSilverlight: Because I didn't want something serious on this page.

SnapSilverlight is a [[User:SnapSilverlight#Wiki Dragon|WikiDragon]].

He enjoys drawing, animation, open source software, long walks in the park...uh... good humor, terrible humor (see the occasional references to ducks in the wiki).

Snap is here editing the wiki because, as he can't code, this seems to be a good way to contribute.

==Wiki Dragon==
A [[User:SnapSilverlight#Wiki Dragon|WikiDragon]] is basically good, much like [http://www.c2.com/cgi/wiki?WikiFaeries WikiFaeries] and [http://www.c2.com/cgi/wiki?WikiGnomes WikiGnomes].

However, [[User:SnapSilverlight#Wiki Dragon|WikiDragons]] are known to author pages as well as clean up others' text, and beautify others' pages. [[User:SnapSilverlight#Wiki Dragon|WikiDragons]] are known to fly across wikis, leaving large swaths of improvements both large and small in their wake. They can also remain dormant for months between activity.

Occasionally a [[User:SnapSilverlight#Wiki Dragon|WikiDragon]] may become obsessed with a particular topic or article. In this event, it's often a good idea to have a (well-armored) user poke them with a large stick.

The best way to satisfy the editing instinct and impulses of a [[User:SnapSilverlight#Wiki Dragon|WikiDragon]] is to get as many [http://c2.com/w4/wikibase/?WikiVirgin WikiVirgins] as possible to try their hand at writing on the wiki.

Dev:Wish list

2006-01-12T01:09:09Z

SnapSilverlight: Moved bugreport to bottom, and cleaned it up.

Got a great idea for a new feature, just add it here.
Please add a rating of how essential this feature is to your workflow according to the following scale:
#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

----

* '''Arbitrary Color Channels''' — The ability for the user to create any number of custom channels for various purposes.

* '''Autorecover History''' — It would be great if autorecover could also recover the associated history of a file in the event of a crash.

* '''[[Render Settings Dialog#Target|Render target filetype]]''' — the ability to save as .mng [http://libpng.org/pub/mng/]

* '''Layer Convert''' (4) — Convert a fill, outline, or gradient, to a fill, outline, or gradient (or layer mask?). So you could, say, duplicate a line and turn it into the background for a shape (if, say, you forgot to use the checkbox to create a layer of that type when you drew it, or the tool does not yet support it) ''It appears that this may be accomplished through the Convert... option for a layer's vertices, allowing you to reference another layer. However the interface for this is not yet completed.'' [[User:SnapSilverlight|SnapSilverlight]] 17:04, 11 Jan 2006 (PST)

* '''Layer hide boolean''' (3) — Removes a layer from consideration on frames when this is active. Tools that consider other layers should ignore layers that are currently set hidden. An option to turn off display of hidden layers in the [[Layers Dialog]] as well, when you don't need to worry about them (you can always show them again to get ahold of them).

* '''Vector fill bucket''' (3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[region layer]]). Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

* '''[[redraw tool]]''' (4-5) — Intutive reshaping of path-based layers. See link.

* '''Restore Default Layout''' (3) — It's very difficult to put all the dialogs back where they were when you started the program, if you've closed them. In addition, with many programs, if you've done something with your window manager to take a window's position off screen, this command is sometimes the only way to bring them back.

* '''Alternate UI''' (2) — An MDI window would be nice on systems that don't support a fixed menu location (like Windows or Gnome/KDE) - or at the very least place the Canvas's context menus along the top of the Canvas window. [http://sourceforge.net/tracker/index.php?func=detail&aid=1401371&group_id=144022&atid=757419]

* '''Flock tool''' (3) — To push around a 'soft-select' region of all layers, or all selected layers. Sort of like a smudge tool in a raster drawing app, or like the soft-mod tool in 3DSMax and Maya. "Flock" because this tool affects all the ducks in an area. ;)

* '''Riding ducks''' (2) — Not chocobos. The ability to link a duck from one shape to an arbitrary position on another path, without creating an extra shape duck on that path.

* '''Plugin API''' (1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. (added as this is a standard request/feature for a graphics or video app)

* '''Python support''' (1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:SnapSilverlight|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

* ''' Uninstall feature for OSX.''' — Install put 80MB of gtkmm rubbish somewhere above slash and then the app failed to run anyway because it couldn't find said rubbish. Not happy, Jan. Perhaps an install prefix for osx where folks could easily delete it?
''Maybe bugreport it instead?'' [[User:SnapSilverlight|SnapSilverlight]] 17:09, 11 Jan 2006 (PST)