Frans Pop wrote:
On Sunday 04 December 2005 23:19, Attilio Fiandrotti wrote:ATM GTK frontend's widh/height are burned-in at compile time, but it should be able to read those parameters from the external world at runtimeCan the frontend not query the framebuffer and ask it what resolution it was started in and use that as the window size?
ATM cdebconf is used for the g-i only that, indeed, uses various framebuffer flavours, but notice that depending directly from FB could prevent future use of cdebconf togheter with X (most of the GTK FE developement was made using X, only final testing and packaging is done using DFB). I would prefer something that doesn't tie the GTK frontend so strictly to the framebuffer.
(global variables? a special couple of cdebconf-gtk/window_width cdebconf-gtk/window_height questions that areset up after boot?)No, let's not bother the user with that.
i was meaning something that is setup at boot time automatically basing on FB parameters: can this be done?
This may be nice especially for those PPC machines that have fixed framebuffer resolution at boot time (like wolfram'spower mac that has fixed 1024x768 resolution).Same for Sparc.A default fallback window size should be provided if the option is not specified.IMO default window size should be equal to FB resolution.Except maybe if we're going to use a smaller window size to avoid getting text lines that are too long for readability (the rest of the display should probably have a nice background in that case).
again, i would suggest not to tie the gTGK frontend to framebuffer too tightly.
ciao Attilio