Yes, that helps. Thanks Sebastian.
Joe
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sebastian
Werner
Sent: Friday, June 08, 2007 3:28 AM
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] .7 release and setCssClassName
Hi Joe.
We cleaned up the Wi
I am still using an old version of the VCL. I just tested again using IE and
it also worked. You can click on the circle or the label, it doesn't matter.
The key is the GROUP id. If they have no id set or they have different id's
then it's not going to work.
Jim
www.D4PHP.org
www.D4PHP-Hosting.co
Since I'm working with D4PHP, qooxdoo, html, etc. I must have confused
them when I posted this. My problem was that I had a
treefullcontrol(treeview in D4PHP) in a Window component. The
treeview was on the left and on the right a div would show when you
clicked it's corresponding leaf. I figured
Jim which version of the VCL are you using? Also I think the way I
was using them was that I had a treefullcontrol component and I had it
where there was a radioButton then the caption. In IE when you
clicked the radio buttons they just wouldn't click. At that point I
don't think I was using t
I just testeed this in D4PHP and they work fine. Are you setting the GROUP
property? All the radio buttons that you want to 'tie together' need to have
the same GROUP id.
Jim
www.D4PHP.org
www.D4PHP-Hosting.com
On 6/8/07, FrozenDice <[EMAIL PROTECTED]> wrote:
It's probably since I'm still usin
FrozenDice <[EMAIL PROTECTED]> writes:
> Thanks setOpen worked perfectly.
Ok, it sounded like you wanted to change the default. setOpen only
effects the node you're creating at the time, whereas the other method
changes the default so you don't need to call setOpen() on each one.
Derrell
> On
FrozenDice <[EMAIL PROTECTED]> writes:
> I tried the code and it didn't seem to work. I'm pretty much a newbie
> in qooxdoo, could you point me to some docs that explain this so I can
> figure out how to fix the code?
Are you using 0.7? That's very much 0.7 code. If you're using 0.6 then
look
It's probably since I'm still using .6.6 instead of the new .7. I'm
limited to .6.6 because I'm using delpi4php and they haven't upgraded
to the latest qooxdoo yet as far as I know. Either it was fixed along
the way or it's a problem with the VCL.
Thanks
- Dan
On 6/8/07, Sebastian Werner <[EMA
Thanks setOpen worked perfectly.
On 6/7/07, Tobias Koller (GERMO GmbH) <[EMAIL PROTECTED]> wrote:
> Hi,
>
> you can use this:
>
> var trs =
> qx.ui.treefullcontrol.TreeRowStructure.getInstance().standard("Testnode",
> "icon/16/places/folder.png", "icon/16/places/folder.png");
> var te1 = new qx.
I tried the code and it didn't seem to work. I'm pretty much a newbie
in qooxdoo, could you point me to some docs that explain this so I can
figure out how to fix the code?
On 6/7/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> FrozenDice <[EMAIL PROTECTED]> writes:
>
> > Is it possible to hav
Hello Tobias,
the behaviour is built into our QxTransformer rpc classes. Have a look
at this (unfinished) totorial:
http://qooxdoo.org/documentation/related_projects/qxtransformer#loading..._popup
The code of the MDataManager mixin on which this is built is here:
http://qxtransformer.svn.sourc
Sebastian,
On 08/06/07, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> Nick,
>
> Ok, thank you for your feedback. I think I know what the issue is in
> some of these cases.
> obj.setToolTip(application.sharedToolTip);
>
> This shared value must not be disposed in this case. I would say that
> ther
If I remember correctly you have to do either this ...
qxsettings = { "qx.application" : Apl" };
Or this
qx.core.Init.getInstance ( ).setApplication ( new Apl );
Both worked for me.
Varol :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Beha
Hi Sebastian,
It's a great news, this widget is very expected !
According to the roadmap (http://qooxdoo.org/about/roadmap), the next major
release is planned for August 2007. It's mean you deliver your WYSIWYG work
is few days/weeks ?
If I can help you, I've already written piece of code : cross
It is for
- easing debugging (some errors are specific to compiled or source builds),
- to open the generated file in JSEclipse, and highlight all the uses of the
method/variable under the cursor. As Javascript is a dynamic language, it's
hard to know inter-dependencies, specially when you have
Created bug
http://bugzilla.qooxdoo.org/show_bug.cgi?id=471
Sebastian Werner wrote:
>
> please open a bug report and attach the problematic part (please try to
> reduce it to only one line (the problematic one))
>
--
View this message in context:
http://www.nabble.com/Possible-generator-bu
Pretty printing is meant for source files. What would be the reason to
format compiled code? (which is normally optimized for size - not for
design).
Sebastian
dperez schrieb:
> Hi,
>
> I would like the generator to pretty print the compiled output script.
> Does the --pretty-print option re
David,
please open a bug report and attach the problematic part (please try to
reduce it to only one line (the problematic one))
Thanks.
Sebastian
dperez schrieb:
> Hi,
>
> I have this expression in my code:
>
> return /* paddingLeft */ 2 + /* paddingRight */ 2 +
> (anchoIco ? 2 : /*
Confirmed this is a bug. If I change
(anchoIco ? 2 : 0/* spacing */)
to
(anchoIco ? 2 : /* spacing */0)
it works ok.
dperez wrote:
>
> Hi,
>
> I have this expression in my code:
>
> return /* paddingLeft */ 2 + /* paddingRight */ 2 +
> (anchoIco ? 2 : /* spacing */ 0) +
> Math.m
Hi,
I would like the generator to pretty print the compiled output script.
Does the --pretty-print option reformat original source files or the
compiled one?
I will update the wiki with any helpful answer
(http://qooxdoo.org/documentation/0.7/custom_builds)
Regards,
David
--
View this message
Hi,
I have this expression in my code:
return /* paddingLeft */ 2 + /* paddingRight */ 2 +
(anchoIco ? 2 : /* spacing */ 0) +
Math.max(queAnchoTxt((param.hayIndReq()
? Const.indReq : '') +
param.queDenominacion()) + anchoIco, param.queAncho(true));
and receive this error:
tree
Hello,
Nick Glencross wrote:
> Table:
>
> * The Table might be leaking many of its backend Widgets, such as
> the model, although I've been inspecting the code closely, and I can't
> see why as it seems to be trying to clean itself up properly
The SimpleTableModel itself also seems to have lea
Hello,
can this also be used to move a widget outside the qooxdoo document and
to the HTML page itself? I need to display a table that is larger than
the actual qooxdoo desktop in a scrollable window for printing it out
somehow without losing rows that are outside the visible qooxdoo area.
Reg
Hi Christian,
I also like the "laoding, please wait".
I made a similar on some time ago and always asked myself how to handle open
RPC-Calls etc.
Could you give me a short snippet of your code which handles the Events and
qx.event.message.Bus?
I thought about inherit my class from the qx.oi.rem
Done!
http://bugzilla.qooxdoo.org/show_bug.cgi?id=470
Sebastian Werner wrote:
>
> Hi David,
>
> it would be helpful if you also add these feature requests to our bug
> tracking system (as feature enhancement) so they don't get forgotten.
>
--
View this message in context:
http://www.nabbl
Hi Frederic,
there is already a internal development of such an editor started. It is
in the early steps and will be get some more touches before added to
(public) SVN. I don't currently know how the further release plan of
this piece of code was planned. I would day that it will be included in
Hi David,
it would be helpful if you also add these feature requests to our bug
tracking system (as feature enhancement) so they don't get forgotten.
Sebastian
dperez schrieb:
> Hi,
>
> The API Viewer would be even better, if settings
> (http://qooxdoo.org/documentation/0.7/user_manual/settin
Hi Dietrich,
it does indeed "compress" them. The queues remember which objects added.
Sebastian
Dietrich Streifert schrieb:
> Hello List,
>
> I introduced some additional states to TextField to reflect the validity
> of input data.
> In some cases I have multiple calls to removeState consecu
They seem to work correctly for me:
http://demo.qooxdoo.org/current/demobrowser/#example~RadioButton_1.html
Sebastian
dperez schrieb:
> It's easy to know. Try the online demos!.
>
>
> FrozenDice wrote:
>> I was just wondering if the bug where radio buttons don't work under
>> IE7 has been fixe
I don't really understand what you wanna archive. Hovever if you are
dealing with HTML fragments the classes HtmlEmbed or Inline could be
interesting for you.
Hope this helps.
Sebastian
FrozenDice schrieb:
> Ah, no unfortunately that code didn't work. Thanks for trying though.
>
> What I'm
You are mixing metaphors. A DIV is not a widget. Your initial question was
how to move a widget to a window and the sample code provided will work to
move a qooxdoo widget from one parent to another. What is in your DIV's? Is
there a reason you aren't using a qooxdoo control like an Atom?
Jim
www
David,
Yes it could be autodetected easily. If you execute the pretty printer
e.g. with a "make pretty" inside your application, this would be one
thing which is automatically added to the members/statics.
These @type constructs are used for a hint to the developer/user of the
class. The start
Nick,
Ok, thank you for your feedback. I think I know what the issue is in
some of these cases.
The property system automatically handles the dispose of assigned
qooxdoo objects if the value defined with the property "check" is known.
Disposing in this case means that the element key will be d
Hi Joe.
We cleaned up the Widget class a bit from things which are nowhere used
in the framework. An alternative method to apply a classname would be:
obj.setHtmlProperty("className", "yourClassName");
Hope this helps.
Cheers,
Sebastian
Joe Hudson schrieb:
> Hello,
>
> How can I accomplish
Yes you are partly right.
The nativeLogger is really a dependency of qx.log.Logger, but only if
the appender setting has not been modified.
The correct fix for this is to add the following to your command line
parameters:
--add-require qx.log.Logger:qx.log.appender.Native
Sorry for the delay.
A #require(qx.log.appender.Native) line in Logger.js solves the problem!
dperez wrote:
>
> Hi,
>
> I think I've found more clues about the problem.
>
> In the defer section of qx.log.Logger, we have this line, that generates
> an error:
>
> statics.ROOT_LOGGER.addAppender(new
> (qx.Class.get
Hi,
I think I've found more clues about the problem.
In the defer section of qx.log.Logger, we have this line, that generates an
error:
statics.ROOT_LOGGER.addAppender(new
(qx.Class.getByName(qx.core.Setting.get("qx.logAppender";
qx.core.Setting.get("qx.logAppender") = "qx.log.appender.Nati
37 matches
Mail list logo
