One more update for version 7.1 is now available for you. In RubyMine 7.1.3 we’ve addressed a number of known issues and performance problems, including performance issues in RubyMotion apps. The full list of fixed issues can be found in the release notes.
Our colleagues on the PhpStorm team have also added a new feature called Remote edit. It allows files to be opened from the remote host (such as FTP, SFTP or FTPS) and edited in the IDE, without adding/downloading them to your local project. Read more about that in the PhpStorm blog.
As usual, a patch update is available from RubyMine 7.1.2. If you’re using a different RubyMine version, please download and install RubyMine 7.1.3 from our website.
Rails refactoring guru Andrzej Krzywda shares his experience and best practices during this session. Andrzej shows how to apply typical refactoring recipes to put your code in order, with examples of service objects and other patterns, all using RubyMine refactorings extended with custom shortcuts:
“In almost all cases, I’m opposed to setting aside time for refactoring. In my view, refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts.”
― Martin Fowler, Refactoring: Improving the Design of Existing Code
Nowadays refactoring is an essential part of most developers’ lives. Ruby developers are not an exception. Knowing this we’ve always focused on refactoring tools in RubyMine. I can’t think of a major IDE update that didn’t bring some improvements for refactoring features. However, many of our users are unaware of some of these useful features. To sort this out, we’ve asked Andrzej Krzywda, a Rails refactoring guru, to share his experience and best practices.
Ever since my colleagues and I visited RailsConf 2015 in Atlanta last month, I’ve been pondering over the closing keynote by Kent Beck. We’re lucky to be a part of the JetBrains family, but like all developers we sometimes ask ourselves, “Does my work matter?”. How can we know if our work on RubyMine is making a difference?
I believe the answer lies in your feedback, and especially the feedback at the conferences we visit: when we get a chance to talk to Ruby developers, sit close together and look at RubyMine with your eyes. That’s what RailsConf was all about. The first day at the booth, so many people stopped by that we barely had a minute to catch our a breath.
And that was great! Thank you for coming to our booth and sharing your joy and passion, asking questions and voicing concerns!
If you are a Mac user and prefer to be on the cutting edge, you might have faced a very unpleasant problem on OS X 10.10.4 beta – RubyMine has not started correctly there. That’s why today we publish one more update for the 7.1 version with the corresponding fix on board. We have fixed a few other problems as well (see full list of fixes).
Use “Check for Updates…” to download and install the update as a patch to your existing installation. Or, download RubyMine 7.1.2 from our website.
Thank you all for your feedback and comments that helped us discover a few pest issues to be fixed on a first-priority basis. RubyMine 7.1.1 is now available for you. We focused mostly on debugger problems and added a few other changes as well (see full list of fixes).
Use “Check for Updates…” to download and install the update as a patch to your existing installation. Or, download RubyMine 7.1.1 from our website.
As of today we start the final countdown for RubyMine 7.1 release! Please welcome RubyMine 7.1 Release Candidate (build 141.564) that you can now download and try.
With several bug-fixes, this version also brings two new features. First, Puppet integration functionality now includes Puppet environments by defining a separate module path for each environment and automatically synchronizing with the git branch of the current environment. Second, there’s a new inspection that warns youif the new variable name is already in use as you apply the Rename refactoring. Take a look at the release notes or read what’s Coming In RubyMine for a fuller list of the RC features.
Please note that since this is a release candidate build, there is no patch-update from the previous EAP version. The release candidate build also requires an active license, meaning you need to start a 30-day trial period to try this build if you don’t have an active RubyMine license.
The release is around the corner, so your feedback is very much appreciated in these last stages when we are focused on ensuring product stability. Please add any issues to our tracker. Thanks!
We’ve spent the last few weeks testing, fixing and polishing all the new features of the upcoming release. While some minor issues remain, Satsuki now feels like it’s ready to go Beta. So starting today RubyMine 7.1 Beta is available to download and try!
Please note that you may get an exception when using Rails 4 with the latest byebug version. We’re working on that but for the moment please add the following require parameter to your gemfile as a workaround:
The debugger now works with the recently released Ruby 2.2.1 (RUBY-16389)
The full list of fixes is available as well. Please use “Check for Updates…” to download and install the update as a patch to previous EAP version. Note also that you may need to restart the IDE manually, if it doesn’t restart automatically after the update.