Open Sch & Brd files together

I agree with the suggestion that eagle tree should be able to open files

of other applications. but this does not mean that EAGLE itself must

have pdf viewer at all. just needs to pass the open command to the OS

and let it launch the user's choice of viewer. That's all we are asking

for.

As far as the opening of single board/schema, I think it is a dangerous

pitfall for the new user. As Joern points out, no need for yet another

option, you don't want both windows, just close one.

maybe when directed to open a .sch or .brd from the OS, EAGLE should

check the folder for a project file and just open, or ask to open, the

project. otherwise just view the file.

"T G" <fightspammers@gmail.com> wrote in message

news:hm6fit$2u0$1@cheetah.cadsoft.de...

No, it doesn't, but so what? How often do you use that swiss army knife?

It does a lot, but none of it well, don't you usually break out the real

tools? Do you really want Eagle to be that way? It will be if the

developers spend lots of time on non-Electronic stuff.

I just want that all files (except backup files) in a project to be visible

in Eagle, and when I double-click one of them, to be opened with associate

program.

This is the right way .

The wrong way is to:

-use Windows explorer to browse to my project,

-click on eagle.epf (generic name, the same for all projects), by default

unassocied with Eagle, so I must choose "Open with..." and browse for

eagle.exe

-wait for Eagle to load all libraries of that project (by default ALL

libraries), and if after loading, I want to add an other component, I must

wait again for ALL libraries to be loaded (try if you don't believe me)

-only then view/edit the schematic/board

Count this one too:

-right click on a component, write down on a paper it's library and package

- from Eagle CP: File/open/library + browse for that library (if it's not in

the first "Library director" it's even worse), and then edit that component,

according to a datasheet:

-use again Windows Explorer to open that datasheet, related to your project,

and stored on the same root folder with your project

How many windows do you have opened by now: 1.Eagle CP, 2. Schematic,

3.Board, 4.Lib editor, 5PDF viewer, 6Windows explorer?

Eagle with tabs + PDF reader should be enaugh.... if Eagle would have tabs,

and it would know how to open other files.

And developpers won't spend lots of time on non-Electronic stuff, because it

means just to pass to the OS commnad to open the file

"Tilmann Reh" <usenet2007nospam@autometer.de> wrote in message

news:hm3ksq$2oo$1@cheetah.cadsoft.de...

Opening a project would be done by opening the .epf by any means (for

example, double click in any file explorer or shell) - just as it is

with any other IDE.

This affirmation is valid only if 1 file does not contain all the

information nedeed.

But .sch file, or .brd or .lbr file contain all it needs to display

schematic, board or library.

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

news:hm5ean$uk9$1@cheetah.cadsoft.de...

Your "eficiency" is rubbish. If in windows explorer you click on an excel

file for example, the explorer calls excel.exe which in turn opens the

excel file. Same goes with eagle. So you should be a little more precise.

It takes 5ms for explorer to call excel to open the excel files,

it takes me 30 seconds to search for excel shortcut and then browse for the

file I want to open

So, yes, what I say it's eficiency

Il 25/02/2010 22.09, Gary Gofstein ha scritto:

I agree with the suggestion that eagle tree should be able to open files

of other applications. but this does not mean that EAGLE itself must

have pdf viewer at all. just needs to pass the open command to the OS

and let it launch the user's choice of viewer. That's all we are asking

for.

Agree. Enough to open an external Pdf viewer (Adobe, Foxit...). This

would greatly help in navigating documentation (datasheets, project docs

etc.). Currently though the Pdf files are not shown in the Eagle CP.

Maybe an option in eaglerc to specify what files to show and howto open

the viewer.

Interface.FileViewer = ".pdf:AcroRd32.exe %1;.txt:Notepad.exe %1"

As far as the opening of single board/schema, I think it is a dangerous

pitfall for the new user. As Joern points out, no need for yet another

option, you don't want both windows, just close one.

You are saying to make Eagle open both sch/brd as defasult, no questions

asked? This is the way I would like Eagle to behave. Then close the file

you don't want/need (remember the dangers). In extreme cases where you

really don't want the other file opened just rename the sch/brd pair to

different names and only one file will be opened.

Gary Gofstein wrote:

I agree with the suggestion that eagle tree should be able to open files

of other applications. but this does not mean that EAGLE itself must

There seem to be two groups of users: The "one task one tool" group

and those who want to have a "do it all" Eagle.

I don't want to use one more file manager with different user

interface. It will never match the maturity of a "real" file manager.

I would prefer a better integration of Eagle to be used with the OS

means.

My programming editor ("IDE"), HTML editor, office software etc. all

do not have file manager functionality and I doubt anyone asks for

such a feature.

IMO the real benefit of the Eagle control panel is the library

handling (browse, copy elements between libraries)!

have pdf viewer at all. just needs to pass the open command to the OS

and let it launch the user's choice of viewer. That's all we are asking

for.

You open a can of worms. Eagle had to handle all the file

associations, shell extensions etc. to do it well. That's not the task

of a development software.

As far as the opening of single board/schema, I think it is a dangerous

pitfall for the new user. As Joern points out, no need for yet another

option, you don't want both windows, just close one.

 

maybe when directed to open a .sch or .brd from the OS, EAGLE should

check the folder for a project file and just open, or ask to open, the

project. otherwise just view the file.

Since the epf is in the same folder, the user could open the epf file

instead of the brd or sch.

And keep in mind that opening the epf file also means changing it if

the epf file is set to "auto save".

Oliver

"Oliver Betz" <obetz@despammed.com> wrote in message

news:m33fo5p7t7alqqss61uf04fa615g1ec25c@news.cadsoft.de...

There seem to be two groups of users: The "one task one tool" group

and those who want to have a "do it all" Eagle.

I don't want to use one more file manager with different user

interface. It will never match the maturity of a "real" file manager.

I would prefer a better integration of Eagle to be used with the OS

means.

We don't want Eagle to know how to open porn!

We create a electronics project. Eagle should have support for files related

to electronics; nothing less, nothing more.

My programming editor ("IDE"), HTML editor, office software etc. all

do not have file manager functionality and I doubt anyone asks for

such a feature.

not quite... office is used to create office documents. It incorporates

image viewer, equation editor (eved external eq. editor), and many many

moote "tools"; Html editor - the same story.

have pdf viewer at all. just needs to pass the open command to the OS

and let it launch the user's choice of viewer. That's all we are asking

for.

 

You open a can of worms. Eagle had to handle all the file

associations, shell extensions etc. to do it well. That's not the task

of a development software.

nop...

If (file !sch and !brd and !lbr and !scr and !ulp), "shell run

filename.ext".

simple enough?!

As far as the opening of single board/schema, I think it is a dangerous

pitfall for the new user. As Joern points out, no need for yet another

option, you don't want both windows, just close one.

 

maybe when directed to open a .sch or .brd from the OS, EAGLE should

check the folder for a project file and just open, or ask to open, the

project. otherwise just view the file.

 

Since the epf is in the same folder, the user could open the epf file

instead of the brd or sch.

and the same novice user will copy only "eagle.epf" file to USB stick, to

give to a friend the "schematic, board and all it needs"

Why? because this is the file he uses to open the project.

Silviu Epure schrieb:

We create a electronics project. Eagle should have support for files related

to electronics; nothing less, nothing more.

Who defines which file types are "related to electronics"?

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

to /EAGLE/. See the difference?

Since the epf is in the same folder, the user could open the epf file

instead of the brd or sch.

 

and the same novice user will copy only "eagle.epf" file to USB stick, to

give to a friend the "schematic, board and all it needs"

Why? because this is the file he uses to open the project.

What would your stupid novice user do when he tries to give his friend

the files of his latest software development? Copy only the project file

of the IDE, without all the sources etc.?

If that novice is /that/ stupid, he will need to copy the correct files

in a second try - and hopefully learn from that. You can't protect

novices from every stupidity.

However, this detail discussion is somewhat meaningless here - there are

more relevant, basic issues that should be addressed first (see the new

thread in the suggest group).

Tilmann

"Tilmann Reh" <usenet2007nospam@autometer.de> wrote in message

news:hm891h$rtl$1@cheetah.cadsoft.de...

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".

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.

Silviu Epure schrieb:

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".

Perhaps you got used to this method because you don't have a

useful/powerful file manager? (This is not meant offensive - but I just

can't imagine doing it that way could be considered as effective.)

We have hundreds of projects organised in a hierarchical tree. Not all

projects contain EAGLE data, and some contain several revisions of EAGLE

files. Of course we have everything that is really related to the

project in that particular project folder - however datasheets or

boardhouse information definitely belongs at other places, since these

are not project related (at least we use the same parts and boardhouses

for more than one project...).

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.

You think of EAGLE as a shell, from where you want to process/manage the

whole workflow. I think this is not what EAGLE was developed for. You

should think about using a shell that is meant for exactly this task.

Then you can do everything you mentioned above from that single program.

You activate the /documents/ (not the programs!) and the OS calls the

needed programs to open them, regardless of document type (EAGLE, PDF,

Word, Picture or whatever else). Of course all project related

documents/files are arranged in the same folder (or related subfolders),

so you have them all at hand when you open that folder.

Please take the time to really think about this. I'm pretty sure your

workflow would be much more efficient (and the needed programs much less

bloated) if your concept was more "object oriented" and less "program

oriented" - perhaps after a short time of getting used to it.

Tilmann