[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: KJWaves - new release (a r)



On Mon, 2008-01-07 at 23:33 +0000, a r wrote:

> No, it is not gschem that does the hierarchy, it is its user. Gschem
> does not (did not) do any hierarchical design checking, hierarchy
> configuration, hierarchical parameters, copying, renaming,
> highlighting nets, etc.

Ok, we've probably got some way to come before all these are met. They
are things we'd like to see, but it takes time.

> > It has had many rounds of drawing fixes recently, and does indeed ship
> > basic symbols ready for use.
> 
> Last time I checked, redrawing a simple schematic was taking almost 1
> second. I wonder how much longer would it take with a real design. As
> for basic symbols, they had many irrelevant parameters (footprint etc)
> and none of important ones (these had to be typed manually as a spice
> card template).

If redrawing is taking a second, something is seriously wrong (or you're
on quite old hardware). It is very true that the basic symbols we have
are mostly targeted towards PCB design. Plans are to deprecate them
eventually, in favour of light symbols which can be the basis of many
different workflows.

> Say I have a MOS transistor instance on schematic. When I open the
> properties dialog of this instance, I expect to see a drop-list of
> available model types/levels, along with a list of text fields where I
> can define parameters that are relevant to the selected model
> type/level. All parameters should accept expressions so that I could
> automate editing and verification of the design a bit.

We're not there yet, but one of the possibilities of having light
symbols + extra workflow rules on top is that this sort of thing becomes
possible. (If/When) this feature is implemented, there is sure to be a
big announcement! 

> > Auto numbering has been added (as a dialog
> > for renumbering components), and I think there is also an option to have
> > on-the-fly numbering of new components.
> 
> I meant on-the-fly numbering. Possibly I missed this feature but why
> it was not enabled in the first place?

Some people hate it. It is found in the system-gschemrc, commented out:

; Comment in this scheme code if you want automatic numbering when
; placing new component and copying components
;
;(load-from-path "auto-uref.scm")
;(add-hook! add-component-hook auto-uref)
;(add-hook! copy-component-hook auto-uref)

I don't use it, so couldn't say for sure whether it still worked or not.

> > If there are areas where gschem shows bugs, or can't do something you
> > need, please let us know. It isn't good for the project (and open source
> > tools as a whole) if people are left with bad impressions of the
> > software, but don't make any feedback known.
> 
> In general, I don't like giving negative feedback. Especially if I can
> clearly see that the project is targeting completely different or
> opposite goals than mine.

Bug reports which are constructive, or explain why the software doesn't
meet your needs are welcome. (So long as they don't come across as
demanding fixes _now_). Part of what we need to do as a project, is to
evaluate what features users want. gschem isn't _supposed_ to target PCB
design explicitly.. it is supposed to be workflow agnostic, although as
you will see, a lot of users do use it for board layout.

PS.. I usually use a text editor to make spice netlists, not because I
don't find gschem capable enough.. it just doesn't always fit my way of
working.


-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)



_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user