Hi,
if I need access to the DOM document element, does it make any
difference whether I refer to the global Javascript variable "document"
or call getTopLevelWidget().getDocumentElement() from a qooxdoo widget?
Thanks, Ralf
---
Hi,
it is possible to show a confirmtion message before leaving a page by
returning a string in Application#close(). Reportedly, this confirmation
dialog is shown twice under certain circumstances in IE. I found some
forum postings about IE sending the onbeforeunload event twice that are
probably
Hi Andreas,
Andreas Ecker wrote:
>> it is possible to show a confirmtion message before leaving a page by
>> returning a string in Application#close(). Reportedly, this confirmation
>> dialog is shown twice under certain circumstances in IE. I found some
>> forum postings about IE sending the onbe
Hi,
when I set a user-defined text/background color to a widget, and reset
the color using e.g. setBackgroundColor( null ), the themed color value
is not reinstalled. Using resetBackgroundColor() works as expected.
Is this method of resetting by setting to null generally discouraged?
From my
Hi Fabian,
thanks for your fast response.
Fabian Jakobs schrieb:
> setting explicitly to null means "don't use any color". This is treated
> as an user value and takes precedence over init and themed values.
> Calling reset means "clear user value". Once the user value is resetted
> either th
Hi again,
I just noticed that the line
decoration: "underline"
in our font theme stopped working. The decoration is not rendered
anymore. Are their any changes to the syntax?
Thanks, Ralf
-
This SF.net email is sponso
Hi,
I added a listener on the "changeTabIndex" event on a
HorizontalBoxLayout. This stopped working with qx 0.7. It seems that
there is no "changeTabIndex" event anymore. Is there any other way to be
notified when the "tabIndex" property changes on a widget?
Thanks in advance,
Ralf
--
Hi,
we currently have a problem with widgets that have a tabIndex of -1 set
(see http://bugzilla.qooxdoo.org/show_bug.cgi?id=495).
As the doc doesn't tell anything about the meaning of -1 anymore, I
wonder whether this is still the recommended method of excluding a
widget from the tab order? Or
Fabian Jakobs schrieb:
> I have updated the API doc for tabIndex with this information.
>
> Best Fabian
Ok, thanks! I just wanted to make sure that we use your API properly ;-)
Ralf
-
This SF.net email is sponsored by D
Hi,
I need to create an appearance theme where a number of widgets are
grayed out when disabled, no matter if a custom color is set or not.
This is the behavior of most widgets on Windows. In qooxdoo, however,
user values generally override theme values.
I have a workaround that works for most
Hi,
it's sometimes useful to reset user data in order to get rid of unused
object references. I currently use code like this:
Widget#setUserData( key, undefined )
However, I'm not sure whether this is the correct practice and I'm
somehow missing a method like
MUserData#resetUserData( St
Hi,
the ComboBox shows a strange behavior when editable. I just filed a bug
on this (http://bugzilla.qooxdoo.org/show_bug.cgi?id=555). The
ComboBoxEx in the demo works as expected.
Although the features of the simple ComboBox seem suitable for my needs,
I wonder, whether the use of the Combo
Hi,
I didn't get many responses here in the last time but I keep on trying ;-)
We currently have several problems with pooled Atom widgets, that still
display stale contents after recycling. It seems that all of these
problems go back to the same pattern, as described in bug 567 [1]:
var at
Hi,
I have a problem running the skeleton using the current qx trunk. I
checked out the latest trunk version from SVN, copied the skeleton to a
separate location, set the correct path in the Makefile, called "make
clean" and "make". The script always stops with the same error:
[...]
raise
Hi Tobias,
Tobias Koller (GERMO GmbH) schrieb:
> Could you post the content of your Application.js?
> Maybe we can see the error ;)
It's the original Application.js file from
qooxdoo/frontend/application/skeleton/source/class/custom/
does this work for you with the current trunk?
Ralf
--
between
> our versions.
>
> Tobias
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ralf Sternberg
> Gesendet: Dienstag, 23. Oktober 2007 16:20
> An: qooxdoo-devel@lists.sourceforge.net
> Betreff
Hi,
just checking out the current qx trunk and find that qx.core.Target is
missing although it still exists in the "current" apiviewer. Where is it
gone? What to do with custom classes derived from Target?
Thanks,
Ralf
-
Thanks for your quick response Hugh,
that explains it. Seems the qx API becomes simpler...
Ralf
Hugh Gibson wrote:
>> just checking out the current qx trunk and find that qx.core.Target
>> is missing although it still exists in the "current" apiviewer. Where
>> is it gone? What to do with custo
Hi,
I just wonder whether there is a "close" event in qx.ui.window.Window? I
cannot find it in the API viewer (even with "Inherited" checked) but I
don't get a warning either when I add an event listener to it (which I do
get for any other invalid event string). It also seems to be never fired.
Is
plementation from within your own
> implementation.
>
> I'm pretty sure there are even more ways to do it..
>
> cheers,
> Lothar
>
>
> On Jan 28, 2008 10:08 AM, Ralf Sternberg <[EMAIL PROTECTED]>
> wrote:
>
>> Hi,
>>
>> I just wonder w
Hi,
will there be some kind of generic support for color gradients in qx 0.8?
I don't even know if this is possible in Javascript without scaling
background images, I'm just curious...
Thanks, Ralf
-
This SF.net email is sp
Hi folks,
is there a chance to keep the browser from processing the Escape key?
By default, browsers interrupt a currently running request when Escape
is pressed. We have a case where Escape triggers a request, when Escape
is pressed twice (for whatever reason), the second key press stops the
Hi Fabian,
Fabian Jakobs wrote:
>> By default, browsers interrupt a currently running request when Escape
>> is pressed. We have a case where Escape triggers a request, when Escape
>> is pressed twice (for whatever reason), the second key press stops the
>> request that the first one issued. An
Hi Fabian,
RAP provides infrastructure that allows switching themes at runtime.
It's not yet API though, as theme-switching caused problems with earlier
qooxdoo versions. However some people asked for it on the RAP newsgroup
and I think there are some people actually do switch themes at runtime
Hi Fabian,
RAP provides infrastructure that allows switching themes at runtime.
It's not yet API though, as theme-switching caused problems with earlier
qooxdoo versions. However some people asked for it on the RAP newsgroup
and I think there are some people actually do switch themes at runtime.
I
Hi Fabian,
Fabian Jakobs wrote:
> I'll give you a small example. Take the "backgroundColor" property. You
> can define a symbolic color in a theme - lets call it "focus". If you
> set the background color using:
>
> this.setBackgroundColor("focus");
>
> Three things happen:
>
> 1. check wheth
Hi,
I build a qooxdoo javascript file using the generator and get this js
error while loading this file:
qx.core.Property is undefined
}}}var
allowed=config.group?qx.core.Prop...roupKeys:qx.core.Property.$$allowedKeys;
It appears that this error occures in a function named "__validatePrope
Hi Thomas,
thron7 wrote:
> Try deleting your cache and re-run the build.
thanks for your help. Unfortunately, the problem is still the same after
deleting the cache and re-building. Tried with latest trunk.
Ralf
-
Sponsor
Hi,
I'm new to qooxdoo and have a problem regarding the concept of themes
and appearances:
When properties of a control like colors or borders are being set
manually (e.g. using "setColor()"), the "state" function of the
appearance can reset those properties whenever a state change occurs.
For
Hi Sebastian,
> The problem is that we need to support multiple values for each
> properties. Then we could add some fallback logic to do something like
> user-value -> appearance-value -> default-value -> null
Yes, that would solve the problem. Then, manually set properties would
always supe
Hi,
setting the property "enabled" on a qx.ui.treefullcontrol.Tree doesn't
change the widget's behavior - the widget and all of its items are still
enabled. I am not sure whether this is a feature or a bug. Anyway, what
is the best way to completely disable a Tree widget? Is there a "grayed
ou
Hi,
I'm trying to add or delete menu items (e.g. qx.ui.menu.Button) to/from
a qx.ui.menu.Menu while the menu is currently seeable. Unfortunately,
the width of the menu is not updated. As a result, if one of the added
menu items is larger than the existing menu, the menu appears with its
old w
Hi Werner,
Sebastian Werner schrieb:
> I am sorry, but I don't think this is possible with the current
> versions. I even don't know of any work-around. I just spend some
> minutes again to find some hack, but nothing useful found.
Thanks for taking the time. Does this mean that there's no way
Hi Sebastian,
(sorry I mixed up your first and last name in the last post)
Sebastian Werner schrieb:
> I think the problem begins when the menu is initially layouted. After
> this point, if seeable or not, the menu is not updateable anymore.
thanks for your quick answer. I filed a bug so the is
Hi,
I get a JavaScript error after removing a currently selected TreeFolder
item from a Tree (using the qx.ui.treefullcontrol classes). After the
selected item has been removed, there is no item selected anymore. The
error occurs when another item is selected thereafter:
qx.manager.selectio
Hi Alex,
Alex Back schrieb:
> your problem can be solved if you first deselect the item you want to remove.
>
> To explain the current behaviour:
> If you select an item after you removed the currently selected one, qooxdoo
> adds two jobs to the state queue:
> * remove the state "selecte
Hi Derrell,
[EMAIL PROTECTED] schrieb:
> Ralf, would you please try the following. I don't have the time to test it
> right now, but on visual inspection it seems like this should work. If it
> works, I'll add it to the distribution...
>
> In the file
>
> frontend/framework/source/class/qx/u
[EMAIL PROTECTED] schrieb:
> It's now checked in to both trunk and legacy_0_6_x. I decided that even
> though it's a new feature, I'd add it to the legacy code because it's easier
> than continuing to answer questions about this problem. :-)
Thank you. Well, in a way, being able to remove tree it
Hi,
when multiple qx windows are open, clicking on a deactivated window
activates it, i.e. brings it to front and sets the active appearance
state. However, when clicking on a qx.ui.treefullcontrol.Tree inside a
deactivated window, the activation does not work. It appears that Tree
and TreeFolder
Hi,
I use a HorizontalBoxLayout with some Labels in it like this:
++
| +--+ +-+ +---+ |
| | "Hello " | | "cruel" | | " World!" | |
| +--+ +-+ +---+ |
++
The leading and
guess there are ways to work around that. For example, if the CSS
property "display" is set to "inline", the whitespace is not swallowed.
Ralf
> Ralf Sternberg schrieb:
>> Hi,
>>
>> I use a Horiz
Sebastian Werner schrieb:
>> Do you say that my expectation was true and the text size calculation
>> fails for strings with leading or trailing whitespace?
>
> It does not fail. But it does it wrong :)
Ah, I see. That's different. But don't you think that qx could replace
leading/trailing spac
Hi Sebastian,
Sebastian Werner schrieb:
>> Ah, I see. That's different. But don't you think that qx could replace
>> leading/trailing spaces with , then?
>
> Maybe. But it will slow down labels which don't rely on this feature,
> too. Maybe we can have a property for this or even a separate cl
Hi,
I noticed that calling setAppearance on a Label resets its wrap property
although the appearance theme contains no definition of this property.
Example code:
label.setWrap( false );
label.debug( "_ wrap before: " + label.getWrap() );
label.setAppearance( "link-ref" );
label.
Hi Alex,
Alex Back schrieb:
> calling setAppearance() resets those properties to its defaultValue which are
> defined in the original appearance but not in the new appearance.
> Let me explain this mechanism with your label example.
>
> The original "label"-appearance in the Classic appearance
Hi Alex,
thanks a lot for your detailed explanations!
Alex Back schrieb:
>> First, there is also an appearance "label" in our appearance theme, that
>> sets "wrap" to false in the "initial" part. This does not explain why
>> wrap is set to true - or am I again missing something?
> The defaultValu
Hi,
is there a way keep a certain window always on top? Z-index doesn't seem
to do this, as the z-index of windows is dynamically modified by qooxdoo
on window activation.
Thanks,
Ralf
-
Take Surveys. Earn Cash. Influe
Hi,
I experience a redraw problem with the scrollbars of a CanvasLayout in
Firefox.
The overflow property of the CanvasLayout is set to "scroll".
Inside the CanvasLayout is another CanvasLayout with a size greater than
the scrolled layout. So far, the scrollbars appear correctly.
When the size
7;s nearly impossible to scan *all* scrollbar related bugs in this
endless list :-(
Do you know of any workaround to update the scrollbars, maybe some
operation that has the same effect as moving the window?
Thanks,
Ralf
> Ralf Sternberg schrieb:
>> Hi,
>>
>> I experie
Hi,
I didn't notice that this thread continues ...
Alex Beck:
> currently there is no solution out-of-the-box available.
> How has to look the API in your case? Should this "on-top" property be
> application-wide or do you need another/finer control?
Application wide suffices. In SWT, which i
Hi Jim,
Jim Hunter schrieb:
> I think you are confusing an Always-On-Top and Modal.
Indeed, there are two different concepts that should not be confused:
*modality* is about blocking other windows, *always-on-top* is about the
highest z-index.
I think we should take existing window managers as
Jim Hunter schrieb:
> You are contradicting yourself. You state that AOT windows are always on
> top, yet you state that a modal window, like a File Dialog would be on
> top when it was created so it can't be created behind an AOT window. You
> can't have it both ways. A window can't always be o
Hi,
is it possible to define a complete theme including the definitions of
colors, borders, appearances etc. within one single file or do I *have*
to define a separate color theme, border theme, etc. and reference them
in a meta theme?
If I understand [1] right, defining the complete theme in
Hi,
While trying to get my themeing to work with qooxdoo 0.7,
I get the warning:
Using set() for new non-themeable property: padding
What's the idea of non-themeable properties and why are box-dimensions
like paddings and margins not themeable? For me, it seems clear that the
sizes of margi
Sebastian Werner schrieb:
> Padding is marked as themeable in current trunk. What version do you
> use, exactly?
Not quite sure right now. We checked out from trunk last Monday and
built a jar library for RAP. However, fine that it works now.
Thanks, Ralf
-
Hi,
to change the font of a button, one must call
button.getLabelObject().setFont()
instead of
button.setFont()
I think, the fact, that at the button consists of sub-elements is an
internal detail and should be handled internally, not as part of the
API. In fact, I don't know of any wi
Hi Sebastian,
Sebastian Werner schrieb:
> in 0.7.x you can use setFont on Buttons, Toolbars, whatever widget. This
> is possible through the inheritance support of the new property system.
Well, I found the problem that prevented the themeing of the button
font: In the Appearance Theme, a defau
Hi Sebastian,
Sebastian Werner schrieb:
>> It seems that property inheritance does not override property values
>> from themeing. Is this generally the case?
>
> Yes. This is the way it was thought out. Generally, in 0.7, one would
> not define a font anywhere else than on the ClientDocument,
Hi Sebastian,
Sebastian Werner schrieb:
> I have just meant that it is better in my opinion to define the default
> font for an application for the client document. Then you can apply the
> exceptions directly on the effected widgets. Just take a look at the
> Classic theme to get an idea. Sett
Hi,
I have the following code in my appearance theme for the "list-item"
appearance:
if( states.selected ) {
result.textColor = "highlighttext";
result.backgroundColor = states.focused ? "colorX" : "colorY";
}
...
This does not work properly anymore, as states.focused seems only t
Hi,
what does the state "abandoned" (class Button) stand for ? I didn't find
any information on available states in the api viewer.
Ralf
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE ver
Hi Sebastian,
Sebastian Werner schrieb:
>> I have the following code in my appearance theme for the "list-item"
>> appearance:
>>
>> if( states.selected ) {
>> result.textColor = "highlighttext";
>> result.backgroundColor = states.focused ? "colorX" : "colorY";
>> }
>> ...
>>
>> Thi
Sebastian Werner schrieb:
> "abandoned" occours if you press a button down and leave it while
> keeping the button pressed. Hope this helps.
Ah, I see. Thank you.
Ralf
-
This SF.net email is sponsored by DB2 Express
Downloa
Hi,
I experience a problem with a text-field that is placed inside of a
toolbar. The text-field is displayed with the correct size, but the text
cursor appeares not only over the text-field, but also ~ 20 px right to
it. The "inspect" facility of Firefox shows that the internal
DOM element e
Hi,
Sebastian Werner schrieb:
> Normally the text-field is automatically synced by the layout engine.
> And this seems to work well, when using something like setWidth(20). Can
> you try to build a small example which demonstrates the bug? Just a
> toolbar and a textfield. Then I can play with
Hi Sebastian,
Ralf Sternberg schrieb:
Sebastian Werner schrieb:
Normally the text-field is automatically synced by the layout engine.
And this seems to work well, when using something like setWidth(20). Can
you try to build a small example which demonstrates the bug? Just a
toolbar and a
Hi Sebastian,
Sebastian Werner schrieb:
> Alternatively it should be possible to use moveAfter() instead.
> Hopefully this works better.
Great! That does the trick. At the end of the day, the sun comes out... ;-)
Thanks a lot,
Ralf
--
Hi,
the enabled property on the TextField is broken. Calling
setEnabled( true )
disables the text and vice-versa.
I tested this with a trunk version of today.
Ralf
Application.js
Description: JavaScript source
-
This S
Sebastian Werner schrieb:
> I think this was already fixed. Please try something r8000+. Thanks.
It works again with 0.7-beta1.
Thanks,
Ralf
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FR
Hi,
is there any way to change the color of selected text in TextFields,
TextAreas, etc.? I don't a way to do so neither with qooxdoo nor CSS,
but however i'd like to align that color with the current themeing.
Any ideas on this?
Thanks, Ralf
-
Hi Sebastian,
Sebastian Werner schrieb:
> some browsers support pseudo classes to change these colors. This is
> however currently not supported in qooxdoo. I currently don't have
> details available. You could try to google for "pseudo classes
> selection" whatever :)
Thanks for the hint.
Hi Fabian,
Fabian Jakobs schrieb:
> Yes, we have considered it but had to dismiss the idea because keyboard
> events are not sufficient for general purpose input fields. It's simply
> not possible to get reliable events for "composed" characters like "*",
> "!", "ä", "~", In fact every cha
72 matches
Mail list logo
