EAGLE FEATURE SURVEY

On 8/23/2012 6:38 PM, Jorge_Garcia wrote:

Hello fellow EAGLE users,

 

I've made a simple GoogleDocs Form as a type of survey and I would like to gather as much feedback as possible. The survey has only one question: What features would you like to see in future versions of EAGLE? Simply select the radio button of the feature you'd like to see, type in a few comments if you so desire and hit the submit button. That's it.

 

Here's the link for the form:

 

http://docs.google.com/spreadsheet/viewform?formkey=dEF4MWdPVXgxNjdHMk9aWE5wOTNyQmc6MQ

 

If you have any questions or concerns, feel free to reply to this thread.

 

Thanks in advance for your participation.

 

Best Regards,

Jorge Garcia

Cadsoft Support

 

Thanks to everyone who has participated. I'm going to let the survey

ride this week and then call it done. If you haven't filled out the

survey this is the last week to do so.

Thank you all for all of your input.

Best Regards,

Jorge Garcia

Cadsoft Support

On 10/15/2012 06:08 PM, Jorge Garcia wrote:

 

Thanks to everyone who has participated. I'm going to let the survey

ride this week and then call it done. If you haven't filled out the

survey this is the last week to do so.

 

Thank you all for all of your input.

Jorge,

Here's something that has just hounded me in the past.  I would like the

ability to add some text (or a circle or such) to the board and have it

associated with a component so that when the component is moved, the

associated text moves with it.  Alternatively or additionally, I would

like the ability to add text to a library package, and be able to smash

the package in the board and move the text (or circle) around in the

same manner that I can now smash and move >NAME and >VALUE.  The

motivation for this is to better document the layout for the assembly

house.  For example, I'd like to place the numeral 1 outside and close

to pin 1 of an IC, and be able to move it slightly in the layout editor

so as not to interfere with nearby components.

Thanks,

    - Chuck

On 10/15/2012 06:08 PM, Jorge Garcia wrote:

 

Thanks to everyone who has participated. I'm going to let the survey

ride this week and then call it done. If you haven't filled out the

survey this is the last week to do so.

 

Thank you all for all of your input.

Jorge,

Here's something that has just hounded me in the past.  I would like the

ability to add some text (or a circle or such) to the board and have it

associated with a component so that when the component is moved, the

associated text moves with it.  Alternatively or additionally, I would

like the ability to add text to a library package, and be able to smash

the package in the board and move the text (or circle) around in the

same manner that I can now smash and move >NAME and >VALUE.  The

motivation for this is to better document the layout for the assembly

house.  For example, I'd like to place the numeral 1 outside and close

to pin 1 of an IC, and be able to move it slightly in the layout editor

so as not to interfere with nearby components.

Thanks,

    - Chuck

Am 16.10.2012 17:04, schrieb Chuck Huber:

Alternatively or additionally, I would

like the ability to add text to a library package, and be able to smash

the package in the board and move the text (or circle) around in the

same manner that I can now smash and move >NAME and >VALUE.

This can already be done (NOT with a circle, but only with TEXT):

  - In the library, add a text that begins with a '>', e.g.,

    >MYATTRIBUTE.

  - In the library, use the ATTRIBUTE command to define a textual

    attribute with the above name (WITHOUT the '>') and give it a

    value of your choice (e.g., define an attribute with the name

    MYATTRIBUTE and the value MYVALUE).

  - That's it: In the above example, the word MYVALUE is displayed

    where you have positioned the >MYATTRIBUTE text. This attribute

    can be smashed as usual, repositioned, changed, etc.

Andreas Weidner

My top requests. I submitted only the first via the form... but here are the others, since I don't want to double-post:

#1 Request - SPEED!

• Problem: on a complex 300mm x 300mm panel, CAM processing of the gerbers takes around 15 minutes on an 8-core 3.6ghz machine. This makes the design process very slow when making revisions based on Gerber outputs
• Suggested Solution: Parallel processing for the CAM processor.
• Comment: From a programmer's perspective, this should be relatively painless, since the different CAM sections are not interdependant - they can be run in parallel without seriously changing the algortihm, eg. spawn new processes/threads for each section (*or even each aperature*!), then join back once all tasks complete. Currently, we have to open a few copies of Eagle.exe at the same time and run the CAM sections in parallel ourselves!

#2 Request - LIBRARY ENHACEMENT

• Problem:Loss of sync on library items if devices are renamed
• Suggested Solution: After a update library command, detect if parts are missing in currently linked libraries, and prompt to "relink missing devices"
• Comment: There is currently no solution to this problem, not even a ULP

#3 Request - ADVANCED COPY/PASTE SCHEMATIC *WITH* BOARD LAYOUT

• Problem: Copying and pasting schematic with the board layout requires too much manual intervention (opening/closing/renaming brd and sch files). The current best methods are prone to user error.
• Suggested Solution: A new option to group copy/paste BOTH schematic+board layout at the same time, with a selectable option to "create new net names to make the copy completely independant" (such that no air-wires exist)
• Comment: This would be incredibly useful for many of us trying to copy sections of existing designs for re-use. Currently, we have to disable forward/back annotation, then fix errors later. Sometimes, mistakes creep their way into our designs as a result, even if board consistency is re-achieved.

That's it... I know it's a lot of stuff, but I have faith in the Eagle development team!

Hope this makes it!

PS I forget to mention, for #1, parallel processing in other areas, such as ratsnest would be AMAZING as well. eg. Each layer's ratsnest should be calculated in parallel. Currently, this can take up to 30 seconds on a complex 300mm x 300mm design, making the routing process very slow.

Message was edited by: B Mac