Re: New class diagram and use case

On Tuesday 03 February 2004 21:36, Nicholas D. Wolfwood wrote:
> On Tue, 2004-02-03 at 12:09, Nathaniel McCallum wrote:
> > The backend doesn't actually do anything until all options have been
> > chosen.  ALL installation activity waits until AFTER the user would
> > click "finish" (just an example).  Nothing should be done until the user
> > has made all choices.  Once the user has made all choices, it will pass
> > the xml file to the backend and perform the whole installation.  This is
> > really the desireable operation.
>
> And as esammer already pointed out, this allows for reuse of the backend
> in both attended and unattended installs.  So, the interactivity is in
> the frontend, the backend's responsibility is to perform an install
> based on an install profile (what to do), and an arch profile (how to do
> it), the frontend just gets an install profile together for the backend
> to use, and optionally gathers status information from the backend as it
> performs the install.

All I ask is for the backend to have a mode designed in that would allow the 
feeding of the install profile incrementally. That would mean that one could 
feed the backend an incomplete install profile and it would do what it could 
based on that. Also take into account that this install profile will not 
necessarilly contain all stages.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: [email protected]
Homepage: http://www.devrieze.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAIAribKx5DBjWFdsRAqGAAJ98ZeufWAwOCuWdDkdIvAr9jiykiwCg2AOy
Oa6LmFnT4E5J8PoeIUCE6B0=
=s6YC
-----END PGP SIGNATURE-----