6 comments
Comment actions Permalink

Why not?

Personally I'm very happy to see this implemented (I've asked (at least commented) for that) -- for me this means if v4 EAP build is screw up somewhere, I still can use v3 without making any manipulations with config files.

Unfortunately I had to copy config files from v3 manually. I would prefer to have PhpStorm detect that v4 config folder is empty (or does not exist at all) and copy previous version config automatically (if available, of course).

0
Comment actions Permalink

3 reasons:

  1. In our deployment scheme, I test and then deploy PHPStorm for all users to use - this means all users have to manually import settings and if we have to go back and forth on versions, which happens early in the EAP for us, any settings changes will have to be made twice (we share much of our configuration)
  2. I publish templates for all users to use - so now, I have to change where those templates are published from and to
  3. PHPStorm will not copy over menus and toolbars for some reason - it took me 45+ minutes today to reconfigure all of my menus (other users will have to do the same)


I disagree with your point of what makes it better, because when we've had that issue in the past, we just rolled back to a previous config (I keep multiple copies, or we make a manual one before a version change like this.)

0
Comment actions Permalink

The easiest way to fix this (to have your routines still working) is to create symbolic link .WebIde40 --> .WebIde10  . This should do the job.

Of course, you can go and use more "official" way -- edit idea.properties file but that's PITA, really.

PHPStorm will not copy over menus and toolbars for some reason - it took me 45+ minutes today to reconfigure all of my menus (other users will have to do the same)

It did OK for me -- at least context menus, as I have not made any customization to main toolbar or main menu.

How did you import settings from v3 to v4 -- File | Export / Import ? I just copied whole config folder over...

0
Comment actions Permalink

Actually we have kind of rule that every major build should have its own config i.e. IntelliJIDEA9, IntelliJIDEA10, IntelliJIDEA11 because they usually have backward incompatible changes. Plus EAP wont screw previous release.

We'll provide a wizard for importing previous configuration and initial setup, as in our other products.

0
Comment actions Permalink

What are the new features/fixes in EAP 4.0 ?

0

Please sign in to leave a comment.