| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Tuesday 03 February 2004 05:13, Eric Sammer wrote: |
| 5 |
> |
| 6 |
> Aha. I see now. No, all action is delayed until all decision making is |
| 7 |
> complete. This is for two reasons (one intended, one a nice side |
| 8 |
> effect): 1. The front end is acting as just a special kind of install |
| 9 |
> profile editor of sorts so teh backend is really the automated |
| 10 |
> deployment part with some of the features missing. This makes for very |
| 11 |
> good reuse of design / code. 2. Users like to experiment and a "Back" |
| 12 |
> button is a nice comfort to newer users. Blowing away their partition |
| 13 |
> table prior to all decisions being made might upset some folks. |
| 14 |
|
| 15 |
One could offer an option to force the actions to be done. It would be |
| 16 |
needed when users perform manual actions (but not in all cases). Of |
| 17 |
course forcing actions will disable the back button so probably warrants |
| 18 |
a warning. |
| 19 |
|
| 20 |
> |
| 21 |
> > Just the same as most installers work, instead of how the GLIS |
| 22 |
> > frontend and backend works. |
| 23 |
> |
| 24 |
> Actually, as far as I know, most installers delay destructive actions |
| 25 |
> even if they *say* they don't. Of course, I haven't looked at the code |
| 26 |
> for any of these products recently, but it seems logical that if you |
| 27 |
> performed a destructive operation such as altering a partition table |
| 28 |
> *and* you provided a back button... well, I just don't know how you'd |
| 29 |
> make that work in a reasonable, predictable, and safe fashion. |
| 30 |
> |
| 31 |
> > With the frontend that Scott Hadfield and I jointly |
| 32 |
> > wrote for GLIS, the frontend creates the config file which gets |
| 33 |
> > passed to the backend when the config is done. That is not |
| 34 |
> > real-time. |
| 35 |
> |
| 36 |
> Right. This will function in a similar manner. I think this is a |
| 37 |
> better design than firing off each part piecemeal. |
| 38 |
|
| 39 |
It is the task of the frontend to either save up the actions or to send |
| 40 |
them to the backend immediately. As long as the backend can perform |
| 41 |
actions as soon as they are received (incomplete xml file) the backend |
| 42 |
can handle whatever you want. |
| 43 |
|
| 44 |
Paul |
| 45 |
|
| 46 |
- -- |
| 47 |
Paul de Vrieze |
| 48 |
Gentoo Developer |
| 49 |
Mail: pauldv@g.o |
| 50 |
Homepage: http://www.devrieze.net |
| 51 |
-----BEGIN PGP SIGNATURE----- |
| 52 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 53 |
|
| 54 |
iD8DBQFAH3ZvbKx5DBjWFdsRAoWcAJ4xW6dh9D4w6in+flp0ws5nPkg5QwCgtQaS |
| 55 |
DZopM4VszYS5hGYQiKX4acQ= |
| 56 |
=Dn/z |
| 57 |
-----END PGP SIGNATURE----- |
| 58 |
|
| 59 |
-- |
| 60 |
gentoo-installer@g.o mailing list |
Archives