2 Replies Last post: Feb 21, 2013 3:11 PM by Anna Bulenkova  
Kedar Mhaswade Novice 112 posts since
Jun 29, 2008
Currently Being Moderated

Feb 16, 2013 7:33 AM

Reloading capabilities should be built in?

I am trying my hands with a classical Sinatra application. Sinatra does not reload the classes by default and their documentation suggests that one should use rerun gem. I am using it and I think it works all right although I see some output like this in the Console:

 

Fast Debugger (ruby-debug-ide 0.4.17.beta16, ruby-debug-base19x 0.11.30.pre11) listens on 127.0.0.1:49290

 

18:27:47 [rerun] Resume-ranker launched

Fast Debugger (ruby-debug-ide 0.4.17.beta16, ruby-debug-base19x 0.11.30.pre11) listens on 127.0.0.1:45555

stty: standard input: Invalid argument

stty: standard input: Invalid argument

Fast Debugger (ruby-debug-ide 0.4.17.beta16, ruby-debug-base19x 0.11.30.pre11) listens on 127.0.0.1:38011

== Sinatra/1.3.4 has taken the stage on 2131 for development with backup from Thin

 

My suggestion here is that this is fine without the IDE. With RM however, shouldn't I expect a setting that does this for me by default, i.e. when a source file is changed in a Sinatra app, IDE reloads the affected classes (or in worst class restarts the app, like rerun gem does, because true code reloading is hard to achieve). Is there such a setting? If not, should I file an RFE?

 

PS -- I have read: http://devnet.jetbrains.com/message/5320329

 

Regards,

Kedar

Anna Bulenkova JetBrains 4 posts since
Nov 3, 2011
Currently Being Moderated
Feb 21, 2013 3:11 PM in response to: Kedar Mhaswade
Re: Reloading capabilities should be built in?

Kedar, using sinatra-reloader gem can be considered as a workaround.

More Like This

  • Retrieving data ...