A few suggests for next major Eagle version

eSilviu wrote on Fri, 13 August 2010 02:52

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,

I'd rather see real features that help with the electronics and designing

boards.

Quote:

2. XML documents structure

I'd rather see real features that help with the electronics and designing

boards.

What the data structure of the internal files are is irrelvant as long as

they hold the data.  It would be nice if they were documented better, but

at least they are accessible via ULPs.  XML can be more of a hassle than a

well thought out binary file.  XML doesn't automatically mean good, and

non-XML bad.  XML is also very verbose.

Quote:

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

I'd rather see real features that help with the electronics and designing

boards.

Quote:

d)  macros - group of components locked together

Hierarchical schematic elements would be useful, although I don't think

that's what you're talking about.  It would be nice to be able to can parts

of a design, then use it as a element in other schematics.  The schematic

would then be a tree structure, with the devices and symbols we have now

being the leaf nodes.

Quote:

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)

I'd rather see real features that help with the electronics and designing

boards.

You can do most of this now yourself.

Quote:

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

So go do it and don't bother CadSoft about it.  See HELP ASSIGN.

Quote:

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

Yes, but this is now lost in your flood of suggestions.

Quote:

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

at home

I'd rather see real features that help with the electronics and designing

boards.

Get real.  How many people that use Eagle at home actually pay for it?

Quote:

10. Bundled text editor should know syntax highlighting and word

completition

I'd rather see real features that help with the electronics and designing

boards.

There are plenty of text editors out there.  Let's not have CadSoft waste

time on reinventing this wheel, or chosing one at the expense of all the

others.  There is no need for Eagle to have a text editor at all.  I edit

ULPs and scripts routinely, but never with Eagle's editor.  Eagle would

have to support exactly the text editor enviroment I use for it to be of

any use.

Quote:

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

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

I'd rather see real features that help with the electronics and designing

boards.

If you want to suggest changes, you should pick the one or maybe two that

you really care about.  You've dumped so much stuff here, with enough of it

silly fluff, that I'd probably dismiss all of it if I were CadSoft.

Keep in mind that everything is a tradeoff.  If they work on one

enhancement, there will be other enhancements that won't get done.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Am 13.08.2010 08:53, schrieb eSilviu:

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.

>

>

>

>

I hate long letters, so I shall not go into the  details. IMHO most of

these suggestions can be done by other ways and programs, and certainly

I don't want eagle to be my next "operation System"

Hierarchical sheet structure is imo more important than customizable

gui's. But we shall see...

--

Gruß / regards

Joern

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:i43alv$liv$1@cheetah.cadsoft.de...

I'd rather see real features that help with the electronics and designing

boards.

I'd rather see real features that help with the electronics and designing

boards.

...

You can do most of this now yourself.

As well as you can draw boards in Paint or on paper by yor self!

Eagle is a tool, and everyone is free to say what it likes or dislike at

that tool. And to propose improvements too.

Get real.  How many people that use Eagle at home actually pay for it?

what tis has to do with any of my suggestions?! you're out of subject!!!

>There is no need for Eagle to have a text editor at all.  I edit

ULPs and scripts routinely, but never with Eagle's editor.

Eagle text editor has one feature that none of other editors don't have: It

know at what line the error is.

So...

I'd rather see you proposing something constructive than just towing stones

on any new proposal....

"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

news:i43f4c$9ct$1@cheetah.cadsoft.de...

Hierarchical sheet structure is imo more important than customizable

gui's. But we shall see...

So:

12. I have forget about hyerarchical structure. It should be there, and it's

just a step away of proposed "project library" and "macro components"

IMHO most of these suggestions can be done by other ways and programs, and

certainly I don't want eagle to be my next "operation System"

When you go to work... would you prefere to use only one pair of shues? or 3

pairs and change them according to the terrain: one for gras, one in

buildings and one on the street?

When I start a project, I would like that all the work for that project to

be in one and only one place. Maybe for you that "place" is called

"computer". But for me "computer" means 1000 places (ordered, but still

1000).

eSilviu wrote on Fri, 13 August 2010 09:43

When I start a project, I would like that all the work for that project

to be in one and only one place.

So go ahead.  You don't need special help from Eagle for that.

I keep all my Eagle projects in a tree structure with each individual board

having its own directory.  I don't need Eagle to do anything special for

that, and don't want it to.  That's what the operating system, text editor,

scripts, and other things are for.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

eSilviu wrote on Fri, 13 August 2010 09:34

I'd rather see you proposing something constructive than just towing

stones on any new proposal....

It's important for CadSoft to hear when people think suggestions are bad

ideas too.

The reason some suggestions are actually bad even if the new feature could

be ignored, is because implementing that feature takes resources from

implementing something more useful.  Everything is a tradeoff.  A long wish

list is just a distraction without prioritization.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:i43j7r$u1e$1@cheetah.cadsoft.de...

eSilviu wrote on Fri, 13 August 2010 09:43

I keep all my Eagle projects in a tree structure with each individual

board

having its own directory.  I don't need Eagle to do anything special for

that, and don't want it to.  That's what the operating system, text

editor,

scripts, and other things are for.

I still don't believe you understand what a "feature" means: It means that a

software CAN do something, but it will not force you to do that way.

I don't see why you couldn't use you OS and text editors further, after (or

if) my suggestions are implemented. In fact I don't see how any of my

suggestions would affect you in any way.

"Olin Lathrop" <eagle@embedinc.com> wrote in message

news:i43jkd$vks$1@cheetah.cadsoft.de...

eSilviu wrote on Fri, 13 August 2010 09:34

The reason some suggestions are actually bad even if the new feature could

be ignored, is because implementing that feature takes resources from

implementing something more useful.  Everything is a tradeoff.  A long

wish

list is just a distraction without prioritization.

>

I see here only big words, spoked in the name of others.

Please, a "I disagree with X,Y and Z" it would be enough from a possible

user.

eSilviu wrote on Fri, 13 August 2010 10:10

In fact I don't see how any of my suggestions would affect you in any

way.

They would take resources from implementing other features that I can't get

from the operating system, text editor, shell scripts, etc.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Am 13.08.2010 15:43, schrieb eSilviu:

"Joern Paschedag"<jpaschedag@t-online.de>  wrote in message

news:i43f4c$9ct$1@cheetah.cadsoft.de...

>

>> Hierarchical sheet structure is imo more important than customizable

>> gui's. But we shall see...

So:

12. I have forget about hyerarchical structure. It should be there, and it's

just a step away of proposed "project library" and "macro components"

>

>> IMHO most of these suggestions can be done by other ways and programs, and

>> certainly I don't want eagle to be my next "operation System"

>

When you go to work... would you prefere to use only one pair of shues? or 3

pairs and change them according to the terrain: one for gras, one in

buildings and one on the street?

>

When I start a project, I would like that all the work for that project to

be in one and only one place. Maybe for you that "place" is called

"computer". But for me "computer" means 1000 places (ordered, but still

1000).

>

>

  I can hardly follow you. We are talking about the eagle layout program.

If you want eagle to do all the work nessesary for a project, are you

willing to pay for that?

--

Gruß / regards

Joern