Travelmate Bundle ecmascript

[Matthias Baumgart-3]

Hello,

I use the TextMate Bundle in the latest version on Mac OSX 10.5.7. After saving qooxdoo java scripts or running Qooxdoo specific tasks like validate syntac I get the following error:

Traceback (most recent call last): File "/Users/matthias/Library/Application Support/TextMate/Bundles/qooxdoo.tmbundle/Support/validate.py", line 18, in from ecmascript.frontend import treegenerator ImportError: No module named ecmascript.frontend

I searched for ecmascript but, the installation description on their page is not very informative. How to configure the bundle right? Or how to install the ecmascript?

Yours,

Matthias.

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Andreas Ecker-2]

Hi Matthias,

I'm not using qooxdoo's TextMate bundle myself (but some of the other
core devs do), so are you using the latest version and have you followed
the installation section at
http://qooxdoo.org/contrib/project/textmate

If that doesn't help, I'm sure the others will comment tomorrow,

Andreas


On Tue, 2009-07-07 at 15:51 +0200, Matthias Baumgart wrote:

> Hello,
>
>
> I use the TextMate Bundle in the latest version on Mac OSX 10.5.7.
> After saving qooxdoo java scripts or running Qooxdoo specific tasks
> like validate syntac I get the following error:
>
>
> Traceback (most recent call last): File
> "/Users/matthias/Library/Application
> Support/TextMate/Bundles/qooxdoo.tmbundle/Support/validate.py", line
> 18, in from ecmascript.frontend import treegenerator ImportError: No
> module named ecmascript.frontend
>
>
> I searched for ecmascript but, the installation description on their
> page is not very informative. How to configure the bundle right? Or
> how to install the ecmascript?
>
>
> Yours,
> Matthias.

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Martin Wittemann]

Hello Matthias,

looks like there is a problem with the configuration of your bundle or with the qooxdoo checkout. If your qooxdoo path is set correct in the shell variable of textmate, you could check if the ecmascript file is available and up to date? The file should be stored in the following path:

<<qooxdoo_root>>/tool/pylib

Perhaps a svn update will fix this?

Best,

Martin

Am 07.07.2009 um 15:51 schrieb Matthias Baumgart:

Hello,

I use the TextMate Bundle in the latest version on Mac OSX 10.5.7. After saving qooxdoo java scripts or running Qooxdoo specific tasks like validate syntac I get the following error:

Traceback (most recent call last): File "/Users/matthias/Library/Application Support/TextMate/Bundles/qooxdoo.tmbundle/Support/validate.py", line 18, in from ecmascript.frontend import treegenerator ImportError: No module named ecmascript.frontend

I searched for ecmascript but, the installation description on their page is not very informative. How to configure the bundle right? Or how to install the ecmascript?

Yours,

Matthias.

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Matthias Baumgart-3]

> oks like there is a problem with the configuration of your bundle or  
> with the qooxdoo checkout. If your qooxdoo path is set correct in  
> the shell variable of textmate, you could check if the ecmascript  
> file is available and up to date? The file should be stored in the  
> following path:
> <<qooxdoo_root>>/tool/pylib
>
> Perhaps a svn update will fix this?

ok, sorry my pitty. I thought my qooxdoo path is right set, because  
the build works fine. But it wasn't so. No evereything works fine.

Sorry.
Matthias.

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[John Spackman]

Hi,

I came across a weird problem yesterday where IE8 would give an "Invalid
argument" exception where FF3 was fine; this was harmless if you had had the
IE8 debugger running but if not would cause the Qooxdoo app to completely
stop responding.

By elimination I eventually tracked it down to a table which had no explicit
"width" and which had a column also with no explicit width;  I haven't been
able to produce a reasonable test case so I'm posting my findings in case it
makes more sense to someone else!

The error occurred on line 335 of qx/bom/element/Style.js, where the code is
setting the "width" property to "-1px".  This was set by a call to
qx.ui.Element.setStyle where the stack trace was:

        Widget.js line 928, function renderLayout:
"content.setStyle("width", innerWidth + pixel);"
        Grid.js line 1282, function renderLayout (cellWidth=4)

John




------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Alexander Back]

Hi John,

On Friday 10 July 2009 John Spackman wrote:

> I came across a weird problem yesterday where IE8 would give an "Invalid
> argument" exception where FF3 was fine; this was harmless if you had had
> the IE8 debugger running but if not would cause the Qooxdoo app to
> completely stop responding.
>
> By elimination I eventually tracked it down to a table which had no
> explicit "width" and which had a column also with no explicit width;  I
> haven't been able to produce a reasonable test case so I'm posting my
> findings in case it makes more sense to someone else!
>
> The error occurred on line 335 of qx/bom/element/Style.js, where the code
> is setting the "width" property to "-1px".  This was set by a call to
> qx.ui.Element.setStyle where the stack trace was:
>
> Widget.js line 928, function renderLayout:
> "content.setStyle("width", innerWidth + pixel);"
> Grid.js line 1282, function renderLayout (cellWidth=4)

I encountered the same issue some time ago. Could you please write us what
kind of table you are using? I'm especially interested whether you use the
reisze behaviour or not.

cheers,
  Alex


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[John Spackman]

Sure - it's the Resize column model and Simple table model.  I'd email you
the code but it might be quite hard to get it going without our entire app
etc (I'm willing to send it but perhaps it should be a last resort); here's
the bits that I think might be relevant:

        table.setDecorator(null);
        table.setKeepFirstVisibleRowComplete(true);
        table.setStatusBarVisible(false);
       
table.getSelectionModel().setSelectionMode(qx.ui.table.selection.Model.SINGL
E_SELECTION);
        table.set({ width: 600, autoAddRows: false, allowGrowX: false });

John

-----Original Message-----
From: Alexander Back [mailto:alexander.back@...]
Sent: 10 July 2009 11:54
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Invalid argument in IE8 (setting width to -1px)

Hi John,

On Friday 10 July 2009 John Spackman wrote:

> I came across a weird problem yesterday where IE8 would give an "Invalid
> argument" exception where FF3 was fine; this was harmless if you had had
> the IE8 debugger running but if not would cause the Qooxdoo app to
> completely stop responding.
>
> By elimination I eventually tracked it down to a table which had no
> explicit "width" and which had a column also with no explicit width;  I
> haven't been able to produce a reasonable test case so I'm posting my
> findings in case it makes more sense to someone else!
>
> The error occurred on line 335 of qx/bom/element/Style.js, where the code
> is setting the "width" property to "-1px".  This was set by a call to
> qx.ui.Element.setStyle where the stack trace was:
>
> Widget.js line 928, function renderLayout:
> "content.setStyle("width", innerWidth + pixel);"
> Grid.js line 1282, function renderLayout (cellWidth=4)

I encountered the same issue some time ago. Could you please write us what
kind of table you are using? I'm especially interested whether you use the
reisze behaviour or not.

cheers,
  Alex


----------------------------------------------------------------------------
--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize

details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[John Spackman]

Hi,

Earlier today my modal windows became non-modal - they'd been working fine
before and that particular code hadn't been touched.  We use an Inline
application and the change which triggered the problem was tracked to the
div outside the div outside where the Qooxdoo app is placed - a designer had
set div's style to "position: absolute; top: 154px".

In qx/ui/root/Page.js, in __syncBlocker the blocker is set to the size of
the body.offsetWidth x body.offsetHeight, but in our case the
body.offsetHeight was returning 101.  Sure enough the partially opaque
blocker only appears at the top of the window.  Oddly, if I put up a modal
window during application startup, the blocker is full screen for about a
second and then __syncBlocker kicks in and resizes it.

Is there a reason for calculating the size instead of just choosing
something impossibly big?

John


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Christian Schmidt-18]

Hi John,

I can remember, that there was a issue with inline applications and
modal windows.

Which qooxdoo version do you use?

Cheers,
Chris

John Spackman schrieb:

> Hi,
>
> Earlier today my modal windows became non-modal - they'd been working fine
> before and that particular code hadn't been touched.  We use an Inline
> application and the change which triggered the problem was tracked to the
> div outside the div outside where the Qooxdoo app is placed - a designer had
> set div's style to "position: absolute; top: 154px".
>
> In qx/ui/root/Page.js, in __syncBlocker the blocker is set to the size of
> the body.offsetWidth x body.offsetHeight, but in our case the
> body.offsetHeight was returning 101.  Sure enough the partially opaque
> blocker only appears at the top of the window.  Oddly, if I put up a modal
> window during application startup, the blocker is full screen for about a
> second and then __syncBlocker kicks in and resizes it.
>
> Is there a reason for calculating the size instead of just choosing
> something impossibly big?
>
> John
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge  
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  

--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Alexander Back]

Hi Hohn,

On Friday 10 July 2009 John Spackman wrote:
> Sure - it's the Resize column model and Simple table model.  I'd email you
> the code but it might be quite hard to get it going without our entire app
> etc (I'm willing to send it but perhaps it should be a last resort);
I think in the first bug hunting phase it's not necessary for me to have the
entire code of your app. I've just wanted to know if I'm on the right track
concerning the Resize column model. I guess the bug is located somewhere in
this area. So the info that you're also using the Resize column is enough for
me at the moment :)


> here's the bits that I think might be relevant:
>
>         table.setDecorator(null);
>         table.setKeepFirstVisibleRowComplete(true);
>         table.setStatusBarVisible(false);
>        
> table.getSelectionModel().setSelectionMode(qx.ui.table.selection.Model.SING
>L E_SELECTION);
>         table.set({ width: 600, autoAddRows: false, allowGrowX: false });
Thanks for this snippet. I've added this to the Bug #2577.

cheers,
  Alex

-> http://bugzilla.qooxdoo.org/show_bug.cgi?id=2577


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[John Spackman]

Hi Chris,

We're using 0.8.1; we're literally a few days away from a major release so if you could point me in the direction of a patch that would be great.

Cheers
John

-----Original Message-----
From: Christian Schmidt [mailto:schmidt.christian@...]
Sent: 13 July 2009 08:19
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Modal blocker is only 101 pixels high!

Hi John,

I can remember, that there was a issue with inline applications and
modal windows.

Which qooxdoo version do you use?

Cheers,
Chris

John Spackman schrieb:

> Hi,
>
> Earlier today my modal windows became non-modal - they'd been working fine
> before and that particular code hadn't been touched.  We use an Inline
> application and the change which triggered the problem was tracked to the
> div outside the div outside where the Qooxdoo app is placed - a designer had
> set div's style to "position: absolute; top: 154px".
>
> In qx/ui/root/Page.js, in __syncBlocker the blocker is set to the size of
> the body.offsetWidth x body.offsetHeight, but in our case the
> body.offsetHeight was returning 101.  Sure enough the partially opaque
> blocker only appears at the top of the window.  Oddly, if I put up a modal
> window during application startup, the blocker is full screen for about a
> second and then __syncBlocker kicks in and resizes it.
>
> Is there a reason for calculating the size instead of just choosing
> something impossibly big?
>
> John
>
>
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge  
> This is your chance to win up to $100,000 in prizes! For a limited time,
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  

--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Christian Schmidt-18]

Hi John,

I found it! The issue was fixed after the 0.8.2 release. The
qx.ui.root.Page has a bug in the "__syncBlocker" method, please use the
attached [2] code instead.

You can patch the file by running these steps:
1) create an own mixin
2) copy the code from [2] into it
3) use the patch method [1] to override the old "__syncBlocker" method.
e.q.:
  //call this line at the beginning of the 'main' method on your
Application.js
  qx.Class.patch(qx.ui.root.Page, myApp.MPagePatch);

I haven't tested this, but I hope this solve your problem.

Cheers,
Chris

[1] http://demo.qooxdoo.org/current/apiviewer/#qx.Class~patch
[2]
__syncBlocker : function()
{
  var doc = this.__doc;

  this._getContentBlocker().setStyles({
    height: doc.documentElement.scrollHeight + "px",
    width: doc.documentElement.scrollWidth + "px"
  });
},


John Spackman schrieb:

> Hi Chris,
>
> We're using 0.8.1; we're literally a few days away from a major release so if you could point me in the direction of a patch that would be great.
>
> Cheers
> John
>
> -----Original Message-----
> From: Christian Schmidt [mailto:schmidt.christian@...]
> Sent: 13 July 2009 08:19
> To: qooxdoo Development
> Subject: Re: [qooxdoo-devel] Modal blocker is only 101 pixels high!
>
> Hi John,
>
> I can remember, that there was a issue with inline applications and
> modal windows.
>
> Which qooxdoo version do you use?
>
> Cheers,
> Chris
>
> John Spackman schrieb:
>  
>> Hi,
>>
>> Earlier today my modal windows became non-modal - they'd been working fine
>> before and that particular code hadn't been touched.  We use an Inline
>> application and the change which triggered the problem was tracked to the
>> div outside the div outside where the Qooxdoo app is placed - a designer had
>> set div's style to "position: absolute; top: 154px".
>>
>> In qx/ui/root/Page.js, in __syncBlocker the blocker is set to the size of
>> the body.offsetWidth x body.offsetHeight, but in our case the
>> body.offsetHeight was returning 101.  Sure enough the partially opaque
>> blocker only appears at the top of the window.  Oddly, if I put up a modal
>> window during application startup, the blocker is full screen for about a
>> second and then __syncBlocker kicks in and resizes it.
>>
>> Is there a reason for calculating the size instead of just choosing
>> something impossibly big?
>>
>> John
>>
>>
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge  
>> This is your chance to win up to $100,000 in prizes! For a limited time,
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@...
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>  
>>    
>
>
>  

--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[John Spackman]

Hi Chris,

That's absolutely perfect, thanks very much :)

John

-----Original Message-----
From: Christian Schmidt [mailto:schmidt.christian@...]
Sent: 13 July 2009 14:02
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Modal blocker is only 101 pixels high!

Hi John,

I found it! The issue was fixed after the 0.8.2 release. The
qx.ui.root.Page has a bug in the "__syncBlocker" method, please use the
attached [2] code instead.

You can patch the file by running these steps:
1) create an own mixin
2) copy the code from [2] into it
3) use the patch method [1] to override the old "__syncBlocker" method.
e.q.:
  //call this line at the beginning of the 'main' method on your
Application.js
  qx.Class.patch(qx.ui.root.Page, myApp.MPagePatch);

I haven't tested this, but I hope this solve your problem.

Cheers,
Chris

[1] http://demo.qooxdoo.org/current/apiviewer/#qx.Class~patch
[2]
__syncBlocker : function()
{
  var doc = this.__doc;

  this._getContentBlocker().setStyles({
    height: doc.documentElement.scrollHeight + "px",
    width: doc.documentElement.scrollWidth + "px"
  });
},


John Spackman schrieb:

> Hi Chris,
>
> We're using 0.8.1; we're literally a few days away from a major release so if you could point me in the direction of a patch that would be great.
>
> Cheers
> John
>
> -----Original Message-----
> From: Christian Schmidt [mailto:schmidt.christian@...]
> Sent: 13 July 2009 08:19
> To: qooxdoo Development
> Subject: Re: [qooxdoo-devel] Modal blocker is only 101 pixels high!
>
> Hi John,
>
> I can remember, that there was a issue with inline applications and
> modal windows.
>
> Which qooxdoo version do you use?
>
> Cheers,
> Chris
>
> John Spackman schrieb:
>  
>> Hi,
>>
>> Earlier today my modal windows became non-modal - they'd been working fine
>> before and that particular code hadn't been touched.  We use an Inline
>> application and the change which triggered the problem was tracked to the
>> div outside the div outside where the Qooxdoo app is placed - a designer had
>> set div's style to "position: absolute; top: 154px".
>>
>> In qx/ui/root/Page.js, in __syncBlocker the blocker is set to the size of
>> the body.offsetWidth x body.offsetHeight, but in our case the
>> body.offsetHeight was returning 101.  Sure enough the partially opaque
>> blocker only appears at the top of the window.  Oddly, if I put up a modal
>> window during application startup, the blocker is full screen for about a
>> second and then __syncBlocker kicks in and resizes it.
>>
>> Is there a reason for calculating the size instead of just choosing
>> something impossibly big?
>>
>> John
>>
>>
>> ------------------------------------------------------------------------------
>> Enter the BlackBerry Developer Challenge  
>> This is your chance to win up to $100,000 in prizes! For a limited time,
>> vendors submitting new applications to BlackBerry App World(TM) will have
>> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
>> details at: http://p.sf.net/sfu/Challenge
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@...
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>  
>>    
>
>
>  

--
Christian Schmidt
Software Entwickler

1&1 Internet AG - Web Technologies
Ernst-Frey-Straße 9 · DE-76135 Karlsruhe
schmidt.christian@...

Amtsgericht Montabaur / HRB 6484
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel