Downgrading brd/sch from V5 -> V4

"Richard Hammerl" <ric@cadsoft.de> wrote in message

news:g3qo41$uhu$1@cheetah.cadsoft.de...

EAGLE can't save the files in an older data format. Changes in the

data structure are partially irreversible and new features can't

be interpreted by older EAGLE version. This could cause losses in

your drawings.

If you read my initial posting, I mentioned that the enhanced functionality

of V5 would have to be removed in the transfer, but the truth is a lot of

that is subtle, such as the treatment of xref lables etc (which can always

go back to being plain lables in V4).

There are ULPs around that extract all sorts of data from SCH/BRD files -

netlists, parts etc. I was merely wondering how hard it would be to export

from V5 & then import into V4 such data.

As I also pointed out, many other products do this - e.g. MS Word 2007 can

export in many formats, including those of previous versions of Word, even

though some formatting etc. may be lost... In Eagle's case, the base

requirements for a consistent schematic at least haven't changed -

components & a netlist. Nice things like attributes etc. can be dropped as

they don't directly impact the logical integrity of the schematic.

And by the way:

A simply written text with a few letters arranged on a sheet

can't be compared to a schematic/layout design, can it? scnr

?? I'm not sure what you mean by this. The whole point of my request is that

there is (and will be for some time) a very large constituency of V4 users

who will not be able to play with anything created under V5, which makes

those who publish designs hold back from upgrading.

Nick

"Richard Hammerl" <ric@cadsoft.de> wrote in message

news:g3qo41$uhu$1@cheetah.cadsoft.de...

EAGLE can't save the files in an older data format. Changes in the

data structure are partially irreversible and new features can't

be interpreted by older EAGLE version. This could cause losses in

your drawings.

If you read my initial posting, I mentioned that the enhanced functionality

of V5 would have to be removed in the transfer, but the truth is a lot of

that is subtle, such as the treatment of xref lables etc (which can always

go back to being plain lables in V4).

There are ULPs around that extract all sorts of data from SCH/BRD files -

netlists, parts etc. I was merely wondering how hard it would be to export

from V5 & then import into V4 such data.

As I also pointed out, many other products do this - e.g. MS Word 2007 can

export in many formats, including those of previous versions of Word, even

though some formatting etc. may be lost... In Eagle's case, the base

requirements for a consistent schematic at least haven't changed -

components & a netlist. Nice things like attributes etc. can be dropped as

they don't directly impact the logical integrity of the schematic.

And by the way:

A simply written text with a few letters arranged on a sheet

can't be compared to a schematic/layout design, can it? scnr

?? I'm not sure what you mean by this. The whole point of my request is that

there is (and will be for some time) a very large constituency of V4 users

who will not be able to play with anything created under V5, which makes

those who publish designs hold back from upgrading.

Nick