diff --git a/ANNOUNCEMENT-0.0.7 b/ANNOUNCEMENT-0.0.7 new file mode 100644 index 0000000..53f288b --- /dev/null +++ b/ANNOUNCEMENT-0.0.7 @@ -0,0 +1,59 @@ +Greetings all, + +it's time for the next release of Gerber Viewer, aka gerbv, +the "aperture macros 'r' us"-release. + +This time I have finally added support for aperture macros. +The aperture macros are converted to small programs in a +very simple "assembler". This "program" is currently executed +everytime an aperture described with this macro is drawn. +Therefore the speed of (re)drawing pages with many aperture +macros can be slow. If you find the slowness tiresome then +complain. I have a couple of ideas on speed improvements, but +I have had correctness as main goal. + +I have written a short description of the assembler in +doc/aperturemacros.txt. There are some caveats though. +Explicit X and Y and exposure given in aperture macros +are currently ignored. + +The RS-274X specification is not always very clear about these +aperture macros. I have tried to verify them as well as I can +(using the hand hacked page in examle/am-test/am-test.gbx), but +it's not 'til it hits reallity it becomes most obviuous how it +really should be. + +I do not guarantee any kind of correctness, even though I've +done my best. If you find any problem, please report back to +me preferably with an example. There are some comments +in the file src/draw.c about question marks I've had. So if +you feel that you know anything about aperture macros, please +look in the code and send some comments to me. + +Please note that the Scheme backend doesn't know anything +about macros as of yet. + +Comments, patches and suggestions are, as always, very welcome. + +Homepage for gerbv is still http://gerbv.sourceforge.net/ + +To download gerbv goto + http://prdownloads.sourceforge.net/gerbv/ +and grab gerbv-0.0.7.tar.gz + +To install the program do +1. gzip -dc gerbv-0.0.7.tar.gz | tar xf - +2. cd gerbv-0.0.7 +3. ./configure +4. make install + +Interesting configure options are: +--help : Lists all options +--disable-batch : Disable compilation of Guile/Scheme backends +--prefix= : Install from dir + + +What's new in 0.0.7 +- Aperture macros! +- Improved detection of drill- or gerber file. + diff --git a/index.html b/index.html index 17fe764..57e4592 100644 --- a/index.html +++ b/index.html @@ -46,7 +46,7 @@
  • Download the source
  • Browse the CVS repository -
  • Info gathered on RS-274X here. +
  • Info gathered on RS-274X here.

    Packaging

    @@ -75,7 +75,7 @@ gerbv is basically known to compile on all system which the above mentioned libraries compile on, basically all flavors of *ix. It has been tested on:
      -
    • Linux (2.2.18pre21) +
    • Linux (2.2/2.4)
    • NetBSD/i386 (1.4.1) (getopt_long not available)
    • NetBSD/Alpha (1.5.1)
    • Solaris (5.7 and 5.8) (getopt_long not available) @@ -88,12 +88,16 @@ License (GPL) version 2.0. See the toplevel COPYING file for more information.

      Programs and associated files are:
      -Copyright © 2001 by Stefan Petersen and the respective +Copyright © 2001, 2002 by Stefan Petersen and the respective original authors (which are listed in respective files).

      News

        +
      • 2002-02-10 : 0.0.7 release availble + here. + Announcement is readable here. +
      • 2001-12-15 : 0.0.6 release availble here. Announcement is readable here. @@ -139,8 +143,7 @@ original authors (which are listed in respective files).

        What's there:

          -
        • Parses a lot of Gerbers. Considered usable with the excepetion for the - aperture macros. +
        • Parses a lot of Gerbers, including aperture macros.
        • Drill file support(NC drill/Excellon).
        • Autodetection of Gerber-or-Excellonfile.
        • Panning and zooming. @@ -154,7 +157,6 @@ original authors (which are listed in respective files).

          What is missing:

            -
          • Aperture macros (red dots shows where they should be).
          • Explicit setting of color on layer.
          • Gerbers definition of layers are ignored.
          • Proper documentation on how to interface the backend.