Open Sch & Brd files together

"Silviu Epure" wrote:

I prefer another definition: Eagle should have support for files related

to /EAGLE/. See the difference?

 

I prefere an other way: "I want to make a board, for a schematic. I need 5

datasheet, informations from the boardhouse, and some pictures. I want to be

able to access all this from only one IDE, the one used for creating

boards".

that's your - very specific - usage scenario. But your PDF-centric

view of things doesn't match everyone's needs.

I'm creating documentation while I'm working with Eagle. That's

project specific documentation I want to store in vicinity of the

Eagle files.

But usually I do not want to store the documentation of the parts

used in the same directory since I re-use the parts in other projects.

Therefore this kind of documentation resides in a completely different

tree. I can put links to them  in the project directory.

That's my - also specific - workflow.

I don't want to open (by hand, one after an other) half of the programs

installed on my HDD to complete this simple project.; I don't want to swim

in backup files to find my 3 usefull files.

If you would learn to use a decent file manager (e.g. some "Commander"

like Freecommander, Total C. etc.), you could filter the Eagle backup

files from your view.

Then you might realize that the "one tool for one task" is usually the

best approach.

A good file manager has preview for many file types, opens

everything with the right (or individually selected) applications,

jumps to your preferred paths quickly and much more.

My approach ist not to make Eagle a better file manager but to improve

Eagle's capabilities of integration to use it with a filemanager (also

"Windows Explorer" is nor the worst file manager).

The strength of the Eagle Control Panel is library browsing and

management.

Oliver

"Silviu Epure" wrote:

I prefer another definition: Eagle should have support for files related

to /EAGLE/. See the difference?

 

I prefere an other way: "I want to make a board, for a schematic. I need 5

datasheet, informations from the boardhouse, and some pictures. I want to be

able to access all this from only one IDE, the one used for creating

boards".

that's your - very specific - usage scenario. But your PDF-centric

view of things doesn't match everyone's needs.

I'm creating documentation while I'm working with Eagle. That's

project specific documentation I want to store in vicinity of the

Eagle files.

But usually I do not want to store the documentation of the parts

used in the same directory since I re-use the parts in other projects.

Therefore this kind of documentation resides in a completely different

tree. I can put links to them  in the project directory.

That's my - also specific - workflow.

I don't want to open (by hand, one after an other) half of the programs

installed on my HDD to complete this simple project.; I don't want to swim

in backup files to find my 3 usefull files.

If you would learn to use a decent file manager (e.g. some "Commander"

like Freecommander, Total C. etc.), you could filter the Eagle backup

files from your view.

Then you might realize that the "one tool for one task" is usually the

best approach.

A good file manager has preview for many file types, opens

everything with the right (or individually selected) applications,

jumps to your preferred paths quickly and much more.

My approach ist not to make Eagle a better file manager but to improve

Eagle's capabilities of integration to use it with a filemanager (also

"Windows Explorer" is nor the worst file manager).

The strength of the Eagle Control Panel is library browsing and

management.

Oliver