Hey,
Is there a possibility to pass the this-reference to the callback function?
No, the converter does not offer the setting of a context so you can use the
closure variant you already suggested. Another way would be to bind the
converter function using the function bind [1], which qooxdoo offe
Ah, yes. I remember that in some cases, it was not possible to detect the
former appearance. If you can supply a sample, I check for the reason why the
fallback could not work.
Am 29.08.2012 um 07:57 schrieb Tobias Oetiker :
> Hi Martin,
>
> Today Martin Wittemann wrote:
>
>> Hey, Hm, that s
Hey,
I don't think the select box or the popup list at all is tested with such a
huge amount of items. That might be worth an enhancement report because we
should make sure the list is always max hight as the screen is and offer some
kind of scrolling to make every item accessible.
> 1. The 10
Hi Martin,
Today Martin Wittemann wrote:
> Hey, Hm, that should work out of the box as far as I can
> remember. We do have a fallback implementation if there is not
> appearance for the child control, we check if the original
> appearance applies. I quite some time ago I did something in that
> a
Hey,
you would need to define your own CSS class containing the same styles as the
label has. This includes the tag the list is in. As soon as you have the
class defined in your custom CSS, you can apply it to the additional lable and
everything should work fine.
Regards,
Martin
Am 24.08.2012
Hey,
Hm, that should work out of the box as far as I can remember. We do have a
fallback implementation if there is not appearance for the child control, we
check if the original appearance applies. I quite some time ago I did something
in that area so I might be wrong. Is that true for every ch
If I replace the template code with the following:
var page1 = new qx.ui.mobile.page.NavigationPage();
page1.addListener("initialize", function()
{
var sel = new qx.ui.mobile.form.SelectBox();
page1.add(sel);
var model = new qx.data.Array([]);
for
Hi,
I found the post [1] quite useful in dealing with the appearance of
child controls.
[1]
http://qooxdoo.678.n2.nabble.com/odd-rendering-behavior-of-child-controls-td5091928.html
See if this is what you are looking for.
Cheers,
Ramakrishna
On 08/28/2012 06:46 PM, Tobias Oetiker wrote
Hi,
I quite like the widget with childcontrols approach for creating my
uis ... BUT eventhough I have not created any special theming
properties, the included child widgets tend to loose part of their
design in the process ...
how can I use controls as child widgets and have them continue to
use
I have a general question about the context of callback functions:
I have, for example, in an arbitrary class a model which I want to modify
with different textboxes, for that I have defined a
converter function because I want to deal with numbers instead of strings:
tf.bind("value", model, ta
On 08/28/2012 11:09 AM, non wrote:
>
> I had a look into these before. They use qx.io.ScriptLoader if I remember
> right.
> I like that approach, because I get rid of those add-scripts...
> But:
> * EXPERIMENTAL – NOT READY FOR PRODUCTION
Better use qx.bom.request.Script.
> * I don't understand
thron7-2 wrote
>
> A possible approach to tackle this might be to wrap the entire 3rd party
> module in a qooxdoo class, which handles the loading, and then use the
> wrapper class throughout of your code. The wrapper class could provide
> means to check the loading status, like firing an even
Hi,
thanks for your feedback. Themeing is not well supported by this contrib,
many things are hardcoded. It would be great, if you have the time and
interest, to change the code itself to better support the different themes.
I cannot do this unfortunately.
Best,
Christian
--
View this message
I'd say it's a timing issue. At the time when the code
period: d3.time.day
is executed, the d3 script has not finished loading (and being
evaluated). I think this is the fate of scripts loaded dynamically by
inserting "script" element in the DOM: The evaluation order is no longer
enforced
Maybe one step further:
I turned off all optimizations and debugged the build version a little:
Inside a class of abc.core:
---
qx.Class.define("abc.core.View", {
extend : abc.core.AbstractView,
statics : {
15 matches
Mail list logo
