Announcement: EAN-02 :: Managing EAGLE Directories

Hello James,

do you think it's possible to limit the line length of your posting to

some 70 characters? Else it's hard to quote.

"Stratford Digital recommends adding a user folder as the base for all

EAGLE related design files and making it the highest priority."

 

Although this seems to mirror the way Cadsoft intended to use Eagle, I

strongly dislike the idea of one big tree of Eagle projects.

 

I put Eagle project files (epf, sch, brd and special project libs) in

subfolders of the product projects where I store also other design

files and docs.

 

What we have suggested doesn't preclude having a large sub-tree of

projects.  In fact, it would be the natural way to do it and is in

fact how we work here.  But it means that you use the EAGLE Control

Panel to move around and open projects.

While I can see that this will work, I'm not sure I'd go to that

extent.  I actually like having a big tree of projects.  It makes

revision control easier for one thing.

The question is whether you want to use the Eagle control panel in

your "big tree of projects". I prefer a good file manager.

If you meant my automatic version selection method: As I wrote, it

depends. E.g. whether you have to make small maintenance changes in

old projects. Usually it's much more efficient to use the according

Eagle version than to convert the project to the new Eagle version,

especially if the old files are still Eagle 3. Or consider a

contractor - he must use the same version as his client.

And the point of this app note was to help newbies understand how

To avoid misunderstandings: I didn't want to criticize your app note,

just wanted to show that in many cases it's more efficient to use a

different method.

things work.  I'd say your setup is more advanced.  For new users

who start with EAGLE 5 then there isn't the concern of auto-updating

projects.

 

Thanks for the input though.  You've obviously thought about this before

Decades .

Oliver

Hello James,

do you think it's possible to limit the line length of your posting to

some 70 characters? Else it's hard to quote.

"Stratford Digital recommends adding a user folder as the base for all

EAGLE related design files and making it the highest priority."

 

Although this seems to mirror the way Cadsoft intended to use Eagle, I

strongly dislike the idea of one big tree of Eagle projects.

 

I put Eagle project files (epf, sch, brd and special project libs) in

subfolders of the product projects where I store also other design

files and docs.

 

What we have suggested doesn't preclude having a large sub-tree of

projects.  In fact, it would be the natural way to do it and is in

fact how we work here.  But it means that you use the EAGLE Control

Panel to move around and open projects.

While I can see that this will work, I'm not sure I'd go to that

extent.  I actually like having a big tree of projects.  It makes

revision control easier for one thing.

The question is whether you want to use the Eagle control panel in

your "big tree of projects". I prefer a good file manager.

If you meant my automatic version selection method: As I wrote, it

depends. E.g. whether you have to make small maintenance changes in

old projects. Usually it's much more efficient to use the according

Eagle version than to convert the project to the new Eagle version,

especially if the old files are still Eagle 3. Or consider a

contractor - he must use the same version as his client.

And the point of this app note was to help newbies understand how

To avoid misunderstandings: I didn't want to criticize your app note,

just wanted to show that in many cases it's more efficient to use a

different method.

things work.  I'd say your setup is more advanced.  For new users

who start with EAGLE 5 then there isn't the concern of auto-updating

projects.

 

Thanks for the input though.  You've obviously thought about this before

Decades .

Oliver