Differences between revisions 37 and 38
Revision 37 as of 2006-08-12 20:41:47
Size: 2824
Editor: ?DavideViti
Comment:
Revision 38 as of 2006-09-25 08:58:40
Size: 3337
Editor: ?fiandro
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
See also open [http://bugs.debian.org/cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb]. A complete list of bugs affecting the g-i can be found in the [http://bugs.debian.org/cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb] page.
Line 9: Line 9:
= Issues = = Per-architecture issues =
Line 11: Line 11:
The main issues left are: We're trying to schematize bugs affecting the g-i on a per-architecture base, architectures considered here are i386, PPC, AMD64 .

== i386 specific ==
 * No known bugs affecting i386 is known ATM :)

== AMD64 specific ==
Line 13: Line 18:
 * inventory of which powerpc systems are supported and which are not; some could maybe be supported with special boot options or rootskel scripts; rootskel scripts could also be udes to disable the gtk frontend for non-compatible systems
 * endianness color issue for powerpc
Line 16: Line 19:
== Other issues ==
 * Option in the main menu to exit to a shell does not work ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339855 #339855]).
== PPC specific ==
PPC showed to be the most problematic architecture of the three to support because DirectFrameBuffer seems particulary willing to crash on those machines.
 
 * Right now HW acceleration provided by DFB seems to be broken for almost every suported video chipset, so it was forced off by default for every architecture.
The situation is folowing (DFB 0.9.25 unaccelerated)
 
 Known good : radeonfb, vesafb (or whatever x86 uses).
  Known bad : atyfb, nvidiafb

 * An endianness color [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341770 issue] for powerpc was experienced some times ago with DFB 0.9.22, but it seems it was fixed in 0.9.25

Introduction

Overview of open issues and things to be done for the ["DebianInstaller/GUI"].

A complete list of bugs affecting the g-i can be found in the [http://bugs.debian.org/cdebconf-gtk-udeb bug reports against cdebconf-gtk-udeb] page.

?TableOfContents([2])

Per-architecture issues

We're trying to schematize bugs affecting the g-i on a per-architecture base, architectures considered here are i386, PPC, AMD64 .

i386 specific

  • No known bugs affecting i386 is known ATM :)

AMD64 specific

PPC specific

PPC showed to be the most problematic architecture of the three to support because ?DirectFrameBuffer seems particulary willing to crash on those machines.

  • Right now HW acceleration provided by DFB seems to be broken for almost every suported video chipset, so it was forced off by default for every architecture.

The situation is folowing (DFB 0.9.25 unaccelerated)

TODO

Porting

The graphical version of the installer is currently available for Intel x86, AMD64 and PowerPC. The PowerPC port [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341597 needs work] to get different types of system correctly supported. Other architectures the graphical installer could be ported to include Sparc, Alpha and HPPA.

Fonts

For font information, please see ["DebianInstaller/GUIFonts"]

Usability

  • Screen resolution.
    • Currently fixed at 800x600. Should be made flexible (adapt to resolution set by system or user).
    • Interface should adapt itself so that text blocks are never too wide for optimal readability.
  • Improve accessability (for the visually handicapped). One way to do this is to [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339735 support different themes] (color schemes). (Note: should not lead to a major increase in initrd size.)

  • Progress bar in separate window.
  • Alternative (graphical) ways to start a shell or browse log files.
  • Interface design.
  • Create custom plug-ins for cdebconf to improve handling of some dialogs and make optimal use of possibilities offered by the graphical environment.

Interface design

Most of the work on the graphical side has been done by Eduardo Silva. He has set up a [http://www.geocities.com/jobezone/d-i_gtk.html webpage] with images he designed and some comments about possible future changes.

Reduce size of initrds

The initrds are currently very large which also results in fairly high memory requirements to run the graphical installer. Size has thus far not been a major concern, our focus has been on getting things working.

Options to reduce initrd size.

  • Library reduction for graphical libraries.
  • Remove unused files from udebs.
  • Reduction of space used by fonts (see above).

Update The size of the initrds is now down to around 10MB. Further reduction would be nice, but it is no longer a major issue.