Hi Karen,
We can easily implement the same functionality as the current GUI
with AI. (Though, perhaps I'm confused in such a thought though.) So the
presentation format can still be what ever we'd like. I think the system
requirements for AI are quite low but should certainly be less than the
GUI.
I think the ability to tap AI's functionality to select what is
installed would be very beneficial to someone using the text installer for
a system with minimal resources, for one example of how AI's power could
be beneficial.
I'm not sure if hooks would or would not be needed but it would
seem that one less interaction would keep things simpler.
Thank you,
Clay
On Thu, 14 May 2009, Karen Tung wrote:
> Clay Baenziger wrote:
>> Since AI is a very rich feature set and provides for our current level of
>> server and install customization, could the text installer be a front end
>> to creating a manifest for an AI install (which could then just be kicked
>> off and reported up through the text installer)? This would prevent needing
>> to add more hooks into libtransfer, etc. for yet another presentation
>> format?
>> Thank you,
>> Clay
>>
> Creating a text-based front end for creating an AI manifest for install is a
> drastically different presentation format
> feature set and have different system requirements compared to the current
> GUI installer. Why is it better for
> the target users of the text installer? Why do you think that more hooks are
> needed into
> libtransfer in order for the text installer to create a similar install
> experience to the GUI installer?
>
> --Karen
>
