Thanks Sebastion.
You make a good point about different UI libraries. And it's a pity that there
are so many different ways to do things in javascript, to the point where many
people are writing their own subclassing utilities. This makes integration and
even IDE use a problem.
In fact I have
[EMAIL PROTECTED] wrote:
> *push*
>
> Can anybody reproduce the bugs I encountered with the files
> attached to my prior mail on 2007/09/11?
>
>
Fabio,
I'm sorry but I cannot get hold of your attachments anymore, and the
copies of your posting on Nabble and Gmain are just garbage. Could you
try
Internationalization
When using internationalization with an APPLICATION_SOURCE_PATH containing
spaces (which are correctly escaped, like "/cygdrive/d/my\ dir" - without
quotes!), xgettext failes with the following error, thus only producing
empty
.po-files, no messa
Hi all,
First, let me say that I've been using Qooxdoo for a few months and
globally I'm very pleased with it. I'd wish more documentation but
well...
Anyway, the current spinner widget didn't seem to support floating
point numbers, so here is a patch to implement such support.
What does this pa
On 9/21/07, Kolodziej Christian <[EMAIL PROTECTED]> wrote:
>
> Yesterday I've updated the framework rom 0.7.1 to 0.7.2. Everything
> seemed to work well, but now I've discovered an error when trying to display
> a number of type double in my table. This number is 127.99 for instance,
> but "127cld
Hi,
When I dispose my app using qx.core.Object.dispose() (and
disposerDebugLevel==1) I get the following message:
Missing destruct definition for '__user$dataRowRenderer' in
qx.ui.table.Table[748]: [object qx.ui.table.rowrenderer.Default]
>From the Table source:
destruct : function()
{
this
Qooxdoo properties are very useful and powerful means for applications
developing.
But properties could be more powerful if they had some options and abilities
which are absent now.
1) It would be useful to have an option in property description that allows
skipping comparison between new and exi
Hello Fabian,as far as I can tell, Derrell's JsonRpc-Classes broke - they no longer work for me. My app worked before the update, now I get the warning and the app doesn't work anymore. I need to investigate more closely-maybe it is my own mistake, but since I have the same symptoms as david, I d
Hi Fabian,
I also tried with following code:
For adding Flex application in qooxdo:
var flash = new qx.ui.embed.Flash("SlideAnnotation.swf");
flash.setHtmlAttribute('id', 'Connection');
flash.setParam('src', 'SlideAnnotation.swf')
flash.setParam('allowScriptAccess
Yesterday I've updated the framework rom 0.7.1 to 0.7.2. Everything seemed to
work well, but now I've discovered an error when trying to display a number of
type double in my table. This number is 127.99 for instance, but
"127cldr_number_decirmal_separator99" is displayed (before the update "127
Fabian Jakobs schrieb:
> frederic schrieb:
>
>> Fabian,
>> finally I choice to patch the Rpc.js in qx 0.7.2 removing only 2 "getData".
>> Warnings disappear but I had to update my script to work properly :
>>
>> In qx 0.7.1 :
>>
>> var req=new qx.io.remote.Rpc();
>> req.set({url: SERVICE_URL, se
bibliograph schrieb:
> Hello,
>
> I don't think it is a good idea to introduce API changes which do not
> add any functionality and break people's code like this. Couldn't this
> have waited until 0.8?
>
> Sorry, but it is a bit frustrating to lose time over things that have no
> apparent benefi
frederic schrieb:
> Fabian,
> finally I choice to patch the Rpc.js in qx 0.7.2 removing only 2 "getData".
> Warnings disappear but I had to update my script to work properly :
>
> In qx 0.7.1 :
>
> var req=new qx.io.remote.Rpc();
> req.set({url: SERVICE_URL, serviceName: myservice, crossDomain: fal
I followed the discussion regarding FF and memory. As far as I can see, the
memory your application need is never given back to the system. Not by
reload and not by leaving the application page. The only way is to restart
the browser.
We have an application with huge trees to browse (virtualTree).
Hello,
I don't think it is a good idea to introduce API changes which do not
add any functionality and break people's code like this. Couldn't this
have waited until 0.8?
Sorry, but it is a bit frustrating to lose time over things that have no
apparent benefit. ;-(
Christian
Derrell Lipman
15 matches
Mail list logo
