When will IntelliJ get RubyMine4 changes?

I was wondering when the ruby plugin for IntelliJ will get the RubyMine4 changes?  If it does will you guys provide what extras you get for using RubyMine instead of IntelliJ with the plugin?

Thanks,
Jay

0
20 comments

The new Ruby plugin will likely be released together with the IntelliJ IDEA 11.1 release.

0
Avatar
Permanently deleted user

Thanks Dmitry, what is the release date for 11.1?

Will this be added to the 11.1 release notes?

Thanks,
Jay

0

IntelliJ IDEA 11.1 will be released in late Q1/early Q2 2012.

The Ruby plugin is not considered a feature of IntelliJ IDEA, so its updates are not promoted as part of IntelliJ IDEA release notes.

0
Avatar
Permanently deleted user

Okay thanks!

0
Avatar
Permanently deleted user

This is considerably awkward.

People who bought RubyMine are getting a better experience - by far - than the people who bought the full IntelliJ IDEA.  If you use the plugin with 11 you're pretty well screwed.

Context highlighting:  N/A
Code formatting:        forget it
Code navigation:        Occasionally, but don't count on it

Please have a care not to throw your loyal users under the bus as you explore new opportunities in other markets.

Slightly run-over,
Jason

0
Avatar
Permanently deleted user

Not sure what you mean by "Please have a care not to throw your loyal users under the bus as you explore new opportunities in other markets." maybe that is just your signature.  Either way I was just wondering for my own curiosity.  I have both RubyMine4 and IntelliJ11 so I will be using RubyMine4 for all my Ruby Development but we have some users that have IntelliJ that do some occasional ruby development and its always good to know that there is still support there.

0

I'm not sure what you mean by that. The plugin available for IntelliJ IDEA 11 supports all features of RubyMine 3.2, which certainly include code formatting and highlighting.

0
Avatar
Permanently deleted user

"This is considerably awkward."

No it's not. And for a presumed developer to make a statement like that is absurd.

The "big" plugins that JetBrains develops for their other product lines often make use of IDE features that aren't present in IntelliJ yet. Emphasis on the "yet". As JetBrains updates IntelliJ the newer versions of the plugins migrate in as well.

You seem to want them to develop for IntelliJ first then disseminate to the specialized IDEs. When, by definition, the people most interested in Ruby, PHP and Python will be focused on those languages and will own the specialized IDEs. It makes logical sense to focus plugin development in the environments tailored to them.

Yet JetBrains still brings the plugins up to date in IntelliJ and not a year later, but some months later.

Cut them some slack, they're doing a damn fine job.

0
Avatar
Permanently deleted user

++ on that.  I like everything Jetbrains produces.

0
Avatar
Permanently deleted user

I'm new to the JetBrains line. Is that generally how IntelliJ is updated, by folding in new features from the other more specialized IDEs? Is IntelliJ, for the most part, a superset of the functionality of the other editors (minues AppCode)?

For example, there's some Coffeescript support in IntelliJ through the plugin, but it seems there's more in RubyMine and/or Webstorm. Should I expect that that functionality might get folded into 11.1?

0

All of JetBrains IDEs are built from a single source tree. All the CoffeeScript features available in RubyMine 4 are also available in current IntelliJ IDEA 11.1 EAP builds and will be available in the final release.

0
Avatar
Permanently deleted user

Got it. Thanks for the quick reply. ;)

0
Avatar
Permanently deleted user

"Should I expect that that functionality might get folded into 11.1?"

That's how they've been working it. They've never published any guarantees I've seen that say they absolutely will continue down that path. That said, it makes sense for them to take that approach.

In general the "specialized" IDEs are pushing things faster for the "main" IntelliJ IDE. JetBrains has been adding features, making architectural changes to the IDE framework in the sub-projects and the corresponding language plugins tend to rely on those changes. So you don't immediately get the plugins pushed "upwards" to IntelliJ. JetBrains has been folding the IDE framework improvements back into IntelliJ at the next IntelliJ release. At that point they release the language plugins for IntelliJ.

That implies however that the language support in IntelliJ for Ruby, Python and PHP will always trail the sub-project IDEs. I personally don't see a problem with that but others obviously do.

0
Avatar
Permanently deleted user

No, it really isn't.  Have you used the available plugin?  The description does not list 11 support, and it's a good thing too, because it doesn't work.

I have downgraded to 10.5 and everything seems to work great.  I don't  remember if I had to pay to upgrade to 11 from 10.5, but if I did then I'm wishing I had waited for 11.1.

Given that it 1) doesn't work, and 2) isn't advertised to work, a reasonable person would assume that it isn't supported.  If that's not true then I apologize for misconstruing the situation, but I have had this sort of experience with a number of companies and it makes me nervous to even think that JetBrains may go that route.  Hence my comment.

I have one open bug relating to my experience, and I probably owe you three  more. Unfortunately I haven't had the time to track down which stack  traces are associated with what actions.

0
Avatar
Permanently deleted user

Charles,
I do a lot of usability work, so I'm trained to complain the way an end user would (or maybe it's vice versa, I can't rightly say anymore).

I understand what you're saying, and I accept that "developers think this way".  I reject the idea that they are right.  Why?  Because customers don't behave as if this were true.  And since my salary, your salary, and their salary comes ultimately from those customers, the developers are frankly wrong.  We have been trying to shape the world to reflect how we wish it to be by pretending it were so.  Being the change, as Ghandi said.  However, we've been doing this for the entire recorded history of computing, and it hasn't worked so far.  Maybe it wasn't meant to be.

You know, like waterfall, big up-front design, or accurate estimates.

0
Avatar
Permanently deleted user

This is good to hear.  It gives me confidence that, while there may occasionally be little gaps like this, that IDEA will still be a good investment.  Thanks for the followup.

0

Which exactly version of IntelliJ IDEA and the Ruby plugin are you using? The plugin version 4.0.20111206 is fully compatible with IntelliJ IDEA 11.0 and subsequent 11.0.x updates. I'm not sure what you mean by "isn't advertised" but it is marked as compatible in the plugin manager.

If you're getting any exceptions with this version of the plugin and a release build of IntelliJ IDEA 11, please file issues in the issue tracker: http://youtrack.jetbrains.net/

0
Avatar
Permanently deleted user

A bit of a PEBCAK there.  I read the plugin description page to say that it supported previous versions, rather than taking the subheading to be a reference to legacy support.  So some of my concerns were based on a misread.

I'm using 11.0.1 with jruby 1.6.6.  Shared project .idea directory.  Most of my coworkers only use RubyMine, not IDEA, and the project files were all generated with RM 4.0.  Except for workspace.xml, which is private (SVN ignore)

  • *.rb files do not have the ruby icon on them
  • the editor unsuprisingly doesn't handle Ruby syntax, completion, or most navigation.
  • I can't open the configuration editor for any Rails configurations:  http://youtrack.jetbrains.com/issue/RUBY-10297
0
Avatar
Permanently deleted user

Well, one person does.

For myself, I think it mattered because the releases were so close.  If I'd bought IDEA in August for instance, would I care that it's missing a feature that came out in February the next year?  Probably not.  Or at least not as much.  But I bought IDEA when 11.0.1 went live, which was about the time my coworkers started using RM 4.0 EAP, and only 6 weeks before RM 4.0 shipped.

0

Please make sure that the .rb extension is mapped to the Ruby file type in Settings | File Types.

0

Please sign in to leave a comment.