Duncan Mac-Vicar P. wrote: > ... > I think the ideal situation is something in the middle. For example, my > modified yast2-qt basically uses the minimum space possible, which is > also not the answer, however the wizard looks much nicer in small > (better said, enough) size. May be some better algorithm which does not > use the screen size, but basically the minimal space needed plus some > buffer so it does not look really packed. Just wanted to start a > discussion on this "taste".
What might be a problem is that the smallest size might change while you run the module, for instance, by switching from tab to tab, or from tree entry to another one. Would you like to recalculate and resize window while running a module? Because if you don't the first dialog might be just to small and the second one might not fit into the window space. On the other hand, resizing doesn't look professional and it would be nasty to resize a Wizard (Back/Next/Finish) with, e.g., four different steps where you can go back and forth. Moreover, the way Qt does it is similar to ncurses (well, ncurses you the whole screen but this is because the much you have there, the better for you). All in all, the default size is a solution for the issues mentioned above, maybe not perfect but a solution. Bye Lukas
signature.asc
Description: OpenPGP digital signature
