EAGLE FEATURE SURVEY

Am 24.08.2012 00:38, schrieb Jorge_Garcia:

I've made a simple GoogleDocs Form as a type of survey

Here some random thoughts about the different list entries. Numbers in

front of the list signify the importance of this entry (10=yes PLEASE,

0=forget it) based on my own very personal opinion.

  8  User Interface Improvements

       (See my previous posts for this)

  1  3D Visualization

       (That WOULD be nice in principle, but takes an AWFUL amount of

       manpower away for 3D library creation, so perhaps better

       not - we NEVER use the libraries from CadSoft, but ALWAYS

       create our own ones...)

10  Pad Stack

       (If 'pad stack' means the possibility of having different pads

       for top and bottom layers, YES PLEASE! If it means something

       else, I don't know)

  9  Schematic Hierarchy and Design Modularity

       (It would be VERY nice to have a sheet with some sort of block

       diagram, and if you double-click on a block, the corresponding

       sheet pops up. Additionally, with multi-channel boards one

       often finds a small error in one channel, and this then needs

       to be corrected eight times. It would be nice if there could

       be some channel connections so that a change oin one channel

       would be reflected in ALL of them. Though HOW this thing can

       be made to work EASILY, I've no idea)

  5  Simulation Facilities

       (Would be nice to have, but we can already do this with

       well-behaved ULPs here)

  4  More Import/Export Formats IDF, DXF, Netlists

       (Proper bitmap/vector imports/exports would be nice to have -

       and NOT only via external strange ULPs - but we don't need that

       SO often)

  2  Auto Placement

       (An auto-placer WOULD be nice in principle, but in order to

       get DECENT results, one would need to define SO many parameters

       that hand-placing might be easier overall)

  0  Multi-core or GPU support

  0  ODB++ Export

  0  Electrical Planning

  0  EAGLE for Tablet or Smartphones

       (or perhaps even MINUS ten instead of a zero in front)

  2  Autorouter improvements, push and shove, shape based, etc.

       (The current autorouter is possibly the worst in industry,

       and doing it correctly is an AWFUL amount of advanced

       programming. There are much more important things at the

       moment)

  8  Simplified Library Management, speedier part creation, etc.

       (though EAGLE has all NECESSARY functions for library management,

       their usage is QUITE outdated and VERY impractical. I'll write

       some additional posts with LOTS of suggestions concerning this

       when I find the time)

  0  Cloud Interface

  3  Version Control

       (With the current XML file scheme, integrating a version control

       should not be THAT difficult. BUT normally, one board is mainly

       created by ONE designer, and not many people fiddle around with

       it at the same time, so a version control might not be THAT

       important)

  4  Visual Difference Tool (Visually see differences between two boards)

       (That WOULD be nice, but I have no idea how the output of such a

       thing MIGHT look. Depending on that, it might be valuable or

       completely useless)

Overall, I think version 7 should include hierarchy and pad stack (for

the professionals), better user interface (for the newbies) and nicer

library handling (for both of them).

Andreas Weidner

Am 05.09.2012 18:20, schrieb Andreas Weidner:

Am 24.08.2012 00:38, schrieb Jorge_Garcia:

>> I've made a simple GoogleDocs Form as a type of survey

 

Here some random thoughts about the different list entries. Numbers in

front of the list signify the importance of this entry (10=yes PLEASE,

0=forget it) based on my own very personal opinion.

Here comes a 10 for Andreas... and i hope you don't mind taking your

list as a base for my vote

 

  8  User Interface Improvements

     8 from  me

  1  3D Visualization

       (That WOULD be nice in principle, but takes an AWFUL amount of

       manpower away for 3D library creation, snip

     1  from me because I see it the same way

10  Pad Stack

    5 from me, nice to have

  9  Schematic Hierarchy and Design Modularity

    10 from me. Certainly not easy imo, but that should be given hi

  priority...

  5  Simulation Facilities

       (Would be nice to have, but we can already do this with

       well-behaved ULPs here)

     Agreed

  4  More Import/Export Formats IDF, DXF, Netlists

       (Proper bitmap/vector imports/exports would be nice to have -

       and NOT only via external strange ULPs - but we don't need that

       SO often)

     6 from me because I often run into time consuming problems..

  2  Auto Placement

       (An auto-placer WOULD be nice in principle, but in order to

       get DECENT results, one would need to define SO many parameters

       that hand-placing might be easier overall)

     Yes, same sight here...

  0  Multi-core or GPU support

     There are more important things...

  0  ODB++ Export

     There are more important things...

  0  Electrical Planning

     There are more important things...

  0  EAGLE for Tablet or Smartphones

     There is always the cry for bigger screens...,or even multi screens

and now some people want a screen the size of three stamps...

  2  Autorouter improvements, push and shove, shape based, etc.

       (The current autorouter is possibly the worst in industry,

       and doing it correctly is an AWFUL amount of advanced

       programming. There are much more important things at the

       moment)

    Yeah, there IS an autorouter...

  8  Simplified Library Management, speedier part creation, etc.

       (though EAGLE has all NECESSARY functions for library management,

       their usage is QUITE outdated and VERY impractical.

     Fully agreed

  0  Cloud Interface

     Imho for the birds... Most work I do is confidential, so it goes to

the client and nowhere else.

  3  Version Control

       (With the current XML file scheme, integrating a version control

       should not be THAT difficult. BUT normally, one board is mainly

       created by ONE designer, and not many people fiddle around with

       it at the same time, so a version control might not be THAT

       important)

       Yes from me

  4  Visual Difference Tool (Visually see differences between two boards)

       (That WOULD be nice, but I have no idea how the output of such a

       thing MIGHT look. Depending on that, it might be valuable or

       completely useless)

     I have not seen that, so I say nothing to this item.

Personally I like to have either a second setting of size, one for

text/label and one for xref, or an automatic calculation that sets the

xref frame size (then with smaller text inside of course)equal to the

normal text size.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Am 05.09.2012 18:20, schrieb Andreas Weidner:

Am 24.08.2012 00:38, schrieb Jorge_Garcia:

>> I've made a simple GoogleDocs Form as a type of survey

 

Here some random thoughts about the different list entries. Numbers in

front of the list signify the importance of this entry (10=yes PLEASE,

0=forget it) based on my own very personal opinion.

Here comes a 10 for Andreas... and i hope you don't mind taking your

list as a base for my vote

 

  8  User Interface Improvements

     8 from  me

  1  3D Visualization

       (That WOULD be nice in principle, but takes an AWFUL amount of

       manpower away for 3D library creation, snip

     1  from me because I see it the same way

10  Pad Stack

    5 from me, nice to have

  9  Schematic Hierarchy and Design Modularity

    10 from me. Certainly not easy imo, but that should be given hi

  priority...

  5  Simulation Facilities

       (Would be nice to have, but we can already do this with

       well-behaved ULPs here)

     Agreed

  4  More Import/Export Formats IDF, DXF, Netlists

       (Proper bitmap/vector imports/exports would be nice to have -

       and NOT only via external strange ULPs - but we don't need that

       SO often)

     6 from me because I often run into time consuming problems..

  2  Auto Placement

       (An auto-placer WOULD be nice in principle, but in order to

       get DECENT results, one would need to define SO many parameters

       that hand-placing might be easier overall)

     Yes, same sight here...

  0  Multi-core or GPU support

     There are more important things...

  0  ODB++ Export

     There are more important things...

  0  Electrical Planning

     There are more important things...

  0  EAGLE for Tablet or Smartphones

     There is always the cry for bigger screens...,or even multi screens

and now some people want a screen the size of three stamps...

  2  Autorouter improvements, push and shove, shape based, etc.

       (The current autorouter is possibly the worst in industry,

       and doing it correctly is an AWFUL amount of advanced

       programming. There are much more important things at the

       moment)

    Yeah, there IS an autorouter...

  8  Simplified Library Management, speedier part creation, etc.

       (though EAGLE has all NECESSARY functions for library management,

       their usage is QUITE outdated and VERY impractical.

     Fully agreed

  0  Cloud Interface

     Imho for the birds... Most work I do is confidential, so it goes to

the client and nowhere else.

  3  Version Control

       (With the current XML file scheme, integrating a version control

       should not be THAT difficult. BUT normally, one board is mainly

       created by ONE designer, and not many people fiddle around with

       it at the same time, so a version control might not be THAT

       important)

       Yes from me

  4  Visual Difference Tool (Visually see differences between two boards)

       (That WOULD be nice, but I have no idea how the output of such a

       thing MIGHT look. Depending on that, it might be valuable or

       completely useless)

     I have not seen that, so I say nothing to this item.

Personally I like to have either a second setting of size, one for

text/label and one for xref, or an automatic calculation that sets the

xref frame size (then with smaller text inside of course)equal to the

normal text size.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag