Hi, I finished Ruby Option Settings redesign (this task I received from A.
Nebuzelsky and Trung).
Please, the implementation should be finished ASAP.
putting also Martin to cc..
Unfortunately, the options area is one which wasn't implemented yet. For Ruby we're going to have pretty
much all the same options that are there in Java. In particular, we need a way to edit hints, occurrences
highlighting, formatting and indentation preferences, etc.
Hi, what it exactly means?
I designed the Ruby settings according to particular ruby settings implemented
in the current Miscellaneous. If you need more settings, we have 2 ways:
* we are doing redesign of languages (JSP, HTML, etc.) They have to be
move into Editor secction
* if you have more settings which you need implement in Miscellaneous, I can
help you to improve current spec for your needs. But I have to know what you
exactly need to have in options.
We will need pretty much all the same editor settings as those available for Java. In other words, lots of formatting options (whitespace handling, indentation
options, method sorting options, etc), options for which hints should be enabled/disabled and whether they apply to the whole file and selected line only,
mark occurrences options, etc.
It's true that these are not implemented yet. I was about to implement them based on the Java settings when I saw the new spec, so now I'm holding off to see
what the Java module does so that the two are consistent in NB 6.
Oops, I did not notice there are separate issues for individual options tabs. I just committed a change to combine ruby
installation and ruby debug options. Commit log is in issue 106376.
I will keep this open to track the changes in ruby editor settings.
Hi, I don't have more information about Ruby options still. I have only information which are collected in the UI spec.
Because we must to have some UI imagination how the settings have to look, I'm finishing UI spec according to my
Ruby Installation and Ruby Debugger will be joining into the one tab with name "Ruby". When the Ruby team will need more
options, please check all settings with me, discuss are with me and I'm sure, we can find some solution how to place it
into the Ruby panel.
Now please, continue according to the UI spec, Ruby panel.
Thank you for cooperation
"I don't have more information about Ruby options still":
I said (two description entries earlier): "We will need pretty much all the same editor settings as those available for Java. In other words, lots of formatting
options (whitespace handling, indentation options, method sorting options, etc), options for which hints should be enabled/disabled and whether they apply
to the whole file and selected line only, mark occurrences options, etc."
We're aiming for feature parity. While one or two options may differ, overall we need the same approach. If there is a Java category, there should be a Ruby
category. If the Java language is in a Language combo box on a number of panels, the Ruby language should too. And so on.
it's perfect. I think is good approach to add Ruby next to Java. If it means, in the Miscellaneous we will not have more
setting then now, it's perfect. If not, that is problem. So I suggest to solve this problem "per-partes". I finalized
the UI for Ruby Installer and Debugger. If you need more settings there, let me know and we can find some good solution.
Have a nice time
I'll also redesign Ruby Debugging part a little. Since there is not auto-detection of "rdebug-ide executable". So the
user does not need to search it manually it anymore. Also "Verbose" mode is little dangerous. Will be possibly removed
(the checkbox). Actually we might get rid of Ruby Debugging part at all, might be. Since it really depends on the chosen
interpreter. Now with fixed issue #103974 and automatic switching from slow to the fast debugger, Ruby Debugger options
might be removed....? Have to thing about it tomorrow.
I would let you know about any changes.
"Since there is *not* auto-detection of..." should be "Since there is *now* auto-detection of..."
I've changed the Ruby Debugger options panel. There is no need for the textfield for ruby-debug-ide executable anymore.
It is auto-detected. Also I've added "Install Fast Debugger" button into the panel. Still leaving choice to use slow
debugger if the user wants. I'll commit tomorrow if nobody is against. Thanks for possible comments. Attaching screenshots.
Created attachment 43981 [details]
Created attachment 43982 [details]
Committed Ruby Debugger Options Panel simplification/enhancements.
new revision: 1.16; previous revision: 1.15
new revision: 1.2; previous revision: 1.1
new revision: 1.36; previous revision: 1.35
new revision: 1.2; previous revision: 1.1
new revision: 1.9; previous revision: 1.8
new revision: 1.11; previous revision: 1.10
new revision: 1.22; previous revision: 1.21
new revision: 1.18; previous revision: 1.17
Reassigning this issue to newly created 'ruby' component.
A couple of more options for Ruby I think we will need:
(*) Prefer parentheses
( ) Prefer spaces
This option will initially be used for code completion (see issue 108966) to decide whether to surround the arglist with spaces or parentheses, but should
probably also be considered as a "formatting option" such that when you reformat code (as opposed to reindent code; I hope we plan to make a UI
distinction about this not only for Ruby but for Java as well) we insert/remove parens as necessary.
A second option:
[x] Continue comments on new lines
This option will automatically insert "# " when you press return at the end of a line comment. (Ruby doesn't have block comments so this is useful for
typing longer comment sections).
Both behaviors are currently controlled by -J-Dfoo=true flags.
Debugger and Ruby Platforms options went somewhere else. Not sure if everything were done in editing area, reassigning.
Might be to-be-closed.
Can you please evaluate whether this issue has been fixed?
The editing area still needs to be redesigned according to the new UI spec:
However, the implementation is pretty much on the editor team side, so I am closing this as a duplicate of issue 137318,
which addresses the new options.
*** This issue has been marked as a duplicate of 137318 ***