X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ar5K3OfhlD8MwIIBt/brZzQV9rqfsLJIOr4Fr3UOWwI=; b=Ny6YqKVLuj9f5O3Bo9o9NhK0iwVOJLy/maIPG7usHA74mdJW8PrZtaUHZGIyN4gBeN Gj6c3nq9EKIOHALIQ4gWoloqrivsGaW8vkWMwJBaT+709gEVjh1qFQ6kfT+Ici+wC0Zu 3tezsne6IY+Yz/zGTBTqahSnpJur3ACSC57F2j2F0NV2gFlW0+1+IIMAoddwPZpaontM 3iz8g+dFUB+nG/75hs5E1IHBVyh02SocJItpS8oIpdcviH/BDDXbcjFO/kQjkDjA4b9y ASzZQV3H53sC38FJwfhlxHEo+F5f+W75/KFFfzk7OmHetSFF3iE6QYSHYaVsjAlaVUH3 wW0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ar5K3OfhlD8MwIIBt/brZzQV9rqfsLJIOr4Fr3UOWwI=; b=Ur9czSKQtYPETUQfuah2gkMUasf9avSg2eWQ/GCYrdOfCWKZ2T17VG4lZ45x/fG3yI 9U7YkWNG0w4kj7lT+tNDLVh/FIX8Dxp5vANDEhezHVhteRLf9Vayqb0EuRW5vd29ux10 4nhFGktCiRO1GkKW98GW5l7bDg3T0PH2OwuKvvxokvo9puhmLpFF+l0QSGowED6sRC3B F7IUwd07OSFe0sG6AeG2x2sGrEJ9kAm+7V28AaQnCKHWRqfIxENjOvG2rRdQIvvSbqxZ Tovruq0ZRtrDQvPyjvhYhAyl5czKARVRoqapBJUT5Ju1NWH0ykQ1IBx7H8sxlpSlkIf7 jP4w== X-Gm-Message-State: AMke39mWCnsKjQ9gtz7x5cR6hvTsBNpxdkHMkrUc4uLVXTyZKieOm3qVrhypXbean4MI50Ruqx2BxX25PuvNqA== X-Received: by 10.200.50.18 with SMTP id x18mr15913489qta.58.1486853870466; Sat, 11 Feb 2017 14:57:50 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20170211183257.GP21523@foo.stuge.se> References: <20170211174559 DOT GM21523 AT foo DOT stuge DOT se> <20170211183257 DOT GP21523 AT foo DOT stuge DOT se> From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" Date: Sat, 11 Feb 2017 22:57:50 +0000 Message-ID: Subject: Re: [geda-user] Announcement - openaltium release To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a1143ac58c83c4705484924b8 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --001a1143ac58c83c4705484924b8 Content-Type: text/plain; charset=UTF-8 On 11 February 2017 at 18:32, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: > Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] > wrote: > > > I know there are people looking into file translation - and I released it > > in the hope it would be useful. > > > > Something you can use in edacore? > > That's what I was thinking. The hard part of edacore is data models, > so it's very interesting to see what can come out of Altium! > > I know there's a tool converting Altium to KiCAD to also look at. > Yes, I did see that (after I wrote the start of this code). I have added a number of additional fields they supported to my code, but did not get as far as attempting to convert entire schematics or layouts. (Wasn't my use-case... I was just after some symbols, footprints, 3D models a vendor had in Altium format). > > If anyone wants to contribute, that would also be cool. > > How about releases? Packaging I mean. Are you interested in doing > that, or would you be cool with someone else doing it, and maybe > even running a repo elsewhere? > Hadn't thought of it, but I suppose were someone interested - it could be cool. github was a convenient place to throw the repository initially, although I almost went repo.or.cz. geda-project.org would be possible (if I ask DJ, but I also wanted to make it more "neutral" project wise). I figured people could work on the repository in any of these places though. FWIW, the "library" isn't really super useful just yet as a proper library - and if it were to be released as a tarball release for packaging - the example program (command line conversion tool) probably ought to be renamed something like "openaltium" or "altium2geda" or whatever. Currently the code basically just reads the Altium files, walks the data within and printf's geda-compatible output as it goes along. As you say, data-models are hard... at some point it would be nicer if it actually parsed the Altium file to some internal representation, then emitted from that. (Needs work to be clean code!) Final PS... I wonder how long it is before I get legal grief for calling it "openaltium" / "libopenaltium"... the title was meant to be descriptive (a library for opening Altium files) - but I can sort of imagine Altium might be unhappy with the name. --001a1143ac58c83c4705484924b8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 11 February 2017 at 18:32, Peter Stuge (peter AT stuge DOT se) [via ged= a-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com= ] wrote:
=C2=A0
> I know there are people = looking into file translation - and I released it
> in the hope it would be useful.
>
> Something you can use in edacore?

That's what I was thinking. The hard part of edacore is data mod= els,
so it's very interesting to see what can come out of Altium!

I know there's a tool converting Altium to KiCAD to also look at.

Yes, I did see that = (after I wrote the start of this code). I have added a number of additional= fields they supported to my code, but did not get as far as attempting to = convert entire schematics or layouts. (Wasn't my use-case... I was just= after some symbols, footprints, 3D models a vendor had in Altium format).<= br>

=C2=A0
> If anyone wants to contribute, that would also be cool.

How about releases? Packaging I mean. Are you interested in doing that, or would you be cool with someone else doing it, and maybe
even running a repo elsewhere?

Hadn'= ;t thought of it, but I suppose were someone interested - it could be cool.= github was a convenient place to throw the repository initially, although = I almost went repo.or.cz.=C2=A0 geda-project.org would be possible (if I a= sk DJ, but I also wanted to make it more "neutral" project wise).= I figured people could work on the repository in any of these places thoug= h.

FWIW, the "library" isn't really super u= seful just yet as a proper library - and if it were to be released as a tar= ball release for packaging - the example program (command line conversion t= ool) probably ought to be renamed something like "openaltium" or = "altium2geda" or whatever.

Currently the code b= asically just reads the Altium files, walks the data within and printf'= s geda-compatible output as it goes along. As you say, data-models are hard= ... at some point it would be nicer if it actually parsed the Altium file t= o some internal representation, then emitted from that. (Needs work to be c= lean code!)


Final PS... I wonder how long = it is before I get legal grief for calling it "openaltium" / &quo= t;libopenaltium"... the title was meant to be descriptive (a library f= or opening Altium files) - but I can sort of imagine Altium might be unhapp= y with the name.

--001a1143ac58c83c4705484924b8--