> Rather than having a component "class", explicitly subclassed in the
> database to contain resistor specific attributes, I would do it similar
> to the following:
>
> 1 "component class" / table, one size fits all. Each has a component ID.
The Component ID is what I list on BOM.
> 1 "attribute
On Wed, 2010-01-27 at 15:18 -0800, Edward Hennessy wrote:
> --- On Wed, 1/27/10, Peter Clifton wrote:
>
> > Good database design dictates that the device types are not
> > hard-coded
> > into the data-structure, there is no explicit "resistors"
> > table JOIN'd
> > to drag in resistor specific d
--- On Wed, 1/27/10, Peter Clifton wrote:
> Good database design dictates that the device types are not
> hard-coded
> into the data-structure, there is no explicit "resistors"
> table JOIN'd
> to drag in resistor specific data etc..
There really isn't a good solution for relational databases.
On Tue, 2010-01-26 at 19:15 -0500, al davis wrote:
> Also .. Do not make the types of electronic components (diodes,
> resistors) inherent in the data base. They are just parts, and
> all parts have schematic symbols, layout footprints, and
> simulation models. Don't even try to make any spe
On Tue, Jan 19, 2010 at 12:29 PM, Peter Clifton wrote:
> On Tue, 2010-01-19 at 08:26 -0800, Edward Hennessy wrote:
>> On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
>> > Anything else to add??
>>
>> A few suggestions for additional parameters:
There gets to be fields needed like "Can a Substit
On Friday 08 January 2010, Edward Hennessy wrote:
> I created a working document for a gEDA parts manager on the
> gEDA wiki.
>
> http://geda.seul.org/wiki/geda:gparts_dd
>
> If anyone has feedback or specific requirements, please
> provide feedback to geda-dev or geda-user mailing
> lists. I
On the chat, you wrote:
On configuration directories, gEDA has the config directory and the
data directory. The parts manager needs to locate the system-gafrc
and the subdirectories for models, symbols, footprints, etc...
It's not just that it has to locate *gafrc: it has to extract the
al davis wrote:
>> On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
>> > Anything else to add??
>>
>
> I guarantee you will leave something out, and that you will
> include some useless stuff.
>
I totally agree here with the part of leaving something out.
> Just make sure the design is such
On Jan 19, 2010, at 8:50 AM, al davis wrote:
>> On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
>>> Anything else to add??
>>
>
> I guarantee you will leave something out, and that you will
> include some useless stuff.
I agree.
> Just make sure the design is such that fields can be added
Hi all,
Peter Clifton wrote:
On Tue, 2010-01-19 at 08:26 -0800, Edward Hennessy wrote:
On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
Anything else to add??
A few suggestions for additional parameters:
- Count (for resistor arrays)
- Pb-free (for RoHS and WEEE)
^__
On Tue, 2010-01-19 at 08:26 -0800, Edward Hennessy wrote:
> On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
> > Anything else to add??
>
> A few suggestions for additional parameters:
>
> - Count (for resistor arrays)
> - Pb-free (for RoHS and WEEE)
^^___ These relate
> On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
> > Anything else to add??
>
I guarantee you will leave something out, and that you will
include some useless stuff.
Just make sure the design is such that fields can be added and
removed in the future without breaking anything.
Same goes fo
On Jan 19, 2010, at 3:41 AM, Florian Teply wrote:
> Anything else to add??
A few suggestions for additional parameters:
- Count (for resistor arrays)
- Pb-free (for RoHS and WEEE)
- Operating temperature range
Cheers,
Ed
___
geda-user mailing list
ginal Message-
> From: geda-user-boun...@moria.seul.org
> [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Steven
> Michalske
> Sent: Monday, January 18, 2010 11:14 PM
> To: gEDA user mailing list
> Subject: Re: gEDA-user: Parts Manager Working Document
>
>
> On
Florian Teply wrote:
> Gabriel Paubert wrote:
>> On Mon, Jan 18, 2010 at 11:05:02AM +0100, Florian Teply wrote:
>>> Florian Teply wrote:
>>> > On Saturday 16 January 2010 06:03:18 Edward Hennessy wrote:
>>> >> On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
>>> >> > I'm gonna try and make up a
Gabriel Paubert wrote:
> On Mon, Jan 18, 2010 at 11:05:02AM +0100, Florian Teply wrote:
>> Florian Teply wrote:
>> > On Saturday 16 January 2010 06:03:18 Edward Hennessy wrote:
>> >> On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
>> >> > I'm gonna try and make up a list of properties of compon
On Jan 18, 2010, at 7:34 PM, Torsten Wagner wrote:
2) missing components
At work we throw away the libraries that come with our $15K a seat
tools. :-P
I'm not sure how much a database would run against one fundamental
of gEDA,
which is the nice nativley use of pure text files. If there
Hi,
Recently, I talked with some people about EDA tools and they main arguments
against gEDA were:
1) no MS-windows support
2) missing components
It's very nice to see that this two topics are heavily discussed here.
As for the Parts Manager I read the proposal and I like to share some
though
On Mon, 2010-01-18 at 22:36 +0100, Gabriel Paubert wrote:
> Probably, but once again, it's a matter of turning the inductor around
> at assembly time.
Sure - although what I was rather indirectly getting at - is that even
for passives which you might "think" you could make the two pins
equivale
On Mon, Jan 18, 2010 at 09:22:56AM -0500, David C. Kerber wrote:
> No, I meant passives, because it's not active. I don't consider
> "semiconductor" to be the opposite of "passive".
>
> To me, a diode fits in the groups "discrete" (vice "integrated"), "passive"
> (vice "active"), and "semicondu
On Mon, Jan 18, 2010 at 02:23:16PM +, Peter Clifton wrote:
> On Mon, 2010-01-18 at 14:45 +0100, Gabriel Paubert wrote:
> > Consider that some inductances that I use are not symmetric. While
> > I don't know of any asymmetric resistors (but maybe they exist),
> > some microwave broadband induct
On Mon, 2010-01-18 at 14:45 +0100, Gabriel Paubert wrote:
> Consider that some inductances that I use are not symmetric. While
> I don't know of any asymmetric resistors (but maybe they exist),
> some microwave broadband inductors are asymmetric (you can't swap
> pins 1 and 2, as for polarized ca
er Clifton
> Sent: Monday, January 18, 2010 9:10 AM
> To: gEDA user mailing list
> Subject: Re: gEDA-user: Parts Manager Working Document
>
> On Mon, 2010-01-18 at 08:49 -0500, David C. Kerber wrote:
> >
> > > -Original Message-
> > > From: geda-user-bou
On Mon, Jan 18, 2010 at 11:05:02AM +0100, Florian Teply wrote:
> Florian Teply wrote:
> > On Saturday 16 January 2010 06:03:18 Edward Hennessy wrote:
> >> On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
> >> > I'm gonna try and make up a list of properties of components starting
> >> > with pass
On Mon, 2010-01-18 at 08:49 -0500, David C. Kerber wrote:
>
> > -Original Message-
> > From: geda-user-boun...@moria.seul.org
> > [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Florian Teply
>
> ...
>
> > Hmm, looks like i have finished said document, at least i
> > can't think
> -Original Message-
> From: geda-user-boun...@moria.seul.org
> [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Florian Teply
...
> Hmm, looks like i have finished said document, at least i
> can't think of anything to add. Surely, it's not finished yet
> and does only cover
Florian Teply wrote:
> On Saturday 16 January 2010 06:03:18 Edward Hennessy wrote:
>> On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
>> > I'm gonna try and make up a list of properties of components starting
>> > with passive devices. I'll go from very generic properties to more
>> > exotic one
On Saturday 16 January 2010 06:03:18 Edward Hennessy wrote:
> On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
> > Just as it enters my mind: This parts manager is essentially a
> > hierarchical parts database. I could imagine that some guys would want
> > to integrate other stuff like inventory,
Florian Teply wrote:
Edward Hennessy wrote:
Florian,
Thanks for the feedback.
I'll add support for simulation models, but I'll need to do a bit more research
on
how the database columns map to symbol attributes.
Just as it enters my mind: This parts manager is essentially a
hierarchical
On Jan 11, 2010, at 2:02 AM, Kai-Martin Knaak wrote:
> Can you elaborate a bit?
> What exactly is the parts manager supposed to do?
> How will/should it integrate with gschem/gsch2pcb/pcb ?
I added a bit more description to the working document including
a graphic showing the integration.
http:
On Jan 12, 2010, at 4:18 AM, Florian Teply wrote:
> Just as it enters my mind: This parts manager is essentially a
> hierarchical parts database. I could imagine that some guys would want
> to integrate other stuff like inventory, preferred dealers, pricing,
> dealer part numbers and such. On the
Edward Hennessy wrote:
> Florian,
>
> Thanks for the feedback.
>
> On Jan 9, 2010, at 3:30 AM, Florian Teply wrote:
>> a) There seems to be a link between part and document missing. Documents are
>> completely described, but never referenced.
>
> I created an ERD and put it in the working docu
On Mon, 11 Jan 2010 10:02:07 +, Kai-Martin Knaak wrote:
> What exactly is the parts manager supposed to do? How will/should it
> integrate with gschem/gsch2pcb/pcb ?
I just read the description in the "blue sky ideas" thread. No need to
post it to the list again.
---<(kaimartin)>---
--
Ka
On Fri, 08 Jan 2010 18:43:13 -0800, Edward Hennessy wrote:
> I created a working document for a gEDA parts manager on the gEDA wiki.
Can you elaborate a bit?
What exactly is the parts manager supposed to do?
How will/should it integrate with gschem/gsch2pcb/pcb ?
---<(kaimartin)>---
--
Kai-Mar
Florian,
Thanks for the feedback.
On Jan 9, 2010, at 3:30 AM, Florian Teply wrote:
a) There seems to be a link between part and document missing.
Documents are
completely described, but never referenced.
I created an ERD and put it in the working document.
b) Symbol: a
On Saturday 09 January 2010 03:43:13 Edward Hennessy wrote:
> All,
>
> I created a working document for a gEDA parts manager on the gEDA wiki.
>
> http://geda.seul.org/wiki/geda:gparts_dd
>
> If anyone has feedback or specific requirements, please provide feedback to
> geda-dev or geda-user mai
All,
I created a working document for a gEDA parts manager on the gEDA wiki.
http://geda.seul.org/wiki/geda:gparts_dd
If anyone has feedback or specific requirements, please provide feedback to
geda-dev
or geda-user mailing lists. I'll continue to update the document as the project
progresses.
Joerg wrote:
>
>
> Yes, that could be done but requires the user to be more diligent. Or
> some warning mechanism like "You cannot start this name with D2PAK".
>
PCB must already have code somewhere to tell when polygons intersect,
which suggests that code could be written to tell if two foot
Bill Gatliff wrote:
> Levente Kovacs wrote:
>> OK. I understand, but I guess it doesn't worth the trouble to implement such
>> complicated stuff. To be honest, I don't see why one would combine some
>> device
>> coming in different packages into one part.
>
> A lot of 7400 stuff is the same devic
DJ Delorie wrote:
>> That is what most CAD systems do. Usually you can't select farther down
>> than footprint, like "oh, I want one with the solder mask tucked some
>> more".
>
> Well, real needs would be like: axial resistor: 0.4" vs 0.5" vs 0.6"
> spacing, TO-220 standing up or laying down, o
> That is what most CAD systems do. Usually you can't select farther down
> than footprint, like "oh, I want one with the solder mask tucked some
> more".
Well, real needs would be like: axial resistor: 0.4" vs 0.5" vs 0.6"
spacing, TO-220 standing up or laying down, or the 0603[LMN]
difference
DJ Delorie wrote:
> Way back when, when I use cadstar, what they did was have multiple
> alternatives within each symbol and footprint. So, the mapping was
> generic part -> generic symbol -> alternative, and generic part ->
> specific part -> footprint. ...
That is what most CAD systems do. Usu
Levente Kovacs wrote:
>
> OK. I understand, but I guess it doesn't worth the trouble to implement such
> complicated stuff. To be honest, I don't see why one would combine some device
> coming in different packages into one part.
A lot of 7400 stuff is the same device (quad 2-input NAND), availabl
Way back when, when I use cadstar, what they did was have multiple
alternatives within each symbol and footprint. So, the mapping was
generic part -> generic symbol -> alternative, and generic part ->
specific part -> footprint. This thread makes me think we need to
allow for footprint alternati
Levente Kovacs wrote:
> On Fri, 15 May 2009 13:32:12 -0500
> Bill Gatliff wrote:
>
>> I think we're in violent agreement, but might be talking about subtly
>> separate things.
>>
>> A given device e.g. a particular transistor may be available in one
>> or more specific physical _packages_, i.e.
On Fri, 15 May 2009 13:32:12 -0500
Bill Gatliff wrote:
> I think we're in violent agreement, but might be talking about subtly
> separate things.
>
> A given device e.g. a particular transistor may be available in one
> or more specific physical _packages_, i.e. TO220, DPAK, etc. If you
> had
Levente wrote:
> Bill Gatliff wrote:
> [...]
>
>> Gosh, I think it almost does. You have a footprint column in your
>> device table, and it seems as though only one footprint would apply to a
>> specific device--- an 0603 resistor is always going to use the 0603
>> footprint. So if you had
Bill Gatliff wrote:
[...]
>
> Gosh, I think it almost does. You have a footprint column in your
> device table, and it seems as though only one footprint would apply to a
> specific device--- an 0603 resistor is always going to use the 0603
> footprint. So if you had resistors with other foot
Levente wrote:
> DJ Delorie wrote:
>
>> Just FYI, I was mostly asking about the database aspect, not the
>> storage aspect. Both aspects are interesting to read about, of
>> course.
>>
>
> You might know it... I have a database for my parts. There is a stock
> table in it. So far, I don't
DJ Delorie wrote:
> Just FYI, I was mostly asking about the database aspect, not the
> storage aspect. Both aspects are interesting to read about, of
> course.
You might know it... I have a database for my parts. There is a stock
table in it. So far, I don't use the stock table, because I buy 10
Cullen Newsom wrote:
> What a headache! I dig through boxes until I find it!
>
> As far as computerized inventory tracking, I have almost zilch. I have a
> few old BOMs lying around. I keep datasheets for parts I own in
> different directories from other parts. I try to keep the files named
> s
Kai-Martin Knaak wrote:
> On Thu, 14 May 2009 16:02:16 -0700, Joerg wrote:
>
>> Neat! 2 Euros for 10 of those is not expensive. But only the last one
>> says ESD-safe
>
> Only the black are ESD-safe. They sell all sizes in all colors.
> http://www.elv.de/SchraubenMagazine/x.aspx/cid_74/detail_1
On Thu, 14 May 2009 16:02:16 -0700, Joerg wrote:
> Neat! 2 Euros for 10 of those is not expensive. But only the last one
> says ESD-safe
Only the black are ESD-safe. They sell all sizes in all colors.
http://www.elv.de/SchraubenMagazine/x.aspx/cid_74/detail_1/detail2_159
Pricing for smallest si
Kai-Martin Knaak wrote:
> On Thu, 14 May 2009 15:02:40 -0500, Bill Gatliff wrote:
>
>> Seems great for cut tapes, at least. Where did you get your boxes?
>
> I got mine from elv:
> http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=4213
>
> The lid of these boxes is spring loaded.
Just FYI, I was mostly asking about the database aspect, not the
storage aspect. Both aspects are interesting to read about, of
course.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Thu, 14 May 2009 15:02:40 -0500, Bill Gatliff wrote:
> Seems great for cut tapes, at least. Where did you get your boxes?
I got mine from elv:
http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=4213
The lid of these boxes is spring loaded. It keeps the parts inside even
when t
DJ Delorie wrote:
>> Also, caps, resistors and such come in loose snippets of paper-reel.
>> That's not very handy to store stuff. They need a better home :-)
>
> Do you put the tape snippets in the coin envelopes, or peel the parts
> out of the tape first?
>
Oh, before it's too late: _Don't_ r
DJ Delorie wrote:
> How do people manage their parts inventories, so they know what
> they've got?
An inventory spreadsheet,
a file case of 66 2 inch tall drawers intended for music sheets holds bags,
reels, boxes,
and some file folders with cut tape SMT parts double-stick-taped on letter size
p
DJ Delorie wrote:
>> Also, caps, resistors and such come in loose snippets of paper-reel.
>> That's not very handy to store stuff. They need a better home :-)
>
> Do you put the tape snippets in the coin envelopes, or peel the parts
> out of the tape first?
>
Depends on the parts. Jelly-bean pa
> Also, caps, resistors and such come in loose snippets of paper-reel.
> That's not very handy to store stuff. They need a better home :-)
Do you put the tape snippets in the coin envelopes, or peel the parts
out of the tape first?
___
geda-user mail
Bill Gatliff wrote:
> Joerg wrote:
>> John Larkin on s.e.design gave me "the" hint: Coin envelopes.
>>
>
> Why not just leave the parts in the little anti-static envelopes they
> came in? They're already labeled, even.
>
They come in too many different sizes and don't stack nicely. Also, th
DJ Delorie wrote:
> I'm gearing up to populate a bunch of powermeter boards, plus the
> sdram board, and got the biggest digikey box I've ever gotten. This
> time, it was cost effective to by reels of two of the parts, and many
> parts were ordered at the next price-point up (10 is cheaper than
I use the watchmaker's cans from Lee Valley and some stainless steel
cans
from McMaster Carr for the parts I use the most.
See [1]http://tinyurl.com/cv29v5
(* jcl *)
--
You can't create open hardware with closed EDA tools.
[2]http://www.luciani.org
References
1. http:/
What a headache! I dig through boxes until I find it!
As far as computerized inventory tracking, I have almost zilch. I have a
few old BOMs lying around. I keep datasheets for parts I own in
different directories from other parts. I try to keep the files named
so that I can find them when I nee
Joerg wrote:
>
> John Larkin on s.e.design gave me "the" hint: Coin envelopes.
>
Why not just leave the parts in the little anti-static envelopes they
came in? They're already labeled, even.
b.g.
--
Bill Gatliff
b...@billgatliff.com
___
geda
Bill Gatliff wrote:
> Joerg wrote:
>> I use a MS-Works database. It lists the qty, part description and (very
>> important) where is is stashed. For SMT stuff that I may need at client
>> sites I use tiny jewel boxes that have around 50 micro-bins each in a
>> 2"*2"*1/3" space, stackable. No cha
On Thu, May 14, 2009 at 3:34 PM, DJ Delorie <[1...@delorie.com> wrote:
How do people manage their parts inventories, so they know what
they've got?
__
Postgres tables and containers with transparent lids ;)
(* jcl *)
--
You can't create
On Thu, May 14, 2009 at 03:34:31PM -0400, DJ Delorie wrote:
>
> How do people manage their parts inventories, so they know what
> they've got?
I have some flat text files of interesting stuff (like microcontrollers
and voltage regulators) and things I have vast quantities of (reels of
0603 caps)
DJ Delorie wrote:
> I'm gearing up to populate a bunch of powermeter boards, plus the
> sdram board, and got the biggest digikey box I've ever gotten. This
> time, it was cost effective to by reels of two of the parts, and many
> parts were ordered at the next price-point up (10 is cheaper than 9
Joerg wrote:
> I use a MS-Works database. It lists the qty, part description and (very
> important) where is is stashed. For SMT stuff that I may need at client
> sites I use tiny jewel boxes that have around 50 micro-bins each in a
> 2"*2"*1/3" space, stackable. No chance for labels or anything
Steven Michalske wrote:
> I use boxes of duplicate parts and a faulty memory!
>
Yea, that one has worked well for me for years too. :)
I've been interested to try something I saw a lawyer use once to track
an incomprehensibly-large pile of documents: divide them up into small,
arbitrary gro
DJ Delorie wrote:
> I'm gearing up to populate a bunch of powermeter boards, plus the
> sdram board, and got the biggest digikey box I've ever gotten. This
> time, it was cost effective to by reels of two of the parts, and many
> parts were ordered at the next price-point up (10 is cheaper than 9
I use boxes of duplicate parts and a faulty memory!
On May 14, 2009, at 12:34 PM, DJ Delorie wrote:
>
> I'm gearing up to populate a bunch of powermeter boards, plus the
> sdram board, and got the biggest digikey box I've ever gotten. This
> time, it was cost effective to by reels of two of the
I'm gearing up to populate a bunch of powermeter boards, plus the
sdram board, and got the biggest digikey box I've ever gotten. This
time, it was cost effective to by reels of two of the parts, and many
parts were ordered at the next price-point up (10 is cheaper than 9
sometimes - I've got a TU
Hi Vinny,
Once you have edited and saved a part, go back to the schematic, select
the part, then select "Edit" and then "Update Component" or use the
shortcut "ep." This should reload that component and update the schematic.
If you have multiple instances of the component, highlight them all
On Sat, 05 Apr 2008 17:58:25 -0500
Vincent Onelli <[EMAIL PROTECTED]> wrote:
> Hi,
> I am fairly new at gschem, I found that if I modify a part then save in the
> same name the modification do not show when the part is reloaded until
> gschem is reloaded. Same if the modified part is saved under d
On Sat, Apr 5, 2008 at 6:58 PM, Vincent Onelli <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
> I am fairly new at gschem, I found that if I modify a part then save in the
> same name the modification do not show when the part is reloaded until
> gschem is reloaded. Same if the modified part is saved under d
Hi,
I am fairly new at gschem, I found that if I modify a part then save in the
same name the modification do not show when the part is reloaded until gschem
is reloaded. Same if the modified part is saved under different name it is not
available until gschem is reloaded.
Is there a way to get
My only request is to design it with the disabled in mind. If its
graphical, include shortcut keys. Using the accessiblity mouse keys and
waiting for the mouse to travel from point to point multiplied by repetitive
tasks effects the time to completion significantly.
On Dec 20, 2007 4:00 PM, John
I'm new to pcb,
as i've worked with it just on the past two months making a simple board (pic
+ L298 to drive a bipolar stepper).
But I can give you my impression and tought about the tools i've used, gschem
and pcb (gtk).
For both a lot of work as been done and a lot of work as to be done, but
Yep, a lot of our designs here start with this is what it has to do and
this is where it has to fit. Physical size limitations are imposed.
On Fri, 2007-12-21 at 10:44 -0600, John Griessen wrote:
> Steve Meier wrote:
> Project matters of course, and is a good place to define different DRCs.
>
Steve Meier wrote:
Project matters of course, and is a good place to define different DRCs.
> 3) If the project is a circuitboard then before then before the netlist
> can be generated at least the package has to be selected (passive) and
> often the device (active).
> A device complete with packa
I have been spending the evening hidding back here in my office puzzling
over eda data structure terminology for capturing the complexity of
devices. This is actually very cowerdly of me as I am avoiding my wife's
quilting bee which has taken over the rest of the house.
In trying to scope the data
On Dec 20, 2007, at 1:24 PM, Dave McGuire wrote:
> On Dec 19, 2007, at 5:47 PM, John Doty wrote:
>>>As do I. I've always thought that gattrib's functionality being
>>> implemented as a separate program is a bit odd. I think there
>>> should
>>> be a menu choice like "Edit all component at
On Dec 19, 2007, at 5:47 PM, John Doty wrote:
>>As do I. I've always thought that gattrib's functionality being
>> implemented as a separate program is a bit odd. I think there should
>> be a menu choice like "Edit all component attributes..." which would
>> bring up what we now see as gattri
Peter TB Brett wrote:
> On Wednesday 19 December 2007 23:51:37 John Doty wrote:
The attribute value in the parts file then
>> overrides the value in the graphics, but the graphical properties of
>> the attribute still originate in the graphics.
>
> For e.g. inductors, how do you make sure that the
Dave N6NZ wrote:
> John Doty wrote:
>> 3. The flat file is a simple interface between BOM management and the
>> schematic->netlist->layout flow. Modular.
>>
>
> I suppose as an intermediate step, you could get the same effect with a
> sch2sch attribute replacer. It could look for the trigger a
On Dec 20, 2007, at 1:51 AM, Peter TB Brett wrote:
> On Wednesday 19 December 2007 23:51:37 John Doty wrote:
>
>> There is no graphical information in the parts file. For an attribute
>> to be visible in the schematic, a visible default/placeholder
>> attribute should be visibly present in the sy
On Wednesday 19 December 2007 23:51:37 John Doty wrote:
> There is no graphical information in the parts file. For an attribute
> to be visible in the schematic, a visible default/placeholder
> attribute should be visibly present in the symbol or visibly attached
> in the schematic. The attribute
John Doty wrote:
> 2. The flat file is another place where one can inspect or intervene in
> the flow.
There is value in that, certainly.
> 3. The flat file is a simple interface between BOM management and the
> schematic->netlist->layout flow. Modular.
>
I suppose as an intermediate step,
On Dec 19, 2007, at 10:01 PM, Dave N6NZ wrote:
>
>
> John Doty wrote:
>> On Dec 18, 2007, at 2:32 PM, Peter TB Brett wrote:
>>
>>> "Rewrite the component library C & Scheme APIs, and make a new GUI
>>> for it in
>>> gschem" is achievable (just). Ideally, I'd like to be able to do
>>> it in a
>>>
John Doty wrote:
> On Dec 18, 2007, at 2:32 PM, Peter TB Brett wrote:
>
>> "Rewrite the component library C & Scheme APIs, and make a new GUI
>> for it in
>> gschem" is achievable (just). Ideally, I'd like to be able to do
>> it in a
>> tidy, self-contained way.
>
> May I suggest the follo
John Doty wrote:
> Consider that a design might contain a bunch of chips, each with a
> bypass capacitor. Now, for sanity, it makes a lot of sense to use the
> *same* bypass capacitor device throughout the design. However, what
> if you need to change it?
This would argue for being able t
> Can the method DJ used for plugins in pcb be used by gschem at all?
That works if you have a way to "register" functions and call them by
name, instead of linking them in. Should be easy with the existing
guile support.
As for *what* to register, I suppose that depends on the user. PCB
just
Peter Clifton wrote:
> If the the core gattrib functionality were a GUI plugin, and gattrib a
> framework shell for loading schematics into memory etc.., then passing
> the TOPLEVEL to the gattrib widget, we might be able to have the best of
> both worlds.
>
> Plugins won't be too far away in gsc
On Dec 18, 2007, at 2:32 PM, Peter TB Brett wrote:
> "Rewrite the component library C & Scheme APIs, and make a new GUI
> for it in
> gschem" is achievable (just). Ideally, I'd like to be able to do
> it in a
> tidy, self-contained way.
May I suggest the following path to the future? I beli
On Dec 19, 2007, at 2:56 PM, Dave McGuire wrote:
> On Dec 19, 2007, at 3:52 PM, Ivan Stankovic wrote:
>>> Is there any barrier to integrating gattrib with gschem? I think
>>> I'd
>>> be
>>> happy with being able to pop up gattrib as a gigantic modal dialog.
>>
>> I had actually proposed just t
On Wednesday 19 December 2007 19:57:58 John Griessen wrote:
> Peter TB Brett wrote:
> > On Tuesday 18 December 2007 23:22:49 Levente wrote:
> >> I wanted to do that, but, to be honest, I have zero knowledge of gschem
> >> internals. I've tried to figure things out, but failed.
> >
> > That's where
On Tuesday 18 December 2007 18:52:39 [EMAIL PROTECTED] wrote:
> What I would quite like to do is to implement something similar to what
> has been described, especially since I have found a major bug which only
> (yet another) serious component library API change will fix.
I'd like to point out t
On Wed, Dec 19, 2007 at 09:15:03PM +, Peter Clifton wrote:
> On Wed, 2007-12-19 at 21:48 +0100, Ivan Stankovic wrote:
> > Yes, I have been working on a gattrib rewrite and I've just barely
> > got to load/save component attribs.
>
> If this is in git, it would be great to be able to track prog
1 - 100 of 175 matches
Mail list logo
