On Mon, Feb 27, 2012 at 20:21, Scott Chapman wrote:
> The tab widget size is set statically to 950x700 below.
> How do I make it dynamic so that it's initial size and resize changes
> as needed by the size of the Page box?
>
It's not done to the Page object; rather, it's done to the TabView to w
The tab widget size is set statically to 950x700 below.
How do I make it dynamic so that it's initial size and resize changes
as needed by the size of the Page box?
(By the way, this is a decent example of how to use OpenLayers Map
with Qooxdoo, using MapQuest's Open Tile servers.)
qx.Class.defin
Hi,
Great to hear, that you give qooxdoo mobile a try. Let us know, if you have any
problems.
The Windows Phone support will come. See bug 5742 for that.
http://bugzilla.qooxdoo.org/show_bug.cgi?id=5742
Unfortunately Windows Phone does not support the flexible box layout right now.
Windows Ph
Hi,
no, neither warnings in "source" or Javascript errors in "build"
happened. I am using Firebug but also tested Chrome Developer Tools.
Are these warnings a new thing in 1.6? I am still on 1.5.
Regards
Christof
2012/2/27 thron7 :
>
>
> On 02/27/2012 02:42 PM, Marc Puts wrote:
>> Hi Christof,
On 02/27/2012 02:42 PM, Marc Puts wrote:
> Hi Christof,
> Great to hear you found the problem.
>
> But I'm puzzled... wouldn't accessing a non-existing object member cause
> a javascript error in the console, even in the build version?
Exactly! And in the 'source' version you should have seen wa
Hi Christof,
Great to hear you found the problem.
But I'm puzzled... wouldn't accessing a non-existing object member cause
a javascript error in the console, even in the build version?
On 02/27/2012 02:30 PM, Christof Rodejohann wrote:
> Hi,
>
> thank you all for your help. It was like Fritz su
Hi,
thank you all for your help. It was like Fritz suggested the access to
a private variable. Child classes trying to access a private variable
defined in the parent class does not work in "build".
Also thx for the debug snippet. I am sure this will come in handy.
Regards
Christof
2012/2/27 Tr
Hi Christof,
so "source" works, but "build" does not. Well, generally this shouldn't happen.
Let's dig a little deeper.
To enable debugging in the build variant, add this to your configuration
("jobs" section):
"build-script" :
{
"environment" :
{
"qx.debug" : true
}
}
One potentia
Another difference between source and build version is that access to
private variables (starting with __) works in the source version, but
doesn't in the build version as the variable names are "optimized away".
You could disable the optimization steps in the build process (config.json,
it's desc
Hi,
did you checked the API fist? When I understood you question, than you mean
"changeShownMonth" and "changeShownYear":
http://demo.qooxdoo.org/current/apiviewer/#qx.ui.control.DateChooser
Cheers,
Chris
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/event-datechooser-tp7321
Hi Christof,
could you please try to clean your artefacts with "generate.py distclean"
and try to rebuild it with "generate.py source". Does the source version
work?
Cheers,
Chris
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Build-broken-How-to-debug-tp7321369p7321552.html
Hi,
I've already solved the problem and the error was about another thing which
exception has not been caught properly. However the exception should arise
in both cases I suppose and not just in second case.
But ok, it's solved!!
Ana Rita Sousa
--
View this message in context:
http://qooxdoo.
Hi,
"source" runs like a charm. No errors, warnings whatsoever. How do i
disable the catching of the errors in "build" to debug the current
error? What might be a situation where i am needed to manually require
a class which is loaded in "source" but not in "build"?
Regards
Christof
2012/2/27 T
hello,
i need a event that appear, wenn i change the month or year by clicken
on the above arrows? is this possible?
--
Try before you buy = See our experts in action!
The most comprehensive online learning library f
Hi Christof,
try "source" first.
The "build" variant may catch and swallow errors depending on your
configuration. Also, qx.debug is off by default. This does make sense for
production, since you usually don't want to confront your users with error
messages. But for debugging, you want to see
Hi,
i have been building quite a complex application in Qooxdoo. I have
been working in the "source-all" build and everything is working
great. Now i am closing in to a first iteration and tried the "build"
build. There are no errors in the generate process of the "source-all"
and "build". And no
Hm, thats not good. Do you think its worth the effort to implement it? I mean
the modern browsers are fast enough anyway. :|
Am 25.02.2012 um 11:22 schrieb benco:
>
> MartinWittemann wrote
>>
>> Let me know the results because I also have a task checking on that. :)
>>
>
> Well, the results
17 matches
Mail list logo
