Thanks a lot for reviewing and committing!
Kind regards, Felix
Am 23.05.2011 00:49, schrieb Krzysztof Kościuszkiewicz:
Thanks for taking the time to report the list - status update below.
On Sun, May 22, 2011 at 06:01:49PM +0200, Felix Ruoff wrote:
Here is the list:
a) Patches for
Kai-Martin:
Stephen Trier wrote:
Kai, try (component-library-search/home/..snip../symbols
Unfortunately, it works only for the first layer. Symbols in
../symbols/analog/diode are still ignored. In other words: gschem
does not descend recursively into sub dirs.
If you are brave, you can
On Mon, 23 May 2011, John Doty wrote:
Well, here I am in Osaka. It's Monday morning, and I just saw the
prototype Soft X-ray Imager (SXI) for the ASTRO-H space mission under
test. Much of the electronics, a large, complex circuit board and some
mixed-signal ASICs, is of my design, using gEDA.
Well done that man.
Cheers,
Andy.
On 23 May 2011 05:18, Steven Michalske smichal...@gmail.com wrote:
Cool,
Got photos?
Steve
On May 22, 2011, at 6:57 PM, John Doty j...@noqsi.com wrote:
Well, here I am in Osaka. It's Monday morning, and I just saw the prototype
Soft
[snip]
I'm doing some maintenance on the gEDA wiki this weekend, so it is
currently in read-only mode. ...
The gEDA wiki is back to read-write mode.
-Ales
___
geda-user mailing list
geda-user@moria.seul.org
k...@aspodata.se (Karl Hammar) writes:
The code that executes the ...-search command is in libgeda/src/g_rc.c
(relative the top of the git repo.), in the function:
SCM g_rc_component_library_search(SCM path);
I have changed that function to a wrapper around
int
Peter:
k...@aspodata.se (Karl Hammar) writes:
[about code that enables recursion in component-library-search]
Nack, for a number of reasons.
1) GRegex was introduced in GLib 2.14, and during the 1.7.x cycle we are
targetting GLib 2.12 or later.
2) This is an absolutely *textbook* example
On 5/23/11 2:18 AM, John Doty wrote:
CCD driver/temperature controller board. This is a gEDA design, published at
https://github.com/noqsi/SXI. Mitsubishi did the layout. They didn't tell me
until very late in the game that they wanted a PADS netlist, but that was no
problem for gEDA.
Video
On Sun, May 22, 2011 at 03:00:35PM -0700, Andrew Poelstra wrote:
I am cleaning up the unit handling for the gerber
exporter, using the guide at
http://www.linux-cae.net/PCB/rs274xrevd_e.pdf
Things are mostly straightforward, but I am lost
as to the /10 factors in
/* These are for
Great!
Well done!
And pictures would be nice.
Robert.
On 23/05/11 03:57, John Doty wrote:
Well, here I am in Osaka. It's Monday morning, and I just saw the prototype
Soft X-ray Imager (SXI) for the ASTRO-H space mission under test. Much of the
electronics, a large, complex circuit board and
On Mon, 23 May 2011 11:09:23 -0700
Andrew Poelstra as...@sfu.ca wrote:
On Sun, May 22, 2011 at 03:00:35PM -0700, Andrew Poelstra wrote:
I am cleaning up the unit handling for the gerber
exporter, using the guide at
http://www.linux-cae.net/PCB/rs274xrevd_e.pdf
Things are mostly
On Sun, 22 May 2011 15:00:35 -0700
Andrew Poelstra as...@sfu.ca wrote:
Why are the drill numbers divided by 10, and why are
they output with leading zeroes?
For the Excellon (NC drill) format:
“Maximum m.n format supported is 2.4” [1].
That means that the units are 1/10 mil rather than the
On Mon, 23 May 2011 17:13:01 +0200 (CEST)
k...@aspodata.se (Karl Hammar) wrote:
There are a lot of symbols available at cvs.gedasymbols.org.
To make them all available to gschem I have added:
(component-library-search
${HOME}/Net/cvs/cvs.gedasymbols.org/www/user)
to my ~/.gEDA/gafrc,
On Mon, 23 May 2011 17:13:01 +0200 (CEST)
k...@aspodata.se (Karl Hammar) wrote:
The result is as seen in attachment (dump.jpg).
Very nice!
Thank you.
However, for this to be usable wouldn't it be important to have a good
I think it usable as is (though not finished).
way to import the
On Mon, 23 May 2011 22:18:54 +0200 (CEST)
k...@aspodata.se (Karl Hammar) wrote:
In the library browser you have the choise to embed the component
in the .sch file. I think that might be the solutions for your
scenarios.
That would be a reasonable solution. I guess I've always overlooked
that
On Mon, 2011-05-23 at 13:31 -0700, Colin D Bennett wrote:
On Mon, 23 May 2011 22:18:54 +0200 (CEST)
k...@aspodata.se (Karl Hammar) wrote:
In the library browser you have the choise to embed the component
in the .sch file. I think that might be the solutions for your
scenarios.
That
On 05/23/2011 10:13 AM, Karl Hammar wrote:
changed component-library-search to descend
into subdirectories (see diff).
The result is as seen in attachment (dump.jpg).
Dang, that was quick Karl!
John
___
geda-user mailing list
On 05/23/2011 11:44 AM, Karl Hammar wrote:
comment on the functionality which the screen dump hints
you at?
Like it.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
I'd like to note that we have a serious power tool in gnetlist, and it's not
too hard to get it to translate attributes. Here's an example:
gnetplug-metadata.scm
Description: Binary data
project_metadata.scm
Description: Binary data
metademo.sch
Description: Binary data
Usage:
gnetlist
On May 24, 2011, at 12:29 AM, Peter Brett wrote:
3) I strongly recommend *not* using component-library-search because it
gives you no control over the precedence ordering of libraries when
searching for a symbol name match -- you're entirely at the mercy of the
order in which the filesystem
I would like to see some options added to the symbol library dialogue:
1. Create a new (e.g. local) library
2. Copy an existing symbol to another (e.g. local) library
3. Create a completely new symbol (perhaps using a wizard interface)
Incorporating DJboxsym (or similar) into the wizard
Thanks to all for the compliments. But I'm standing on the shoulders of giants,
even though said giants:
1. Aren't too happy with me at the moment.
2. Don't seem to understand how tall they are.
Note the excessively modest description at http://www.geda.seul.org/wiki/start.
This work
On May 24, 2011, at 5:18 AM, Karl Hammar wrote:
In the library browser you have the choise to embed the component
in the .sch file. I think that might be the solutions for your
scenarios.
There are a couple of problems with embedded symbols:
1. You can't edit them.
2. Once embedded, they
On May 23, 2011, at 1:40 PM, DJ Delorie wrote:
In a heirarchy, only the higher level schematics know what
the heirarchy is, the sub-schematics don't, so the higher ones need to
retain the instance-specific data.
Hierarchy isn't the only reuse scenario. Consider transition from breadboard to
Colin D Bennett wrote:
In the library browser you have the choise to embed the component
in the .sch file. I think that might be the solutions for your
scenarios.
That would be a reasonable solution. I guess I've always overlooked
that option.
There is a catch: Unembed works only for
Ales Hvezda wrote:
The gEDA wiki is back to read-write mode.
Fine. So I can go ahead and add the component-search tip.
---)kaimartin(---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53
I'd like to note that we have a serious power tool in gnetlist,
Yup. I had hoped to move some of the heavyifying data into a
database or the layout (or whatever), and have gnetlist gather all the
attribute data from the schematic, the database, and the layout. It
can then combine the data in
but I avoid name conflicts in project libraries.
If we find ourselves gaining popularity and a plethora of libraries
comes into being, we may no longer have the luxury of avoiding name
conflict. name scoping came up a few times in the library
discussion, I think keeping the issue in mind, even
Hierarchy isn't the only reuse scenario. Consider transition from
breadboard to prototype to production. A top-level schematic might
not change, even though attributes of parts might change (different
packages, tighter specs, ...). In that case, the instance-specific
data can't be in *any*
29 matches
Mail list logo
