[Bug 26299] New: Add a "9-slice element" in the next version of the SVG specifications

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26299

            Bug ID: 26299
           Summary: Add a "9-slice element" in the next version of the SVG
                    specifications
           Product: SVG
           Version: SVG 2.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Basic Data Types
          Assignee: schepers@w3.org
          Reporter: fmuaddib@gmail.com
        QA Contact: www-svg@w3.org

Created attachment 1492
  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1492&action=edit
9-slice graphic element contraints

The 9-slice scaling grid has been around in desktop graphics software for some
years already and is well known to users of Flash and Illustrator. It's a
brilliant technique for scaling images by dividing them into sections that have
a fixed size (the corners) and sections that are flexible (the edges and the
center). In fact this method is so powerful that 9-slice elements are standard
classes in most development platforms (Android, Flash, Flex, etc). A similar
technique (9-tiles or 9-grid) is used in HTML pages and native 9 sliced images
are exported by graphic software like Photoshop.
The only platform missing 9-slice elements is the SVG one. This means that to
create a 9-slice svg element we currently need to use convoluted techniques
that are quite complicated to implement, like this popular one devised by Dirk
Weber:

http://w3.eleqtriq.com/2014/03/the-holy-grail-of-image-scaling/

Because of this you cannot even make a resizeable button (a very common web
page element) with SVG without resorting to tricks.

To solve this problem affecting all web designers I propose to add a "9-slice
element" in the next version of the SVG specifications. It will be a special
group element, with some simple transformation constraints applied to any 9
elements composing the group.

Thank you.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 9 July 2014 19:18:34 UTC