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.

Bug 139609 - Using parameters with Rake runner is cumbersome
Summary: Using parameters with Rake runner is cumbersome
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Rake (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-10 16:14 UTC by Erno Mononen
Modified: 2011-01-28 20:12 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erno Mononen 2008-07-10 16:14:43 UTC
Consider for example db:fixtures:load FIXTURES=my_fixtures. To run it with the rake task runner, you need to either 
type in the params first or type in the whole task name, making it a bit cumbersome to use.
Comment 1 Martin Krauskopf 2008-07-10 20:06:27 UTC
I don't understand. You do not need to type the whole task name. Just type e.g. 'load', select the task (if it is not
the first match), then type your parameters and press Enter. Selected task is used.
I'm welcomed to any ideas for enhancements.
Comment 2 Erno Mononen 2008-07-11 07:59:01 UTC
Well I guess I was confused about how it works since the task name that gets run is not filled in the filter field, 
which is what I think should happen when the focus is lost from the filter field (i.e. when tabbing to the param field).
Comment 3 Erno Mononen 2008-07-11 08:09:18 UTC
On a second thought, maybe the current behaviour is better than filling in the filter field. Just that there is 
something counterintuitive in the UI for me, probably specifying params above the actual task for those params below 
the param field.
Comment 4 Martin Krauskopf 2008-07-11 08:20:31 UTC
Yes, it would not behave well if the filter field was fulfilled with full task name on filter field's focus lost, since
it would apply the filter and this would change the list of task to just one list - all on focus lost. That would be
strange.

What about to provide read-only field on the bottom which would show what is going to be invoked, like

Command: [rake db:fixtures:load FIXTURES=my_fixtures                               ]

Might be 'Command' is not the best choice. Any ideas?
Comment 5 Erno Mononen 2008-07-11 09:10:47 UTC
Hmm, just noticed that I reopened this which I didn't mean to. Changing to an enhancement. The read-only field would 
probably help, not sure about 'Command' either, but can't think of anything better now. 
Comment 6 Martin Krauskopf 2008-07-11 17:40:41 UTC
With recent changes this might not be such a big issue. I'm leaving it opened in the case there are more people
confused. If you have any idea for improvements they are welcomed.