Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Netbook Friendly

(1/7) > >>

dmoore:
I picked up a eee pc yesterday. nice piece of kit for the money. First thing  I did was put an eee derivative of ubuntu (eeebuntu) and installed C::B from source. C++ compiling obviously isn't a netbook strong suit, but it gets the job done eventually.

most things worked without a hitch, except netbooks suffer from a reduced screen resolution on a small screen (1024*600, 10inch). Quite a few of the dialogs are too big for the screen and toolbars create a lot of clutter. It's easy enough to work around the too big dialog's with compiz moveable windows shortcuts, but it would be nicer if things fit on screen

Here's a list of issues
* Environment Settings dialog: ThreadSearch settings form makes the overall dialog too tall
* Editor Settings dialog too tall: General settings (could probably redistribute some of these items to other panes), CodeCompletion, wxSmith, and maybe IncrementalSearch
* Build Option Dialog, Compiler and Debugger Settings: too tall, not sure of cause
* CodeCompletion toolbar very wide and not sizeable.

thomas:
I have the opposite problem. :)

Working on a 24'' display, it annoys me greatly that the dialogs are too small. Whenever I access compiler options, I have to scroll down the list (and you can't even use the mouse wheel for that!) for the sole reason that the dialog uses only a third of the available screen height (of which less than half is used for the option list).

Maybe we should invent something like a "large mode" and "small mode" of operation, which adjusts the default sizes to reasonable sizes (for example assuming a screen height of 600 for "small", 768 for "normal", and 1200 (or 1050) for "large").

dmoore:
yes, I agree. no point not using the screen real estate if it's there.

dmoore:
the challenge is coming up with a system that doesn't burden C::B and plugin devs

Ceniza:
The only idea I come up with is to organize everything in virtual tabs. You classify a bunch of widgets enough for a small screen into a virtual tab. You use as many of those as you need to fit everything you want to show. For a small screen, each virtual tab maps to a real tab. If the screen is slightly bigger, you can show two of those virtual tabs per real tab. The bigger the screen, the more virtual tabs you can map to real ones. With a big screen you would expect to have no tabs at all, only a big window with everything in it.

My 2 euro cents.

Navigation

[0] Message Index

[#] Next page