Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Netbook Friendly
Biplab:
--- Quote from: MortenMacFly on February 20, 2009, 09:23:09 pm ---
--- Quote from: jens on February 20, 2009, 07:12:49 pm ---I just tested it with the wxAui-branch and it works more or less out of the box.
--- End quote ---
Nice work Jens! Looks very good to me. How mature is wxScrollingDialog? Is it a (Julian Smart) 3rd Party addon or even already within a wx branch?
--- End quote ---
I believe it's already inside wx branch in the form of wxScrolledWindow. Follow this url for more details.
--- Quote ---http://docs.wxwidgets.org/stable/wx_wxscrolledwindow.html
--- End quote ---
Jenna:
--- Quote from: Biplab on February 21, 2009, 03:28:06 am ---
--- Quote from: MortenMacFly on February 20, 2009, 09:23:09 pm ---
--- Quote from: jens on February 20, 2009, 07:12:49 pm ---I just tested it with the wxAui-branch and it works more or less out of the box.
--- End quote ---
Nice work Jens! Looks very good to me. How mature is wxScrollingDialog? Is it a (Julian Smart) 3rd Party addon or even already within a wx branch?
--- End quote ---
I believe it's already inside wx branch in the form of wxScrolledWindow. Follow this url for more details.
--- Quote ---http://docs.wxwidgets.org/stable/wx_wxscrolledwindow.html
--- End quote ---
--- End quote ---
No,
But wxScrollingDialog uses wxScrolledWindow.
wxScrollingDialog is a convenience class that makes it easy to use standard dialogs with wxScrolledWindow, without having to change them all manually or to care about the screens size.
I include the readme.txt comimg with wxScrollingDialog, that describes how it works:
--- Quote ---wxScrollingDialog
=======================================
This class turns your existing wxWidgets dialogs into scrolling dialogs,
when there isn't enough space to show all of the dialog at once. The standard
buttons remain on the screen at all times. This is especially useful for
devices such as the Eee PC which have a small screen.
To use, just derive from wxScrollingDialog. If you have dialog buttons that do
not have the standard identifiers (such as wxID_OK, wxID_CANCEL and wxID_APPLY)
then call AddButtonId multiple times with the identifiers of the buttons to be
left unscrolled.
The class works by searching first for a wxStdDialogButtonSizer, then a horizontal
wxBoxSizer containing standard buttons, and then individual standard buttons.
These sizers and/or buttons are removed from the existing sizer hierarchy and
added to the bottom of the dialog, while the rest of the hierarchy is attached
to a new wxScrolledWindow. The dialog is then laid out again, and if the dialog
is too big for the display, the scrollbars are enabled and the dialog resized to
fit the display.
In most situations, the layout will be similar to the original dialog. However,
if you wish to disable the layout changes, you can call SetAdaptationLevel with
0 before calling Show or ShowModal. You might want to do this, for example,
if you know in advance that the display is large enough.
For further discussion about adaptation to the Eee PC screen, see
http://wxwidgets.blogspot.com/2007/12/programming-for-eee-pc-with-wxwidgets.html
Julian Smart, December 2008
--- End quote ---
Ceniza:
--- Quote from: dmoore on February 20, 2009, 10:02:33 pm ---certainly a decent workaround. my only fear is that Thomas will now demand 2400x1600 dialogs. :D
more seriously, I'd still like to see a prototype of ceniza's proposal as well.
--- End quote ---
I also have a 24" screen, and it is true small dialogs do not make much sense. A 2400x1600 dialog would be nice if we could fit it in the so limited 1920x1200 resolution of a 24" screen :P
For the prototype, at least a decision about screen distribution would be necessary. The algorithm should be given the screen resolution, size of virtual tab (should be the same for all of them, or just calculate the longest width and height) and number of virtual tabs. It should try to distribute them with an aspect ratio close to the screen's, and leaving as few empty spaces as possible. A constraint would be, of course, to group into tabs when no more columns/rows can be added.
Another issue to discuss can be best described by quoting a Pink Floyd's song:
--- Quote ---"What shall we use to fill the empty spaces?"
--- End quote ---
dmoore:
jens: patch file?
Jenna:
--- Quote from: dmoore on February 22, 2009, 09:52:54 pm ---jens: patch file?
--- End quote ---
I patched an old wxAui-branch.
That means I have to patch the actual trunk to create a patch.
Hopefully this evening/night (it's 10pm here) or tomorrow.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version