Public SourceMage Discussion List

[Juuso Alasuutari <iuso AT sourcemage.org>]

On Sunday 16 April 2006 23:57, seth AT swoolley.homeip.net wrote:
> On Sun, Apr 16, 2006 at 11:51:38PM +0300, Juuso Alasuutari wrote:
<clip>
> > 3) The first query (config_query VAR1 yadayada...) is presented. The ui
> > that does this can be anything basically)
>
> Why not expose all queries at once since you've got that info at this
> point?
>
<clip>
> > 5) Now the next prompt is presented, "next" meaning "the one following
> > the prompt which sets VAR1"
>
> see my response to 3.  Instead of going to the next prompt, you redisplay
> the options to expose new changes until they decide they are done.

You're right, that would be nicer of course. In fact I had something like 
this 
in mind, I was visualizing a dialog type of menu. For this example though I 
just used how it works now. And if/when the abstraction layer is implemented, 
we could of course have the original one-question-at-a-time ui as an option, 
too.

> > And so it goes on, until all prompts have been answered. The same happens
> > with DEPENDS, and of course you can also later return to CONFIGURE after
> > you've left it.
>
> DEPENDS is more complicated.  Go for CONFIGURE first, see how well it works
> and then look at DEPENDS (which will need a bit more thinking).
>
> > Of course this kind of system means that you would have to strictly
> > restrict user interaction to specific spell files (almost done already),
> > and allow no other scripting in them. At the moment I believe PREPARE is
> > allowed to have both, so it couldn't be sourced multiple times like this.
>
> Yes, we need stronger policies and checks in place to make this realistic.

I'm glad I've understood some of the issues here. So, do you have any 
suggestions how we could further the goal and prepare the ground? As I said, 
I feel a roadmap would be good. (Keeping in mind of course the priorities of 
things with such a small crew that we have.)

Juuso