Bug 4012 ...
Cheers,
Fritz
On Fri, 20 Aug 2010, Alexander Steitz wrote:
> Hi Fritz,
>
> the generator should be aware of this case. So I guess you can go ahead
> and file a bug report for this issue.
>
> Thanks for sharing this info!
>
> cheers,
> Alex
>
> Am 20.08.2010 08:48, schrieb Fritz Za
Hi Fritz,
the generator should be aware of this case. So I guess you can go ahead
and file a bug report for this issue.
Thanks for sharing this info!
cheers,
Alex
Am 20.08.2010 08:48, schrieb Fritz Zaucker:
> the following worked for me with pre1.3 until I did an svn update last night
> (ha
Hi,
the following worked for me with pre1.3 until I did an svn update last night
(hadn't updated for a few days). It fails with 1.2.0 and with the current
trunk (I am not sure that it will always fail):
Create two classes
myapp.Ticket.Test (.../source/class/myapp/Ticket/Test.js)
The trunk, 20551
thron7 wrote:
>
> Matthew Gregory wrote:
>> Hi All,
>> I think I might have stumbled across a generator bug. In a build version
>> of our app, windows are not displayed at all. I have tracked it down to
>> the following: calling this.getBounds() on a window returns this:
>>
>>
Matthew Gregory wrote:
> Hi All,
> I think I might have stumbled across a generator bug. In a build version
> of our app, windows are not displayed at all. I have tracked it down to
> the following: calling this.getBounds() on a window returns this:
>
> "function () { var Q = this.__dT; if (!Q)
Hi All,
I think I might have stumbled across a generator bug. In a build version
of our app, windows are not displayed at all. I have tracked it down to
the following: calling this.getBounds() on a window returns this:
"function () { var Q = this.__dT; if (!Q) { Q = this.__dT = new
(qx.ui.core.
Here's an interesting one with 0.8.2-pre but I suspect it applies everywhere.
I had a member like:
someName:function(){
var qx = ..
}
Interestingly enough I didn't use the qx namespace within that
function, so it worked fine in the source version. But it made the
build version bark.
It was s
Hi Kenny,
> Is there a list of specific bugs/changes?
You can look at this bugzilla query, which shows tool-related bugs for
0.8.1:
*http://preview.tinyurl.com/6x8ndd*
> I had a problem when optimize
>
There were various rumors about optimization issues, but I'm not aware
of any reporte
Tobi,
I could repro the issue with a simple skeleton, but only with the
'source' version of the app. But I'm not sure I will be able to fix it
for 0.8.1. But I will open up a bug for it anyway, and set you on CC.
Please stick to the cache work-around meanwhile.
Thanks,
Thomas
Tobias Oetiker w
thron7 wrote:
> Hi all,
>
> I would like to declare tomorrow, Tuesday December 16th, Generator Bug
> Hunting Day :-).
>
> We have applied a lot of changes to the build process recently, some
> fixing bugs, but also user-visible changes to config keys and their
> processing.
Is there a list of
thanks, tobi, i'll look into that
t.
Tobias Oetiker wrote:
> Thomas,
>
> one thing that keeps occuring to me (and has been for some time) is
> that if I run 'lint' and lint runs into trouble due to a syntax
> error in the javascript code, then next time I try to run a normal
> source or build tas
Thomas,
one thing that keeps occuring to me (and has been for some time) is
that if I run 'lint' and lint runs into trouble due to a syntax
error in the javascript code, then next time I try to run a normal
source or build task some classes can not be found anymore and the
problem only goes away a
Hi all,
I would like to declare tomorrow, Tuesday December 16th, Generator Bug
Hunting Day :-).
We have applied a lot of changes to the build process recently, some
fixing bugs, but also user-visible changes to config keys and their
processing. All of you who are working on applications using
Hi David,
the variableoptimizer.py module have been updated in the trunk after the
release of qx 0.7.2 ; perhaps this update breaks your code ; have you try
with 0.7.2 ?
cheers.
fred
dperez wrote:
>
> Through trial and error, I've come to the conclusion that the dangerous
> flag is:
> --optimi
Through trial and error, I've come to the conclusion that the dangerous flag
is:
--optimize-strings
dperez wrote:
>
> I have this simple class:
>
> qx.Class.define('CeldaClicable', {
> extend: qx.ui.table.cellrenderer.Default,
>
> members: {
> _getCellStyle: fu
I have this simple class:
qx.Class.define('CeldaClicable', {
extend: qx.ui.table.cellrenderer.Default,
members: {
_getCellStyle: function(cellInfo) {
return (cellInfo.style || '') + ';cursor:pointer
!important'
}
16 matches
Mail list logo
