David Crossley a écrit :
Johannes Schaefer wrote:
...
Somebody typing just 'forrest' does not know how it is
used. She would maybe expect some help or even better:
an interactive guide to getting started with forrest.
Yes that is a better place for the interactive target I described. So
options would be things like:
site - build a forrest site in the current directory
run - run forrest in dynamic mode in the current directory
seed - create a simple starter site in the current directory
seed-sample - create a sample site...
seed-business - create a simple site template for a business
available-plugins - list all the plugins available for Forrest
Should add default values to go faster (just type enter key) :
(Based on properties to be able to change them...)
If the guide was intelligent, options would be like:
$forrest
"This directory does not contain a forrest project.
You can:
0 . Get more help on options (forrest project-help)
[1]. Seed an example project with content (forrest seed or seed-sample)
2 . Seed a project skeleton (forrest seed-basic)
3 . Seed a business example (forrest seed-business)
4 . ...
Your choice: _ ([1] Default)"
$forrest
"This directory contains a forrest project.
You can:
0 . Get more help on options (forrest project-help)
[1]. Start forrest in live mode (forrest run)
2 . Create a static site (forrest site)
3 . Create a webapp to deplay in tomcat (forrest webapp)
4 . ...
Your choice: _ ([1] Default)"
But then, this looks like a wizard ;-)
Command-line wizards can be useful too.
Of course - always separate "GUI" and behaviours.
Amicalement,
Cyriaque,
-David
Doing this will hekp users learn/remember the targets available and does
not prevent them from running any of the targets directly, i.e. "forrest
seed", "forrest run", "forrest site"
Ross
Johannes
