> To do these optimizations we have added a new concept
> we call variants. If the code above should be removed from the build
> you have to use:
Neat.
I look forward to including lots of this sort of code in our app to tighten up
on debug testing.
Is there a simple "ASSERT" method in qooxdoo
> Our argument at the development time was the same. Background
> intervals are really ugly. I you want to use them, use them. But I
> don't like to have such things in the framework. Finally.
Search on "window.setTimeout" and you will find 7 hits in 0.6.5.
(Why aren't these qx.client.Timer.once?)
> To use a timeout in these cases is always a good idea.
I'm going to put my naive user hat on here.
qooxdoo hides browser complexity. I've really enjoyed the fact that I can just
program to a fixed API, and it works in various browsers.
This behaviour breaks that. If I didn't test in FF I mig
> I also observed something strange, everytime I refreshed my App,
> Firefox took additional 8-10 MB without freeing. Even with disabled
> memory and browser cache Firefox seems not to free memory. I think
> this problem occurs not only when using qooxdoo, but might be a
> general Firefox probl
Hi,
Am 16.02.2007 um 17:37 schrieb [EMAIL PROTECTED]:
> My intention and hope is to be able to copy over new versions of
> qooxdoo with
> no changes to the qooxdoo internals at all, including to any
> tools. Therefore
> what I need for target.mk and/or impl.mk to be modified such that I
>
Hi,
Am 16.02.2007 um 23:07 schrieb Sebastian Werner:
>> What do others think (Andreas Ecker, Derrell, ...)? IMHO we have a
>> nice opportunity here to reduce a source of developer head scratching
>> and unnecessary support queries in qooxdoo. The overhead would be
>> absolutely minimal, and UI up
Am 16.02.2007 um 20:52 schrieb Andreas Junghans:
> Hi,
>
> Am 16.02.2007 um 20:13 schrieb Sebastian Werner:
>
The timer maybe flush the queue in a moment
which is completely wrong and bad.
>>>
>>> No, that's not possible. JavaScript is not multi-threaded, and it's
>>> _absolutely guaran
Just thought I would pass this along for anyone who cares.
Some months ago, I reported problems with "make" reporting
recursion errors. It seems that this problem is internal to
python's regex engine, and it seems limited to 64-bit RHEL.
I'm running RHEL 4.3 x86_64, with python-2.3.4-14.3.
I tri
Hi,
Am 16.02.2007 um 20:13 schrieb Sebastian Werner:
>>> The timer maybe flush the queue in a moment
>>> which is completely wrong and bad.
>>
>> No, that's not possible. JavaScript is not multi-threaded, and it's
>> _absolutely guaranteed_ that the currently executing code (which
>> handles a si
Sebastian Werner <[EMAIL PROTECTED]> writes:
> I don't think here is any misunderstanding on my side. The problem is
> not something regarding JavaScript (control flow, threading, foo,
> bar) it is something with your application. After mouse or keyboard
> events it is 100% guaranteed that t
Am 16.02.2007 um 17:22 schrieb Andreas Junghans:
> Hi Sebastian,
>
> Am 16.02.2007 um 16:19 schrieb Sebastian Werner:
>
>> Andreas Junghans schrieb:
>>> I would suggest to change the flush behaviour in a way that makes it
>>> much more predictable and makes manual flushGlobalQueues calls
>>> comp
I've come across a problem with Samba's use of qooxdoo. The qooxdoo build
system uses the gettext tools for translation. OS X, however, does not have
that package installed by default. Rather than requiring the user to install
the gettext tools, I would much prefer to just detect that it doesn't
Do the scripts yet exist to migrate to the new 0.7 Clazz structure? I see a
number of converted modules, so I assume so. What command line would I use to
upgrade some 0.6.5 source to the new structure? I'd like to try it out.
Thanks,
Derrell
---
Hi Sebastian,
Am 16.02.2007 um 16:19 schrieb Sebastian Werner:
> Andreas Junghans schrieb:
>> I would suggest to change the flush behaviour in a way that makes it
>> much more predictable and makes manual flushGlobalQueues calls
>> completely unnecessary:
>>
>> - In all addToGlobalXXXQueue method
Sebastian Werner <[EMAIL PROTECTED]> writes:
> Hoewever I think you are wrong. It is not a good idea to mix different
> concepts with different needs to solve them with one single solution. It is
> better to differenciate here. You are right in the thing that we need a
> "standardized way for peop
Andreas Junghans schrieb:
> Hi list,
>
> just minutes ago, there was yet another case of someone stumbling
> upon a typical (but really awkward) qooxdoo behaviour: You always
> have to flush the queues yourself if you change the UI in response to
> timer events. The same is true for handling
[EMAIL PROTECTED] schrieb:
> Sebastian Werner <[EMAIL PROTECTED]> writes:
>
>>> That would be a really nice capability. Having a default of true means that
>>> the settings will typically be used as you expect they will. It allows,
>>> however, for the possibility of using the settings for somet
Hi list,
just minutes ago, there was yet another case of someone stumbling
upon a typical (but really awkward) qooxdoo behaviour: You always
have to flush the queues yourself if you change the UI in response to
timer events. The same is true for handling asynchronous server
responses.
IMH
Sebastian Werner <[EMAIL PROTECTED]> writes:
>> That would be a really nice capability. Having a default of true means that
>> the settings will typically be used as you expect they will. It allows,
>> however, for the possibility of using the settings for something other than
>> what we/you (th
[EMAIL PROTECTED] schrieb:
> Sebastian Werner <[EMAIL PROTECTED]> writes:
>
>> Normally this should changed in the class. Settings where never
>> thought to be used in such a way like in Json. The restriction is a
>> good choice in about 95% of cases. The problem of Json you have
>> mentione
Hi Jeroen,
Am 16.02.2007 um 15:17 schrieb Jeroen Vriesman:
> I tried to make something move, just testing, simple function with an
> atom "c1":
>
> var timer = new qx.client.Timer(50);
>
> function move(e) {
> var x = c1.getLeftValue();
> c1.setLeft( x + 1 );
> }
> timer.addEvent
What Makefile have you used? The skeleton one? Seems to be the one from
the sample directory. Please search for layout.js in your Makefile.
Greetings,
Sebastian
Tobias Koller (GERMO GmbH) schrieb:
> Hello,
>
>
>
> I try to make the source code form my app.
>
>
>
> The following error oc
Sebastian Werner <[EMAIL PROTECTED]> writes:
> Normally this should changed in the class. Settings where never
> thought to be used in such a way like in Json. The restriction is a
> good choice in about 95% of cases. The problem of Json you have
> mentioned can maybe solved using the log le
Hi all,
I tried to make something move, just testing, simple function with an
atom "c1":
var timer = new qx.client.Timer(50);
function move(e) {
var x = c1.getLeftValue();
c1.setLeft( x + 1 );
}
timer.addEventListener("interval", move );
timer.start();
It works, but atom onl
Hello,
I try to make the source code form my app.
The following error occurs:
*Generating source/script/layout.js
Python: can't open file 'tool/layout.js': ["Errno 2] No such file or
directory
Make: *** [layout-source] Fehler 2
I never had a layout.py-File. There is one in the sample
Hello again J
I want to migrate version 0.6.4 to 0.6.5.
I tried this in cygwin:
/cygdrive/c/project/testapp/qooxdoo-0.6.5-sdk/frontend/framework/tool/ge
nerator.py -class-path
/cygdrive/c/project/testapp/qooxdoo-0.6.4-sdk/frontend/application/testa
pp/source/class \ --migrate-source -mig
Hello all,
has anyone experience with integrating qooxdoo into a classical web
application with many pages, that uses a serverside framework like
Struts for the page flow?
I mean qooxdoo is excellent for building single-page Webapps with its
Layout Managers and rich Widgets. But is it possible
No,
the documentation is good. It was my fault.
I thought I have to write the Root-Path of my VirtualDirectory (I don't know
why ;) ).
In my case: ../../../../ (this is the root-Directory of my VirtualDirectory).
So don't worry about the quality of your docu ;)
Thanks!
-Ursprüngliche Nachr
Well. Maybe you can send us a suggestion how to better document this part?
Greetings,
Sebastian
Tobias Koller (GERMO GmbH) schrieb:
> Hello,
>
>
>
> i solved the problem ;)
>
> i had to write this into the makefile:
>
> QOOXDOO_URI = ../../../../qooxdoo-0.6.5-sdk
>
>
>
> I misunderstoo
Hugh Gibson schrieb:
> However, FF 1.5 and 2.0 never seems to give memory back.
I also observed something strange, everytime I refreshed my App, Firefox
took additional 8-10 MB without freeing. Even with disabled memory and
browser cache Firefox seems not to free memory. I think this problem
oc
Hello,
i solved the problem ;)
i had to write this into the makefile:
QOOXDOO_URI = ../../../../qooxdoo-0.6.5-sdk
I misunderstood the description "# The same as above, but from the
webserver point of view".
Sorry for the List-Spamming ;)
Thanks tobi
Von: [EMAIL PROTECTED]
[
Hello,
i tried to put the sample-Application from the
VirtDir\qooxdoo-0.6.5-sdk\frontend\application\sample
To
VirtDir\sample.
I changed the makeFile to:
# Location of your qooxdoo distribution
# Could be relative from this location or absolute
#
QOOXDOO_PATH = ../qooxdoo-0.6.5-s
32 matches
Mail list logo
