I've included a test jelly script.  You can test it normally using
Windows, etc. but currently the only easy way to test the console
version of things is to have Linux or something and run it on non-X mode
like runlevel 3 or something.

I would like to integrate an override switch for forced-console mode,
however...I'll look into that tomorrow first thing.

Also, I'd like to take a second and mention a couple of features I
forgot about until now:

- Option on the property-sheet to store results to file.
- Option to provide autofill.properties for automation of otherwise
interactive executions, so that default values are automatically used
instead of prompting and waiting forever.

Anyway, here's the test script that I used...see what you think.

Regards,
John



On Thu, 2002-07-18 at 17:46, St�phane MOR wrote:
> John Casey wrote:
> 
> >I submitted this once before to the maven-dev list, since I saw more
> >Jelly traffic on that than on commons-dev, but here goes again...
> >
> Hi John !
> 
> Last time you posted that, you forgot the sources ! :-)
> As I started something identical that on my side, I simply finished it 
> and put it in
> the org.apache.commons.jelly.interaction package.
> 
> >I'm attaching the source code for an interaction tag library, that will
> >prompt the user for input and save the result to a variable...
> >
> By now, there is only an AskTag that asks the user a question, and sets 
> the value
> to a variable (like yours), which is the basic thing that I would expect 
> from an Interaction thing !
> 
> >Additional features include:
> >
> >- input types: text, password, boolean, numeric text, and drop-down list
> >(comma-separated default value supplied)
> >
> I like those ideas, the password is something that we could need, and 
> the boolean value
> is essential in interactive scripts.
> I thought about a ChoiceTag, which must be the same as you drop-down 
> list, even if
> I can't see how my console would show me that drop-down list ...
> 
> >- auto-detection of GUI-enabled JVM's; console display for otherwise
> >
> Cool !
> If my JVM is GUI-enabled and if I don't want any GUI, do I have a way to
> disable it somehow ?
> 
> >- solid domain object model backing tags, to promote extensibility and
> >reimplementation into Ant task
> >
> hmmm, I need more infos there, I should find that in the sources :-)
> 
> >The source files here are [mostly] well-documented.  I'm posting them
> >here with the hope that they will be integrated into the Jelly project,
> >so that I can maintain them as a standard part of the Jelly tool.
> >
> I'd love to help you to integrate that, as I feel that it's something 
> that can be very
> valuable.
> 
> Cheers,
> St�phane
> 
> ___________________________________________________________
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
> Yahoo! Mail : http://fr.mail.yahoo.comm
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 

<?xml version="1.0"?>

<j:jelly xmlns:j="jelly:core" 
        xmlns:i="jelly:org.apache.commons.jelly.tags.interact.InteractTagLibrary"
        xmlns:a="jelly:ant">
  
  start

  <i:property-sheet>
    <i:property key="pull_cvs" prompt="Pull new source files from CVS" 
type='boolean'/>
    <i:property key="phase" prompt="Build phase" type='drop-down' 
defaultValue='one,two,three' />
    <i:property key="retries" prompt="Maximum retries" type='numeric' defaultValue='3' 
/>
    <i:property key="config_file" prompt="Path of config file" type='text' />
    <i:property key="password" prompt="Web server password" type='password' />
  </i:property-sheet>
  
  Pulling from CVS? ${pull_cvs}
  Build Phase: ${phase}
  Maximum Retries: ${retries}
  Using Config File: ${config_file}
  Using Password: ${password}
  
  end
  
  <a:echo message="done..."/>

</j:jelly>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to