Wish List for New Features

On Fri, 06 Feb 2009 12:19:04 -0500, Harvey White

<madyn@embarqmail.com> wrote:

On Thu, 05 Feb 2009 21:50:11 -0500, James Morrison

<james@eaglecentral.ca> wrote:

 

James Morrison wrote on Wed, 04 February 2009 22:04

Hello everyone,

 

Now that there has been time for a lot of us to evaluate EAGLE 5, let's

compile a list of features that we'd like to see in new releases.

 

 

OK: adding things as well:

 

1) ability to determine if a pad can be reached by the autorouter. 

 

Reason:  I'm having a lot of problems trying to route 0.5mm spacing

packages (TQFP 100 packages),

 

2) ability to highlight a signal and have it stick

 

Reason:  want to check signal routing for a particular signal and keep

it highlighted while I do other things.

 

3) ability in a library to add/delete pins without having to

disconnect the pins from the schematic.

 

4) ability to highlight used libraries for display

 

5) ability to group select libraries for use with a single keystroke.

 

Reason: helps in managing library use

 

6) Ability to switch parts on a schematic from one library to another.

 

7) ability to see range of "part can go here" on the board layout.

 

Reason:  I'm tired of positioning a part with the "this version of

eagle can't... etc." and not knowing where the part can actually go.

 

8) ability to constrain trace angle when moved to a specific angle,

say 0, 45, 90, etc.

 

Reason:  moving one end of a trace is good, but often we'd wish to

move traces and keep the angle alignment.

 

9) ability to draw a trace and have it obey the design rules both in

size and spacing from other traces.

 

reason: this would minimize design check errors.  This takes two forms

at least:  1) manually routing a trace would pick up the default class

trace width and use it.  You can still change trace width, but

manually routing things takes the default width to start.  2) when

manually routing a trace, the trace will change color (or otherwise

tend to "snap" to the minimum spacing from the adjacent trace).  This

allows you to more easily arrange parallel tracks.

 

10) radius command for direction changes.

 

11) ability to take another board design as a reference layer and base

other board designs on that. 

 

reason: this allows matching of daughterboards to a motherboard system

or layered boards with the next board in the sequence.

 

12) ability to determine the overall length of the ratsnest wires so

that the layout can be judged for efficiency.

 

13) ability to panelize print outputs regardless of the version of the

editor.

 

reason: really needed for panelize.  The restriction does not make a

lot of sense since you can design a board only the size of your

license.

 

14) ability to print multiple layer views of the board on the same

sheet.

 

reason: needed to have the most efficient use of board/transfer paper.

What I'd like to see is the ability to print out the silk screen layer

set, the top set, and the bottom set on the same piece of paper.  Also

useful for documentation.

 

15) ability to memorize different layer setups and reproduce them as

views.

 

reason:  Need to switch constantly between top view layers, bottom

view layers, and so on.  Existing layer visibility tools are useful,

but cumbersome to use.  This is a good thing for layout purposes.

 

16) switch to allow autorouting that disallows any between board layer

connections except vias.

 

Reason:  a convenience on the way that I route boards, but it would be

a nice feature and allow me to use the autorouter a bit more easily.

 

17) switch to turn off "unreachable SMD pad in layer n"  Ignore

further messages like this would be fine.

 

Reason:  I can use the autorouter to route one layer, say bottom, but

if I have anything on the other layer, the autorouter complains

constantly.  I can also route the top layer separately, but it'll

complain about the bottom layer.  Not the most efficient way to do

things, but a method that will work.

 

 

Harvey

 

 

 

 

 

OK, I'll start on the english side:

 

- already mentioned in German group:  hierarchy in designs.  Joerg, where

are you

- Footprints to allow named copper, abnormal pad shapes, custom copper,

..

- configurable colours of ratsnest wires-user can define ratsnest wire to

be a certain colour per signal

- control panel being able to open non-EAGLE files using OS default

programs

- edit local instance of footprint directly from PCB editor

- better find functionality out of the box and configured to use (i.e. if

it is done in ULP then already configured to assign statement by default so

new users can access it right away)

- store colour palette in design file if defined

- inner layer keepouts

- push aside router

 

I'll stop there for now.  I have more on my list that I've pulled out of

the suggest newsgroups (at least the english ones).

 

Please add ideas you have had.  CadSoft won't know if you don't speak up.

 

Kudos to CadSoft for the FollowMe router.  That was on my list when I

started last week (or at least something similar).  That one caught be off

guard and I was pleasantly surprised.

 

Cheers,

 

James.

--

James Morrison  ~~~  Stratford Digital

 

email:  sales2009@eaglecentral.ca

fax:    888.701.8097

web:    http://www.eaglecentral.ca

 

Online EAGLE Dealer for US and Canada

EAGLE Design Experts

EAGLE Enterprise Toolkit

• • • Dave Pollum - YES YES YES ***

2) ability to highlight a signal and have it stick

 

Reason:  want to check signal routing for a particular signal and keep

it highlighted while I do other things.

• • • YES YES YES ***

When manually routing, when I choose a routing layer (i.e. top),

I do not want EAGLE to change it!  This is a case of EAGLE

being too helpful, like MS Word is sometimes.  This issue comes

up when I have a SMD part on the top layer and another SMD part

opposite on the bottom layer. so there are 2 close airwires.  I

have to select the correct routing layer (i.e. bottom), and then

hide the other layer (i.e. top).      

Sometime I also have to "argue" with EAGLE when starting a route

from an existing via.

-Dave Pollum

On Fri, 06 Feb 2009 12:19:04 -0500, Harvey White

<madyn@embarqmail.com> wrote:

On Thu, 05 Feb 2009 21:50:11 -0500, James Morrison

<james@eaglecentral.ca> wrote:

 

James Morrison wrote on Wed, 04 February 2009 22:04

Hello everyone,

 

Now that there has been time for a lot of us to evaluate EAGLE 5, let's

compile a list of features that we'd like to see in new releases.

 

 

OK: adding things as well:

 

1) ability to determine if a pad can be reached by the autorouter. 

 

Reason:  I'm having a lot of problems trying to route 0.5mm spacing

packages (TQFP 100 packages),

 

2) ability to highlight a signal and have it stick

 

Reason:  want to check signal routing for a particular signal and keep

it highlighted while I do other things.

 

3) ability in a library to add/delete pins without having to

disconnect the pins from the schematic.

 

4) ability to highlight used libraries for display

 

5) ability to group select libraries for use with a single keystroke.

 

Reason: helps in managing library use

 

6) Ability to switch parts on a schematic from one library to another.

 

7) ability to see range of "part can go here" on the board layout.

 

Reason:  I'm tired of positioning a part with the "this version of

eagle can't... etc." and not knowing where the part can actually go.

 

8) ability to constrain trace angle when moved to a specific angle,

say 0, 45, 90, etc.

 

Reason:  moving one end of a trace is good, but often we'd wish to

move traces and keep the angle alignment.

 

9) ability to draw a trace and have it obey the design rules both in

size and spacing from other traces.

 

reason: this would minimize design check errors.  This takes two forms

at least:  1) manually routing a trace would pick up the default class

trace width and use it.  You can still change trace width, but

manually routing things takes the default width to start.  2) when

manually routing a trace, the trace will change color (or otherwise

tend to "snap" to the minimum spacing from the adjacent trace).  This

allows you to more easily arrange parallel tracks.

 

10) radius command for direction changes.

 

11) ability to take another board design as a reference layer and base

other board designs on that. 

 

reason: this allows matching of daughterboards to a motherboard system

or layered boards with the next board in the sequence.

 

12) ability to determine the overall length of the ratsnest wires so

that the layout can be judged for efficiency.

 

13) ability to panelize print outputs regardless of the version of the

editor.

 

reason: really needed for panelize.  The restriction does not make a

lot of sense since you can design a board only the size of your

license.

 

14) ability to print multiple layer views of the board on the same

sheet.

 

reason: needed to have the most efficient use of board/transfer paper.

What I'd like to see is the ability to print out the silk screen layer

set, the top set, and the bottom set on the same piece of paper.  Also

useful for documentation.

 

15) ability to memorize different layer setups and reproduce them as

views.

 

reason:  Need to switch constantly between top view layers, bottom

view layers, and so on.  Existing layer visibility tools are useful,

but cumbersome to use.  This is a good thing for layout purposes.

 

16) switch to allow autorouting that disallows any between board layer

connections except vias.

 

Reason:  a convenience on the way that I route boards, but it would be

a nice feature and allow me to use the autorouter a bit more easily.

 

17) switch to turn off "unreachable SMD pad in layer n"  Ignore

further messages like this would be fine.

 

Reason:  I can use the autorouter to route one layer, say bottom, but

if I have anything on the other layer, the autorouter complains

constantly.  I can also route the top layer separately, but it'll

complain about the bottom layer.  Not the most efficient way to do

things, but a method that will work.

 

 

Harvey

 

 

 

 

 

OK, I'll start on the english side:

 

- already mentioned in German group:  hierarchy in designs.  Joerg, where

are you

- Footprints to allow named copper, abnormal pad shapes, custom copper,

..

- configurable colours of ratsnest wires-user can define ratsnest wire to

be a certain colour per signal

- control panel being able to open non-EAGLE files using OS default

programs

- edit local instance of footprint directly from PCB editor

- better find functionality out of the box and configured to use (i.e. if

it is done in ULP then already configured to assign statement by default so

new users can access it right away)

- store colour palette in design file if defined

- inner layer keepouts

- push aside router

 

I'll stop there for now.  I have more on my list that I've pulled out of

the suggest newsgroups (at least the english ones).

 

Please add ideas you have had.  CadSoft won't know if you don't speak up.

 

Kudos to CadSoft for the FollowMe router.  That was on my list when I

started last week (or at least something similar).  That one caught be off

guard and I was pleasantly surprised.

 

Cheers,

 

James.

--

James Morrison  ~~~  Stratford Digital

 

email:  sales2009@eaglecentral.ca

fax:    888.701.8097

web:    http://www.eaglecentral.ca

 

Online EAGLE Dealer for US and Canada

EAGLE Design Experts

EAGLE Enterprise Toolkit

• • • Dave Pollum - YES YES YES ***

2) ability to highlight a signal and have it stick

 

Reason:  want to check signal routing for a particular signal and keep

it highlighted while I do other things.

• • • YES YES YES ***

When manually routing, when I choose a routing layer (i.e. top),

I do not want EAGLE to change it!  This is a case of EAGLE

being too helpful, like MS Word is sometimes.  This issue comes

up when I have a SMD part on the top layer and another SMD part

opposite on the bottom layer. so there are 2 close airwires.  I

have to select the correct routing layer (i.e. bottom), and then

hide the other layer (i.e. top).      

Sometime I also have to "argue" with EAGLE when starting a route

from an existing via.

-Dave Pollum