Compiling svg how and why
This presentation is the property of its rightful owner.
Sponsored Links
1 / 14

Compiling SVG: How and Why PowerPoint PPT Presentation


  • 86 Views
  • Uploaded on
  • Presentation posted in: General

Compiling SVG: How and Why. Michael Levy , Quetzalcoatl Bradle y and Calin Somosan NewHeights Software Corporation. The Natural History of UI-1. The Natural History of UI-2. The Natural History of UI - 3. The Natural History of UI - 4. Convergence. Human Interface Guidelines

Download Presentation

Compiling SVG: How and Why

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Compiling svg how and why

Compiling SVG: How and Why

Michael Levy, Quetzalcoatl Bradley and Calin Somosan

NewHeights Software Corporation


The natural history of ui 1

The Natural History of UI-1


The natural history of ui 2

The Natural History of UI-2


The natural history of ui 3

The Natural History of UI - 3


The natural history of ui 4

The Natural History of UI - 4


Convergence

Convergence

  • Human Interface Guidelines

    • Are metaphors still appropriate?

    • Do they reflect converged offerings?

    • Can they project a brand?

  • Mitel Design Center

    • Unify the device (phone on desk) and application

    • Input vehicle should be irrelevant to user


What about web applications

What about Web Applications?

  • Interim technology

    • Many advantages, but

    • Step backwards in responsiveness

      • Human perception is continuous, not discreet

      • Transaction based processing is as bad as Menu driven DOS-like processing


The role of the architect

The Role of the Architect

  • GUI Libraries

    • Simplify programming

    • Enforce “look-and-feel”

    • Biased towards Shell designers metaphor

    • Too complex for industrial designer

  • Today’s design tools

    • Illustrator, Flash


New design paradigm

New Design Paradigm


Helixrad

HelixRAD

  • Graphical element has 4 major parts

    • Template

      • VML/DHTML/CSS

    • Parameters

    • Elements

      • Attribute invariants for each element

    • Semantics

      • Handlers for actions (Javascript)


Why use svg

Why use SVG?

  • Elegance/ power of descriptive language

  • Tools support

    • Xml compliant

    • Graphics editors


Why compile

Why Compile?

  • Interpreted code is not, and never will be, good enough to compete with compiled code

  • Example - menu as SVG:

    • Load the XML

    • Create the DOM

    • Change the text attribute for the Menu name

    • Clone an item node for each menu item

    • Set the text attribute of each item

    • Traverse the resulting DOM tree, rendering it.


How to compile svg

How to Compile SVG

  • On Win32, GDI+ library provides most of what is needed

  • Provide an abstract library for general elements

  • Compiler subclasses or instantiates particular SVG files

  • Scheme needed to automate attachment of semantic actions


Conclusions and future work

Conclusions and Future Work

  • Mismatches between GDI+ and Adobe reference implementation are problematic

  • Better SVG tool support:

    • Grouping

    • Most meaningful element that fits

      • EG: Square instead of four paths; circle instead of (closed) arc

  • SVG lacks adequate alternative to DOM clone for class instantiation

  • Standards for semantics?


  • Login