I can confirm r16518 is fine.
Ian Horst
thron7 wrote:
> Ian,
>
> we're at r16517 currently. Could you just check this revision and get
> back if you still have the problem? Johnny is working on a difficult
> issue and sometimes the trunk is broken.
>
> Thomas
>
> Ian Horst wrote:
>> Updated
Ian,
we're at r16517 currently. Could you just check this revision and get
back if you still have the problem? Johnny is working on a difficult
issue and sometimes the trunk is broken.
Thomas
Ian Horst wrote:
> Updated my qooxdoo trunk to latest and got js error:
>
> Dock.js (line 810)
> child
Hello everybody,
I want to inform you that the trunk is working again.
Did I heard "bleeding edge"? ;-)
Kind regards,
Jonathan
Fabian Jakobs wrote:
> Hello Ian,
>
> the trunk is temporarily broken. We are currently working hard to fix
> it. We'll let you know when the trunk is stable again.
That's ok. That's what trunk is for. Thanks, it would be nice to know when
trunk is back. :)
I just use trunk for development and production server. I wanted to inform
others which use trunk the same way I do.
Ian Horst
Fabian Jakobs wrote:
> Hello Ian,
>
> the trunk is temporarily broken. W
Hello Ian,
the trunk is temporarily broken. We are currently working hard to fix
it. We'll let you know when the trunk is stable again. Meanwhile you
should revert to your previous revision.
Best Fabian
> Updated my qooxdoo trunk to latest and got js error:
>
> Dock.js (line 810)
> children is
Updated my qooxdoo trunk to latest and got js error:
Dock.js (line 810)
children is null
var length = children.length;
I rolled back my qooxdoo to r16509
--
Ian Horst
-
This SF.Net email is sponsored by the Moblin Your
