On Dec 13, 2007, at 7:03 AM, Steve Meier wrote:
>
>
> I am in agreement with the concept of a database conating all of this
> and more and then the database application could generate symbols that
> gschem could use and it could also be queeried for the additional info
> that the drc or netlister
> (after
> i complete the basic schematic, symbol file io migration to guile)
> and a
> trivial translation application.
>
> Steve Meier
>
>
>
> Dan McMahill wrote:
>> Steven Ball wrote:
>>
>>> The PDIF writer seems to be able to convert anything
I've been thinking about this a bit, and here's my 2 cents:
gschem and pcb both really just want light symbols/footprints. It
would never really be a good idea to expect to stick one into the
other, I mean, what if you change packages or something? I guess you
could up rev the schematic o
Howdy guys,
I'd noted this before, but it had been a while and it still seems to
be an issue.
If I place an image, say, a logo, on my schematic, if I do not zoom in
on it before printing, gschem will print it very blocky, like it
scales it to what it is currently set to on the scre
I was just looking into this myself. You have to explicitly tell SVN
that it can modify your file by setting the svn:keywords property, ie:
$ svn propset svn:keywords "LastChangedDate Author" schematic.sch
Of course, I have not tested, but this is what the docs at
http://svnbook.red-bean.com
, 2007, at 12:28 PM, Steve Meier wrote:
> Sure post an example and see if you can convert a symbol to an ascii
> format.
>
> Steve Meier
>
> On Wed, 2007-11-28 at 12:19 -0700, Steven Ball wrote:
>> On Nov 28, 2007, at 11:48 AM, Steve Meier wrote:
>>
>>> Ste
On Nov 28, 2007, at 11:48 AM, Steve Meier wrote:
> Steven,
>
> Are the files in a text based format?
>
There is a text header (PC-CAPS database file version, copyright), and
then the rest of the file is binary gibberish.
However, running it through the 'PDIF Writer' produces a .pdf, which
i
On Nov 28, 2007, at 9:53 AM, Dan McMahill wrote:
> Peter Clifton wrote:
>> On Wed, 2007-11-28 at 12:41 -0300, Alex Lopes Pereira wrote:
>>> Does someone knows how to convert a schematic made in PCAD to gEDA
>>> gschem ?
>>>
>>> Thanks a lot,
>>> Alex
>>
>> Not off the top of my head, but if PCAD
On Nov 15, 2007, at 1:01 PM, DJ Delorie wrote:
>
> That's why I license all my stuff so that you don't need to worry
> about the license :-)
Much appreciated. I currently work for a small company doing
electronic repair and design, and the gEDA suite is just the ticket
for getting things do
So, to go on a tangent here, what about 'code' in the form of Gerbers
and etc produced by PCB? Would you consider the resultant board
produced by PCB to fall under a GPL license? Would I have to offer
'source' if I sold boards produced with the software?
I realize a lot of the 'code' is s
s Lepple wrote:
> On Sep 27, 2007, at 6:13 PM, Steven Ball wrote:
>
>>
>> Built from source, no issues now.
>>
>> I guess there is an issue with the binary package, then.
>
> Can you elaborate a little on what changed when you built from source?
>
> Which v
Built from source, no issues now.
I guess there is an issue with the binary package, then.
Thanks all for your help!
-Steve
On Sep 27, 2007, at 1:47 PM, John Doty wrote:
> Build from source is what worked for me.
>
> On Sep 27, 2007, at 1:45 PM, Steven Ball wrote:
>
>>
>
On Sep 27, 2007, at 1:26 PM, John Doty wrote:
>
>
> Have you tried installing guile18, and then reinstalling geda-bundle?
> I really suspect the Guile compatibility issues are biting you here.
> There are some hoops the installer needs to jump through depending on
> which version of Guile you have
Guile 1.6.7
On Thu, 27 Sep 2007 13:55:11 -0400 (EDT), Stuart Brorson <[EMAIL PROTECTED]>
wrote:
>> Probably parenthesis mismatch in /sw/etc/gEDA/system-gschemrc
>> Most recently read form: ([EMAIL PROTECTED] (build-path geda-rc-path
> gschem-darkbg))
>
> This sounds like a guile problem. Pleas
/sw/etc/gEDA/gschem-darkbg exists, but you bring up a good point.
The older, working version of the geda-bundle uses:
(define gedadata (getenv "GEDADATA"))
(define gedadatarc (getenv "GEDADATARC"))
(load (string-append gedadatarc "/gschem-darkbg")) ; dark background
The newer version uses
(l
Whups, I looked right over your post, sorry.
Regardless, the #@ is -not- in the file it is sourcing. I have not
looked through the source code, so I am unsure if it is parsing the
file incorrectly or if it is just reporting it as #@ for... some reason.
Would love to have it working, though,
I've sent stuff to PCB Express using PCB, and it always comes out
like a champ.
Note that the 'board.plated-drill.cnc' is only the plated drill
holes, and does not include any holes you have that are unplated. I
usually open up 'board.unplated-drill.cnc' and copy over any holes
(and dr
Hi all,
I dug through the mailing list as best as I could, and did not find
any specific mention of this issue, so I thought I would post here
and see if anyone else is experiencing it or has a solution.
I am running gschem version 20050820 on a Mac OSX machine. I realize
this version i
18 matches
Mail list logo
