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: | provide posibility of user input | ||
---|---|---|---|
Product: | ruby | Reporter: | Tomas Danek <musilt2> |
Component: | Code | Assignee: | Torbjorn Norbye <tor> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Tomas Danek
2006-12-18 15:39:49 UTC
Fixed in build 196. It's a bit suboptimal; the input is entered through a text field at the bottom of the output window. This is unfortunately how input is done in the NetBeans output window - it's identical to the way it's done for Java. Currently, I've enabled input for project execution (ruby on main file) and file execution (ruby on editor file). I've not done it for rdoc, rails, or rake. Do you think it's likely that a Rakefile would require user input? > Do you think it's likely that a Rakefile would require user input?
When using for main purpose - in the Ant way; probably not. But could be used
for whatever, like ad hoc administration interactive scripts and is just
internal Ruby DSL, so you can use Ruby as you want. E.g. artifical:
task :get_a_lib do |t|
printf "Enter password: "
password = $stdin.gets
# connecting with #{password}...
end
Probably would be nice to have but I would leave it until there are some actual
users wanting it.
> Probably would be nice to have but I would leave it until there are some
actual users wanting it.
Agreed. My motivation for this was that a lot of people are new to ruby (like
me:-)) and they just want to try it, so they go through with some ruby
tutorials, and almost all tutorials have a chapter that uses input like this.
for now, i consider as
verified in #196
Reassigning this issue to newly created 'ruby' component. Changing target milestone of all resolved Ruby issues from TBD to 6.0 Beta 1 build. |