Ian Horst | 3 Jul 16:09

qx.ui.table.model.Simple.setSortMethods()

I wonder why there are 2 sort methods, one for ascending, second for descending.

It's enough to define ascending sort method. Descending is just
reverse of ascending sort method.

ascending:
ascSortMethod();

descending:
- ascSortMethod();

---
Ian

------------------------------------------------------------------------------
monika.falk | 3 Jul 13:56
Favicon

Appearance id in table cell

Hi Everyone
 
I need to change an appearance in table cell. However I cannot find anywhere the id of the table cell. Any help would be much appreciated.
 
S pozdravem / Best regards,
 
Monika Falk, Software Specialist
 
Tieto
email monika.falk <at> tieto.com, direct +420597459905,  fax +420597459928
Výstavní 292/13, 70200 Ostrava, Czech Republic,  www.tieto.com

Meet the new Tieto: www.tieto.com/newtieto
 
Please note: The information contained in this message may be legally privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorised use, distribution or copying of this communication is strictly prohibited. If you have received this
 
 
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Java RPC + Qooxdoo as Maven artifacts

Thank you for your answer Jean-Baptiste,
In fact, I've already built the JAR with ant and I'm ready to deploy it 
in the Jspresso Maven repository. I just wanted to check with the 
owner(s) of the code if he doesn't have any problem with that - even 
though the license(s) allows to do so.

Regards,
Vincent

Jean-Baptiste BRIAUD -- Novlog a écrit :
> Hi,
>
> I'm not a big fan of Maven and so I'm not using it, but there is an  
> ant build.xml file if you checkout JavaRPC from SVN.
> As Maven rely on ant, it may "fit the hole".
> If it helps, I can provide you a jar file quickly.
>
>
> On Jul 2, 2009, at 15:34 , Vincent Vandenschrick wrote:
>
>   
>> Hi Qooxdoo team,
>>
>> I'm making quite good progress in porting the Jspresso framework to
>> Qooxdoo. I'm almost 100% done with it but now comes the "hard" part
>> (couldn't guess it at first sight) : the Maven build integration ;-)
>>
>> I'm almost done with configuring the Qooxdoo toolchain (manifest +
>> config) for eating a more standard maven project layout (e.g.
>> src/main/js, src/main/resources, target/, ...) and the next step
>> constists in allowing the developer to do as little manual setup as
>> possible on the build machine.
>> I dropped the idea of running the build with Jython since I could'nt  
>> get
>> it right (the "maximum recursion depth" problem). So I made my mind on
>> using a normal python interpreter so this one will have to be manually
>> installed if not already there (M$...). So far, so good.
>>
>> The question is now to have the java RPC backend packaged and deployed
>> as a Maven artifact (a jar containing the compiled classes) for later
>> inclusion as a dependency in the Maven built WAR. I can manage to  
>> build
>> the JAR from the contrib source code and my proposition is to host the
>> resulting unmodified archive into the Jspresso Maven repository so  
>> that
>> it gets publicly accessible to the build. I think that the license
>> allows it but I would like to hear that you don't have any objection
>> against it.
>>
>> Same goes for the Qooxdoo framework and toolchain. The idea I have  
>> is to
>> make a "light" zip archive of Qooxdoo that would only contain the
>> framework JS files + resources + python toolchain (I would mainly get
>> rid of the "application" and "component" directories). Then again, I
>> could host it into the Jspresso Maven repository so that it would get
>> automatically downloaded, unpacked and used during the build of a
>> Jspresso application. Of course this Qooxdoo artifact will be  
>> versioned
>> (0.8.2, 0.8-SNAPHOT, ...) so that a target application build can run
>> against a predefined Qooxdoo release depending on what has been  
>> declared
>> into the project POM file. Same question than before : any objection /
>> licensing issue against it ?
>>
>> If you don't see any showstopper for both points, I think I can manage
>> to seamlessly integrate the Qooxdoo build into the Jspresso Maven  
>> build
>> with only python as a requirement. Of course, all licensing, IP, site
>> reference informations would be retained in both deployed artifacts.
>>
>> Thanks in advance,
>> Vincent
>>
>> -- 
>> Vincent Vandenschrick
>> Jspresso Framework
>> http://www.jspresso.org
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel <at> lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>     
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>   

--

-- 
Vincent Vandenschrick
 Jspresso Framework
 http://www.jspresso.org

------------------------------------------------------------------------------

Java RPC + Qooxdoo as Maven artifacts

Hi Qooxdoo team,

I'm making quite good progress in porting the Jspresso framework to 
Qooxdoo. I'm almost 100% done with it but now comes the "hard" part 
(couldn't guess it at first sight) : the Maven build integration ;-)

I'm almost done with configuring the Qooxdoo toolchain (manifest + 
config) for eating a more standard maven project layout (e.g. 
src/main/js, src/main/resources, target/, ...) and the next step 
constists in allowing the developer to do as little manual setup as 
possible on the build machine.
I dropped the idea of running the build with Jython since I could'nt get 
it right (the "maximum recursion depth" problem). So I made my mind on 
using a normal python interpreter so this one will have to be manually 
installed if not already there (M$...). So far, so good.

The question is now to have the java RPC backend packaged and deployed 
as a Maven artifact (a jar containing the compiled classes) for later 
inclusion as a dependency in the Maven built WAR. I can manage to build 
the JAR from the contrib source code and my proposition is to host the 
resulting unmodified archive into the Jspresso Maven repository so that 
it gets publicly accessible to the build. I think that the license 
allows it but I would like to hear that you don't have any objection 
against it.

Same goes for the Qooxdoo framework and toolchain. The idea I have is to 
make a "light" zip archive of Qooxdoo that would only contain the 
framework JS files + resources + python toolchain (I would mainly get 
rid of the "application" and "component" directories). Then again, I 
could host it into the Jspresso Maven repository so that it would get 
automatically downloaded, unpacked and used during the build of a 
Jspresso application. Of course this Qooxdoo artifact will be versioned 
(0.8.2, 0.8-SNAPHOT, ...) so that a target application build can run 
against a predefined Qooxdoo release depending on what has been declared 
into the project POM file. Same question than before : any objection / 
licensing issue against it ?

If you don't see any showstopper for both points, I think I can manage 
to seamlessly integrate the Qooxdoo build into the Jspresso Maven build 
with only python as a requirement. Of course, all licensing, IP, site 
reference informations would be retained in both deployed artifacts.

Thanks in advance,
Vincent

--

-- 
Vincent Vandenschrick
 Jspresso Framework
 http://www.jspresso.org

------------------------------------------------------------------------------
Ian Horst | 2 Jul 13:07

Firefox 3.5 and multiple requests in queue time out

Hi all,

RequestQueue handles the first 3 requests fine in FF3.5, but the
following requests in queue time out ALWAYS.

Code to replicate.
------------------------------------------------
qx.core.Setting.set('qx.ioRemoteDebug', true);
for (var i = 0; i < 4; i++) {
    var request = new qx.io.remote.Request('sleep.php');
    request.send();
}
------------------------------------------------

sleep.php
------------------------------------------------
<?php
    sleep(10);
------------------------------------------------

firebug log
------------------------------------------------
 ....loading....
3629ms qx.core.Init: Load runtime: 3629msfrontend (line 53)
3649ms qx.io.remote.Request[13]: State: queuedfrontend (line 53)
3651ms qx.io.remote.RequestQueue[14]: Progress: 0/1frontend (line 53)
3653ms qx.io.remote.RequestQueue[14]: Progress: 1/1frontend (line 53)
3656ms qx.io.remote.Exchange[16]: Using implementation:
qx.io.remote.transport.XmlHttpfrontend (line 53)
3663ms qx.io.remote.transport.XmlHttp[17]: State: configuredfrontend (line 53)
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912057
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912057
	
		5.02s	XmlHttp.js (line 323)
3669ms qx.io.remote.Request[19]: State: queuedfrontend (line 53)
3671ms qx.io.remote.RequestQueue[14]: Progress: 1/2frontend (line 53)
3672ms qx.io.remote.RequestQueue[14]: Progress: 2/2frontend (line 53)
3675ms qx.io.remote.Exchange[1a]: Using implementation:
qx.io.remote.transport.XmlHttpfrontend (line 53)
3677ms qx.io.remote.transport.XmlHttp[1b]: State: configuredfrontend (line 53)
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912078
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912078
	
		5.53s	XmlHttp.js (line 323)
3682ms qx.io.remote.Request[1c]: State: queuedfrontend (line 53)
3684ms qx.io.remote.RequestQueue[14]: Progress: 2/3frontend (line 53)
3702ms qx.io.remote.RequestQueue[14]: Progress: 3/3frontend (line 53)
3706ms qx.io.remote.Exchange[1d]: Using implementation:
qx.io.remote.transport.XmlHttpfrontend (line 53)
3709ms qx.io.remote.transport.XmlHttp[1e]: State: configuredfrontend (line 53)
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912091
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912091
	
		5.47s	XmlHttp.js (line 323)
3715ms qx.io.remote.Request[1f]: State: queuedfrontend (line 53)
3718ms qx.io.remote.RequestQueue[14]: Progress: 3/4frontend (line 53)
3720ms qx.core.Init: Main runtime: 90msfrontend (line 53)
3726ms qx.core.Init: Finalize runtime: 4msfrontend (line 53)
8669ms qx.io.remote.RequestQueue[14]: Timeout: transport 16frontend (line 53)
8673ms qx.io.remote.RequestQueue[14]: 5014ms > 5000msfrontend (line 53)
8675ms qx.io.remote.Exchange[16]: Timeout: implementation 17frontend (line 53)
8677ms qx.io.remote.transport.XmlHttp[17]: Timeout...frontend (line 53)
8679ms qx.io.remote.transport.XmlHttp[17]: State: timeoutfrontend (line 53)
8681ms qx.io.remote.transport.XmlHttp[17]: Ignore Ready State
Changefrontend (line 53)
8686ms qx.io.remote.Exchange[16]: State: configured => timeoutfrontend (line 53)
8690ms qx.io.remote.Request[13]: State: timeoutfrontend (line 53)
8695ms qx.io.remote.RequestQueue[14]: Progress: 2/3frontend (line 53)
8697ms qx.io.remote.RequestQueue[14]: Progress: 3/3frontend (line 53)
8701ms qx.io.remote.Exchange[16]: Using implementation:
qx.io.remote.transport.XmlHttpfrontend (line 53)
8705ms qx.io.remote.transport.XmlHttp[17]: State: configuredfrontend (line 53)
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912124
GET http://localhost/core2/hd2/public/sleep.php?nocache=1246532912124
	
		5.47s	XmlHttp.js (line 323)
9169ms qx.io.remote.RequestQueue[14]: Timeout: transport 1dfrontend (line 53)
9174ms qx.io.remote.RequestQueue[14]: 5464ms > 5000msfrontend (line 53)
9176ms qx.io.remote.Exchange[1d]: Timeout: implementation 1efrontend (line 53)
9178ms qx.io.remote.transport.XmlHttp[1e]: Timeout...frontend (line 53)
9181ms qx.io.remote.transport.XmlHttp[1e]: State: timeoutfrontend (line 53)
9183ms qx.io.remote.transport.XmlHttp[1e]: Ignore Ready State
Changefrontend (line 53)
9187ms qx.io.remote.Exchange[1d]: State: configured => timeoutfrontend (line 53)
9190ms qx.io.remote.Request[1c]: State: timeoutfrontend (line 53)
9194ms qx.io.remote.RequestQueue[14]: Progress: 2/2frontend (line 53)
9196ms qx.io.remote.RequestQueue[14]: Timeout: transport 1afrontend (line 53)
9198ms qx.io.remote.RequestQueue[14]: 5494ms > 5000msfrontend (line 53)
9200ms qx.io.remote.Exchange[1a]: Timeout: implementation 1bfrontend (line 53)
9203ms qx.io.remote.transport.XmlHttp[1b]: Timeout...frontend (line 53)
9206ms qx.io.remote.transport.XmlHttp[1b]: State: timeoutfrontend (line 53)
9209ms qx.io.remote.transport.XmlHttp[1b]: Ignore Ready State
Changefrontend (line 53)
9212ms qx.io.remote.Exchange[1a]: State: configured => timeoutfrontend (line 53)
9216ms qx.io.remote.Request[19]: State: timeoutfrontend (line 53)
9219ms qx.io.remote.RequestQueue[14]: Progress: 1/1frontend (line 53)
14170ms qx.io.remote.RequestQueue[14]: Timeout: transport 16frontend (line 53)
14173ms qx.io.remote.RequestQueue[14]: 5469ms > 5000msfrontend (line 53)
14176ms qx.io.remote.Exchange[16]: Timeout: implementation 17frontend (line 53)
14179ms qx.io.remote.transport.XmlHttp[17]: Timeout...frontend (line 53)
14181ms qx.io.remote.transport.XmlHttp[17]: State: timeoutfrontend (line 53)
14185ms qx.io.remote.Exchange[16]: State: configured =>
timeoutfrontend (line 53)
14189ms qx.io.remote.Request[1f]: State: timeoutfrontend (line 53)
14192ms qx.io.remote.RequestQueue[14]: Progress: 0/0frontend (line 53)

------------------------------------------------

---
Ian Horst

------------------------------------------------------------------------------
Helder Magalhães | 1 Jul 13:26

Contrib: Hijax and cache directory


Hi everyone,

Just noticed "Hijax" being committed to the contrib repository. Without
investigating the contribution itself, I've noticed a "cache" directory
("Hijax/trunk/demo/default/cache") being committed, something which probably
wasn't intended.

I'd report this as an issue but "Hijax" wasn't added to the contrib
"product" yet [1]. ;-)

Hope this helps,
 Helder

[1] http://bugzilla.qooxdoo.org/enter_bug.cgi?product=contrib
--

-- 
View this message in context: http://www.nabble.com/Contrib%3A-Hijax-and-cache-directory-tp24288225p24288225.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Raymond Cote | 1 Jul 21:33

How to restrict keystrokes in a TextField.

Hello,

I have a TextField which I'd like to limit to accepting only digits.

I've added a listener to the TextField and can grab each keystroke as it 
is entered.

However, I'm unclear as to how I could decide whether or not to let this 
keystroke through.
The TextField is not being updated until after I receive the keystroke, 
so I suspect there's something I can do to say "not this keystroke."

Any hints and pointers greatly appreciated.

Thanks
--Ray

------------------------------------------------------------------------------
Narasimha Patkar | 1 Jul 20:03

Local time-out error for async RPC call

Hi,

I am using async RPC call in an application built using Qooxdoo 0.8.2-sdk and I am using example back-end provided with Qooxdoo implemented in perl.

In the client application I have something like this,

###########################################
   var rpc = new qx.io.remote.Rpc();
   rpc.setTimeout(1000);
   rpc.setUrl("http://127.0.0.1:8080/cgi-bin/Qooxdoo/.qxrpc");
   rpc.setServiceName("qooxdoo.test");
   // asynchronous call
   var handler = function(result, exc) {
   if (exc == null) {
        alert("Result of async call: " + result+exc);
   } else {
       alert("Exception during async call: " + exc+result);
      }
   };

   rpc.callAsync(handler, "echo", "Test");
  
try {
    var result = rpc.callSync("echo", "here");
    alert("Result of sync call: " + result); } catch (exc) {
    alert("Exception during Gulnaz call: " + exc); }
###############################################

And I have deployed the server back end <at> apache server's cgi-bin directory and jsonrpc.pl has following path settings

*************************************************
# Change this space-separated list of directories to include
# Qooxdoo::JSONRPC.pm and co-located Services
use lib qw(. Qooxdoo Qooxdoo\Services\qooxdoo);
*************************************************

With this I am getting null as result for Sync call and timeout for async call.

Can you please help me in this regard, as I am new to Qooxdoo.

Regards
Narasimha
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
Andreas Junghans | 1 Jul 13:28

Re: Refactored JavaRpc - JSONObject from json.org

Hi Jean-Baptiste,

Am 01.07.2009 um 09:03 schrieb Jean-Baptiste BRIAUD -- Novlog:

>>> BTW, what about the transient Java keyword ? Are transient  
>>> attributes
>>> excluded from json serialization ?
>>
>> Just to make it clear, this point no longer concerns the low-level
>> JSON lib (layer b2 above), but the higher level serialization of Java
>> objects (layer b1). The current implementation doesn't work by  
>> looking
>> at member variables. Instead, getters and setters according to the
>> JavaBean convention are examined. And there's no way to tell whether
>> an underlying member variable is transient by looking at its getter.
>>
>> It works this way in order to be able to transmit almost arbitrary
>> Java objects. There are often classes that you cannot change (e.g.
>> from 3rd party libs) and that are not serializable (and thus don't  
>> use
>> the transient keyword for their attributes). On the other hand,  
>> almost
>> every Java class adheres to the JavaBean convention. So by looking at
>> the accessor methods, we usually can transmit these objects just fine
>> (except for reference cycles, but this problem would also occur when
>> looking at the attributes directly, and you can use the filter
>> mechanism to avoid it).
>>
>
> That the thing. After some more thoughts about my needs and JavaRPC, I
> can now explain why I'll need to add some behavior, at least in my
> code using JavaRPC and later on inside JavaRPC if anyone is
> interested : I can't rely only on that bean philosophy.
>
> It doesn't fit my need to serialize any property that have a getter
> and to keep OO and maintenance, I want that choice (serialize or not)
> to be in the bean rather that in a global filter at servlet level.
> Also, as I'm using Hibernate, the runtime introspection of my bean is
> different than the source code because of AOP dynamic code injection
> and I'll also have to handle that after the bean thing.
>
> Basically, I need to use existing bean than I can modify but I can't
> have new classes just for serialization.
> I also want to declare which attribute will not be serializable on a
> per attribute basis (not getter method basis).
>
> I also don't want to rely on a global filtering mecanism at Servlet
> level, I want to declare that in the bean because it depends of the
> bean.
> If there are some global rules, it is Ok to use a global property
> filter in the servlet that would apply to all bean.
> finally, I can't think to a simpler way to do that than using the
> transient Java keyword.(not the @Transient JPA annotation, it is
> different).
>
> To implement that behavior without touching JavaRPC code, I used the
> property filter at servlet level in a generic way : I explore the Java
> metamodel, check if the given property of the given class is or not
> transient and I remove it from the map if the property is transient.
>
> I'm happy to have found a way (it is still under work) to use JavaRPC
> with my own constraints.
> I'll be more than happy to integrate it at JavaRPC level if it is
> found usefull.

The serialization behaviour you need is quite different from what's  
currently done (JavaBean-based vs. attribute-based). I don't think it  
would be good idea to completely replace the existing approach.  
Instead, the algorithm should be configurable so that users can choose  
between JavaBean-based and attribute-based serialization (or plug in  
their own custom code).

Regards,

   Andreas J.

------------------------------------------------------------------------------
Kanugula | 30 Jun 19:53
Favicon

How to reload SimpleTableModel


Hi,

Is there an api to reload SimpleTableModel data like the one
qx.ui.table.model.Remote.reloadData()?

Thanks.
Kanugula.

--

-- 
View this message in context: http://www.nabble.com/How-to-reload-SimpleTableModel-tp24276611p24276611.html
Sent from the qooxdoo-devel mailing list archive at Nabble.com.

------------------------------------------------------------------------------
monika.falk | 30 Jun 14:20
Favicon

Re: progressive table problem with cell events


 Hi Derrell

Please find below the original contexts of the message. Sorry for not including it on the first place.

I understand how override _identifyImage method, the only problem is that those cells already have HTML
renderer and I need to add cell click events on the top of that. Do you think this can be done? 

S pozdravem / Best regards,

Monika Falk, Software Specialist
Tieto

----------------------------------------------------------------------

Message: 1
Date: Fri, 26 Jun 2009 08:16:23 -0400
From: Derrell Lipman <derrell.lipman <at> unwireduniverse.com>
Subject: Re: [qooxdoo-devel] Progressive table
To: qooxdoo Development <qooxdoo-devel <at> lists.sourceforge.net>
Message-ID:
	<cdc91d420906260516h107189adv6c2e84e00acda2e1 <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Fri, Jun 26, 2009 at 7:05 AM, <monika.falk <at> tieto.com> wrote:

>  Hi Everyone
>
> I want to ask if progressive table has most of the functionality of 
> ordinary table? Like click and double click events etc? I could not 
> find it in docs.
>

Hi Monika,

Progressive's Table allows one to create such events in a cell renderer or row renderer but by default it
doesn't provide them. To see how/where you'd add such events, look at the boolean cell renderer:
qx.ui.progressive.renderer.table.cell.Boolean, and search for where the allowToggle property is
used. You'll see where it creates onclick events to handle the toggling of the icon, which is also were
you'd add any events you want generated. The easiest way to do this would be to subclass the cell renderer
and override the _identifyImage method.

Cheers,

Derrell
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------------------------------------------------------

Gmane