Most users will just move the preferences over. But you raise a good point, and should repeat it in the new feature request section. It should be simple for the upgrade install to ask you if you want to bring in any old preferences.
Just think about it.
Successive versions of the program are always sufficiently different to make using old preferences impossible. And in any case it’s necessary to work through all the preferences to set the new features.
If you keep third party plug-ins, actions and brushes in their own folders it is a matter of moments to point the new version at them.
In any case just "hoping" that a plug-in written for CSx will work with CSx+1 is a bit dodgy or even downright dangerous.
how hard would it be to bring across my preferences,
Possibly doable for some parts, not for others.
my filters,
Filters are recompiled for each release due to changes in the SDK. As of CS4, they can even create persistent panels for instance. Copying the old ones certainly would be doable, but since Adobe can’t guarantee that one of those legacy plugins would not break the new version, it’s probably better to not do it.
my actions,
Depends. Actions often refer to menu items and their internal ID numbers may change. An automatic conversion/ import may not take care of updating these references…
my scripts?
Possibly, but similar to the other things, updates may be required or the scripts may pose more risk than enjoyment.
And I know CS4 has new layout capabilities, but why not offer the option of bringing across my old familiar layout?
Impossible. CS4 uses a completely different GUI layout engine from CS3.
Mylenium
Okay, so instead I’ve had to do it all by hand. And so far all of the plugins that I was using with CS3 are still working (whew!) and at least the actions and scripts I have "restored" so far are working (still more to come).
It’s just a lot of work. And, at least from my perspective (since nothing I’ve tried so far has broken) it appears it could have been done automatically by the install program.
If, as developers, you’re worried about things not working between releases, then why not code them up with release numbers and such.
I have this bit of "free" software that uses plugins. They have a method for keeping track of which plugins work across versions. You might have heard of it .. it’s called Firefox.
Can’t help but think my $700 editor should be capable of something similar.
All I’m really saying is … time is money.
And if the Red Sea parted, you’d complain about walking in the mud, LOL.
Maybe!
I just figure if I don’t speak up and I don’t get what I want, I have nobody to blame but me.
Can’t help but think my $700 editor should be capable of something similar.
But then again, third-party vendors don’t share their code publicly for the most part, yes? 😉 This is one more thing that can be seen either way – if you used some exotic custom medical image format plugin and it would prevent you from even launching the app, the screaming would be even bigger. Perhaps Adobe will include automated functions for this in the future, perhaps they won’t. And to "speak up", use the right boombox:
<
http://www.adobe.com/go/wish>
Mylenium
Time is money
You must be making a lot of it, since you can’t spare that one hour every 18 months 🙂
Why must an upgrade act like it’s a new install?
Basically because it is a new install, that’s why. You’ve upgraded your licence. The actual software, however, is exactly the same as it would be when installing a new full version.
Actually, I was surprised to see that Bridge CS4 took over both my saved workspace seetings and the Bridge cache location from Bridge CS3.
— Olaf
Lightroom installs to a brand new directory, yet is smart enough to pull over an existing catalog and settings.
There are many programs that are capable of going through an "upgrade process" as they install. It’s true, not everything can be upgraded (or upgraded safely), especially when dealing with third party software.
Still, it would be nice if they put in some effort to pull across settings at least (they have 100% control over that) and then work with third party developers (similar to how Firefox does) so that those too can be ported over to the upgraded install.
To the naysayers that so quickly want to say it can’t be done … I’ve been a programmer all my life. This is software. It CAN be done. Anything in software CAN be done. It all depends on time and money and priorities.
This is a good point and something that adobe should take into consideration after all it’s an update not a totally new software.
It is a lot better if an installation is totally divorced from the previous version.
A little preparation in advance by the user is all that is needed.
I have moved step by step from Version 3.0 to CS4 using this philosophy.
I’d want to be sure my install works before moving my settings/scripts/third party stuff into it. Then I can have a better idea where to look if something acts up.
Why must an upgrade act like it’s a new install?
A perfect Prof. Higgins question.
A little preparation in advance by the user is all that is needed.
I have moved step by step from Version 3.0 to CS4 using this philosophy.
Me too. Not quite as long … I started with version 6.0.
But wouldn’t it be grand if the computer did the work for the human … instead of the other way around???
With a little pre-planning at the programming stages, the upgrade process could be handled for the user instead of by the user. I’ve been writing software since 1976, I’ve dealt with similar issues with third party add-ons to the software that I’ve worked on. I know it can be done.
(I think it’s funny how people have to come to the aid of a product that clearly could be "improved upon" … it’s only software … it’s not like I’m bashing it, I’m just looking forward to a little improvement, that’s all)
With a little pre-planning at the programming stages, the upgrade process could be handled for the user instead of by the user.
Not with the plethora of krazy konfigurations I’ve seen out there!
If people manage to get their machines into a state where even a simple install fails, how are you going to cater for an automatic migration?
Not with the plethora of krazy konfigurations I’ve seen out there!
I already mentioned that Firefox manages to upgrade their plugins … but if you want to see "krazy konfigurations", how about Microsoft and Windows? The market is a thousand times bigger with an even bigger set of configurations.
And yet … the only time I have ever done a "fresh install" of Windows is when I’ve gotten a brand new machine. Whenever I’ve simply upgraded Windows, I’ve let the Windows’ upgrade process bring everything right along with it. That includes the upgrade to Vista.
If Firefox and Microsoft can do it … Adobe can.
Stop making excuses. It’s only software. As long as Adobe’s own customers are quick to defend the current software and say how much trouble it would be, Adobe’s programmers will just say "ah, they don’t really need it" and move on to the next task.
If Firefox and Microsoft can do it … Adobe can.
Apples and Oranges!
not really. he has a good point.
If Firefox and Microsoft can do it … Adobe can.
Apples and Oranges!
Really? How so?
The way I see it, Firefox is in the best position because they have controlled the versioning of their plugins and provided a common distribution mechanism.
Microsoft, on the other hand, has a heckuva challenge trying to keep everything working. The number of applications that "reach below the surface" of their APIs. The number of "old" applications that still must continue to run. And OMG, the hardware drives. It’s amazing they succeed at all.
Adobe, in my opinion, is somewhere between the two. They have not controlled their plugins as well as Firefox has, so they have a harder time of controlling upgrades. But the number and diversity of Adobe’s plugins is miniscule compared to what Microsoft faces with Windows.
Again … can it be done? Those two companies alone prove it can.
If I were Adobe I would try to adopt something akin to the Firefox approach, even if they have to phase it in over time.
Again, it’s only software. Anything is possible.
