Ben Alex schrieb:
Sebastian Werner wrote:
That's exactly the problem. Currently Tabs will be aligned according
their auto width. You can't change the content or width while
layouting them. You must do this before you do, but this require to
know the width of each tab before and then shrink it
Sebastian Werner wrote:
That's exactly the problem. Currently Tabs will be aligned according
their auto width. You can't change the content or width while
layouting them. You must do this before you do, but this require to
know the width of each tab before and then shrink it as long as
allowed
please search the archive of this mailing list.
some days ago we discussed this. search for appearance.
you can also have a look at my patch against the tree demo i sended
yesterday to this list
Olli
Yue schrieb:
Hi
Thanks for the new release of qooxdoo. Great job!
A question concerning t
Ben Alex schrieb:
Sebastian Werner wrote:
In our opinion the most times dialogs which needs this should simply
be structured in a better way. Scrolling in Tabs or even multiline
tabs are not really usable in my opinion.
However I hope we could add the scroll feature sometimes, as this is
IMH
Sebastian Werner wrote:
In our opinion the most times dialogs which needs this should simply
be structured in a better way. Scrolling in Tabs or even multiline
tabs are not really usable in my opinion.
However I hope we could add the scroll feature sometimes, as this is
IMHO the best fallback
Hej Sebastian!
> just some more comments regarding QxSplitPane:
>
> * The constructor parameter "vContinousLayout" seems to be unused.
> * Could you also add a QxHorizontalSplitPane and QxVerticalSplitPane?
Of course. Good idea. But isn't it really a property instead?
> * I really don't like
Hej Kent,
just some more comments regarding QxSplitPane:
* The constructor parameter "vContinousLayout" seems to be unused.
* Could you also add a QxHorizontalSplitPane and QxVerticalSplitPane?
* I really don't like to define the first and second widget inside the
constructor, as this require t
Kent Olsson schrieb:
Hej!
First of all it looks quite good.
Thanks!
Just a few comments:
* Please remove the "splitpane" color value. We could add this later as
qooxdoo support more of these values.
Do you want it to be hard coded in the theme.js?
yes, this would be identical to the t
Ben Alex schrieb:
Sebastian Werner wrote:
As this looks very well already, and we have released the 0.5 of
qooxdoo, I could imagine to develop this splitpane in the real qooxdoo
widgets folder (Which includes a CVS access, but also means that you
could not change all of the core without discus
Hej!
> First of all it looks quite good.
Thanks!
> Just a few comments:
>
> * Please remove the "splitpane" color value. We could add this later as
> qooxdoo support more of these values.
Do you want it to be hard coded in the theme.js?
> * Please don't use width/height = 100% in the appeara
Hej!
> Thanks for the contribution. Unfortunately I cannot get it to work. I
> receive:
>
> Exception ``Invalid color:splitpane'' thrown from function
> anonymous(vEvent=Object:{6}, vEnableDispose=boolean:true) in
> line
> 19. [e] message = [string] "Invalid color:splitpane"
Oh sorry! I fo
Sebastian Werner wrote:
As this looks very well already, and we have released the 0.5 of
qooxdoo, I could imagine to develop this splitpane in the real qooxdoo
widgets folder (Which includes a CVS access, but also means that you
could not change all of the core without discuss the matter with u
12 matches
Mail list logo
