Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Kurt Cagle's OpenSVG Keynote

Posted by ScuttleMonkey on Wed Aug 17, 2005 04:24 PM
from the magnitude-with-direction dept.
Metaphorically writes "Kurt Cagle has posted a summary of his keynote speech from the SVG Open 2005. Inspiring for an SVG enthusiast, informative for any geek. He covers a lot of ground on XML and the next generation of GUI. It connects a lot of technologies that people might otherwise not totally grasp. If you haven't been following the development of XForms, E4X, SVG and XAML then this is a great way to catch up."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Anonymous Coward on Wednesday August 17 2005, @04:32PM (#13342918)
    <?xml version="1.0" ?>
    <plan>
      <step>Learn XML</step>
      <step>Give keynote speech about XML subset</step>
      <step>Profit!</step>
    </plan>
    • You forgot the <step/> before "Profit!"
    • by generic-man (33649) on Wednesday August 17 2005, @05:05PM (#13343157) Homepage Journal
      <?xml version="1.0" ?>
      <sentence type='declarative'>
      <!-- The user-agent should handle the closing period. -->
        <subject>
          <pronoun target='generic-man'>I</pronoun>
        </subject>
        <predicate>
          <verb sense='intransitive'>agree</verb>
          <prepositional_phrase>
            <preposition>with</preposition>
            <object>
              <adjective>this</adjective>
              <noun quantity='singular'>post</noun>
            </object>
          </prepositional_phrase>
        </predicate>
      </sentence>
    • <!-- And Now To Make That A Web Page :) -->
      <?xml version="1.0" encoding="utf-8"?>
      <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
      <xsl:output method="html"/>
      <xsl:template match="/">
      <html><head><title>The XML Underwear Gnomes Business Plan</title></head><body>
      <h1>XML Underwear Gnomes Business Plan</h1>
      <ul><xsl:apply-templates/>
      </ul></body></html></xsl:template>
      <xs
  • by KillShill (877105) on Wednesday August 17 2005, @04:32PM (#13342926)
    i'm really tempted to read the article and it isn't available.

    www.understandingxmlandtheslashdoteffect.com
  • What is this new technology and why should I care about it? The article link does not work, Slashdot effect.

    As a computer expert of 20 years and programmer of 15 years, how will this effect me? Will I have to learn totally new things, or does it build on the old ones? Who owns the patents to this new technology? Will Microsoft release their own version of it and crush everyone?
    • Re:Que? No Explaino! (Score:4, Informative)

      by AKAImBatman (238306) * <(akaimbatman) (at) (gmail.com)> on Wednesday August 17 2005, @04:49PM (#13343055) Homepage Journal
      What is this new technology

      SVG? New? Not that is news! SVG 1.1 was ratified on the 14th of January, 2003. Most SVG users either view the files in the Adobe Plugin [adobe.com], or translate to raster images [apache.org] for vector charting and the like. (I actually had a pretty cool 3D pie chart program for awhile there. SVG came out of one end, translated by Batik, then viewed as a PNG.)

      why should I care about it

      You shouldn't. It's just technology marching on. If you need to do vector graphics, you'll find it far more up-to-date and better supported than PostScript. If you don't need to do Vector graphics (or don't even know what vector graphics ARE) then you definitely don't care.

      As a computer expert of 20 years and programmer of 15 years, how will this effect me?

      You'll need a new bullet-point on your resume in a few years?

      Will I have to learn totally new things, or does it build on the old ones?

      You know XML? You know PostScript? How about ECMAScript? Yes? You're good to go then.

      Who owns the patents to this new technology?

      It's older than the hills technology. I dunno, maybe my great grandmother had a patent at some point, but there are none now. (Unless someone invents a stupid one like "Method for storing Vector graphics in XML." Hmm... maybe it is patented.)

      Will Microsoft release their own version of it and crush everyone?

      Microsoft Internet Explorer (Exploder in my book) needs the Adobe plugin. AFAIK, Microsoft is mostly ignoring it.
      • >>> "AFAIK, Microsoft is mostly ignoring it."

        Well you clearly haven't come across the beta for Acrylic - http://www.microsoft.com/products/expression/ [microsoft.com] - which merges vector graphics (SVG, yee-haw) and raster.

        I use Inkscape still as my download of Acrylic didn't even get past the install stage (I'm using Inkscape on Slack and WinXP - if you haven't got the latest install get it now, it's awesome). I've read good things about Acrylic(some whilst stood in my local news agents!).

        I'd be prepared to bet
      • Most SVG users either view the files in the Adobe Plugin, or translate to raster images for vector charting and the like

        Actually, some users use a subset of SVG on their desktop, especially some Gnome users on Linux for their icons (not for all the GUI yet), with SVG themes like Nuvola.
    • by starling (26204) <strayling20@gmail.com> on Wednesday August 17 2005, @05:04PM (#13343153)
      [...]how will this effect me?

      It won't. Your parents did that.
    • SVG [wikipedia.org] or "Scalable Vector Graphics" is a way of describing visual information (graphics is perhaps misleading, as it can include text) in a way that is independant of parameters like dimensions of your display, type of display device, etc.

      Some advantages of SVG:
      • For the Web, the browser gets to decide how to render graphical information (so for example, client-side anti-aliasing preferences can be used).
      • because the client has access to the high-level description, you could do something like write a browser
        • The logo at the top of your screen is here: http://images.slashdot.org/title.gif [slashdot.org].

          It is 3473 bytes. As an SVG, it would be something like this (really awful, off the cuff) example: http://www.ajs.com/~ajs/slashdot.svg [ajs.com] which is 3255 bytes uncompressed and I'm sure that that's wasteful in several ways because I'm an SVG newbie. Given compressed HTTP bodies by default, the SVG would save Slashot quite a bit in bandwidth every month.

          SVG is a lot smaller than you think....

          Better, your browser could do the right t
            • > http://images.slashdot.org/title.gif [slashdot.org]

              That's not a logo.

              Yes, it is. Slashdot has (as another poster pointed out) two primary logos. The other is the slash and the dot, and at your suggested 80-pixes, that's 2744 bytes as a PNG [ajs.com] and 2189 as an uncompressed SVG [ajs.com].

              Again, SVG is a lot smaller than you think. When you start trying to display very complicated images (like the classic tiger postscript demo), that's where it becomes larger, and that's really not what SVG is best at, and at lower resolutions, I wo

    • Microsoft have already tried to push their own vector markup language called VML (surprise). I think it was proposed as a standard at one point, but it tanked. So I expect that even MS would be enthusiastic about SVG - it's already gotten enough momentum that it would be quite hard and rather pointless trying to go against it.

      If there is a problem with SVG & many other W3C recommendations is that they're getting to be horribly, horrifically difficult to implement and implementing SVG (for example) means

  • MirrorDot (Score:5, Informative)

    by Anonymous Coward on Wednesday August 17 2005, @04:37PM (#13342967)

    MirrorDot of the Keynote [mirrordot.org]

  • SVG and Mozilla (Score:3, Informative)

    by starwed (735423) on Wednesday August 17 2005, @04:44PM (#13343020)
    There's a blog post here [mozillazine.org] with a link to another presentation from the conference.
  • by ikekrull (59661) on Wednesday August 17 2005, @05:20PM (#13343257) Homepage
    It seems to me that any W3C standard needs a complete and free reference implementation before it should be ratified as a W3C standard.

    Even if it is somewhat slow and clunky, at least it shows that it is possible to do.

    At this point, it is such a monumental task to implement all the intricacies of the full SVG specs that *nobody* - Not Microsoft,Adobe,Apache, Sun,Apple of anyone in the open source arena is able to do it, or even come close, it seems.

    Apps like Inkscape are probably the most advanced SVG showcases, but for some reason everybody wants to write their own browser plugin from scratch instead of starting from the authoring tools and extending them to support a 'playback' mode.

    Has nobody noticed Flash and what made it so popular?

    You can publish standards till the cows come home but the only way anything becomes popular is by being useful.

    A reference implementation of a standard is immediately useful, both to users and to developers. Why isn't it there, and if the answer is 'it's too much work' then maybe, just maybe, the overcomplexity of the standard is the problem.

    Standards are a good thing, but standards must be both implementable, and accompanied by an implementation, unless they want to float in limbo for years like SVG.

    • > It seems to me that any W3C standard needs a complete and free reference implementation before it should be ratified as a W3C standard.

      XForms [w3.org] had as exit criteria for becoming a recommendation one complete and two interoperable implementations . One of the complete implementations that served to meet this goal was X-Smiles [x-smiles.org], a GPL implementation of XForms (and co-indcidentally SVG, XHTML 1.0, CSS of various levels, SMIL, etc.).

      The Mozilla XForms [mozilla.org] project also aims to provide a complete XForms 1.0 implem
    • At this point, it is such a monumental task to implement all the intricacies of the full SVG specs that *nobody* - Not Microsoft,Adobe,Apache, Sun,Apple of anyone in the open source arena is able to do it, or even come close, it seems.

      Complete implementation? No. But pretty much every feature has been implemented and tested in some implementation as of the end of last year:
      http://www.w3.org/Graphics/SVG/Test/20030813/stat u s/matrix.html [w3.org]

      Apps like Inkscape are probably the most advanced SVG showcases,
    • It seems to me that any W3C standard needs a complete and free reference implementation before it should be ratified as a W3C standard.

      This is insightful? Nobody has ever made a full implementation of CSS2, and it's very popular. And the word "standard" doesn't come from the W3C - Their finished documents are called "recommendations".

      IMNSHO: SVG will become popular because it can be used to make tiny, scalable, non-blocky-printable images, which will be popular with the average joes on modem/ISDN, shortsi

      • The other approach is to first let the world sort out what features are actually desirable, then standardize what's there and try to get implementers to converge towards the standard... Common Lisp is an example of this from programming languages.

        Don't, don't, don't follow Common LISP as an example. Common LISP has been a disaster. There are far fewer people earning their living from LISP now than there were before Common LISP standard was introduced, and far fewer programs in regular use written in LISP.

        Common LISP is a very bad standard. As Scott Fahlman [cmu.edu] wrote [google.com]:

        The result is a language that... not even its mother could love. Like the camel, Common Lisp is a horse designed by committee. Camels do have their uses.

        He should know. As he says on his home page [cmu.edu]:

        I was one of the principal designers of the Common Lisp language.

        Common LISP essentially destroyed LISP as a usable, productive language. It made an incredible number of simply wrong technical decisions; and too many of those decisions were made by the smaller companies of the eastern United States - Symbolics, LMI, Franz - trying to write a standard which was as different as possible from InterLISP [wikipedia.org], in order to kill competition from Xerox. I'm not pretending InterLISP was brilliant or the answer to all problems. It wasn't. Like Common LISP, it was a LISP2, making an artificial distinction between data and code; and it was in many ways clumsy and unorthogonal itself. But there was a great deal of creativity coming out of the InterLISP community, which Common LISP effectively killed.

        We would have been so much better with a standard based on Portable Standard Lisp [metu.edu.tr], or on EuLisp [bath.ac.uk], or on Scheme [mit.edu]. We would have been so much better with no standard at all. Instead, we got a LISP2 with a bizarrely complex lambda-list syntax, with a comment syntax which was incompatible with the LISP reader (so that in-core editing and development were effectively impossible), with so many horrible design errors.

        Of course, it succeeded in its primary goal. Xerox was driven out of the LISP marketplace. But the cost for LISP has been horrendous: the language has been effectively destroyed. And for what was and should be the queen of programing languages, that's a disaster.

        Oh, yes - I was during the eighties a very junior member of the British Standards Institution's LISP working group. I was there. I still think LISP is the best possible programming language, but these days I use Java.

  • by Soong (7225) on Wednesday August 17 2005, @05:22PM (#13343273) Homepage Journal
    I had some data, I wanted to lay it out graphically, a little perl script to transform it and *poof!* there it was!

    Although, batik [apache.org] is a little bit slow. Hmpf. The Adobe plugin is nice though.
  • by michaelbuddy (751237) on Wednesday August 17 2005, @06:59PM (#13343820) Homepage
    What is so cool about SVG is talked about in this keynote. SVG, is vector graphics AND text, AND placed raster images, AND animation described in an open, easy to read format.

    One advantage is that you can design a webpage the same way you design a printed piece. Where you have just as much control over it. MS explorer requires an adobe plugin to display it, similarly to how it displays flash. Firefox is going to display SVG natively in the 1.1 browser (actually already does with the deerpark alphas.

    The code is easily visible like HTML. The desktops that use SVG for the gui, I don't know much about, but it's fantastic. Nice icons, or buttons or any visual element that is smaller in file size, breaks out of the square we are used to, and the elements can be enlarged or reduced and still be rendered beautifully.

    check out inkscape if you want to experiment with svg, or the open clipart library to see some cool examples. of SVG.

    http://inkscape.org/ [inkscape.org]
    http://openclipart.org/ [openclipart.org]

    Here's what mozilla is doing with SVG:
    http://www.mozilla.org/projects/svg/ [mozilla.org]