Re: gEDA-user: Bug triage

2011-01-07 Thread Colin D Bennett
On Fri, 07 Jan 2011 16:17:55 -0500
DJ Delorie  wrote:

> 
> The minimimum size is still set to 1000, but was never updated when we
> switched to centimils, so the smallest board is now limited to 10
> mils!
> 
> Yes, the GTK sizes dialog still enforces it!

OK, then I have included you comment in the bug comments and marked this
bug as Fix Released.

Regards,
Colin


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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Kai-Martin Knaak
Dietmar Schmunkamp wrote:

> Start a design with gschem --> simulate it --> get it thru
> pcb --> extract physical paramaters from the layout --> OPTIMIZE* -->
> feedback to gschem --> restart the loop.

Unfortunately, at the current state of geda and friends the simulate 
step is a weak spot. Not so much because of weaknesses in the 
simulation algorithm. With gnucap and ngspice there are two very 
capable engines. It is the absence of readily available models and 
almost no GUI support that blocks the road.

---<)kaimartin(>---
-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: origin/master ... origin/stable-1.6 ?

2011-01-07 Thread Kai-Martin Knaak
Peter Clifton wrote:

>> PS: Any Peter A. around :-? 
> 
> I'm just heading to bed, and IIRC from IRC, so was Peter B.

I was thinking like "Peter A.", "Peter B.", "Peter C", ...

---<)kaimartin(>---(finally heading for bed, too) 

-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread DJ Delorie

Kai-Martin Knaak  writes:
> (I smell the scent of a feature request ;-)

Like http://www.delorie.com/pcb/pin-mapping.html ?

That lets the designer defer slot, package, and pin assignments until
layout time.

It assumes there's a unique identifier (not the refdes!) for each
symbol, so PCB can swap/merge/assign gates across packages.


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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Kai-Martin Knaak
Stefan Salewski wrote:

> For footprint shape that is correct -- for slots and pin numbers not.

Slot numbers and their influence on pin numbers can safely be ignored 
in the first stages of schematic capture. With single/dual/quad 
packages it is not that simple. No algorithm could reliably guess what 
the designer wants -- which symbols to merge, which pair to choose from 
a quad. The best gschem might do, is to offer a way to achieve these 
goals with a minimum hassle. Maybe some kind of multiple symbol mode.
(I smell the scent of a feature request ;-)


> If I currently place an OpAmp symbol, its inverting, non-inverting
> and output pin have already pinnumbers, pinseq,  and slotdef
> attribute. An enable or offset correction pin may exist or may not
> exist. So it is better to know ahead what you want.

Regarding offset correction, you better do. If used, the offset needs 
extra components and nets. 

---<)kaimartin(>---
-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: Launchpad up & running [was: SourceForge bug trackers frozen]

2011-01-07 Thread Kai-Martin Knaak
Peter Clifton wrote:

> I've added you to the geda-bugs team,

Thanks!
I noticed more options shown when I log into launchpad.


> but that might well mean
> you get spammed with a lot of bug-mail (sorry!)
> 
> If that is the case, let me know if it is a problem, and we'll
> investigate if it is possible to workaround it.

I will advise my local mail system to send all geda/pcb related 
launchpad mail to a special mailbox. That way, it does not clutter
my default inbox and I still can check what is going on.

---<)kaimartin(>---
-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: Symbol question - suggestions?

2011-01-07 Thread Kai-Martin Knaak
Johnny Rosenberg wrote:

> So, if I decide to use a 74-power symbol after all, is there 
> any way I can design it making it automatically understand 
> where it belongs, 

No. 


> so I don't need to manually enter all those ”U1, U2, U3” und 
> so weiter?

Even if you don't use the power symbol, you still have to distribute 
the refdes strings of slotted symbols manually. gschem has no way to 
know which symbols you intend to put in the same package. Yes, some 
kind of heuristics may be imaginable. Ideas have been floating on the 
mailing list. But none has been coded, yet.

 
> If I wanted a lot of work, I could draw my components with a pen
> on a piece of paper and then scan the whole thing…

this approach wouldn't produce a valid netlist :-P

---<)kaimartin(>---
-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: origin/master ... origin/stable-1.6 ?

2011-01-07 Thread Peter Clifton
On Sat, 2011-01-08 at 03:02 +0100, Kai-Martin Knaak wrote:
> Hi Peter B, Peter C.
> 
> Just noted that "git fetch" of git://git.gpleda.org/gaf reports 
> two branches. origin/master and origin/stable-1.6 . What is the 
> significance of these? Where should I look for the brave new features 
> that get pushed in the aftermath of the move from sourceforge to 
> launchpad?

origin/master is the place development happens
origin/stable-1.6 is the branch where the 1.6.x series is based

Typically, a fix lands in origin/master, and if it is a suitable fix for
the stable series, it will be cherry-picked into the stable branch as
well.

so - in short, "origin/master". 

> PS: Any Peter A. around :-? 

I'm just heading to bed, and IIRC from IRC, so was Peter B.

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


Re: gEDA-user: origin/master ... origin/stable-1.6 ?

2011-01-07 Thread Peter TB Brett
On Saturday 08 January 2011 02:02:38 Kai-Martin Knaak wrote:
> Hi Peter B, Peter C.
> 
> Just noted that "git fetch" of git://git.gpleda.org/gaf reports
> two branches. origin/master and origin/stable-1.6 . What is the
> significance of these? Where should I look for the brave new features
> that get pushed in the aftermath of the move from sourceforge to
> launchpad?
> 

I've pushed some patches to the 1.6.x branch ('stable-1.6') in preparation for 
1.6.2.  There are no new features or bugfixes in the 1.6.x branch, only 
backports of bugfixes already present in the unstable ('master') branch.

Sorry to disappoint,

  Peter

-- 
Peter Brett 
Remote Sensing Research Group
Surrey Space Centre


signature.asc
Description: This is a digitally signed message part.


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


gEDA-user: origin/master ... origin/stable-1.6 ?

2011-01-07 Thread Kai-Martin Knaak
Hi Peter B, Peter C.

Just noted that "git fetch" of git://git.gpleda.org/gaf reports 
two branches. origin/master and origin/stable-1.6 . What is the 
significance of these? Where should I look for the brave new features 
that get pushed in the aftermath of the move from sourceforge to 
launchpad?

---<)kaimartin(>---

PS: Any Peter A. around :-? 
-- 
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53



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


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 18:47 -0500, DJ Delorie wrote:
> I would like some field that the release managers can use for scheduling
> if/when a bug/patch/feature should be in a release.  I.e. if I tag a bug
> as "next bug release", then the next bug release has to wait until that
> bug is fixed, but "future bug release" won't hold it back.  Etc.

Take a look at the "milestone" feature in Launchpad. I've set up some
release milestones (on the main launchpad.net/pcb/ page), and you can
target particular bugs for particular milestones.

See for example:
https://launchpad.net/pcb/+milestone/next-bug-release

The release manager would just need to scan for bugs in the list which
are not "Fix Released". (I think they sort by status, so that should be
easy even with lots of bugs).

You could also do an "advanced search", and pick which milestone(s) you
want to find bugs targeted for. The URL gets a bit long then:

https://bugs.launchpad.net/pcb/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.milestone%3Alist=36187&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&search=Search

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread DJ Delorie

I would like some field that the release managers can use for scheduling
if/when a bug/patch/feature should be in a release.  I.e. if I tag a bug
as "next bug release", then the next bug release has to wait until that
bug is fixed, but "future bug release" won't hold it back.  Etc.


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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Dietmar Schmunkamp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Am 07.01.2011 20:21, schrieb Kai-Martin Knaak:
> Colin D Bennett wrote:
> 
>> The orthogonality
>> of these three pieces (schematic, footprint mapping, and PCB layout) is
>> pleasing to me, but I have to admit that you would rarely find a need
>> to create different PCBs from the exact same schematic.  
> 
> ack. Up to now, I _never_ had this situation in real projects. Some aspect
> of the schematic beyond footprints and packages always needs to be changed.
> On the other hand: Almost all projects need debugging and/or service. For
> this task, footprints printed on the schematic help to locate the part in 
> the layout.
>  
> 
>> Still, by
>> separating the footprint mapping entirely from schematic capture, you
>> can stay focused on one task at a time.
> 
> If this is your preferred way to work, you can already do it, even with
> heavy symbols: Just ignore the footprint attribute while placing symbols.
> Use gattrib, a text editor or a script to replace dummy values of the 
> footprints in a separate step.
> The mere fact that the footprint information is contained in the schematic
> does not imply, you have to set it during schematic capture.
> 
> ---<)kaimartin(>---

Hi,

maybe a little off topic and sorry to say, but I fear the discussion
about soft/hard/light/heavy symbols is going to over-optimize a certain
step in the design flow, the overall objective should be a working
product. And to achieve that we need to put some feedback into the
design loop. Start a design with gschem --> simulate it --> get it thru
pcb --> extract physical paramaters from the layout --> OPTIMIZE* -->
feedback to gschem --> restart the loop.

I'm aware that this can't be done by one person (unless there you have
infinte time), but each process step should propagate all
knowledge/implications to the next step (wire impedance, shielding ...).

I haven't pushed gaf/pcb to these limits yet, but ... my message is: Use
any kind of inforamtion regardless where it has been gathered to be
better next time.


BTW: In my day job (chip design, and I am in a close loop with all pro's
and con's :-) ) I  had an example of just changing physical footprints:

We had a ceramic module ($$$ and a huge manufacuring turn around time)
with 4 silicon chips on it that was attached to a pcb. The footprint of
each of hte 4 chips was fixed and the board layout was fixed, too. But
to debug the 4 chips there were 2 flavours of the ceramic carrier: One
ver y costly for the engineering hardware being capable of probing all
chip interconnects and another costreuced  (smaller) without exploiting
all chip to chip interconnects.


- -- 

Mit freundlichen Gruessen

Dietmar Schmunkamp
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk0nok4ACgkQn22l+QvEah13uQCeM0GxhA91GPX+EdURdEvZ7obv
VDMAni08Zv/8nnQ5+S53QCxngYKQI0cC
=vcPr
-END PGP SIGNATURE-


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


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 22:59 +, Peter Clifton wrote:
> On Fri, 2011-01-07 at 22:15 +, Peter Clifton wrote:
> > Hi,
> > 
> > Kai-Martin has rightly pointed out that by default, users don't have
> > access to set certain flags on bugs - such as priority. This comes in
> > handy if you know you're submitting a feature-request (which by default,
> > should be the status "Wishlist").
> 
> It has just been pointed out to me that I should _remind_ people, that
> setting the priority status on their own bugs is BAD FORM.

Further suggestions.. as I've altered two of these already.

Just a style nit, but I don't think we should close any bugs with
"sf-patches" as "Invalid".

This rather suggests that the problem the user is trying to patch is
somehow non-existent. If we decide we can't / won't accept a patch,
please close it with "WontFix"

"Invalid" should only be used for submitted patches if the issue is
filed against the wrong project, or works around a problem in the wrong
place - e.g. fixing a GTK theme bug by patching some horrific kludge
into PCB (NB: - that was a made-up example, not from an actual patch).


-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


Re: gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 22:15 +, Peter Clifton wrote:
> Hi,
> 
> Kai-Martin has rightly pointed out that by default, users don't have
> access to set certain flags on bugs - such as priority. This comes in
> handy if you know you're submitting a feature-request (which by default,
> should be the status "Wishlist").

It has just been pointed out to me that I should _remind_ people, that
setting the priority status on their own bugs is BAD FORM.

The exception here really being "Wishlist" is a decent status to set
your feature-requests to. Leave them as "New" though, so a second pair
of eyes will look and review it too.

If you're triaging patches / bugs from other people.. I'm not sure quite
what statuses to suggest - lets try not to be too formal for now, but my
suggestions would be:

Crasher / data loss -> "High" (or perhaps even "Critical" if it is likely to be 
hit).

Board output fault or incorrect netlist likely to cause design breakage
-> "High" (or "Medium" depending on likelihood / severity of the design
breakage)

UI wart / cosmetics -> "Low"
Feature request -> "Wishlist"

If unsure.. leave it as "Undecided"

Most important is confirming the bug, and / or commenting on /
discovering a minimal reproduction if not well stated by the original
submitter.

Best wishes,

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


gEDA-user: Apply to join the geda-bugs team to triage bugs...

2011-01-07 Thread Peter Clifton
Hi,

Kai-Martin has rightly pointed out that by default, users don't have
access to set certain flags on bugs - such as priority. This comes in
handy if you know you're submitting a feature-request (which by default,
should be the status "Wishlist").

Anyone who wants to help triage bugs for the community, please apply to
join the geda-bugs team (we should be able to approve the request pretty
much straight away).

https://launchpad.net/~geda-bugs/+join

and for PCB:

https://launchpad.net/~pcb-bugs/+join

You won't be spammed with bug-mail, as the team is set to email the
existing bug mailing lists, rather than each team member individually.

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


Re: gEDA-user: Launchpad up & running [was: SourceForge bug trackers frozen]

2011-01-07 Thread Peter Clifton
On Fri, 2011-01-07 at 20:02 +0100, Kai-Martin Knaak wrote:
> Peter Clifton wrote:
> 
> >> There seemed to be nothing like the old "feature request" category. So 
> >> I introduced the tag "feature-request". 
> > 
> > Set the priority to "wish-list", that should do it.
> 
> This was my first guess, too. But unfortunately, I can't set the importance 
> of a report. There is no edit button next to this property.

I've added you to the geda-bugs team, but that might well mean you get
spammed with a lot of bug-mail (sorry!)

If that is the case, let me know if it is a problem, and we'll
investigate if it is possible to workaround it.

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Stefan Salewski
On Fri, 2011-01-07 at 12:20 -0800, Colin D Bennett wrote:

> > 
> > If this is your preferred way to work, you can already do it, even
> > with heavy symbols: Just ignore the footprint attribute while placing
> > symbols. Use gattrib, a text editor or a script to replace dummy
> > values of the footprints in a separate step.
> > The mere fact that the footprint information is contained in the
> > schematic does not imply, you have to set it during schematic capture.
> 
> Thanks; these are both excellent points.
> 

For footprint shape that is correct -- for slots and pin numbers not. If
I currently place an OpAmp symbol, its inverting, non-inverting and
output pin have already pinnumbers, pinseq,  and slotdef attribute. An
enable or offset correction pin may exist or may not exist. So it is
better to know ahead what you want.



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


Re: gEDA-user: [Pcb-bugs] [Bug 699553] Re: tented mounting holes

2011-01-07 Thread DJ Delorie

Colin D Bennett  writes:
> OK, just realized that the solder mask was going to cover the mounting
> holes on my board after reading this bug report.  It seems like the
> default for "holes" (i.e., not plated) should be no solder mask over
> them.  Otherwise, what is the purpose of the hole if it is covered but
> is not a conductive via?

I use real footprints for mounting holes, and call them out on the
schematic.  I have a small collection of screw-sized one-pin footprints
for this purpose.

But PCB's default is "vias are tented, pins are not" because 99% of the
time, that's what the user wants.  I can see where a via->hole
conversion should do something smarter, though, but we've always had
weird luck with defining "the right thing" for conversions to/from
holes.


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


Re: gEDA-user: Bug triage

2011-01-07 Thread DJ Delorie

The minimimum size is still set to 1000, but was never updated when we
switched to centimils, so the smallest board is now limited to 10 mils!

Yes, the GTK sizes dialog still enforces it!


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


Re: gEDA-user: Bug triage

2011-01-07 Thread Colin D Bennett
On Fri, 07 Jan 2011 10:14:19 +
Peter Clifton  wrote:

> There are a lot of bugs which are still "New", ie.. haven't been
> confirmed or triaged yet, and I'd like to encourage EVERYONE to come
> and help with that task.

I have a question regarding the validity of the following bug:

“Make minimum size 1000x1000 mil”
.

This bug report states that pcb won't let you create a layout less than
1200 mil x 1200 mil.  However I have a layout that is much smaller than
that and have not encountered any restriction or problem yet.

This report is from 2004 and last commented on in 2005, so I am fairly
sure it is _Invalid_.  Can anyone confirm?

Regards,
Colin


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


Re: gEDA-user: Bug triage

2011-01-07 Thread Peter TB Brett
On Friday 07 January 2011 20:55:31 Colin D Bennett wrote:
> On Fri, 7 Jan 2011 10:22:53 +
> 
> Peter TB Brett  wrote:
> > Please use "Fix released" only if the fix has been in a released
> > version (the latest release was 1.6.1).  Otherwise, use "Fix
> > committed".
> 
> Is there any special tag or status indicator I can use for a bug which
> has a working bugfix patch attached?  It seems like bugs with a
> confirmed fix should be given high priority to get the fix committed to
> HEAD.
> 
> I am speaking presently about
> https://bugs.launchpad.net/pcb/+bug/699498
> which has a working patch that I have been using myself for some time.
> 

Well, the usual thing to do in that case is to complain on the mailing list, 
in which case a bug administrator (such as myself) may well go and find 
someone to nag about it.

Cheers,

Peter

-- 
Peter Brett 
Remote Sensing Research Group
Surrey Space Centre


signature.asc
Description: This is a digitally signed message part.


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


Re: gEDA-user: Bug triage

2011-01-07 Thread Colin D Bennett
On Fri, 7 Jan 2011 10:22:53 +
Peter TB Brett  wrote:

> Please use "Fix released" only if the fix has been in a released
> version (the latest release was 1.6.1).  Otherwise, use "Fix
> committed".

Is there any special tag or status indicator I can use for a bug which
has a working bugfix patch attached?  It seems like bugs with a
confirmed fix should be given high priority to get the fix committed to
HEAD.

I am speaking presently about
https://bugs.launchpad.net/pcb/+bug/699498
which has a working patch that I have been using myself for some time.

Regards,
Colin


signature.asc
Description: PGP signature


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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Colin D Bennett
On Fri, 07 Jan 2011 20:21:29 +0100
Kai-Martin Knaak  wrote:

> Colin D Bennett wrote:
> 
> > The orthogonality
> > of these three pieces (schematic, footprint mapping, and PCB
> > layout) is pleasing to me, but I have to admit that you would
> > rarely find a need to create different PCBs from the exact same
> > schematic.  
> 
> ack. Up to now, I _never_ had this situation in real projects. Some
> aspect of the schematic beyond footprints and packages always needs
> to be changed. On the other hand: Almost all projects need debugging
> and/or service. For this task, footprints printed on the schematic
> help to locate the part in the layout.
> 
> > Still, by
> > separating the footprint mapping entirely from schematic capture,
> > you can stay focused on one task at a time.
> 
> If this is your preferred way to work, you can already do it, even
> with heavy symbols: Just ignore the footprint attribute while placing
> symbols. Use gattrib, a text editor or a script to replace dummy
> values of the footprints in a separate step.
> The mere fact that the footprint information is contained in the
> schematic does not imply, you have to set it during schematic capture.

Thanks; these are both excellent points.

Regards,
Colin


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


Re: gEDA-user: Soft and Hard symbols

2011-01-07 Thread Kai-Martin Knaak
Colin D Bennett wrote:

> The orthogonality
> of these three pieces (schematic, footprint mapping, and PCB layout) is
> pleasing to me, but I have to admit that you would rarely find a need
> to create different PCBs from the exact same schematic.  

ack. Up to now, I _never_ had this situation in real projects. Some aspect
of the schematic beyond footprints and packages always needs to be changed.
On the other hand: Almost all projects need debugging and/or service. For
this task, footprints printed on the schematic help to locate the part in 
the layout.
 

> Still, by
> separating the footprint mapping entirely from schematic capture, you
> can stay focused on one task at a time.

If this is your preferred way to work, you can already do it, even with
heavy symbols: Just ignore the footprint attribute while placing symbols.
Use gattrib, a text editor or a script to replace dummy values of the 
footprints in a separate step.
The mere fact that the footprint information is contained in the schematic
does not imply, you have to set it during schematic capture.

---<)kaimartin(>---
-- 
Kai-Martin Knaak  tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik  fax: +49-511-762-2211 
Welfengarten 1, 30167 Hannover   http://www.iqo.uni-hannover.de
GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get



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


Re: gEDA-user: Launchpad up & running [was: SourceForge bug trackers frozen]

2011-01-07 Thread Kai-Martin Knaak
Peter Clifton wrote:

>> There seemed to be nothing like the old "feature request" category. So 
>> I introduced the tag "feature-request". 
> 
> Set the priority to "wish-list", that should do it.

This was my first guess, too. But unfortunately, I can't set the importance 
of a report. There is no edit button next to this property.

---<)kaimartin(>---
-- 
Kai-Martin Knaak  tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik  fax: +49-511-762-2211 
Welfengarten 1, 30167 Hannover   http://www.iqo.uni-hannover.de
GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get



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


Re: gEDA-user: Symbol question - suggestions?

2011-01-07 Thread Johnny Rosenberg

Den 2011-01-07 14:58:59 skrev Martin Kupec :


On Fri, Jan 07, 2011 at 12:06:12PM +0100, Johnny Rosenberg wrote:
So, if I decide to use a 74-power symbol after all, is there any way I  
can
design it making it automatically understand where it belongs, so I  
don't

need to manually enter all those ”U1, U2, U3” und so weiter?

You need to manualy assign number to that particular component.

Either you can autonumber everything and than manualy renumber
the 74-power (probably leaving holes in the numbering) or number
the 74 and 74-power when you place it with the same number
manualy and use autonumbering without the 'override' feature.


If I wanted a lot of work, I could draw my components with a pen on a
piece of paper and then scan the whole thing…



Martin Kupec


Sounds like a great source for errors. How do I prevent giving them the  
wrong numbers by accident (except trying extra hard when doing the manual  
job)?


--
Kind regards

Johnny Rosenberg


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


Re: gEDA-user: Symbol question - suggestions?

2011-01-07 Thread Martin Kupec
On Fri, Jan 07, 2011 at 12:06:12PM +0100, Johnny Rosenberg wrote:
> So, if I decide to use a 74-power symbol after all, is there any way I can  
> design it making it automatically understand where it belongs, so I don't  
> need to manually enter all those ”U1, U2, U3” und so weiter?
You need to manualy assign number to that particular component.

Either you can autonumber everything and than manualy renumber
the 74-power (probably leaving holes in the numbering) or number
the 74 and 74-power when you place it with the same number
manualy and use autonumbering without the 'override' feature.
> 
> If I wanted a lot of work, I could draw my components with a pen on a  
> piece of paper and then scan the whole thing…


Martin Kupec



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


Re: gEDA-user: Symbol question - suggestions?

2011-01-07 Thread Johnny Rosenberg

Den 2011-01-07 01:31:28 skrev Kai-Martin Knaak :


Johnny Rosenberg wrote:


First I manually set the ”device=” to match existing components,


No need. The device attribute is not used by anything in the gschem
to pcb work flow.



then I added ”numslots=” to match.


This is not useful. The slotting mechanism is only for copies of
the same symbol in a physical component. But the pwr symbol is a
_different_ symbol. Don't use slotting inside the pwr symbol.
You can set numslots=0 if you like. But this is not required.

There's no need to add any attributes to (my) 74_pwr.sym. Just put
it on the schematic like it is.



What am I missing? Should I edit the symbol itself or should I set
something in the schema or what?


Just make sure, that all the symbols that belong to a component all
get the same refdes. You have to do this manually. The autonumber
script has no idea which symbols belong to a group.
Also make sure to not add the pwr symbol first. The reason is that
this symbol does not include a footprint attribute. gsch2pcb only
accepts footprint attributes from the first symbol in a set. If this
symbol fails to provide a footprint, gsch2pcb gives up and issues an
error. This is a long standing bug that was fixed just a few days ago.



It was all so easy before, when I had the ”net=” thing in the component
symbols, but someone said that that's not the way to go, for some  
reason.


"Some reason" is schematic style seen from an advanced level of
experience. Take it as good advice from the old boys. You may ignore
it but don't complain if it this bites you later.

---<)kaimartin(>---


So, if I decide to use a 74-power symbol after all, is there any way I can  
design it making it automatically understand where it belongs, so I don't  
need to manually enter all those ”U1, U2, U3” und so weiter?


If I wanted a lot of work, I could draw my components with a pen on a  
piece of paper and then scan the whole thing…


--
Kind regards

Johnny Rosenberg


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


Re: gEDA-user: Bug triage

2011-01-07 Thread Peter TB Brett
On Friday 07 January 2011 10:14:19 Peter Clifton wrote:
> Grab "git HEAD" of whichever package the bug is in (if you don't have it
> already), and try to confirm whether the bug is still present or not.
> 
> Bug present: New -> Confirmed
> Bug absent: Make a comment - set bug to "Invalid",
> "Fix released", or
> "Incomplete"...
> depending on how confident you are that the bug was bogus,
> fixed by some commit since the bug reported, or "Incomplete"
> if you ask the reporter a question which requires answering.
> 

Please use "Fix released" only if the fix has been in a released version (the 
latest release was 1.6.1).  Otherwise, use "Fix committed".

Thanks for any help you can give me in ploughing through the backlog!

  Peter

P.S. It is not good form to set your own bug reports to "Confirmed". :-P


-- 
Peter Brett 
Remote Sensing Research Group
Surrey Space Centre


signature.asc
Description: This is a digitally signed message part.


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


gEDA-user: Bug triage

2011-01-07 Thread Peter Clifton
Hello everyone,

Peter Brett seems to have gone mad... he's triaging bugs and coding
fixes at an astonishing rate. Rather than our newly imported bugs in
Launchpad sitting abandoned and ignored, they are being FIXED!

There are a lot of bugs which are still "New", ie.. haven't been
confirmed or triaged yet, and I'd like to encourage EVERYONE to come and
help with that task.

If everyone did ONE bug, we'd be a _lot_ further on with this job.


Pick a bug from here:
https://launchpad.net/geda/+bugs?search=Search&field.status=New  (gEDA)
or:
https://launchpad.net/pcb/+bugs?search=Search&field.status=New   (pcb)


Grab "git HEAD" of whichever package the bug is in (if you don't have it
already), and try to confirm whether the bug is still present or not.

Bug present: New -> Confirmed
Bug absent: Make a comment - set bug to "Invalid",
"Fix released", or
"Incomplete"...
depending on how confident you are that the bug was bogus,
fixed by some commit since the bug reported, or "Incomplete"
if you ask the reporter a question which requires answering.

Does the bug affect you personally?
If so, hit the link about 2-3 inches down the page, under the title,
which lets you state that?

Interested in getting email about progress on this bug?
Hit "Subscribe" on the right hand toolbar.

Is your name on any bug?
Be sure to link the Sourceforge import with your SF email address to
your "proper" Launchpad account. Click your name if it isn't already
linked..

For example, Ineiev:
https://launchpad.net/~ineiev-users

Follow the Are you ineiev? link to:
https://launchpad.net/people/+requestmerge?field.dupe_person=ineiev-users


Lets all help with this task.. a lot of hands will make light work.

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)



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