Thanks !
De la: thron7
Către: qooxdoo Development
Trimis: Vineri, 28 Iunie 2013 8:09:19
Subiect: Re: [qooxdoo-devel] qooxdoo 3
On 06/28/2013 06:11 AM, tedi tedi wrote:
When will qooxdoo 3 be released? and what will be the new features it comes
with?
>
On 06/28/2013 06:11 AM, tedi tedi wrote:
When will qooxdoo 3 be released? and what will be the new features it
comes with?
Is there a page that answers this question?
Indeed, there is:
http://news.qooxdoo.org/release-schedules
T.
When will qooxdoo 3 be released? and what will be the new features it comes
with?
Is there a page that answers this question?
Thanks :)
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.s
Do not hesitate to enrich the "reallife examples" area once your application
is made (if possible, of course)
http://qooxdoo.org/community/real_life_examples
Regards
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/class-extend-qx-ui-toolbar-ToolBar-fireEvent-tp7583957p7583
qooxdoo => simple and clever
Tanks!!
Best Regards.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/class-extend-qx-ui-toolbar-ToolBar-fireEvent-tp7583957p7583987.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
Hi,
You lauch event with Boton_Cambiar_Empresa context.
Add the third parameter to change context, like this
line 77 => Boton_Cambiar_Empresa.addListener( "execute", this.Nueva_Empresa,
*this*);
Now, "this" is toolbar context inside Nueva_Empresa function (line 131, 132,
133)
http://tinyurl.co
Hi,
Line 77 => as this
Boton_Cambiar_Empresa.addListener( "execute", this.Nueva_Empresa);
Don't invoke Nueva_Empresa, just the name of it.
Bye
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/class-extend-qx-ui-toolbar-ToolBar-fireEvent-tp7583957p7583984.html
Sent from the q
> Ok. That worked. Finally ;-)
>
> Looks like qx.ui.container.Composite is missing a ";" in the very end.
That's right, it does. But why should that be a problem?! I've run this
class in various browsers, all without problems.
Are you setting 'use strict' somewhere? Or is there an issue in your
c
Ok. That worked. Finally ;-)
Looks like qx.ui.container.Composite is missing a ";" in the very end.
Cheers,
Cajus
Am 27.06.13 17:00, schrieb thron7:
> On 06/27/2013 04:17 PM, Cajus Pollmeier wrote:
>> Hmm. Neither OPTIMIZE, nor "format: true" show any effect.
> Did you run 'distclean' in between
Sorry.but
With this modified code http://tinyurl.com/oqbx8vc i get the error
[20:37:06.296] 268585 playground.Application[18-0]: Unfortunately, an
unrecoverable internal error was caused by your code. This may prevent the
playground application to run properly.
Failed to add event listener f
On 06/27/2013 04:17 PM, Cajus Pollmeier wrote:
> Hmm. Neither OPTIMIZE, nor "format: true" show any effect.
Did you run 'distclean' in between?!
> Maybe because I'm building a separate version for every engine? Or - is
> there a place where these options can be inserted so that it works in
>
Hmm. Neither OPTIMIZE, nor "format: true" show any effect. Maybe because I'm
building a separate version for every engine? Or - is there a place where these
options can be inserted so that it works in
every case?
{
"let" :
{
...
"OPTIMIZE" : []
},
"build" :
{
"desc"
On 06/27/2013 02:04 PM, Cajus Pollmeier wrote:
> On 27.06.2013 12:38, thron7 wrote:
>> Cajus,
>>
>> - What is the commit that you pulled? (The issue might have been fixed
>> meanwhile)
> I don't know, but I tried again using
> d6b28021dc9dd527a4604cb37acb220f2079a118 which seems to be the latest
On 27.06.2013 12:38, thron7 wrote:
> Cajus,
>
> - What is the commit that you pulled? (The issue might have been fixed
> meanwhile)
I don't know, but I tried again using d6b28021dc9dd527a4604cb37acb220f2079a118
which seems to be the latest one available on github. Same error.
Chrome:
Uncaug
Cajus,
- What is the commit that you pulled? (The issue might have been fixed
meanwhile)
- Which code caused the exception? A minimal example to trigger it would
be helpful.
T.
On 06/27/2013 11:56 AM, Cajus Pollmeier wrote:
> Hiho,
>
> I'm updating to qx master for a development project from t
Hiho,
I'm updating to qx master for a development project from time to time - just to
see if we're on the right track for qx 3.0.
For the last pull, I've noticed that source works fine, but build bails out
claiming "Uncaught SyntaxError: Unexpected token &&". I gave it a quick glance,
but gave
Hi Fritz,
I was able to reproduce the bug you are describing, but only in the playground.
This is due to the structure of the playground.
So your code is working well.
Regards,
Romeo
-Ursprüngliche Nachricht-
Von: Fritz Zaucker [mailto:fritz.zauc...@oetiker.ch]
Gesendet: Mittwoch, 26. J
Indeed, you have to stick to the JSDoc syntax rules (which include /**
... */ comment decorations).
T.
On 06/27/2013 10:10 AM, fprijate wrote:
> Hi
>
> Sorry.
>
> Before I had asserts in block comments without '*' at the begining of
> every comment row, which
> was Ok:
>
> /***
>
>
Hi
Sorry.
Before I had asserts in block comments without '*' at the begining of
every comment row, which
was Ok:
/***
#assert(...)
***/
after change to
/***
@assert(...)
***/
doesn't work anymore.
Changing to
/**
*
* @assert(...)
*
*/
everything is OK
sorry for interrupting again ;)
A very good read on this topic is this chapter here:
http://books.google.de/books?id=6TAODdEIxrgC&lpg=PP1&hl=de&pg=PA33#v=onepage&q&f=false
of the "Java Script - The definitive guide" ( *the* Book on JavaScript) Pages
33 and 34.
On 6/27/2013 9:10 AM Peter Schne
...like Derrell said, the value you are setting is not 'NULL'.
Here some examples how to create some (not-null) values:
var x = 1/0; // => x is Infinity
var x = -1/0; // => x is -Infinity
var x = 0/0; // => x is NaN (Not A Number)
var x; // => x is undefined
var x = null; // =>
21 matches
Mail list logo
