Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I'm designing a website that has a constant CLI and optional GUI's for every functionality. What i'm basically doing is an automated form generated for each parameter and a description.

I'm also indicating with a red asterisk the required parameters.

It works pretty much like this:
cmd is a generic command. visual is a command that makes the form for the command:

visual cmd

Then it makes something like this: Sample

That's all i have, can you point me to improvements on this subject?

My goal: The system is mainly for the cli, so i want to drive users to it. This autoform thing should be a transition/helper, what else should i add?

share|improve this question
    
What is the problem you're trying to solve? Right now your question doesn't sound constructive. –  dnbrv Mar 9 '12 at 23:41
    
What am i missing? The visual mode is for beginners. –  alfa64 Mar 10 '12 at 0:27
3  
"What else should I add?" and "Can you point me to improvements on this subject?" are very vague questions. It's unclear what the workflow is and whether users stumble in it somehow. –  dnbrv Mar 10 '12 at 0:37

1 Answer 1

It seems to me that CLI systems have been doing similar things for years: 1) help (cmd) and 2) (cmd) /?

have both been used in OS like DOS and VMS. Asking (presumably novice) users to learn a new command to get help seems counter-intuitive. While not as pretty as your solution, those systems have been effective in providing help.

Unless your command line interface is significantly more complex than what you have presented, perhaps you have a solution in search of a problem.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.