From: DongInn Kim [mailto:[EMAIL PROTECTED]
Sent: Thu 08/06/2006 10:48
To: Bernard Li
Cc: oscar-devel@lists.sourceforge.net
Subject: Re: [Oscar-devel] OSCAR Wizard step buttons
Bernard Li wrote:
> Hi DongInn:
>
> Just some
quick comments:
>
>
>> I understand what we
figured out at the above old SF ticket but I am
>> still uncomfortable
with this situation that a user can click on any
>> step buttons
regardless of the order at the first
>> installation of
OSCAR.
>> I think it is fine for a user to re-run/re-click any step
buttons once
>> an oscar_wizard is gone through and I think this is
good.
>> However, the first installation should not allow a user to
click any
>> step buttons randomly. I know that we have already setup
the wizard to
>> throw an error when a user clicks on a step button in
a wrong order. A
>> user can do the right thing then but this is not
quite acceptable.
>>
>
> I think
the hard part here is how can you exactly determine that the
> user has
gone through the whole process?
>
Off the top of my head,
why don't we have a flag to save what step a
user has gone through in a plain
text file or in ODA?
I think saving this kind of data to ODA is not a problem
for me.
So, I would save the flag information to the following table when a
step
is successfully done.
Wizard_status
==========
0 :
Null
1 : Null
2 : Null
3 :
Off
4 : Off
5 : Off
6 :
Off
7 : Off
8 : Off
So, if a user clicks on the
step 3 button and it is done successfully,
then we update the table
"Wizard_status" something like the above table
to set "Off" to "On" where id
is 3. And then we can activate the step 4
button which is the next
step.
Since now we know what status is done by querying the above table,
we
can figure out when each step should be turned on or off at the
first
installation. If all the status or 3~8 status are "On", all the
step
buttons are activated then.
BTW, I think we can do this flag
stuff in a plain text too but I prefer
ODA though
;-)
Regards,
>
>> So, I am wondering if it
is too difficult to activate or
>> deactivate the
>> step
buttons at the GUI side?
>> If not, can we deactivate all the step
buttons which are not
>> ready for a
>> user to click on at
the first installation?
>> Of course, once the wizard is gone through,
all the step
>> buttons should
>> be
activated.
>>
>> What do you think of
this?
>>
>
> It's a good idea - I
think some parts of the code already protects the
> user from doing steps
out of order (eg. you cannot define clients
> without images built) but
some parts do not (eg. you can bring up Setup
> Networking from the
getgo).
>
> If you can implement something quick for each step to
"sanity check" the
> environment before continuing and/or disable some
buttons, that should
> be sufficient for now. However, this is up to
the release manager to
> decide whether this feature should go in 5.0 or
5.1.
>
> Cheers,
>
> Bernard
>
-
DongInn
_______________________________________________ Oscar-devel mailing list Oscar-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-devel
