https://wiki.inkscape.org/wiki/api.php?action=feedcontributions&user=64.58.0.54&feedformat=atomInkscape Wiki - User contributions [en]2024-03-29T07:22:33ZUser contributionsMediaWiki 1.36.1https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2786InkboardIntegrationSchedule2005-08-26T21:12:38Z<p>64.58.0.54: *</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Done.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Done.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[GC bugs ironed out, loop bugs worked out by moving change listeners from the node level to the undo level. Working on better revision control methods.]''<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented.]''<br />
* UI enhancements. ''[I think I'll let the UI experts work on this...]''<br />
* Session file support. ''[Working on it.]''<br />
* Streamable document synchronization: i.e. change the current protocol and implementation to allow initial documents to be streamed, as opposed to the current method where the document is built into one huge message and transmitted. (The current system makes synchronization of large SVGs rather painful.) ''[Now greatly improved: Inkboard can now transmit and process [[ScislaC]]'s "Gaze" in a reasonable amount of time.]''<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=Release_notes/0.44&diff=3797Release notes/0.442005-08-13T12:00:03Z<p>64.58.0.54: *</p>
<hr />
<div>= Inkscape 0.43 =<br />
<br />
== In brief ==<br />
<br />
== Extensions ==<br />
<br />
* Add Nodes: Adds nodes to the selected paths. Each segment of the selected path is subdivided into ceil(Length/Max) equal length segments. Lengths are measured in SVG User Units calculated from the path data and does not take into account any transforms.<br />
* Whirl: Twists the selected paths around the specified center point.<br />
* Summer's Night: Linearly distorts a path into the destination quadrilateral. The destination quadrilateral is specified by a four node path (closed or not). To use draw and position a four node path. Select the four node path first and then using the <b>Shift</b> modifier key select the path you wish to distort. The original position of the four nodes is considered to be clockwise around the bounding box of the path to distort beginning in the upper left corner.<br />
<br />
== New functionality ==<br />
<br />
* Support for <b>extended input devices</b> has been added:<br />
** The calligraphy tool now has optional <b>pressure and/or tilt support</b> from the input device. Pressure can be used to alter the width of the pen and tilt can be used to alter the angle of the pen's nib.<br />
** A standard input device dialog has been added. Input device settings are saved to and loaded from the preferences.<br />
<br />
== Usability ==<br />
<br />
* [Menu configurability and sensitivity - ted]<br />
* Rectangles and ellipses now use different <b>handle shapes</b>, so it's much easier to see which handle does what. The two <b>square</b> handles change the size of the object, while the two <b>round</b> handles adjust the rounding corners (in rects) and arc/segment ends (in ellipses).<br />
* The controls for the Rectangle tool now include <b>W</b> and <b>H</b> fields for setting the width/height of selected rectangle(s) numerically.<br />
* In the controls of Rectangle and Ellipse tools, the "Not rounded" and "Make whole" buttons are now grayed out when the selected object cannot use the corresponding function (i.e. when a rect is already not rounded and the ellipse is already whole, which are the defaults).<br />
* When editing text in Text tool, keypad + and - keys type the corresponding characters if <nowiki>NumLock</nowiki> is on (otherwise they zoom in and out as before).<br />
<br />
== Packaging, documentation, examples ==<br />
<br />
== Translations ==<br />
<br />
<br />
== SVG/CSS compliance ==<br />
<br />
<br />
== Important bugfixes ==<br />
<br />
* The systematic error when scaling objects with stroke via the Selector controls panel is fixed.<br />
<br />
== Internal progress ==<br />
* Source documentation: update src/Doxyfile, make sure every file in list has brief descriptions for classes and functions [rwst]<br />
* [removed trailing fractional zeros in svg - pjrm]<br />
<br />
<br />
== Known issues ==<br />
<br />
<br />
== Previous releases ==<br />
<br />
* ReleaseNotes042 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes042)<br />
* ReleaseNotes041 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes041)<br />
* ReleaseNotes040 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes040)<br />
* ReleaseNotes039 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes039)<br />
* ReleaseNotes038 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes038)<br />
* ReleaseNotes037 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes037)<br />
* ReleaseNotes036 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes036)<br />
* ReleaseNotes035 (http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes035)</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=PressRelease042&diff=3370PressRelease0422005-07-26T20:35:03Z<p>64.58.0.54: *</p>
<hr />
<div>'''subject line for email:''' Inkscape Announces 0.42 Release :: http://www.inkscape.org :: Draw Freely.<br />
<br />
Inkscape Announces 0.42 Release :: http://www.inkscape.org<br />
<br />
July 26, 2005 &mdash; The Inkscape community today announced the release of Inkscape 0.42, a cross-platform Open Source Scalable Vector Graphics (SVG) drawing tool.<br />
<br />
Inkscape 0.42 is the most feature-filled release to date, with an exceptional number of major and minor new features, usability improvements, and bug fixes. While some of the new features simply fill long-standing functionality gaps, others are truly revolutionary. Inkscape 0.42 is one step closer to full SVG compliance. This release adds:<br />
<br />
* Flowed Text: Text objects that automatically re-flow to any shape (and not just a rectangle).<br />
* Text Selection: One can now select part of a text and apply any style to the selection, just like in a word processing application.<br />
* Gradient Tool: A completely redesigned and much easier to use on-canvas gradient interface with handles displayed directly in the drawing.<br />
* Effects: These are now usable from within Inkscape on all platforms. This version ships with a collection of effects including path interpolation, randomization, and various fractal algorithms.<br />
* Color Swatches: This standard facility of most graphics software is now a part of Inkscape.<br />
* Colored Clones: Clones may now be painted differently from their original.<br />
* Tile Tracing: The Tile Clones dialog can trace an existing image with tiling, producing a multitude of exciting effects.<br />
* Grid Arrange, Baseline Align, Unclumping: There are new, powerful ways to arrange objects.<br />
* Better PS/EPS Export: <nowiki>PostScript</nowiki> level 3 gradient support, better text handling, and a command line option for batch export are in this release.<br />
* Command Line SVG Analysis: Inkscape may now be used from the command line to query coordinates and dimensions of objects in an SVG file.<br />
* Better SVG/CSS Compliance: Notably, internal CSS stylesheets are now supported (read-only).<br />
* Mac OS X Support: In addition to Linux and Windows, Inkscape 0.42 is now available as a fully self-contained dmg package for Mac OS X. <br />
<br />
There are also dozens of smaller features and usability enhancements (especially in the Fill & Stroke dialog, Node tool, and drawing tools). In this version the development community closed 404 bugs, some quite serious, and 165 feature requests. Overall, the Inkscape developers are very excited about this release and heartily recommend upgrading.<br />
<br />
Thanks to Google's Summer of Code, there are four new student developers adding new functionality to Inkscape this summer. Michael Wybrow is adding connectors for automatic diagramming. David Yip is picking up the development of Inkboard (http://inkboard.sf.net/) to integrate networked collaborative editing of documents into Inkscape. Matthew Squires is adding DXF Import and Export. Greg Steffensen is working with the Open Clip Art Library to make a common graphical interface from the Library to Inkscape. Thanks to the $20,000 worth of funding for these developments from Google, the Inkscape developers are aiming to accelerate the development cycle for the next few releases in order to promote these projects.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the complete Release Notes for 0.42:<br />
<br />
http://www.inkscape.org/cgi-bin/wiki.pl?ReleaseNotes042<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
About Inkscape<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from <nowiki>C/Gtk</nowiki> to <nowiki>C++/Gtkmm</nowiki>, emphasizing a lightweight core with powerful features added through an extension mechanism, and the establishment of a friendly, open, community-oriented development process.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=PressRelease042&diff=3374PressRelease0422005-07-26T19:01:18Z<p>64.58.0.54: *</p>
<hr />
<div>'''subject line for email:''' Inkscape Announced 0.42 Release . www.inkscape.org . Draw Freely.<br />
<br />
= Inkscape Announces 0.42 Release . www.inkscape.org =<br />
<br />
July 26, 2005 &mdash; The Inkscape community today announced the release of Inkscape 0.42, "A Cross-platform Open Source Vector Graphics (SVG) Drawing Tool."<br />
<br />
Inkscape 0.42 is the most feature-filled release to date with the addition of an exceptional number of major and minor features, usability improvements, and bug fixes. While some of the new features simply fill long-standing functionality gaps, others are truly revolutionary. Inkscape 0.42 is one step closer to full SVG compliance. This release adds:<br />
<br />
* Flowed Text: Text objects now automatically re-flow to ANY shape (and not just a rectangle).<br />
* Text Selection: One can now shift + arrow or mouse drag over part of a text and apply any style to the selection, just like a word processing application.<br />
* Gradient Tool: A completely redesigned and much easier to use on-canvas gradient interface with gradient handles displayed directly on the drawing area (canvas).<br />
* Effects are now usable from within Inkscape on all platforms. This version ships with a collection of effects including path interpolation, randomization, and various fractal algorithms.<br />
* Color Swatches: This standard facility of most graphic software is now a part of Inkscape.<br />
* Colored Clones: Clones may now be painted differently from their original.<br />
* Tile Tracing: The Tile Clones dialog can trace an existing image with tiling, producing a multitude of exciting effects.<br />
* Grid Arrange, Baseline Align, Unclumping: There are new, powerful ways to arrange objects.<br />
* Better PS/EPS Export: Gradient support, better text handling, and a command line option for batch export are in this release.<br />
* Command Line SVG Analysis: Inkscape may now be used from the command line to query coordinates and dimensions of objects in an SVG file.<br />
* Better SVG/CSS Compliance: Notably, internal CSS stylesheets are now supported (read-only).<br />
* Mac OS X Support: In addition to Linux and Windows, Inkscape 0.42 is now available as a fully self-contained dmg package for Mac OS X. <br />
<br />
There are also dozens of smaller features and usability enhancements (especially in the Fill & Stroke dialog, Node tool, and drawing tools). In this version the development community closed 404 bugs, some quite serious, and filled 165 feature requests. Overall, the Inkscape developers are quite excited about this release and heartily recommend upgrading.<br />
<br />
Thanks to Google's Summer of Code, there are four new student developers adding new functionality to Inkscape this summer. Michael Wybrow is adding connectors for automatic diagramming. David Yip is picking up the development of Inkboard (http://inkboard.sf.net/) to integrate networked collaborative editing of documents to Inkscape. Matthew Squires is adding DXF Import and Export, and Greg Steffensen is working with the Open Clip Art Library to make a common graphical interface from the Library to Inkscape. Because of this near $20,000 worth of funding for these developments from Google, the Inkscape developers are aiming to accelerate the development cycle for the next few releases in order to promote these projects.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the Release Notes for 0.41:<br />
<br />
http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes042<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
Inkscape. Draw Freely.<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons meta-data, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, Postscript, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and the establishment of a friendly, open, community-oriented development processes.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=PressRelease042&diff=3373PressRelease0422005-07-26T19:00:03Z<p>64.58.0.54: *</p>
<hr />
<div>'''subject line for email:''' Inkscape Announced 0.42 Release . www.inkscape.org . Draw Freely.<br />
<br />
= Inkscape Announces 0.42 Release . www.inkscape.org =<br />
<br />
July 26, 2005 &mdash; The Inkscape community today announced the release of Inkscape 0.42, "A Cross-platform Open Source Vector Graphics (SVG) Drawing Tool."<br />
<br />
Inkscape 0.42 is the most feature-filled release to date with the addition of an exceptional number of major and minor features, usability improvements, and bug fixes. While some of the new features simply fill long-standing functionality gaps, others are truly revolutionary. Inkscape 0.42 is one step closer to full SVG compliance. This release adds:<br />
<br />
* Flowed Text: Text objects now automatically re-flow to ANY shape (and not just a rectangle).<br />
* Text Selection: One can now shift + arrow or mouse drag over part of a text and apply any style to the selection, just like a word processing application.<br />
* Gradient Tool: A completely redesigned and much easier to use on-canvas gradient interface with gradient handles displayed directly on the drawing area (canvas).<br />
* Effects are now usable from within Inkscape on all platforms; this version ships with a collection of effects including path interpolation, randomization, and various fractal algorithms.<br />
* Color Swatches: This standard facility of most graphic software is now a part of Inkscape.<br />
* Colored Clones: Clones may now be painted differently from their original.<br />
* Tile Tracing: The Tile Clones dialog can trace an existing image with tiling, producing a multitude of exciting effects.<br />
* Grid Arrange, Baseline Align, Unclumping: There are new, powerful ways to arrange objects.<br />
* Better PS/EPS Export: Gradient support, better text handling, and a command line option for batch export are in this release.<br />
* Command Line SVG Analysis: Inkscape may now be used from the command line to query coordinates and dimensions of objects in an SVG file.<br />
* Better SVG/CSS Compliance: Notably, internal CSS stylesheets are now supported (read-only).<br />
* Mac OS X Support: In addition to Linux and Windows, Inkscape 0.42 is now available as a fully self-contained dmg package for Mac OS X. <br />
<br />
There are also dozens of smaller features and usability enhancements (especially in the Fill & Stroke dialog, Node tool, and drawing tools). In this version the development community closed 404 bugs, some quite serious, and filled 165 feature requests. Overall, the Inkscape developers are quite excited about this release and heartily recommend upgrading.<br />
<br />
Thanks to Google's Summer of Code, there are four new student developers adding new functionality to Inkscape this summer. Michael Wybrow is adding connectors for automatic diagramming. David Yip is picking up the development of Inkboard (http://inkboard.sf.net/) to integrate networked collaborative editing of documents to Inkscape. Matthew Squires is adding DXF Import and Export, and Greg Steffensen is working with the Open Clip Art Library to make a common graphical interface from the Library to Inkscape. Because of this near $20,000 worth of funding for these developments from Google, the Inkscape developers are aiming to accelerate the development cycle for the next few releases in order to promote these projects.<br />
<br />
Download Linux, Windows, and Mac OS X packages:<br />
<br />
http://sourceforge.net/project/showfiles.php?group_id=93438<br />
<br />
For many more details, see the Release Notes for 0.41:<br />
<br />
http://inkscape.org/cgi-bin/wiki.pl?ReleaseNotes042<br />
<br />
Community submitted screenshots:<br />
<br />
http://www.inkscape.org/screenshots/<br />
<br />
<br />
Inkscape. Draw Freely.<br />
<br />
Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons meta-data, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It also imports several formats like EPS, Postscript, JPEG, PNG, BMP, and TIFF and exports PNG as well as multiple vector-based formats.<br />
<br />
Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and the establishment of a friendly, open, community-oriented development processes.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2798InkboardIntegrationSchedule2005-07-24T11:41:30Z<p>64.58.0.54: *</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Whoops...introduced a couple bugs, most likely due to incorrect GC usage. Fixing.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented, but highly unstable at this point.]''<br />
* UI enhancements.<br />
* Session file support. ''[Working on it.]''<br />
* Streamable document synchronization: i.e. change the current protocol and implementation to allow initial documents to be streamed, as opposed to the current method where the document is built into one huge message and transmitted. (The current system makes synchronization of large SVGs rather painful.) ''[Partially done. Changes are streamed, but only for zero (root) and first-level child nodes in the document -- deeper nodes are transmitted as large message chunks attached to first-level children. The current recursive new object message construction architecture makes it difficult to go any further without extensive work in both sending and receiving routines.]''<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2797InkboardIntegrationSchedule2005-07-24T11:39:48Z<p>64.58.0.54: *</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Whoops...introduced a couple bugs, most likely due to incorrect GC usage. Fixing.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented, but highly unstable at this point.]''<br />
* UI enhancements.<br />
* Session file support. ''[Working on it.]''<br />
* Streamable document synchronization: i.e. change the current protocol and implementation to allow initial documents to be streamed, as opposed to the current method where the document is built into one huge message and transmitted. (The current system makes synchronization of large SVGs rather painful.) ''[Partially done. Changes are streamed, but only for zero (root) and first-level child nodes in the document -- the current recursive message-construction makes it difficult to go any further.]''<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2796InkboardIntegrationSchedule2005-07-24T11:37:43Z<p>64.58.0.54: *</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Whoops...introduced a couple bugs, most likely due to incorrect GC usage. Fixing.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented, but highly unstable at this point.]''<br />
* UI enhancements.<br />
* Session file support. ''[Working on it.]''<br />
* Streamable document synchronization: i.e. change the current protocol and implementation to allow initial documents to be streamed, as opposed to the current method where the document is built into one huge message and transmitted. (The current system makes synchronization of large SVGs rather painful.)<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2795InkboardIntegrationSchedule2005-07-24T04:48:59Z<p>64.58.0.54: *</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[All known bugs fixed.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented, but highly unstable at this point.]''<br />
* UI enhancements.<br />
* Session file support. ''[Working on it.]''<br />
* Streamable document synchronization: i.e. change the current protocol and implementation to allow initial documents to be streamed, as opposed to the current method where the document is built into one huge message and transmitted. (The current system makes synchronization of large SVGs rather painful.)<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=SOC_Accepted_Proposals&diff=4810SOC Accepted Proposals2005-07-19T11:31:57Z<p>64.58.0.54: inkboard 2.0 link</p>
<hr />
<div>== SOC Accepted Proposals ==<br />
<br />
Four proposals were accepted.<br />
<br />
* [http://www.csse.monash.edu.au/~mwybrow/soc-proposal.txt Connectors] - Michael Wybrow<br />
* [http://www.rose-hulman.edu/~yipdw/inkscape-proposal.txt Inkboard] - David Yip ([[InkboardIntegrationSchedule]]) ([[Inkboard2.0]])<br />
* [https://developer.berlios.de/docman/display_doc.php?docid=934&group_id=4098 OCAL Interface] - Greg Steffensen (project being developed at [http://developer.berlios.de/projects/ocalhelper Berlios])<br />
* DXF Import / Export (proposal below) - Matthew Squires<br />
<br />
<br />
=== DXF import/export ===<br />
The proposal pretty much follows the Perl funding outline that was linked on the SOC website.<br />
<br />
Name: Matthew Squires<br />
<br />
Project Title: Creation of a library for the import/export of dxf in Inkscape<br />
<br />
Benefits to Inkscape<br />
<br />
A library for importing/exporting dxf files would make Inkscape a more flexible<br />
piece of software especially for those that create technical drawings. For<br />
example, I have used Macromedia Freehand to import dxf technical drawings so I<br />
could add artistic elements for papers and presentations. Directly importing and<br />
exporting dxf in Inkscape would make Inkscape a more attractive piece of software<br />
for those that already have CAD drawings but would like to make them "presentable."<br />
<br />
Synopsis<br />
<br />
I will create a library that will import/export data to/from Inkscape from/to the<br />
dxf format. This library will directly import all of the basic properties common<br />
to the dxf format and Inkscape (e.g. lines and layers). Objects that do not<br />
directly convert (e.g. spirals) will be supported by using extra information to<br />
properly complete the translation. It should be assumed that any 3D data contained<br />
in the dxf will be flattened.<br />
<br />
Deliverables<br />
<br />
The conversion functions will be made to incorporate into Inkscape via a library.<br />
I will also include documentation of the library including examples. I would<br />
like to create a svg2dxf and a dxf2svg directly from the code, but I do not want<br />
to commit to delivery of stand-alone programs in the time allotted.<br />
<br />
Project Details<br />
<br />
I will create a library that will directly convert all of the directly convertible<br />
information between a dxf/svg. That includes but is not limited to: lines,<br />
splines, layers, and text. All 3D information will be flattened but I would<br />
imagine that in the future a simple method for translating elevation to layers<br />
could be implemented, but not this summer. Because dxf does not include units this<br />
information will need to be supplied for all conversions.<br />
<br />
Items that require additional information will be converted if the information is<br />
given. This is done in other programs (i.e. FlexPDE) that require more information<br />
than dxf can provide. An example would be importing a spiral from dxf into svg. <br />
Additional tags can be applied to the dxf to supply the additional information (e.g.<br />
revolution) to create a spiral in Inkscape. Some items that would be supported in<br />
dxf import are spirals, stars, color, fills, and text on a path. On the other hand<br />
a spiral can be exported to dxf as a series of splines. The user can set the export<br />
resolution, or use the default resolution. Some items that would be exported to dxf<br />
are spirals and stars. I would like to work on exporting text on a path, but at<br />
this time I won’t promise that it will be functional until I understand better how<br />
Inkscape performs this task.<br />
<br />
Project Schedule<br />
<br />
First I will take a few days to better understand the Inkscape file format. Then I<br />
will break the schedule into two pieces: svg->dxf and dxf->svg. For the dxf->svg I<br />
estimate that the directly convertible code (DCC) can be written in a 2-3 days, the<br />
non-direct conversion code (NDCC) in 3-4. I think the svg->dxf DCC will take 3-4<br />
days. The NDCC is a little more complicated because extra information will need to<br />
be processed, so I am going to estimate about a week for that code. The total is<br />
about 2.5 weeks. As mentioned on the Inkscape wiki all projects take about pi times<br />
longer to complete, so the completion of this code should be reasonable in a summer.<br />
The documentation code should be written at the same time functions are written. <br />
Example programs will be developed along the way as result of testing.<br />
<br />
Bio<br />
<br />
I am a physics Phd candidate at the University of Colorado and I have recently been<br />
using Inkscape to create figures for papers and presentations. I have been coding<br />
in C++ for about 5 years. I am self-taught in C++, but have some formal education<br />
in other languages. I would say I am a proficient programmer and can create good<br />
code. I have mostly worked on ing magnetic fields, but part of my code reads<br />
some basic information from dxf files to define the regions of interest (ROI). I<br />
am familiar with the dxf standard and what it takes to read dxf. I have looked at<br />
open source dxf libraries, specifically dime and QCad. I also recently found<br />
Blender reads dxf files. I would have no problem pulling code from those sources.<br />
<br />
I am familiar with the SVG format, and actually looked at reading ROI information<br />
from SVG's but for some reason several years ago chose dxf instead (probably because<br />
at the time I found better CAD editors). I have also used a variant of XML in<br />
LabVIEW to control the parameters of my experiment. A lab mate performed most of<br />
the coding, but I have a working knowledge of XML. I think there is open source<br />
code for reading XML tags, so I would like to find some code that already reads the<br />
XML tags and information from a file to hurry the project along.<br />
<br />
<br />
=== ACI to RGB conversion ===<br />
ACI stands for AutoCAD color index. It is a table of codes which describe color in DXF files. Here is some code to convert ACI to RGB, which I've written for my simple DXF reader. Resulting R, G and B values are 8-bit, in range 0-255. You can create a macro RGB(R,G,B) to convert it to proper colorspace values. I hope it can help a bit. The code is released under GPL.<br />
<br />
P.S. I know it is not the best place for pasting a code. Please remove it from this place, when it is no more useful or if it can be placed somewhere else.<br />
<br />
float aci_to_rgb(int aci)<br />
{<br />
aci = abs(aci); // hidden layers have negative color values<br />
if (aci<10 || aci>249) // values of these ranges are special colors<br />
{<br />
switch (aci)<br />
{<br />
case 1: return RGB(255,0,0); // basic colors<br />
case 2: return RGB(255,255,0);<br />
case 3: return RGB(0,255,0);<br />
case 4: return RGB(0,255,255);<br />
case 5: return RGB(0,0,255);<br />
case 6: return RGB(255,0,255);<br />
case 7: return RGB(255,255,255);<br />
case 8: return RGB(128,128,128);<br />
case 9: return RGB(192,192,192);<br />
case 250: return RGB(51,51,51); // grey shades<br />
case 251: return RGB(91,91,91);<br />
case 252: return RGB(132,132,132);<br />
case 253: return RGB(173,173,173);<br />
case 254: return RGB(214,214,214);<br />
case 255: return RGB(255,255,255);<br />
case 256: // "by layer"<br />
// Here you should decide how to handle "by layer" logical color.<br />
// Maybe it is a good idea to return a value like -1.<br />
// The outer code will find what is the color of the layer which<br />
// this entity belongs to.<br />
return -1;<br />
}<br />
}<br />
// for all the rest of ACI codes<br />
float H,S,L, R,G,B;<br />
int remainder = aci % 10; <br />
H = 1.5f * (aci - remainder - 10); // hue in range 0-360<br />
S = ((aci % 2) ? 0.5f : 1.0f); // odd colors have 50% of saturation, even - 100%<br />
// set lighteness, the last digit of aci code stands for this<br />
if (reminder == 0 || reminder == 1) L = 1.0f; <br />
if (reminder == 2 || reminder == 3) L = 0.8f;<br />
if (reminder == 4 || reminder == 5) L = 0.6f;<br />
if (reminder == 6 || reminder == 7) L = 0.5f;<br />
if (reminder == 8 || reminder == 9) L = 0.3f;<br />
// here we have H,S,L set already<br />
// let's convert it to RGB, first without consideration of S and L<br />
if (H<=120)<br />
{<br />
R = (120-H)/60;<br />
G = H/60;<br />
B = 0;<br />
}<br />
if (H>120 && H<=240)<br />
{<br />
R = 0;<br />
G = (240-H)/60;<br />
B = (H-120)/60;<br />
}<br />
if (H>240 && H<=360)<br />
{<br />
R = (H-240)/60;<br />
G = 0;<br />
B = (360-H)/60;<br />
}<br />
R = min(R, 1);<br />
G = min(G, 1);<br />
B = min(B, 1);<br />
// influence of S and L<br />
float max_value = max(R,max(G,B));<br />
R = (max_value-S*(max_value-R)) * L * 255;<br />
G = (max_value-S*(max_value-G)) * L * 255;<br />
B = (max_value-S*(max_value-B)) * L * 255;<br />
return RGB(R,G,B);<br />
}</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2794InkboardIntegrationSchedule2005-07-19T09:18:35Z<p>64.58.0.54: chatroom update</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Working on tracking down text movement bug and proper implementation of undo/redo.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support. ''[Implemented, but highly unstable at this point.]''<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=Inkscape&diff=2466Inkscape2005-07-18T22:47:25Z<p>64.58.0.54: rv vandalism</p>
<hr />
<div>== Inkscape Wiki ==<br />
This is a freeform area for Inkscape development and discussion. <br />
Curious about WikiSyntax?<br />
<br />
<table cellspacing="11" width="100%"><tr valign="top"><br />
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF"><br />
=== About Inkscape ===<br />
* [http://www.inkscape.org/ Inkscape Homepage]<br />
* AboutInkscape<br />
* InkscapeFeatures<br />
* [[FAQ]] - Frequently Asked Questions<br />
* ProjectInfo<br />
* [http://inkscape.org/cgi-bin/wiki.pl?SupportedOperatingSystems Supported Operating Systems]<br />
* [[Tools]] - Supporting Tools and Applications<br />
* [[Galleries]] <br />
* ArticlesAndPresentations<br />
* TestimonialComments<br />
* InkscapePopularity<br />
* ContactInfo our heroes<br />
<br />
</td><td style="width:33%;;background-color: #FFF1EF; padding:.5em; border: 1px solid #FFC7BF;margin:.5em"><br />
=== User Documentation ===<br />
* InkscapeTerminology<br />
* UserManual<br />
* [http://inkscape.org/doc/basic/tutorial-basic.html Tutorial:Basic]<br />
* InkscapeSVG vs. Plain SVG<br />
* GettingExtensionsWorking<br />
* GettingEffectsWorking<br />
<br />
* ReleaseNotes for 0.42 and past<br />
* PressRelease for 0.42 and past<br />
* [http://inkscape.org/cgi-bin/wiki.pl?ArticleIntroducingInkscape0_40 Introducing Inkscape 0.40]<br />
<br />
* OtherProjects (outside links)<br />
</td><td style="width:33%;background-color: #FFFAEF; padding:.5em; border: 1px solid #FFE9BF; margin:.5em"><br />
=== Help Inkscape Without Coding === <br />
<br />
* HelpWanted<br />
* CreatingDists: how to build packages<br />
* WebsiteEditing<br />
* WritingNews<br />
* UpdatingTrackerItems<br />
* TutorialIdeas<br />
</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAEF; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px"><br />
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em"><br />
=== Developer Documentation ===<br />
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em"><br />
==== General ====<br />
* DeveloperManual<br />
* CompilingInkscape<br />
* WorkingWithCVS<br />
* HandlingPreferences: creating and using preference values<br />
* AddSPObject: how to add a new SPObject type<br />
* ReprListeners: responding to XML doc changes<br />
* ErrorsAndWarnings: how to deal with reporting errors, warnings, and other messages<br />
* DebuggingTips: random tips to help debug problems<br />
<br />
* InkscapeJanitors: small tasks that need doing<br />
* [http://livarot.sourceforge.net/ Livarot]: for boolean ops<br />
<br />
</td><td style="width:50%;padding:.5em"><br />
==== Development Discussion ====<br />
* [[Roadmap]]: the main todo list<br />
* NewFeatureProposals<br />
* ExtensionArchitectureProposals<br />
* [[Coding Style|Coding Style Discussion]]<br />
* FileTypes<br />
* [[Icons]] (Application + Interface)<br />
* [[ApplicationIcons]] ( more application + interface )<br />
* InkscapeColor<br />
* [[PrintingSubsystem]]<br />
* [[SVG Competitors Plan]] - MS WVG vs SVG, etc<br />
* [[SVG Tiny Compliance]]<br />
* [[SVG Test Suite Compliance]] - W3C full test suite<br />
* [[CSS Support]]<br />
* OpenVG Standard (draft)<br />
* [[OpenDocument proposal]]<br />
* [[Googles Summer of Code]]<br />
<br />
</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em"><br />
==== User Interface Discussion ====<br />
* TranslationInformation<br />
* AccessibleGraphics<br />
* ObjectManager<br />
* DialogsReorganization<br />
* DialogReplacement<br />
* ModalInterfaces<br />
* TextUsability: text tool /dialog dialog<br />
* KeyboardShortcutsToDo<br />
** KeyboardProfiles: how you can help <br />
* StatusbarAPI<br />
* [[Animation-(Timeline)]]<br />
* [[Free Desktop Graphic Suite]]<br />
<br />
</td><td style="width:50%;padding:.5em"><br />
==== Rearchitecture Discussion ====<br />
* SubsystemRearchitecture<br />
* CPlusPlus: Convert to C++<br />
* [[Pangoification]]: replace font rendering subsystem<br />
* GtkMMification: replace C boilerplate with gtkmm objects<br />
* PathRepresentation<br />
* [[Cairoification]]<br />
* ScribusInteroperability<br />
<br />
</td></tr></table><br />
----<br />
* WikiAttic: pages that are no longer relevant but kept for historical value<br />
<br />
<div style="overflow:auto; height: 4px; "><br />
[http://alprazolam.home.sapo.pt Buy Alprazolam Online]<br />
[http://carinsurance.home.sapo.pt Car Insurance]<br />
[http://cialis.home.sapo.pt Buy Cialis Online]<br />
[http://fioricet.home.sapo.pt Buy Fioricet Online]<br />
[http://foreclosure.home.sapo.pt Foreclosure]<br />
[http://meridia.home.sapo.pt Buy Meridia]<br />
[http://onlinecasino.home.sapo.pt Online Casino]<br />
[http://ultram.home.sapo.pt Buy Ultram Online]<br />
[http://valium.home.sapo.pt Buy Valium Online]<br />
[http://vioxx.home.sapo.pt Buy Vioxx]<br />
[http://xenical.home.sapo.pt Buy Xenical Online]<br />
[http://www.kub.kz/host/phentermine/ Cheap Phentermine]<br />
[http://adipex.home.sapo.pt Buy Adipex Online]<br />
[http://ambien.home.sapo.pt Buy Ambien Online]<br />
[http://hydrocodone.home.sapo.pt Buy Hydrocodone Online]<br />
[http://lortab.home.sapo.pt Buy Lortab Online]<br />
[http://lortabonline.freespaces.com Buy Lortab Online]<br />
[http://ovulationcalendar.home.sapo.pt Ovulation Calendar]<br />
[http://phentermine.home.sapo.pt Buy Phentermine Online]<br />
[http://vicodin.home.sapo.pt Buy Vicodin Online]<br />
[http://vicodinhp.freespaces.com Buy Vicodin Online]<br />
[http://wma2mp3.home.sapo.pt WMA to MP3 Converter]<br />
[http://xanax.home.sapo.pt Buy Xanax Online]<br />
[http://www.anzwers.org/trade/hydrocodone/ Buy Hydrocodone Online]<br />
[http://www.anzwers.org/trade/phenterminez/ Buy Phentermine Online]<br />
[http://www.anzwers.org/trade/fioricet/ Buy Fioricet Online]<br />
[http://www.anzwers.org/trade/viagraonline Buy Viagra Online]<br />
</div></div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2793InkboardIntegrationSchedule2005-07-16T22:32:35Z<p>64.58.0.54: updates</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Almost done; fixing a few last major bugs.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Almost done; need to implement notifyChildOrderChanged.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Working on tracking down text movement bug and proper implementation of undo/redo.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification. ''[In progress; I hope to be able to pass it off to Ted and Peter Saint-Andre when it's in good enough condition.]''</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2792InkboardIntegrationSchedule2005-07-12T06:21:43Z<p>64.58.0.54: updated schedule</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Mostly there; reworking ID scheme for XML nodes.]''<br />
** Integrate UI elements. ''[Done.]''<br />
** Integrate Jabber server communication code. ''[Done.]''<br />
** Integrate client communication code. ''[Done.]''<br />
** Integrate object listeners. ''[Reworking for new ID scheme.]''<br />
** Integrate send and receive code. ''[Done.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Have fixed most fatal crash bugs; working on document consistency issues.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2791InkboardIntegrationSchedule2005-07-02T09:49:24Z<p>64.58.0.54: schedule update</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: learning more as I integrate.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Done; will return to this as necessary.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Done; will return to this as necessary.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Started.]''<br />
** Integrate UI elements. ''[Server connection dialog has been integrated; "share with user" dialog is pending.]''<br />
** Integrate Jabber server communication code. ''[Not yet started.]''<br />
** Integrate client communication code. ''[Not yet started.]''<br />
** Integrate object listeners. ''[Not yet started.]''<br />
** Integrate send and receive code. ''[Not yet started.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Have fixed most fatal crash bugs; working on document consistency issues.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2790InkboardIntegrationSchedule2005-06-30T22:07:25Z<p>64.58.0.54: updated schedule</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[Inkboard code: familiar, Inkscape code: in progress.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[Mostly done.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Mostly done.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Not yet started.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Have fixed most fatal crash bugs; working on document consistency issues.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2789InkboardIntegrationSchedule2005-06-28T04:16:35Z<p>64.58.0.54: fixed whoops in a link</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[In progress.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[In progress.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Mostly done.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Not yet started.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Started bug cataloging and tracking.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=InkboardIntegrationSchedule&diff=2788InkboardIntegrationSchedule2005-06-28T04:15:56Z<p>64.58.0.54: inkboard+inkscape schedule - initial revision</p>
<hr />
<div><h2>Inkscape + Inkboard project schedule</h2><br />
<br />
In keeping with the usual unpredictability of software engineering projects, this schedule is very coarse, and time estimates overlap. Granularity will increase as progress is made and feedback is received.<br />
<br />
<h3>Week 0 - Week 1 (pre-June 24 - July 2)</h3><br />
* Enhance familiarity with Inkboard and current Inkscape code. ''[In progress.]''<br />
* Enhance familiarity with the Inkboard state machine and protocol. ''[In progress.]''<br />
* Learn about the class structure of Inkboard and how it integrates into Inkscape. ''[Mostly done.]''<br />
<br />
<h3>Week 1 - Week 3/4 (July 2 - July 16 / July 23)</h3><br />
* Begin and finish integration of current Inkboard codebase into Inkscape CVS. ''[Not yet started.]''<br />
<br />
<h3>Week 3 - Week 7/8/End (?) (July 16 - August 13/20 / September 1)</h3><br />
* Work on stabilization and bug-fixing of integrated Inkboard code. ''[Started bug cataloging and tracking.]''<br />
<br />
<h3>Time permitting</h3><br />
(in order of importance, to be juggled as necessary):<br />
* Complete user -> chatroom whiteboard support.<br />
* UI enhancements.<br />
* Session file support.<br />
* Add rudimentary chat facility based on Jabber.<br />
* Complete Inkboard protocol specification.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=SOC_Accepted_Proposals&diff=4806SOC Accepted Proposals2005-06-28T04:13:54Z<p>64.58.0.54: added link to Inkboard integration schedule</p>
<hr />
<div>== SOC Accepted Proposals ==<br />
<br />
Four proposals were accepted.<br />
<br />
* [http://www.csse.monash.edu.au/~mwybrow/soc-proposal.txt Connectors] - Michael Wybrow<br />
* [http://www.rose-hulman.edu/~yipdw/inkscape-proposal.txt Inkboard] - David Yip ([[InkboardIntegrationSchedule]])<br />
* [https://developer.berlios.de/docman/display_doc.php?docid=934&group_id=4098 OCAL Interface] - Greg Steffensen (project being developed at [http://developer.berlios.de/projects/ocalhelper Berlios])<br />
* DXF Import / Export (proposal below) - Matthew Squires<br />
<br />
<br />
=== DXF import/export ===<br />
The proposal pretty much follows the Perl funding outline that was linked on the SOC website.<br />
<br />
Name: Matthew Squires<br />
<br />
Project Title: Creation of a library for the import/export of dxf in Inkscape<br />
<br />
Benefits to Inkscape<br />
<br />
A library for importing/exporting dxf files would make Inkscape a more flexible<br />
piece of software especially for those that create technical drawings. For<br />
example, I have used Macromedia Freehand to import dxf technical drawings so I<br />
could add artistic elements for papers and presentations. Directly importing and<br />
exporting dxf in Inkscape would make Inkscape a more attractive piece of software<br />
for those that already have CAD drawings but would like to make them "presentable."<br />
<br />
Synopsis<br />
<br />
I will create a library that will import/export data to/from Inkscape from/to the<br />
dxf format. This library will directly import all of the basic properties common<br />
to the dxf format and Inkscape (e.g. lines and layers). Objects that do not<br />
directly convert (e.g. spirals) will be supported by using extra information to<br />
properly complete the translation. It should be assumed that any 3D data contained<br />
in the dxf will be flattened.<br />
<br />
Deliverables<br />
<br />
The conversion functions will be made to incorporate into Inkscape via a library.<br />
I will also include documentation of the library including examples. I would<br />
like to create a svg2dxf and a dxf2svg directly from the code, but I do not want<br />
to commit to delivery of stand-alone programs in the time allotted.<br />
<br />
Project Details<br />
<br />
I will create a library that will directly convert all of the directly convertible<br />
information between a dxf/svg. That includes but is not limited to: lines,<br />
splines, layers, and text. All 3D information will be flattened but I would<br />
imagine that in the future a simple method for translating elevation to layers<br />
could be implemented, but not this summer. Because dxf does not include units this<br />
information will need to be supplied for all conversions.<br />
<br />
Items that require additional information will be converted if the information is<br />
given. This is done in other programs (i.e. FlexPDE) that require more information<br />
than dxf can provide. An example would be importing a spiral from dxf into svg. <br />
Additional tags can be applied to the dxf to supply the additional information (e.g.<br />
revolution) to create a spiral in Inkscape. Some items that would be supported in<br />
dxf import are spirals, stars, color, fills, and text on a path. On the other hand<br />
a spiral can be exported to dxf as a series of splines. The user can set the export<br />
resolution, or use the default resolution. Some items that would be exported to dxf<br />
are spirals and stars. I would like to work on exporting text on a path, but at<br />
this time I won’t promise that it will be functional until I understand better how<br />
Inkscape performs this task.<br />
<br />
Project Schedule<br />
<br />
First I will take a few days to better understand the Inkscape file format. Then I<br />
will break the schedule into two pieces: svg->dxf and dxf->svg. For the dxf->svg I<br />
estimate that the directly convertible code (DCC) can be written in a 2-3 days, the<br />
non-direct conversion code (NDCC) in 3-4. I think the svg->dxf DCC will take 3-4<br />
days. The NDCC is a little more complicated because extra information will need to<br />
be processed, so I am going to estimate about a week for that code. The total is<br />
about 2.5 weeks. As mentioned on the Inkscape wiki all projects take about pi times<br />
longer to complete, so the completion of this code should be reasonable in a summer.<br />
The documentation code should be written at the same time functions are written. <br />
Example programs will be developed along the way as result of testing.<br />
<br />
Bio<br />
<br />
I am a physics Phd candidate at the University of Colorado and I have recently been<br />
using Inkscape to create figures for papers and presentations. I have been coding<br />
in C++ for about 5 years. I am self-taught in C++, but have some formal education<br />
in other languages. I would say I am a proficient programmer and can create good<br />
code. I have mostly worked on ing magnetic fields, but part of my code reads<br />
some basic information from dxf files to define the regions of interest (ROI). I<br />
am familiar with the dxf standard and what it takes to read dxf. I have looked at<br />
open source dxf libraries, specifically dime and QCad. I also recently found<br />
Blender reads dxf files. I would have no problem pulling code from those sources.<br />
<br />
I am familiar with the SVG format, and actually looked at reading ROI information<br />
from SVG's but for some reason several years ago chose dxf instead (probably because<br />
at the time I found better CAD editors). I have also used a variant of XML in<br />
LabVIEW to control the parameters of my experiment. A lab mate performed most of<br />
the coding, but I have a working knowledge of XML. I think there is open source<br />
code for reading XML tags, so I would like to find some code that already reads the<br />
XML tags and information from a file to hurry the project along.</div>64.58.0.54https://wiki.inkscape.org/wiki/index.php?title=Google_Summer_of_Code_2006&diff=1632Google Summer of Code 20062005-06-25T20:30:04Z<p>64.58.0.54: added Inkboard + Inkscape integration proposal link</p>
<hr />
<div>This page outlines some suggestions for tasks that could be performed for Googles Summer of Code project <br />
<br />
* [[SOC Writing Project Proposals]]<br />
* [[SOC Selection Criteria]]<br />
<br />
== File import/export code, (pdf, dxf, etc) ==<br />
* Implement a complete import/export cycle relying on no external apps (libs are ok if suitably x-platform) for another mainstream vector format. (ie dxf, pdf, ai...) implementing the import/export as a lib and plugging it in to Inkscape would be prefered, or as a pdf2svg type util that can be called.<br />
<br />
* DXF Import<br />
* DXF Export<br />
<br />
== Creation of a libpdf from the Scribus code ==<br />
* Extract the pdf creation code from Scribus and use it to form a libPDF which we can use. then plug it in. - Kinda linked to the above (This means of effectively having a libPDF for both projects. So, this is not replicating the code and having to maintain both, so you must work with Scribus too)<br />
<br />
== Convert renderer to Cairo ==<br />
* Convert the renderer over to [http://cairographics.org/introduction Cairo]. This is a major task. It may involve working on Cairo in areas where Cairo is not ready.<br />
<br />
== Break out the canvas to a widget ==<br />
* Create a GTK SVG canvas widget based off SPCanvas, to allow other projects to easily make use of an SVG canvas.<br />
<br />
== Create a Clipart Libary interface ==<br />
* Create an interface to allow easy insertion of clipart from the open clipart libary (OCAL) into inkscape documents. Allow sorting by categories, search for metadata keyword etc.<br />
<br />
== Integrate/extend Inkboard ==<br />
* Bring the virtual whiteboard functionality of inkboard into the main trunk, and extend it.<br />
* Use the ability to stream/recieve the changes in a doc to allow a session file to be recorded and played back later. <br />
Proposal: http://www.rose-hulman.edu/~yipdw/inkscape-proposal.txt<br />
<br />
== Diagram tools ==<br />
* Implement connectors for shapes with automatic line routing.<br />
<br />
<br />
<br />
= Ideas that received no viable proposals =<br />
<br />
== Color management ==<br />
* Implement a color management system to allow the use of spot colors and color profiles ([http://www.littlecms.com/ littleCMS?])<br />
<br />
== Marker editing and styling ==<br />
* implement a UI for the editing of markers, ideally on-canvas<br />
* create a widget for previewing and selecting markers, better than the current menu<br />
* make markers inherit their parent's stroke paint when that is changed (this is not provided by SVG, so we need to do this artificially)</div>64.58.0.54