This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
|Summary:||Intuitive & Simpler Gem installation|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description arungupta 2008-08-14 17:07:36 UTC
The current Gem manager takes a while to load the entire list of gems. A gem installer typically knows the name of the gem and so providing an interface to "jruby -S gem install <GEM_NAME>" would be really helpful.
Comment 1 Martin Krauskopf 2008-08-15 10:59:43 UTC
Thanks for filing. If you have idea how such UI should look like, it will be welcomed. I'll come with something what comes to my mind otherwise ;)
Comment 2 arungupta 2008-08-15 16:52:20 UTC
One option could be: - Gem Manager shows all the installed gems by default - Loads all the Available gems if they are in cache - If the Available gems are not in cache, shows two buttons "Load Gems" and "Load a Gem" - "Load Gems" button should possibly show a warning "It may take a while ..."
Comment 3 Martin Krauskopf 2008-08-15 17:19:07 UTC
Thanks, but I do not see how the points are related to this issue. > - Gem Manager shows all the installed gems by default Sure, will do this, but this is slightly different issue. > - Loads all the Available gems if they are in cache This is done now. > - If the Available gems are not in cache, shows two buttons "Load Gems" and "Load a Gem" If remote gems are not cached yet, they will be automatically fetched on the background and the user will see kind of: <Please wait, fetching remote gems....> in "New Gems" tab (currently the user see the progress bar which might be enough in the end). So no need to care about any buttons. > - "Load Gems" button should possibly show a warning "It may take a while ..." ? There is already "Reload Gems" button. Anyway, this issue is about how to provide UI for `gem install <GEM_NAME>` when remote gems are not loaded yet and user knows the <GEM_NAME>. Once they are loaded, user will just choose in the list of gems and press install. This might be solved by some kind of "Quick Installation" text-field. Or actually, if we come with Terminal Emulator then it is solved automatically.
Comment 4 arungupta 2008-08-15 17:25:23 UTC
I explained the Gem Manager flow where "gem install <GEM_NAME>" is included. Instead of using terminal emulator, I think it should still be invoked from Gem Manager only. This will keep gem management at one place together.
Comment 5 roamy 2009-03-04 18:09:56 UTC
ONe of the promising aspects of Netbeans is it attracts programmers just starting out - obviously like myself. Probably the worst experience so far has been Gems with netbeans 6.5 and 6.7 I have no clue whatsoever of how to update the gems as it just keeps complaining about repositories or paths This is quite disturbing. In addition if someone is just starting out they may as well go with 6.7 > ruby 1.9 and rails 2.3 if you don't you will be starting all over in a few months So netbeans should be very easy to configure thanks
Comment 6 Erno Mononen 2009-03-05 08:30:17 UTC
Hi roamy, thanks for the feedback. I can't promise to do much improvements in this area for 6.7, but will definitely keep this on the radar any try to make the experience smoother.