It's bug #2116
2009/3/12 Petr Kobalíček :
> Hi Fabian,
>
> this is best idea, I can remove these lines by postprocessing. I must
> first try it.
>
> I will open bug report for this.
>
> Cheers
>
> 2009/3/12 Fabian Jakobs :
>> Petr Kobalíček schrieb:
>>> Hi,
>>>
>>> is there any way to invoke appli
Hi Fabian,
this is best idea, I can remove these lines by postprocessing. I must
first try it.
I will open bug report for this.
Cheers
2009/3/12 Fabian Jakobs :
> Petr Kobalíček schrieb:
>> Hi,
>>
>> is there any way to invoke application initialization manually ?
>>
>> I mean to completely ski
Petr Kobalíček schrieb:
> Hi,
>
> is there any way to invoke application initialization manually ?
>
> I mean to completely skip qxsettings["qx.application"] and call
> something like qx.core.Init.init().
>
> Is this possible ?
>
No. We know of this limitation and we would like to remove it. Cou
Hi devs,
so my solution to problem is very simple, I added these linces to qx.core.Init
/**
* Explicit application initialization. Can be used to manually initialize
* application (internally calls qx.core.Init.__ready().
*
* @note This method can be used only once. Callin
2009/3/11 Petr Kobalíček
> Hi Alex,
>
> I know that there is currently no solution, my I'm talking here to
> know that if I write patch (and this is quite simple) if there is
> chance to get it into svn. I want to support qxbuild and make it
> working without black magic:)
>
Petr, might you be a
Hi Alex,
I know that there is currently no solution, my I'm talking here to
know that if I write patch (and this is quite simple) if there is
chance to get it into svn. I want to support qxbuild and make it
working without black magic:)
2009/3/11 Alexander Back :
> Hi Petr,
>
> On Wednesday 11 Ma
Hi Petr,
On Wednesday 11 March 2009 Petr Kobalíček wrote:
> Alex I need to explain you my problem:
>
> calling qx.event.handler.Application.onScriptLoaded() not helps me.
> Under FF, Opera and Chrome there is no problem, but under IE i get
> this message:
>
> 002063 qx.core.Init: Load runtime: 206
Alex, to better explain,
I can't set __application in qx.core.Init manually, there must be
method to explicitly call the handler:
look at this:
defer : function(statics)
{
qx.event.Registration.addListener(window, "ready",
statics.__ready, statics);
qx.event.Registration.addListener(
Hi Petr,
On Wednesday 11 March 2009 Petr Kobalíček wrote:
> Hi Alex,
>
> thanks for explanation. A have last question. Can I disable automatic
> qooxdoo initialization ? If I can call
> qx.event.handler.Application.onScriptLoaded(); then I don't need
> qooxdoo to call it on init.
Does qooxdoo disp
Alex I need to explain you my problem:
calling qx.event.handler.Application.onScriptLoaded() not helps me.
Under FF, Opera and Chrome there is no problem, but under IE i get
this message:
002063 qx.core.Init: Load runtime: 2063ms
002063 Missing application class: bfly.main.Application
bfly.main.
Hi Alex,
thanks for explanation. A have last question. Can I disable automatic
qooxdoo initialization ? If I can call
qx.event.handler.Application.onScriptLoaded(); then I don't need
qooxdoo to call it on init.
Cheers
- Petr
2009/3/11 Alexander Back :
> Hi Petr,
>
> On Monday 09 March 2009 Petr
Hi Petr,
On Monday 09 March 2009 Petr Kobalíček wrote:
> is there any way to invoke application initialization manually ?
>
> I mean to completely skip qxsettings["qx.application"] and call
> something like qx.core.Init.init().
>
> Is this possible ?
It is possible, but you need to know what you'r
Qooxoo devs, i'm waiting if it's possible to add explicit initialization :-)
Derrell,
just one note about your solution. Your solution to not use
application main() method will not work. Because domloaded event is
fired by IE too early, there is no such application class declared -
qooxdoo only p
Hi Derrell,
I understand you. But my problem with this solution is that
application using qxbuild needs different code than application that
uses qooxdoo build system. And this all for IE :)
For me this is no problem, I'm not using IE and I can tell customers
to not use IE in admin, but for other
2009/3/9 Petr Kobalíček
> Hi Derrell,
>
> I tested it now and it's the same behavior. I think that only solution
> is ability to tell qooxdoo to initialize manually.
>
> Main problem for me is that IE is not preserving the script order, so
> I must append scripts one-by-one (I tested in head and
Hi Derrell,
I tested it now and it's the same behavior. I think that only solution
is ability to tell qooxdoo to initialize manually.
Main problem for me is that IE is not preserving the script order, so
I must append scripts one-by-one (I tested in head and body too).
Personally, I think that m
On Mon, Mar 9, 2009 at 2:43 PM, Petr Kobalíček wrote:
> Hi,
>
> is there any way to invoke application initialization manually ?
>
> I mean to completely skip qxsettings["qx.application"] and call
> something like qx.core.Init.init().
>
> Is this possible ?
>
> I need this for qxbuild. It works fi
Hi,
is there any way to invoke application initialization manually ?
I mean to completely skip qxsettings["qx.application"] and call
something like qx.core.Init.init().
Is this possible ?
I need this for qxbuild. It works fine for all browsers except IE.
Qxbuild loads all scripts by adding scri
18 matches
Mail list logo
