On Apr 14, 2011, at 2:14 PM, Krzysztof Kościuszkiewicz wrote:
But I think we're actually getting farther from something that:
* is backwards compatible with the name=value attribute definition/syntx
* can be simply used to add hierarchy/depth to attribute assignments
It would be best
On Thu, Apr 14, 2011 at 10:14:13PM +0200, Krzysztof Kościuszkiewicz wrote:
On Wed, Apr 13, 2011 at 10:41:23PM +0100, Peter Clifton wrote:
pin[pinnumber=1] {pinnumber=2;}
pin[pinnumber=2] {pinnumber=1;}
I've long seen this to be the most sane way of managing back-annotation
into a
On Fri, 2011-04-15 at 11:54 +0200, Gabriel Paubert wrote:
And a small comment regarding hierarchy separators - I would personally
choose anything that does not require shift-keystroke to type the most
commonly used separator - so '/' and '.' seem to be the two natural
candidates.
Gabriel Paubert paub...@iram.es writes:
A french or german keyboard will be different (I'm french,
but I can't stand the layout of french keyboards).
I'm using us keyboards exclusively, in Germany. I type a lot more
[]{}\| than äöüß.
I do not think that easy of typing should drive this
On Fri, Apr 15, 2011 at 02:16:23PM +0200, Stephan Boettcher wrote:
Gabriel Paubert paub...@iram.es writes:
A french or german keyboard will be different (I'm french,
but I can't stand the layout of french keyboards).
I'm using us keyboards exclusively, in Germany. I type a lot more
Gabriel Paubert wrote:
I believed that the ß has been suppressed in a recent reform of the
german language.
Actually, its use was regularized. No ß after short vowels anymore.
This replaced daß by dass and thus removed the most frequent
appearance of the character. Anyway, the Swiss don't
On Wed, 13 Apr 2011 22:41:23 +0100
Peter Clifton pc...@cam.ac.uk wrote:
On Wed, 2011-04-13 at 22:26 +0100, Peter Clifton wrote:
pin[pinnumber=1] {
pinnumber=99;
}
And regarding stuff like the above - where we key off one attribute
and change it in the rule, IF that is ever legal
Equality test AssignmentComment
x = y x := yAda, ALGOL, Dylan, Eiffel, Pascal
x = y x - yR, Objective Caml
x == y x = y C, C++, Java, C#, Python
Even though I am most accustomed to C/C++/Java style, I think that
On Wed, Apr 13, 2011 at 10:41:23PM +0100, Peter Clifton wrote:
pin[pinnumber=1] {pinnumber=2;}
pin[pinnumber=2] {pinnumber=1;}
I've long seen this to be the most sane way of managing back-annotation
into a hierarchy. I would go as far to say refdes should be
back-annotated as such:
On Tue, Apr 12, 2011 at 04:31:03PM +0100, Peter Clifton wrote:
This is a really neat idea..
P pin number :1 doesn't really matter, it is just a way of referring
to a particular pin. If we could reference by other means, that would
also be cool. I'm thinking of some kind of id=... attribute
We'd have to work a bit on the syntax, precedence, resolution rules and how to
For PCB attributes, we're going with foo:bar for heirarchy (or at
least grouping), so U3:14.net=+5v ?
(: for heirarchy, . for attributes ?)
___
geda-user mailing list
I thought we used / for netlist hierarchy. At least - that is what I
coded for the netlist viewer in PCB.
I suggested Attributes use : to assign attributes to owners, to
avoid conflict.
Like PCB:background-color=yellow
The syntax for what the owner owns can be different.
On Wed, 2011-04-13 at 22:16 +0200, Krzysztof Kościuszkiewicz wrote:
So we are more or less looking at a simplified hierarchical path syntax, where
elements without explicit id= provide default id based on the type and other
attributes?
Examples:
U1.1.net=Vcc (global attribute, pinnumber
On Wed, 2011-04-13 at 16:58 -0400, DJ Delorie wrote:
I thought we used / for netlist hierarchy. At least - that is what I
coded for the netlist viewer in PCB.
I suggested Attributes use : to assign attributes to owners, to
avoid conflict.
That is a good separator prefix for namespacing,
That is ancestory.
I'm a big fan of backwards compatibility :-)
But it does point out that no one style seems to have a clear majority
of the mindset :-P
___
geda-user mailing list
geda-user@moria.seul.org
On Wed, 2011-04-13 at 22:26 +0100, Peter Clifton wrote:
pin[pinnumber=1] {
pinnumber=99;
}
And regarding stuff like the above - where we key off one attribute and
change it in the rule, IF that is ever legal - we should do it like a
PLC executes its processing cycles.
Freeze a view of
On Mon, Apr 11, 2011 at 6:45 PM, John Doty j...@noqsi.com wrote:
On Apr 11, 2011, at 4:25 PM, Peter Clifton wrote:
I would advise a note of caution. In general, I don't like it when tools
start special casing things like this.. it just feels wrong.
I've long thought it a minor design flaw
On Mon, 2011-04-11 at 23:54 -0700, Russell Dill wrote:
On Mon, Apr 11, 2011 at 6:45 PM, John Doty j...@noqsi.com wrote:
On Apr 11, 2011, at 4:25 PM, Peter Clifton wrote:
I would advise a note of caution. In general, I don't like it when tools
start special casing things like this.. it
On Mon, Apr 11, 2011 at 8:45 PM, John Doty j...@noqsi.com wrote:
On Apr 11, 2011, at 4:25 PM, Peter Clifton wrote:
I would advise a note of caution. In general, I don't like it when tools
start special casing things like this.. it just feels wrong.
I've long thought it a minor design flaw
On Mon, Apr 11, 2011 at 11:25:19PM +0100, Peter Clifton wrote:
What about the cases where this is a mistake? The net= attribute was
supposed to refer to some implicit power pin - not the device's one
symbolic pin, but the user forgot the suffix.
The special case applies only to symbols with a
On Tue, 2011-04-12 at 22:35 +0200, Krzysztof Kościuszkiewicz wrote:
On Mon, Apr 11, 2011 at 11:25:19PM +0100, Peter Clifton wrote:
What about the cases where this is a mistake? The net= attribute was
supposed to refer to some implicit power pin - not the device's one
symbolic pin, but the
How about component-level attributes like pin.5=vdd, pin.1=gnd ?
You could make a blank rectangle symbol with a refdes and a list of a
few of those pin.N= visible, let the user edit them... gnetlist would
have to look for all pin.N attributes, and connect that pin N to the
given net.
How about component-level attributes like pin.5=vdd, pin.1=gnd ?
Bonus if you make pin.foo= for for a pin with pinlabel foo :-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Peter Clifton pc...@cam.ac.uk writes:
On Tue, 2011-04-12 at 22:35 +0200, Krzysztof Kościuszkiewicz wrote:
On Mon, Apr 11, 2011 at 11:25:19PM +0100, Peter Clifton wrote:
What about the cases where this is a mistake? The net= attribute was
supposed to refer to some implicit power pin - not
On Apr 12, 2011, at 2:56 PM, Stephan Boettcher wrote:
A non-graphical netlist format could be a gschem schematic file with a
generic symbol without any pins, with just a list of attributes.
You mean like the files produced by pins2gsch?
On Tue, 2011-04-12 at 16:51 -0400, DJ Delorie wrote:
How about component-level attributes like pin.5=vdd, pin.1=gnd ?
Bonus if you make pin.foo= for for a pin with pinlabel foo :-)
We can't differentiate like that, since pinnumber can be a text string
as well. pinnumber is what gnetlist
On Sun, Apr 10, 2011 at 11:22:54PM +0200, Markus Traidl wrote:
Actually I would like to use only the net attribute. There I could
assign net=3V3 instead of net=3V3:1.
You might have missed a recent discussion on the topic:
http://archives.seul.org/geda/user/Mar-2011/msg00074.html
--
On Sun, Apr 10, 2011 at 11:22:54PM +0200, Markus Traidl wrote:
Actually I would like to use only the net attribute. There I could
assign net=3V3 instead of net=3V3:1.
I know that the :1 is that the gnetlist tool knows that the 3V3 is
connected to pin 1.
But in case of a One-Pin-Symbol
On Mon, 2011-04-11 at 23:59 +0200, Krzysztof Kościuszkiewicz wrote:
On Sun, Apr 10, 2011 at 11:22:54PM +0200, Markus Traidl wrote:
Actually I would like to use only the net attribute. There I could
assign net=3V3 instead of net=3V3:1.
I know that the :1 is that the gnetlist tool knows
On Mon, 2011-04-11 at 23:25 +0100, Peter Clifton wrote:
I would advise a note of caution.
What some people do not like is the visible :1 in schematics -- can we
simple suppress that output for symbols with only one pin and digit 1
after the :
That would be a not too dangerous patch, because it
I would advise a note of caution.
What some people do not like is the visible :1 in schematics -- can
we
simple suppress that output for symbols with only one pin and digit
1
after the :
That would be a not too dangerous patch, because it concerns only
Snip.
I agree that we should not special case it. I would prefer varibles that
refered to other attributes.
This example: value = 3v3
net = $value:1
where the default scope is the local symbol and no lookups to higher scopes.
A resistor divider:
R1
Value= 1000
R2
Value =
On Mon, Apr 11, 2011 at 8:19 PM, Steven Michalske smichal...@gmail.com wrote:
Snip.
I agree that we should not special case it. I would prefer varibles that
refered to other attributes.
This example: value = 3v3
net = $value:1
where the default scope is the local symbol and no
On Apr 11, 2011, at 4:25 PM, Peter Clifton wrote:
I would advise a note of caution. In general, I don't like it when tools
start special casing things like this.. it just feels wrong.
I've long thought it a minor design flaw that indexed attributes attach the
index to the value rather than
Mark Rages wrote:
I've often though it would be extremely handy to have spreadsheet-like
automatic calculations in gschem.
You mean like specify the R1/R2 and R1 for the four resistors
of a differential opamp circuit? That would be cool!
---)kaimartin(---
--
Kai-Martin Knaak
Email:
On Mon, Apr 11, 2011 at 8:57 PM, Kai-Martin Knaak k...@lilalaser.de wrote:
Mark Rages wrote:
I've often though it would be extremely handy to have spreadsheet-like
automatic calculations in gschem.
You mean like specify the R1/R2 and R1 for the four resistors
of a differential opamp
Hello,
I am drawing some new symbols for my library. Currently I am doing GND
and Power Symbols. There I have following question:
I have drawn a power symbol for the 3V3 power supply. Therefore I used
one pin with the pinnumber 1. In addition I attached the attribute
net=3V3:1
37 matches
Mail list logo
