1 |
On Tuesday 03 February 2004 21:09, Nathaniel McCallum wrote: |
2 |
|
3 |
> The backend doesn't actually do anything until all options have been |
4 |
> chosen. ALL installation activity waits until AFTER the user would |
5 |
> click "finish" (just an example). Nothing should be done until the user |
6 |
> has made all choices. Once the user has made all choices, it will pass |
7 |
> the xml file to the backend and perform the whole installation. This is |
8 |
> really the desireable operation. |
9 |
|
10 |
Why? Many people would want to be able to do parts of the installation |
11 |
manually while doing others automatically. As some parts cannot be performed |
12 |
out of order this means that if we want to support such a hands-on mode for |
13 |
the installer, we need to allow partial scripts to be executed. |
14 |
|
15 |
Basically what I want to say is that controlling the processing time etc. |
16 |
should be the business of the frontend. One could add a "verification" stage |
17 |
in the backend which would mean that the backend would first verify the whole |
18 |
file for correctness. This would basically function as a buffer for the |
19 |
execution engine. |
20 |
|
21 |
Paul |
22 |
|
23 |
ps. Further I am not convinced why in all cases execution needs to be |
24 |
performed only after the user clicked finish. |
25 |
|
26 |
pps. Note that I don't want to say that execution must happen immediately. I |
27 |
want to say that if we don't design it into the backend from the start, we |
28 |
probably would end up with a kludge that would need to be fixed later |
29 |
(incurring possibly a full redesign) |
30 |
|
31 |
ppps. designing in just includes thinking how it fits into the architecture |
32 |
and keeping a place (where it can be added later), it does not mean that |
33 |
everything needs to be in place allready. |
34 |
|
35 |
-- |
36 |
Paul de Vrieze |
37 |
Gentoo Developer |
38 |
Mail: pauldv@g.o |
39 |
Homepage: http://www.devrieze.net |