Difference between revisions of "SVG Tiny Compliance"

From Inkscape Wiki
Jump to navigation Jump to search
 
(* Move some text to Animation-(Timeline) and refer to that page.)
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
> What do you think if we set a goal for 0.42 or 0.43 to fully support
It'd be a nice feather in the cap to be able to declare full compliance to one of the SVG specs.  SVG Tiny is a good thing to aim for.  A number of developers have voiced support for trying to achieve this.
> 100% of SVG Tiny?  That'd be a nice feather in the cap to be able to
> declare full compliance to one of the SVG specs.


As a first glance without looking much at either the spec or inkscape
As a first glance without looking much at either the spec or inkscape
source, I believe we need the following: don't rely on style attributes
source, I believe we need the following: don't rely on style attributes
working (use fill=... attributes); switch; SVG fonts; animation.
working (use fill=... attributes); switch; SVG fonts; animation.


  Styling
In more detail:
    We must write `fill="..." etc. attributes instead of using
    style="fill:...".  (I.e. when writing SVG Tiny documents, we must
    not use style attributes -- or at least use only "redundant"
    style attributes if that's easier to implement.)


  switch Minimum requirement is that we render it correctly (e.g. as a
Styling:
    viewer would, showing just one child).  Interface for viewing other
* We must write `fill="..." etc. attributes instead of using style="fill:...". (I.e. when writing SVG Tiny documents, we must not use style attributes -- or at least use only "redundant" style attributes if that's easier to implement.)
    branches would be nice (perhaps a non-modal dialog box listing the
    children named by their requiredFeatures, requiredExtensions and
    systemLanguage attributes. The layers dialog box may be a good
    base.


  SVG fonts: font, font-face, font-face-src, font-face-name,
<switch>:
  missing-glyph, glyph
* Minimum requirement is that we render it correctly (e.g. as a viewer would, showing just one child).  Interface for viewing other branches would be nice (perhaps a non-modal dialog box listing the children named by their requiredFeatures, requiredExtensions and systemLanguage attributes.  The layers dialog box may be a good base.
    massifr has started work on this.  He's still new to inkscape
    source code, so could use guidance.


  a  Especially relevant to Inkview.  For Inkscape (editor), ability
SVG fonts: font, font-face, font-face-src, font-face-name, missing-glyph, glyph:
    to launch URLs from the context menu might be nice but not
* massifr has started work on this.  He's still new to inkscape source code, so could use guidance.
    essential.  An ability to create <a> elements other than using the
    XML editor would also be nice.


  Animation: animate, animateColor, animateMotion, animateTransform,
Anchors (&lt;a&gt;):
  mpath, set
* Especially relevant to Inkview.  Inkscape can create <a> elements with right-click on an existing item, and has a textual dialog box for filling in attribute values (object-attributes.cpp).  We have a "follow link" item in the contextual menu, but it does nothing (object-ui.cpp:sp_anchor_link_follow).
    My reading is that we can't claim to support all of SVG Tiny
    without supporting animation.


    Easier in a viewer than in an editor... For editing interface,
Animation: animate, animateColor, animateMotion, animateTransform, mpath, set:
    Brisgeek says that Macromedia Flash is a good example.  He couldn't
* My reading is that we can't claim to support all of SVG Tiny without supporting animation.
    off hand think of free software examples, but mentioned Moho as a
* See [[Animation-(Timeline)]] for implementation notes.
    gratis-but-non-free example.  (Written in Java.)
    F4L is a non-functional free-software mock-up of the Flash 4 interface.
    Of course we should search for existing relevant free software.


    For advanced stuff (research territory), we may be able to work
(&lt;foreignObject&gt;: I believe we don't need to do anything to support the foreignObject element.  We already have the property of not discarding unrecognized elements like foreignObject and its children.)
    with the project Opera people at INRIA, possibly working with the
    Madeus editor.  (I mention this example only because our group at
    Monash has worked with them before.)
 
(I believe we don't need to do anything to support the foreignObject
element.  We already have the property of not discarding unrecognized
elements like foreignObject and its children.)

Revision as of 23:48, 6 January 2005

It'd be a nice feather in the cap to be able to declare full compliance to one of the SVG specs. SVG Tiny is a good thing to aim for. A number of developers have voiced support for trying to achieve this.

As a first glance without looking much at either the spec or inkscape source, I believe we need the following: don't rely on style attributes working (use fill=... attributes); switch; SVG fonts; animation.

In more detail:

Styling:

  • We must write `fill="..." etc. attributes instead of using style="fill:...". (I.e. when writing SVG Tiny documents, we must not use style attributes -- or at least use only "redundant" style attributes if that's easier to implement.)

<switch>:

  • Minimum requirement is that we render it correctly (e.g. as a viewer would, showing just one child). Interface for viewing other branches would be nice (perhaps a non-modal dialog box listing the children named by their requiredFeatures, requiredExtensions and systemLanguage attributes. The layers dialog box may be a good base.

SVG fonts: font, font-face, font-face-src, font-face-name, missing-glyph, glyph:

  • massifr has started work on this. He's still new to inkscape source code, so could use guidance.

Anchors (<a>):

  • Especially relevant to Inkview. Inkscape can create <a> elements with right-click on an existing item, and has a textual dialog box for filling in attribute values (object-attributes.cpp). We have a "follow link" item in the contextual menu, but it does nothing (object-ui.cpp:sp_anchor_link_follow).

Animation: animate, animateColor, animateMotion, animateTransform, mpath, set:

  • My reading is that we can't claim to support all of SVG Tiny without supporting animation.
  • See Animation-(Timeline) for implementation notes.

(<foreignObject>: I believe we don't need to do anything to support the foreignObject element. We already have the property of not discarding unrecognized elements like foreignObject and its children.)

Retrieved from "https://wiki.inkscape.org/wiki/index.php?title=SVG_Tiny_Compliance&oldid=4510"