introduction.sgml 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. <!-- retain these comments for translator revision tracking -->
  2. <!-- $Id$ -->
  3. <chapter id="introduction">
  4. <title><acronym>Introduction</acronym></title>
  5. <para>Synfig, like most every other competent graphics program, breaks down
  6. individual elements of a Canvas into Layers. However, it differs from other
  7. programs in two major ways:</para>
  8. <orderedlist>
  9. <listitem>
  10. <para>An individual layer in Synfig usually represents a single "Primitive".
  11. ie: A single region, an outline of a region, an imported JPEG, etc... This
  12. allows you to have a great deal of flexibility and control. It is not
  13. uncommon for a composition to have hundreds of layers(organized into a
  14. hierarchy for artist sanity of course).</para>
  15. </listitem>
  16. <listitem>
  17. <para>A layer can not only composite information on top of the image below it,
  18. but also distort and/or modify it in some other way. In this sense, Synfig
  19. Layers act much like filters do in Adobe Photoshop or the GIMP. For example,
  20. we have a Blur Layer, Radial Blur Layer, Spherical Distortion Layer,
  21. color-correct layer, bevel layer, etc... </para>
  22. </listitem>
  23. </orderedlist>
  24. <para>Each layer has a set of parameters which determine how it behaves. When
  25. you click on a layer (either in the canvas window, or in the Layer Dialog),
  26. you will see its parameters in the Params Dialog.</para>
  27. <para>Synfig Studio has an autorecover feature. If it crashes, even if the
  28. current file has not been saved, it will not lose more than 5 minutes of work.
  29. At restart it will automatically prompt the user to recover the unsaved changes.
  30. Unfortunately history isn't recovered yet. That feature comes later.</para>
  31. <para>One thing you may notice is that Synfig Studio is SLOW, making it
  32. practically unusable on hardware that is over 3 years old. The biggest reason
  33. for this is that all of the color calculations are done in floating point
  34. because Synfig Studio was built from the ground up with High-Dynamic-Range
  35. Imaging in mind. HOWEVER, this will not be the case forever.</para>
  36. <para>darco has some fairly major re-implementations and optimizations that
  37. he plans to implement that should quite dramatically improve the performance
  38. of Synfig on all platforms. The goal is not a 200% speed increase, it is at
  39. least a 2000% speed increase. With the optimizations that are planned to be
  40. implemented, we will be able to pipeline operations in such a way that this
  41. performance improvement can be realized. It should also pave the way to hardware
  42. acceleration using todays powerful graphics processors, which should yield
  43. further performance improvements measurable in orders of magnitude.</para>
  44. </chapter>
  45. <!-- Local Variables: -->
  46. <!-- sgml-parent-document: "synfig-studio.sgml" -->
  47. <!-- End: -->