From: "Darius Blaszijk" <[EMAIL PROTECTED]>

I suggest you take a look here: http://wiki.lazarus.freepascal.org/index.php/GUI_design. Although it needs some cleanup and reordering and a lot of adding to, it is a good start.

OK.

I have learned over time that picking just some interface guide is simply not sufficient. It depends on the widgetset how the form will showup. So implementing a look and feel should work for all widgets, unless we implement some mechanism that will enable a look per widget.

I think the main problem is font sizes in different widgetsets. It can be solved by implementing UI scaling depending on current screen/font DPI.
UI guidelines will consider 96 dpi of the screen.
Does UI scaling work in Lazarus?

But before we go there there's a bunch of other more important stuff to do. For instance, there are still a lot of forms that are hardcoded (see at the bottom of the wikipage) we need to do them first. Second step is redoing some of the forms that are just too crowded.

Yes. That's why I am talking of UI guidelines now. Such guidelines are needed for forms to lfm conversion and redesigning pages.

- Images on regular buttons (OK, Cancel, etc)
That's subject to taste. But generally cosidered all "standard" icons are equiped with a glyph to make the form more intuitive.

At least it need to be configurable - disable/enable images on buttons.

- Different size of buttons. They must be the same size, except some special cases where caption is long.
I think this is not good practice. How do you decide when the caption is too > long seing the captions are translated too.

I can say based on my experience only small number of buttons need to be wider due to translated text size. I always use 75x23 px buttons if possible. 75x23 buttons is default in all MS programs.

Yury Sidorov.

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to