-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lukas Ocilka wrote: > 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.
You may not find any application in the world that has this problem, why? Yes, that is YaST specific problem, where those 2 widgets get the content replaced, instead of all the content being there, and see what you are supposed to see, then the sizes would be correctly calculated. In this case, DumbTab is not only dumb, but dumb with influece :-). Something to think on how to improve. Improving that would also solve the case we talked about dialogs loaded from xml files. Then you could actually describe all pages for the tab widget in the same file. Same goes for wizard. While it is a real issue, I wonder if yast2-gtk would resize the topmost dialog or not. Michael? > 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. No, there is no application in the world that will resize the main window while clicking in it. Just forget that example. > 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). For ncurses it is a valid case, because either you are in a terminal which can't show more than one application at the same time, or you are in a graphic console, for which it is the same case. However, assuming that in X11 mode you are the only application is not always true, and using 70% of the screen space is basically using a lot, but still not leaving space for other windows, so it is even worse as fullscreen. > All in all, the default size is a solution for the issues mentioned > above, maybe not perfect but a solution. I don't think a global design solution is just valid because it serves as a workaround for one specific issue. Duncan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkj+MTgACgkQzR62qWZ+QtFj6gCgt1gYv/C+Na/imQ83WrnX2RuH TWIAoIaARDtHhnw1ylJD45SHupikGFyu =4Vnm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
