--- On Tue, 2/8/11, Kai-Martin Knaak wrote:
>
> Let's aim for the lowest possible denominator: The Planck
> length!
> http://en.wikipedia.org/wiki/Planck_length
>
Conveniently, there is also a measure of time for the performance analysis:
http://en.wikipedia.org/wiki/Planck_interval
C
On Feb 7, 2011, at 10:41 AM, DJ Delorie wrote:
>
> * nanometer internal units
>
> * 32-bit values on 32-bit machines, 64-bit on 64-bit.
>
> * configure option for 64-bit values regardless of machine in case you
> need a board larger than seven feet across.
What about storing both imperial and
On Jan 12, 2011, at 11:29 AM, al davis <[1]ad...@freeelectron.net>
wrote:
Both of these are areas where we could take the lead, but I need
help to do that. I can't do it alone, and can't do it if people
are fighting it. Does anyone want to help?
I would like to help with this
On Jan 3, 2011, at 8:20 AM, Stefan Salewski wrote:
> I guess all this was discussed on the list multiple times in the past,
> so this is more a note to myself...
>
> I think it may be useful to have two types of symbols, soft and hard.
> Hard symbols have an footprint attribute and maybe additio
On Oct 9, 2010, at 3:25 AM, Armin Faltl wrote:
>
>
> Edward Hennessy wrote:
>> On Apr 29, 2010, at 2:14 AM, Armin Faltl wrote:
>>
>>> To express the many-to-many relation between parts and symbols it uses
>>> a table called "device". This i
All,
The part manager needs to know the location of system-gafrc file. When
installing from a Debian package on Ubuntu 10.04 LTS, the file is located in
/etc/gEDA/system-gafrc. This prefix does not match any of the build directory
variables in the part manager or match anything returned from
g
On Apr 29, 2010, at 2:14 AM, Armin Faltl wrote:
> To express the many-to-many relation between parts and symbols it uses
> a table called "device". This is fed by the infamous device attribute
> in the symbol libraries. There's nothing wrong in the theory of DB-design
> with it, but the indiscrim
All,
The part manager needs to know the location of system-gafrc file. When
installing from a Debian package on Ubuntu 10.04 LTS, the file is
located in /etc/gEDA/system-gafrc. This prefix does not match any of
the build directory variables in the part manager or match anything
re
On Sep 28, 2010, at 12:59 PM, Steven Michalske wrote:
>
> On Sep 28, 2010, at 6:00 AM, Andrew Miner wrote:
>
>> would also like to see a pwr_src pin type which would be the output of the
>> voltage regulator (or source). That way the DRC would warn you if you
>> shorted two power sources toget
On May 6, 2010, at 10:48 AM, John Doty wrote:
>
> On May 6, 2010, at 11:38 AM, John Doty wrote:
>
>> On May 6, 2010, at 11:26 AM, Edward Hennessy wrote:
>>
>>> I didn't know of another way to implement this function. GParts is looking
>>> for whe
On Apr 29, 2010, at 12:28 PM, Armin Faltl wrote:
> Hi,
>
> I read some of the SQL files yesterday and just started an attempt to build
> gparts.
> The INSTAL file list requirements for building with MySQL and PostgreSQL.
> The later are present on my machine and I'm used to that DB.
>
> Then i
On Apr 29, 2010, at 1:01 PM, Armin Faltl wrote:
> Another strange thing with gparts:
>
> in 'sql/mysql/create-basic.sql' one finds:
> cut
> ...
> CREATE TABLE Symbol (
>
> SymbolIDINTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
> SymbolPa
On May 1, 2010, at 3:12 PM, Felipe De la Puente Christen wrote:
> Hi,
> Just to let you (Developers of gparts) know that I have compiled the
> git version of gparts, and when I run the program it segfaults searching
> for parts data.
Thanks for the report.
>
> fel...@monster:/usr/local/s
On May 6, 2010, at 5:17 AM, Armin Faltl wrote:
> Thanks for all the hints on working with the current tools.
>
> Still my current concern is how I get gparts working with PostgreSQL and I
> found
> these BUGS:
> *) configure doesn't react in a sensible way to a missing MySQL installation.
> It
--- 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 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
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
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
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
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.
Regarding component databases:
I'm working on a parts manager for gEDA. Although not completely functional
yet, the source is located in the git archive.
The program allows a user to browse and select a component from a database. The
parts manager will instantiate the component and then perform
On Feb 12, 2009, at 9:06 AM, al davis wrote:
>
> That is one of the reasons we need a translator system that
> (among others) will translate a PCB to a netlist format. When
> that happens, Gnucap is ready to do a full SI simulation,
> including IBIS. ... and of course trace impedance.
Is there
23 matches
Mail list logo
