[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: web version of gschem/pcb



    web-geda would save and load files in the current geda format and only
    draw in SVG.  SVG is really efficient to parse in javascript, panning
    and zooming will as responsive or more responsive than desktop-geda.
    SVG also has built in events such as mouseover and click that work on
    vector elements.
    --- On Mon, 6/20/11, Andrew Poelstra <asp11@xxxxxx> wrote:

      From: Andrew Poelstra <asp11@xxxxxx>
      Subject: Re: gEDA-user: web version of gschem/pcb
      To: "gEDA user mailing list" <geda-user@xxxxxxxxxxxxxx>
      Date: Monday, June 20, 2011, 2:46 PM

    On Mon, Jun 20, 2011 at 10:42:45AM -0700, Josh Jordan wrote:
    >     I think it would be a big advance to port the gschem/pcb formats
    to
    >     javascript and svg.  It would make geda accessible to every
    platform
    >     and really make it easy for new users to get started.  It would
    make
    >     development easier if you only support a set of standards instead
    of
    >     different build environments that overall run on a minority of
    the
    >     systems out there.  Javascript and SVG with local data can
    perform as
    >     well as any desktop application in 2d graphics.
    >     -Josh Jordan
    SVG is hard to read, hard to diff, hard to parse and hard to validate.
    It's not something we would want geda/pcb core to care about. What
    happens when people open pcbs in inkscape and draw gradients, filters,
    links, animation, etc?
    How would ideas like DRC rules, electrical attributes, netlists and
    pin mappings translate to/be preserved by browsers and SVG editors?
    Importing and exporting to (a limited subset of) SVG would be very
    cool. I don't mean to discourage people from exploring this. But I
    doubt very much that full functionality could be achieved from a svg-
    based webui.
    Looking far into the future, a nice path would be:
      1. Figure out how we want to handle symbols and layers and the
         other ugly parts of the current file formats.
      2. Move pcb and gschem to appropriate (extensible) file formats
         like xml/yaml/sexprs/whatever.
      3. Get a javascript parser -for these formats-
      4. Build a web-based system that works with gEDA.
    --
    Andrew Poelstra
    Email: asp11 at sfu.ca OR apoelstra at wpsoftware.net
    Web:   [1]http://www.wpsoftware.net/andrew/
    _______________________________________________
    geda-user mailing list
    [2]geda-user@xxxxxxxxxxxxxx
    [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user

References

   1. http://www.wpsoftware.net/andrew/
   2. file://localhost/mc/compose?to=geda-user@xxxxxxxxxxxxxx
   3. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user

_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user