1 |
Dan Armak wrote: |
2 |
> Do screen definitions live in the arch templates, so that a FE only knows |
3 |
> about individual UI elements? |
4 |
|
5 |
Probably and most likely, yes. |
6 |
|
7 |
> If so, how do are the screens described in a |
8 |
> FE-independant way? |
9 |
|
10 |
As XML which the arch templates are. Think of something similar to the |
11 |
way glade works for gtk, but much more generic. |
12 |
|
13 |
> Or does a FE know what each screen looks like? |
14 |
|
15 |
It has to since it has to be displayed. |
16 |
|
17 |
The view glue and implementation information is obviously absent from |
18 |
the class diagram. That is not a mistake. It's just that the view code / |
19 |
system will, most likely, be the most complex part of the installer. If |
20 |
we didn't have to worry about multiple UIs, multiple archs, changing |
21 |
steps and stages, and generics, we'd be on better ground, but that would |
22 |
be directly against our design goals. :) |
23 |
|
24 |
-- |
25 |
Eric Sammer |
26 |
Gentoo Linux |
27 |
http://www.gentoo.org |