New storage location

eaglecandies wrote:

Basically, how can you select EXACTLY where each project folder is

stored,

with its own independent path?

The way I would do it is, from the control panel, go to the Options menu

and choose "Directories..." and add the new directory to the front of the

"Projects" path.  Then your new project will be created in that directory.

You can always drag and drop the projects to a different directory if you

want...

--

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

Why can't you just do "save as" and pick your desired project location?  Or

can you?

Having to edit a directory path seems like rather poor planning.

--

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

On 8/18/2014 10:46 AM, Hoyt wrote:

Why can't you just do "save as" and pick your desired project location?  Or

can you?

Having to edit a directory path seems like rather poor planning.

 

Hello Hoyt,

I hope you're doing well. Usually EAGLE expects users to organize

everything in one major directory which you can organize however you

wish. My recommendation would be to select such a directory and then

under that directory create the /sam/... and /bill/... directories as

necessary.

hth,

Jorge Garcia

Jorge Garcia schrieb:

On 8/18/2014 10:46 AM, Hoyt wrote:

Why can't you just do "save as" and pick your desired project location?  Or

can you?

Having to edit a directory path seems like rather poor planning.

 

Hello Hoyt,

 

I hope you're doing well. Usually EAGLE expects users to organize

everything in one major directory 

...and this is completely crap right from the start.

It is, and has always been, absolutely boring and senseless to put the

project files in a central directory resp. structure. The normal way of

organising projects in a company is to keep everything belonging to a

project in a well structured scheme, and this includes many other

documents and files as well - with the EAGLE files being only a small

part of the files belonging to the hardware design part of the project.

The only "right way" would be to allow us to us project files *wherever

we want* (and also named as we like).

Just have a look at all those IDEs for software development to get a clue...

The wish/request for ambiguously named and located project files is

decades old, but still ignored by CadSoft - though it would be very easy

to implement.

(For central files like libraries, scripts, ULPs and design rules, EAGLE

must of course use central directories - but these must reside in

AppData, not the program directory...)

Tilmann

"Tilmann Reh"  skrev i nyhetsmeldingen: lsuqgp$rp6$1@cheetah.cadsoft.de ...

...and this is completely crap right from the start.

Agree, this is ancient thinking..

(For central files like libraries, scripts, ULPs and design rules, EAGLE

must of course use central directories - but these must reside in

AppData, not the program directory...)

Careful here. I think some libs, scripts and ulp's also need some degree of

maintainance and project control. You may want to keep your old lib

definitions for old projects, and even diff them. I've kind of gotten used

to make local scr/lib/ulp and even cam folder for every project I do. The

original libs are just used to copy from, when needed. This does make it

necessary to add path to the options-directories, so I think there is room

for improvements.

I do not really feel its time to suggest additions to Eagle, cause it has

quite a few slightly annoying old quirks (and even some new since v6) that

needs to be fixed first, but a version control with diff tools should be on

the list somewhere, maybe on v9..

Am 18.08.2014 00:57, schrieb Hoyt:

For this newest project, I want a totally different path, such as

c:/sam/was/here/project....

How do you select this?  I don't want to change my old projects in any way

or how they are accessed. A different upcoming project will be

c:/bill/was/there/project....

 

Basically, how can you select EXACTLY where each project folder is stored,

with its own independent path?

What people do here is the following:

  1. If it is not already installed that way, make your OS react to

     double-clicks on any SCH or BRD file by opening EAGLE with the

     clicked file. At least under Windows, that's easily possible.

  2. Do NOT open EAGLE and THEN try to access the folder, but look

     at that folder with your favourite file manager and THEN

     double-click on the desired file, so EAGLE opens up appropriately.

  3. This has the additional advantage (or disadvantage, depending on

     your needs) that every double-clicked design opens a NEW instance

     of EAGLE, so you can look at designs side-by-side.

Andreas Weidner

Morten Leikvoll schrieb:

"Tilmann Reh"  skrev i nyhetsmeldingen: lsuqgp$rp6$1@cheetah.cadsoft.de ...

...and this is completely crap right from the start.

Agree, this is ancient thinking..

 

(For central files like libraries, scripts, ULPs and design rules, EAGLE

must of course use central directories - but these must reside in

AppData, not the program directory...)

 

Careful here. I think some libs, scripts and ulp's also need some degree of

maintainance and project control. You may want to keep your old lib

definitions for old projects, and even diff them. I've kind of gotten used

to make local scr/lib/ulp and even cam folder for every project I do.

I don't think this is a good idea... You end up with zillions of

different libraries, maybe of similar names, with true and only apparent

duplicates of parts - you really can't manage that reliably.

The original libs are just used to copy from, when needed. This does

make it necessary to add path to the options-directories, so I think

there is room for improvements.

The "original" libraries are so bad that they don't even serve this

purpose. IMHO, it's better to use only self-defined libraries.

I do not really feel its time to suggest additions to Eagle, cause it has

quite a few slightly annoying old quirks (and even some new since v6) that

needs to be fixed first, but a version control with diff tools should be on

the list somewhere, maybe on v9..

Sadly, there are so many long-standing issues that were never addressed

(or even acknowledged), and that could have been fixed rather easily,

that I don't think they are really listening to us.

Tilmann

"Tilmann Reh"  skrev i nyhetsmeldingen: lt095p$740$1@cheetah.cadsoft.de ...

 

Morten Leikvoll schrieb:

 

"Tilmann Reh"  skrev i nyhetsmeldingen: lsuqgp$rp6$1@cheetah.cadsoft.de

...

...and this is completely crap right from the start.

Agree, this is ancient thinking..

 

(For central files like libraries, scripts, ULPs and design rules, EAGLE

must of course use central directories - but these must reside in

AppData, not the program directory...)

 

Careful here. I think some libs, scripts and ulp's also need some degree

of

maintainance and project control. You may want to keep your old lib

definitions for old projects, and even diff them. I've kind of gotten

used

to make local scr/lib/ulp and even cam folder for every project I do.

 

I don't think this is a good idea... You end up with zillions of

different libraries, maybe of similar names, with true and only apparent

duplicates of parts - you really can't manage that reliably.

Imo, a proper management tool has no problems with that. It would show the

different version parts in a list - by date - and then you could ask to see

them and hilite the differences. Then it would ask you to overwrite the

latest to all the other locations.

The original libs are just used to copy from, when needed. This does

make it necessary to add path to the options-directories, so I think

there is room for improvements.

 

The "original" libraries are so bad that they don't even serve this

purpose. IMHO, it's better to use only self-defined libraries.

Oh, you are right there. I dont trust them, but sometimes I import from

them, check and rework them. I can probably count the times Ive done that on

my two hands.

I do not really feel its time to suggest additions to Eagle, cause it has

quite a few slightly annoying old quirks (and even some new since v6)

that

needs to be fixed first, but a version control with diff tools should be

on

the list somewhere, maybe on v9..

 

Sadly, there are so many long-standing issues that were never addressed

(or even acknowledged), and that could have been fixed rather easily,

that I don't think they are really listening to us.

They did listen to us on the licensing But maybe it was all the noise

they listened to and not what we said..

Maybe we should ask for a voteable todo list

Morten Leikvoll schrieb:

Sadly, there are so many long-standing issues that were never addressed

(or even acknowledged), and that could have been fixed rather easily,

that I don't think they are really listening to us.

 

They did listen to us on the licensing But maybe it was all the noise

they listened to and not what we said..

...or they realized that most of the voices said "I definitely won't buy

V7". Trying to sell a product that noone wants to buy is hard.

Obviously, all those long-standing issues didn't have (enough) influence

on the cash side.

Maybe we should ask for a voteable todo list

We already did - this is one more long-standing issue... :-\

(And of course one needs to take care - many insane wishes would

probably flood the list and eventually even get more votes than the

really necessary improvements. Just have a look at the kind of questions

coming from element14 to get in impression...)

Tilmann