gEDA-dev: gEDA: the newbie experience

[Bernd Jendrissek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Jul 12, 2006 at 12:57:18PM -0600, John Doty wrote:
> On Jul 12, 2006, at 11:52 AM, Bernd Jendrissek wrote:
> > * Does it make sense to merge the library hierarchies in each tool so
> >   that if I have a directory under ~/gaf/symbols with the same  
> >name as
> >   one in the distributed library, the symbols under both will show up
> >   together in a list?
> 
> Remember that this is a modular system: some of us don't use PCB.

I do remember that.  Here's what I mean: in both gschem and PCB I have a
hierarchy (and oh, BTW, wouldn't a multi-level tree be cool too?) of
library widgets.  For example in gschem:

  foo
  xilinx
  bar
  st [one ST device in gaf CVS]
  baz
  st [my OWN ST device here, in ~/gaf/symbols/st/upsd325x.sym]

Annoyingly I have "st" *twice* in the list.

Maybe I just shouldn't do that then, and choose a unique name, fair
enough, but I see the library window as a widget browser, not a
filesystem explorer, so it would be nice to be able to see ALL ST
devices together.

I didn't mean to have a merged gschem/PCB library that would link
symbols with footprints.  After actually using the toolchain I found I
quite like the light-symbols approach, where I can choose the footprint
with gattrib after drawing the schematic.

> > * gschem crashes quite often.  Sorry this is vague, I'll try to get
> >   around to getting more info.  Luckily I didn't lose any work  
> >with the
> >   backups in /tmp.
> 
> Probably the infamous slice bug. Try:
> 
> export G_SLICE=always-malloc
> 
> (or if you're using csh, "setenv G_SLICE always-malloc")
> 
> before invoking gschem.
> 
> Ales looked into this, says it's fixed in the CVS dev version.

Thanks, I'll give this a bash or I'll just update CVS.

- -- 
I've generally found that the fastest way to get the right answer on the net
is to confidently assert the answer you believe to be right; those who know
will immediately correct you, while if you just ask, often no answers arrive.
All it requires is a willingness to look bad on occasion.
                                               - Joe Buck on gcc at gcc.gnu.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Please fetch my new key 804177F8 from hkp://wwwkeys.eu.pgp.net/

iD8DBQFEtVBfwyMv24BBd/gRAroVAJ402p0+7CENRsNdpFjCy9fYQ7RlWgCgpv0d
H04aoF0Zb20Ukf9IHQcJcWc=
=uX8M
-----END PGP SIGNATURE-----