Mail Archives: geda-user/2015/09/06/11:48:26.1
Lev (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> On Sat, 5 Sep 2015 16:51:37 -0800
> "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]"
> <geda-user AT delorie DOT com> wrote:
>
>
>> Peter suggested using the parser in pcb rather than rewrite in perl.
>>
>> I had a look and I think it's not a bad idea. Would get a faster
>> parser and not too painful I think. I'm considering using SWIG
>> with some functions to iterate over PCBType contents to rebuild
>> the lists perl-side. As a bonus you would get parsers for lots of
>> languages for cheap. It would be easiest to do this in-tree.
>>
>> Would this work for what you have in mind on your end?
>>
> I think it is a good idea to use something that is well written. I'm okay
> with SWIG. However, it doesen't have to be perl. So yes, if this is towrds the
> goal of creating a parser, I think this is a good way.
>
> Btw, it has a name now, it is called Apollon-PCB.
>
> I crated a github project, as my server went down. So I can grant you (and
> anyone) commit access.
>
> https://github.com/leventelist/apollon
>
> I look for other developers who can contribute to this project.
>
> As the readme states, I want to integrate this into pcb, OR create a brand new
> project, and use as much code as we can from gEDA/pcb.
>
> The schema is changed a bit. I removed hard wired attributes, and created an
> attribute table.
>
> Lev
>
>
>
Hi Levente,
You could ask for an account on upstream pcb.git and do your work in a
branch named like "home/levente/apollon", or any other branch name
starting with "home/levente/".
This way we can have the best of both worlds ;-)
Easier for you to cherry pick commits that get added after branching,
and vice versa.
Kind regards,
Bert Timmerman
- Raw text -