Actions
Forum Thread Details
  • Replies 69 replies
  • Subscribers 185 subscribers
  • Views 3839 views
  • Users 0 members are here
Related

A few suggests for next major Eagle version

Former Member

1. Tabbbed interface, with detachable tabs (for people that use more than 1

screen). See GUI that mikroe

(http://www.mikroe.com/eng/categories/view/2/compilers/) uses for their

compillers. It will suit very well to Eagle,

 

2. XML documents structure;

 

3. "Project" should be a folder to contain:

a)  sch,

b)  brd,

c) - lbr with all components added in sch or brd; this will become THE

library that holds all components, any change should be made only in this

library,

d)  macros - group of components locked together ; ymbols only, or symbols +

routed tracks in brd (this should solve the "duplicate part of the routed

schematic"),

e)  a subfolder for fabrication files (gerber),

f)  a subfolder with documentation files (doc, pdf, txt, images, etc).

Either Eagle should be able to open all that files, either it will pass the

name to the OS to manage opening that files,

g)  a subfolder with archived versions of the project (you right click on

the project name, choose "Save version XX", and the associated archive will

be created)

 

4. Should be possible to edit any component from project, without modifying

the others (if there are 4 0805 resistors in the schematic, to be able to

right click on one of them - edit - and only that component to be changed) -

very easy to implement with the proposed 3.c)

 

5. Cut/copy behaviour shoud be as the one that any other software in this

world uses.

 

6. Color palette to be saved in the active file (sch, brd or lbr file).

Colors should be changed directly from the "Layer selection" window, to any

possible combination

 

7. A quick "DRC check" button should be placed somwhere handy. It will just

run DRC without displayng settings window

 

8. DRC behaviour should be improved - there are many to discuss here

 

9. Panelized printing should easy the work for people that makes boards at

home

 

10. Bundled text editor should know syntax highlighting and word

completition

 

11. Editable GUI of the main program. Either by customizable menus and

toolbars, either by making-it open source, as ULP.

 

This is a lot of work, but all my suggestions are based on what missed me

while I was using Eagle.

 

 

 

 

 

Parents

  • Why don't the programmers concentrate on improving the really fiddly workarounds for some of the missing functions that other packages include as normal?  A text editor is the least important requirement surely? For example; when you want to step and repeat a schematic and corresponding pcb that has already been routed you have to go through a right rigmaroll see below:

     

    1/ Make a copy of the pcb you want to step and repeat and renumber both boards and associated schematics so there are no common designators. using ULP cmd_renumber_2 . Save both,  we will name them PCB1 & PCB2

    2/ Rename all the nets using ULP renamesig_3

    3/Open the board to be added, (PCB2) group it and cut.

    4/Open the original pcb (board only PCB1) and paste in the one we cut (PCB2).

    5/Save the dual board layout as PCB1.brd

    6/Open the PCB2 schematic group and cut.

    7/Open PCB1 schematic and paste in PCB2 schematic. Save as PCB1.sch

    8/Now open PCB1 and the schematic should be more or less consistent. A few gnds and power nets may require tidying

     

    All this! and this is just one step and repeat!

    I wrote 'PCB Designer' for the Spectrum 48K in pure Z80 machine code all those years ago and even this allowed step and repeat operations. Granted it was not on the same level as modern packages but the point is; electronic engineers (I'm one), want electronic functionality and convenience. Incidentally I love Eagle and use it a lot but this work-around really tests my patience.

     

    Robert P Beales

     

    The element 14 interface automatically generated the emoticon after entering colon, end bracket. I have just removed it. Originally used to show that this sentence was meant as a joke. Message was edited by: Rob Beales

  • in reply to robprof

     

    "robprof"  wrote

     

    ....................machine code all those years ago and even this allowed

    step and repeat operations . Granted it was not on the same level as modern packages but the

    point is; electronic engineers (I'm one), want electronic functionality and

    convenience. Incidentally I love Eagle and use it a lot but this work-around

    really tests my patience.

     

    Klaus

    Please forward this example to the responsible person  at Farnell. The

    Element14 interface should be removing the emoticon coding.

     

    Thanks

    Warren

     

     

     

Reply
  • in reply to robprof

     

    "robprof"  wrote

     

    ....................machine code all those years ago and even this allowed

    step and repeat operations . Granted it was not on the same level as modern packages but the

    point is; electronic engineers (I'm one), want electronic functionality and

    convenience. Incidentally I love Eagle and use it a lot but this work-around

    really tests my patience.

     

    Klaus

    Please forward this example to the responsible person  at Farnell. The

    Element14 interface should be removing the emoticon coding.

     

    Thanks

    Warren

     

     

     

Children
  • in reply to Former Member

    "Warren Brayshaw" wrote:

     

    >"robprof"  wrote

    >....................machine code all those years ago and even this allowed

    >step and repeat operations . Granted it was not on the same level as modern packages but the

    >point is; electronic engineers (I'm one), want electronic functionality and

    >convenience. Incidentally I love Eagle and use it a lot but this work-around

    >really tests my patience.

    >>

    >

    >Klaus

    >Please forward this example to the responsible person  at Farnell. The

    >Element14 interface should be removing the emoticon coding.

     

    shouldn't we discuss this in the thread "The big NNTP vs HTML forum

    war collection" 2010-10-08 in the group eagle.userchat.eng,

    Message-ID: <news:i8mj4t$khk$1@cheetah.cadsoft.de>?

     

    Oliver

     

  • in reply to Former Member

    On 10/14/10 21:38, Warren Brayshaw wrote:

    ...

    Klaus

    Please forward this example to the responsible person  at Farnell. The

    Element14 interface should be removing the emoticon coding.

     

    Done.

     

    Klaus Schmidinger

    --

    _______________________________________________________________

     

    Klaus Schmidinger                       Phone: +49-8635-6989-10

    CadSoft Computer GmbH                   Fax:   +49-8635-6989-40

    Pleidolfweg 15                          Email:   kls@cadsoft.de

    D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de

    _______________________________________________________________