Kent Olsson schrieb:
Ah! But if you, as you have most times, a form created by QxGridLayout.
Can you do the same. I tried but I had some problems with the children.
I appreciate your answers...
In a QxGridLayout you can define the column alignment for example. I am
quite sure that there are some example (Grid_Layout_*) in our CVS
showing this.
Sebastian
Kent
On Wed, 2006-01-04 at 13:41 +0100, Sebastian Werner wrote:
Kent Olsson schrieb:
Hej Sebastian!
Either you misunderstood what I wrote or you were to fast to answer. I
will explain what I meant.
a statusbar is just a "horizotanlBoxLayout" IMHO. So it is just a
setVerticalChildrenAlignment("middle") IMHO.
No extra information! This statement does not help. I was commenting on
this because I am a lazy programmer and user and I think we all should
be. The less we need to do of reinvention or reiteration the better. My
concern was to avoid doing this setVertical on all labels in for example
a form. It is pretty much of a job and a lot to parse. Instead you
suggest we should do it on all text items in the form. "It is not just
a...", at least not for me. I can not see that we have a discussion
here, but you are the bozz....
you need not to setVerticalAlignment on each QxLabel. You just need to
define "verticalChildrenAlignment" for the horizontalBoxLayout. This is
just one line in the constructor of a possible QxStatusBar (which
inherits ideally from QxHorizontalBoxLayout).
We could discuss here. I have no problem with this. But I don't like
things which do to many things implicit somewhere in the code because
some guy found this reasonable some time ago.
2. Layout problems. If minor changes of the general layout mechanism is
done, no extra code in separate widgets will be necessary. Look in
previous e-mail with the title "Percentage relative location of
widgets..."
a minor change? In the layout stuff their exist no "minor" things.
A little bit nicer, please.
3. Border problems with a QxWindow. the borders from the statusbar and
the window demarcate each other. There must be some change to the border
rendering, such that the borders of the two widgets float together. Do
you have any ideas of how to do that Sebastian? As I can see it, changes
are needed in both the border class as well as in the window class.
Do we really need stuff like this? Why not just define the border for
just one widget.
I think you have misunderstood what I meant. I have a problem when
ridges between widgets occur where I do not want them. If par of a side
of a border shall have a 3D effect but part of it shall not have it,
there will be a "ridge". Where the borders of these two ridges touch
each other, it does not look very nice. I would prefer a flat surface.
I just don't understand what you mean. Probably an example could help
and a screen shot how it looks currently and how it should look in your
opinion.
For the best of Qooxdoo....
Well we will hope so.
Sebastian
Kent
4. I have some other minor problem with the looks, but I see them as
possible to solve.
The following will come later:
1. listeners
2. broadcasting
3. some other smaller changes...
Does anyone have a solution for the above problems?
Kent
Sebastian
------------------------------------------------------------------------
qooxdoo: The new era of web interface development | DEVELOPMENT BRANCH
[Go to: Public
<javascript:void(window.location.href=window.location.href.replace(/\/source\//,
'\/public\/'))>] [Go to: Developer Examples
<http://www.perevotech.com/qooxdoo/source/test/developer/Index.html>]
clearhideshowdispose
QxInit
003471: qooxdoo/0.2_beta-3
003490: datestamp/20051230
QxApplication[HASHCODE:0]
053420: Loading Data: 53419ms
053447: Available Classes: 152
053452: Client Detection: gecko 1.7.12
053686: Initialize Application: 240ms
053691: Created Instances: 81
054384: Executing User Application: 693ms
054411: Preloading Images: 23ms
055087: Created Instances: 261
055091: Initialize Interface: 549ms
055863: Postloading Images: 34ms
Testing StatusBar implementation.
The elements of the status bar will be created on the first open of the
QxStatusBar.
3:21:16 PM
Test of status bar
File
Edit
Ready
3:21:16 PM
New
Open
Save as..
Close
Exit
Undo
Redo
Cut
Copy
Paste
Delete
Select all
Preferences
------------------------------------------------------------------------
Testing StatusBar implementation.
The elements of the status bar will be created on the first open of the
QxStatusBar.
------------------------------------------------------------------------
qooxdoo: The new era of web interface development | DEVELOPMENT BRANCH
[Go to: Public
<javascript:void(window.location.href=window.location.href.replace(/\/source\//,
'\/public\/'))>] [Go to: Developer Examples
<http://www.perevotech.com/qooxdoo/source/test/developer/Index.html>]
clearhideshowdispose
QxInit
003468: qooxdoo/0.2_beta-3
003494: datestamp/20051230
QxApplication[HASHCODE:0]
052489: Loading Data: 52489ms
052534: Available Classes: 151
052538: Client Detection: gecko 1.7.12
052772: Initialize Application: 239ms
052777: Created Instances: 81
052835: Executing User Application: 59ms
052841: Preloading Images: 2ms
053100: Created Instances: 97
053105: Initialize Interface: 160ms
053593: Postloading Images: 27ms
Testing StatusBar implementation.
The elements of the status bar will be created on the first open of the
QxStatusBar.
12:55:09 PM
Ready
12:55:09 PM
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
