Ruby projects (and especially Rails projects) rely heavily on the use of the ruby core libraries and installed gems.
However Netbeans hides these away and makes it very hard to work with these files.
I have already requested the ability to search in these files ( issue #130366 ).
I believe however these need to be handled as first class citizens in the IDE. I would like to see a node in the project
tree for gems and core on each project. (names are examples only, chosen any appropriate names you like).
Selecting the "core" node shows the ruby core libraries.
Selecting the "gems" node shows ruby gems the user has selected as wanting to show for this project.
- This will probably require a dialog allowing users to select what gems + versions to show.
- Need to support the Rails infrastructer (new in 2.1 I think) for access plugins as gems.
- perhaps based on analysis of projects "requires" statements detect used gems (perhaps at runtime/debug detect the
gems that are accessed and included them).
Both of these new nodes can be "hidden" and only shown when a option in the project is selected.
I'm not sure on the impact this should have interms of the gems tests etc.. I would imagine these should still be kept
separate from the projects tests.
I can't express enough how frustrating it is developing Rails apps and having to "vendorise*" stuff to allow useful
searching and access to the code.
*vendorise is the process of extracting Rails code and gems into the vendor subdirectory of a Rails project.
I have worked around this to a certain degree by creating NetBeans projects in the gems directory of specifc gems, but
this is a little clunky.
issue #130366 (Add ability to search ruby core and gems)
use the favorites Window (ctrl+3) to navigate to the gems/library you want to edit/view.
If the one of the files for the gem is already open (say from a debugging session) then use the command "Navigate Select
in Favorites (ctrl+shift+3)" to navigate to the file in the favorites window.
Nice idea. I'll start with something like Platform node and might be file few other separate issue.
(6.5 is feature frozen, TM -> Future)