kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #39590
Re: Processing older versions (topic split from v6 Upgrade)
Making the latest version of KiCad behave as older versions of KiCad is
like teaching a horse to eat with a fork.
On Thu, Feb 28, 2019 at 10:28 PM cedric.dewijs@xxxxxxxxxx <
cedric.dewijs@xxxxxxxxxx> wrote:
>
> >----Origineel Bericht----
> >Van : seth@xxxxxxxxxxxxx
> >Datum : 27/02/2019 18:00
> >Aan : Simon.Richter@xxxxxxxxxx
> >Cc : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >Onderwerp : Re: [Kicad-developers] Processing older versions (topic split
> from v6 Upgrade)
> >
> >Am 2019-02-27 11:52, schrieb Seth Hillbrand:
> >> Am 2019-02-26 12:11, schrieb Simon Richter:
> >>> Hi Cedric,
> >>>
> >>> On 26.02.19 06:55, cedric.dewijs@xxxxxxxxxx wrote:
> >>>
> >>>> I'm opposed to any program that modifies a file when I open
> >>>> it.
> >>>> In my opinion the file should only change when I press the
> >>>> "save" button.
> >>>
> >>> Of course, we'd have to ask first. The advantage would be that you can
> >>> stop before you do any changes to the board, so if you meant to be
> >>> using
> >>> an older version, you don't have to re-do your changes, and you get a
> >>> defined time where only the upgrade has taken place, but no other
> >>> changes, so you can do another version control check-in there.
> >>
> >>
> >> Hi Simon-
> >>
> >> I like how Solidworks handles this situation. You can open an older
> >> version but it has a flag so that as soon as you try to edit the file,
> >> you get the attached dialog (with the appropriate "Don't show again"
> >> checkbox).
> >>
> >> Would something similar address your concerns?
> >>
> >> -Seth
> >
> >As an aside, this also changes the save icon and tooltip for the save
> >button to warn the user as well. As soon as you save it in the new
> >version, this reverts to normal.
> >
> >-S_______________________________________________
> >Mailing list: https://launchpad.net/~kicad-developers
> >Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> >Unsubscribe : https://launchpad.net/~kicad-developers
> >More help : https://help.launchpad.net/ListHelp
>
> Hi All,
>
> How does an earlier version of Kicad handles a file that has been created
> by a newer version of Kicad?
> Altium opens files that have been created by a newer version, and warns
> the user. I use an older version of Altium than my co worker and so far we
> did not have issues yet. I can copy and paste from his designs to my
> designs without problems.
>
> As far as I can see Pcbnew does not offer to save the file as an older
> version.
>
> My main motivation to let the user continue to use older version of the
> file format in newer versions of Kicad is to prevent the forced upgrade
> path that all the commercial vendors use. This boils down to the question:
> Do we want to force the entire team to upgrade to a the same version of
> Kicad if they collectively work on the same files?
>
> Cheers,
> Cedric
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
Remember The Past, Live The Present, Change The Future
Those who look only to the past or the present are certain to miss the
future [JFK]
kandrey89@xxxxxxxxx
Live Long and Prosper,
Andrey
References
-
V6 merge update
From: Wayne Stambaugh, 2019-02-21
-
Re: V6 merge update
From: Seth Hillbrand, 2019-02-22
-
Re: V6 merge update
From: Wayne Stambaugh, 2019-02-22
-
Re: V6 merge update
From: Seth Hillbrand, 2019-02-22
-
Re: V6 merge update
From: Simon Richter, 2019-02-22
-
Re: V6 merge update
From: hauptmech, 2019-02-25
-
Re: V6 merge update
From: cedric.dewijs@xxxxxxxxxx, 2019-02-26
-
Re: V6 merge update
From: Simon Richter, 2019-02-26
-
Processing older versions (topic split from v6 Upgrade)
From: Seth Hillbrand, 2019-02-27
-
Re: Processing older versions (topic split from v6 Upgrade)
From: Seth Hillbrand, 2019-02-27
-
Re: Processing older versions (topic split from v6 Upgrade)
From: cedric.dewijs@xxxxxxxxxx, 2019-03-01