Passing named parameter without the URL

[Kenny Tilton-2]

I am trying to get something pretty simple, a layoout that
expands/shrinks to utilize the full browser window (absent toolbars of
course).

I want for now a fixed header in the form of a jpg img, and below that a
tab view using the rest of the available space. The setup below achieves
that with regards to width, but I cannot get the tabview to use the full
available height. You can see I have tried allowGrowY and flex properties:

qx.Class.define("nuvia.Application",
{
extend : qx.application.Standalone,
members :
{
main : function()
     {
       this.base(arguments);
      ...snip...

        var rootc = new qx.ui.container.Resizer();
        rootc.setLayout(new qx.ui.layout.Grow());
               
      var lay = new qx.ui.layout.VBox();
      lay.setSpacing(0);

        var c = new qx.ui.container.Composite(lay);
        c.set({backgroundColor: "#FF0000"});
        rootc.add(c);

        c.add(new qx.ui.basic.Image("resource/nuvia/by-ghx-untabbed.jpg"));

        var tabView = new qx.ui.tabview.TabView().set({allowGrowX:true
                                                        ,allowGrowY:true ,flex:2
                                                        ,height:400 ,backgroundColor:"#00FF00"});


That does not show any pages being added, but I am doing that and what I
see is that the tabview height is coming from the tallest page. I will
eventually want a table inside a page expanding to fill the tabview, so
I first want to get the tabview driven by its container.

I looked at a Dock layout but that just allows docking to one edge and I
need edges south /and/ east.

I thought about putting the tabView inside a wrapper container with a
Grow layout, but then I would still have the same problem of making that
wrapper expand right and down -- the "grow" is howit handles its children.

Canvas seems to have the most flexibility, I just need to see to the
vertical stacking myself. I could hardcode that just to keep moving, but
would it be possible to reference the height or bottom of the image
widget when specifying the y coordinate of the tabview (meant to be just
below the image)? My concern is how soon qooxdoo learns the size of the
JPEG.

I'll just go with a hardcoded tabview height to keep moving, but any
insights are welcome.

cheers, kenny


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Petr Kobalíček]

Hi Darrell,

Is this really true that POST parameters can be combined with GET parameters ?

I'm using python and some days ago I used django and I wasn't able to
do it. Then after reading documentation about HTTP protocol I read
something like "If request method is POST, server can discard GET
parameters". After this, I never combined GET parameters with POST.

If anybody has better informations about this, please write here

Cheers
- Petr

2008/11/18 Derrell Lipman <derrell.lipman@...>:

> On Tue, Nov 18, 2008 at 8:14 AM, thron7 <thron7@...>
> wrote:
>>
>> >> Using setParameter() specifically tells it to encode the parameters in
>> >> the
>> >> URL.  I believe you're looking for setFormField().
>> >>
>> > If you have form fields, then a different transport will be used.
>>
>> This is true, but I strongly object against the XmlHttp transport being
>> restricted to GET and URL parameters. If this is really the case,
>> somebody has to open up a bug for it. XmlHttp transport has to support
>> POST and setParameters() working on the request body!
>
> XmlHttp transport _does_ support POST.  That's not the issue.  The issue
> which has been discussed in depth in the past is that even with POST, it
> must be possible to add parameters to the URL.  You (and the reset of those
> in this discussion) are right that there *should* be a way to add parameters
> to the POST request body.  There's just no way to explicitly specify that
> currently.   This is just one of many issues that have been addressed in the
> past, that should be addressed in a rewrite of qx.io.remote.*
>
> Cheers,
>
> Derrell
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Jean-Baptiste BRIAUD -- Novlog]

GET and POST are some possible HTTP actions like not really used  
DELETE, PUT, ...

Here are the exhaustive list from the reference, the IETF :
http://www.ietf.org/rfc/rfc2616.txt

    9.2   OPTIONS .....................................................
52
    9.3   GET .........................................................
53
    9.4   HEAD ........................................................
54
    9.5   POST ........................................................
54
    9.6   PUT .........................................................
55
    9.7   DELETE ......................................................
56
    9.8   TRACE .......................................................
56
    9.9   CONNECT .....................................................
57

That said, both GET and POST, as far as I know (but I didn't checked  
with reference, too lazy for now ...) are able to have a map of  
parameters with key and value, both text.
That parameters, could be coded in the URL itself or in the request  
body.

After that, whatever it is specified for the server to act, the real  
modern server implementation are probably completly different.
I mean, it is important to distinguish the HTTP protocol by itself  
witch is relatively well followed and what software (called previously  
"the server") do with that protocol.

On 18 Nov 2008, at 19:24, Petr Kobalíček wrote:

> Hi Darrell,
>
> Is this really true that POST parameters can be combined with GET  
> parameters ?
>
> I'm using python and some days ago I used django and I wasn't able to
> do it. Then after reading documentation about HTTP protocol I read
> something like "If request method is POST, server can discard GET
> parameters". After this, I never combined GET parameters with POST.
>
> If anybody has better informations about this, please write here
>
> Cheers
> - Petr
>
> 2008/11/18 Derrell Lipman <derrell.lipman@...>:
>> On Tue, Nov 18, 2008 at 8:14 AM, thron7  
>> <thron7@...>
>> wrote:
>>>
>>>>> Using setParameter() specifically tells it to encode the  
>>>>> parameters in
>>>>> the
>>>>> URL.  I believe you're looking for setFormField().
>>>>>
>>>> If you have form fields, then a different transport will be used.
>>>
>>> This is true, but I strongly object against the XmlHttp transport  
>>> being
>>> restricted to GET and URL parameters. If this is really the case,
>>> somebody has to open up a bug for it. XmlHttp transport has to  
>>> support
>>> POST and setParameters() working on the request body!
>>
>> XmlHttp transport _does_ support POST.  That's not the issue.  The  
>> issue
>> which has been discussed in depth in the past is that even with  
>> POST, it
>> must be possible to add parameters to the URL.  You (and the reset  
>> of those
>> in this discussion) are right that there *should* be a way to add  
>> parameters
>> to the POST request body.  There's just no way to explicitly  
>> specify that
>> currently.   This is just one of many issues that have been  
>> addressed in the
>> past, that should be addressed in a rewrite of qx.io.remote.*
>>
>> Cheers,
>>
>> Derrell
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@...
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Kenny Tilton-2]

Kenny Tilton wrote:
> I am trying to get something pretty simple, a layoout that
> expands/shrinks to utilize the full browser window (absent toolbars of
> course).
>
...


> I looked at a Dock layout but that just allows docking to one edge and I
> need edges south /and/ east.

Ah, on second glance this looks promising. I will also consider a
one-column, two-row "grid". :)

cheers, kenny

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Petr Kobalíček]

Hi all:)

Maybe I should more propagate qxbuild package :-)

My web is currently in "Internal Server Error" state, but after some
time I will write page in English with detailed description what
qxbuild is and for what it should be used.

On the other hand, if there are developers that will not try qooxdoo
only by reason that it needs Python to build application, it's only
their problem.

I think that qooxdoo is one of best web frameworks for for free. Most
of us are using it for commercial projects and all of us are happy (I
hope) working with qooxdoo. Also the community, maybe smaller than
others, is great and helped me a lot at startup.

PS: I created qxbuild for me, after some posts in mailing list I
decided to release it to the public to help some people to start with
qooxdoo. It's also demonstration what is possible with qooxdoo build
system itself.

Cheers
- Petr

2008/11/18 Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...>:

> On 18 Nov 2008, at 17:28, thron7 wrote:
>
>> Kenny,
>>
>>> [CUT]
>> Another reason was we were afraid of people starting to build heavy
>> applications on top of the quickstart package (which was really just
>> thought to give someone a quick start into trying out qooxdoo, as the
>> name indicates), and then leaving qooxdoo because they feel it is too
>> heavy and too inflexible (which are just trade-off's in using the
>> quickstart), never looking into the opportunities the SDK offers. -
>> You
>> see, there is danger lurking on both sides of the road ;).
>>
> I would not be afraid of people that would like to leave after trying
> qooxdoo.
> Due to the hight quality of qooxdoo and people here, I'm convinced
> this is unlikly to happen massively.
> On the other hand, I'm afraid that not enough people could give
> qooxdoo a try because of they feel it is too hard just to try.
> That is maybe pure marketing but this is the real danger.
>
> For me, the danger is far away now I was able to give qooxdoo a real
> deep try without bothering with Python, build, optimization, size and
> other stuff I was even not aware it could be good or bad since I just
> didn't know qooxdoo.
>
>> We also felt that with the build system everybody could create their
>> own
>> "quickstart" if they so desire. It seemed just too much of a stretch
>> to
>> properly support both styles of development. So we removed the package
>> from the public interface.
> I understand, I even feel I could in a near future give a serious
> study to that build. I have to admit that for absolutly no reasons, "I
> don't like Python" but I now feel that I won't have to learn it to use
> qooxdoo.
>>
>>
>> Maybe Andreas can say more about it.
>>
>> Thomas
>>
> Anyway, I just want to express one more time that I'm very happy that
> I had discovered qooxdoo.
> Now, I'll go back to my qooxdoo code ;-)
>>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@...
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:

On 18 Nov 2008, at 14:23, Derrell Lipman wrote:

On Tue, Nov 18, 2008 at 8:14 AM, thron7 <thron7@...> wrote:

>> Using setParameter() specifically tells it to encode the parameters in the
>> URL.  I believe you're looking for setFormField().
>>

> If you have form fields, then a different transport will be used.

This is true, but I strongly object against the XmlHttp transport being
restricted to GET and URL parameters. If this is really the case,
somebody has to open up a bug for it. XmlHttp transport has to support
POST and setParameters() working on the request body!

XmlHttp transport _does_ support POST.  That's not the issue.  The issue which has been discussed in depth in the past is that even with POST, it must be possible to add parameters to the URL.  You (and the reset of those in this discussion) are right that there *should* be a way to add parameters to the POST request body.  There's just no way to explicitly specify that currently.   This is just one of many issues that have been addressed in the past, that should be addressed in a rewrite of qx.io.remote.*

I didn't know it was discussed before, sorry ...

So, I do agree with you : parameter to the POST request body is a need.

Jean-Baptiste, would you please test the attached patch (or pull from SVN; I've checked it in).  Note the new parameter available to setParameter() which specifies whether you want the parameter to be in the URL or as data.  This should do exactly what you're looking for.  Let me know whether this works properly for you.

Cheers,

Derrell

[y.patch]

---

diff --git a/qooxdoo/framework/source/class/qx/io/remote/Request.js b/qooxdoo/framework/source/class/qx/io/remote/Request.js
index 8191db7..edb9f78 100644
--- a/qooxdoo/framework/source/class/qx/io/remote/Request.js
+++ b/qooxdoo/framework/source/class/qx/io/remote/Request.js
@@ -51,7 +51,8 @@ qx.Class.define("qx.io.remote.Request",
     this.base(arguments);
 
     this.__requestHeaders = {};
-    this.__parameters = {};
+    this.__urlParameters = {};
+    this.__dataParameters = {};
     this.__formFields = {};
 
     if (vUrl !== undefined) {
@@ -335,7 +336,8 @@ qx.Class.define("qx.io.remote.Request",
   {
 
     __requestHeaders : null,
-    __parameters : null,
+    __urlParameters : null,
+    __dataParameters : null,
     __formFields : null,
     __seqNum : null,
 
@@ -791,48 +793,110 @@ qx.Class.define("qx.io.remote.Request",
     /**
      * Add a parameter to the request.
      *
-     * @param vId {String} String identifier of the parameter to add.
-     * @param vValue {var} Value of parameter. May be a string (for one parameter) or an array of
-     *     strings (for setting multiple parameter values with the same parameter
-     *     name).
+     * @param vId {String}
+     *   String identifier of the parameter to add.
+     *
+     * @param vValue {var}
+     *   Value of parameter. May be a string (for one parameter) or an array
+     *   of strings (for setting multiple parameter values with the same
+     *   parameter name).
+     *
+     * @param bAsData {Boolean | false}
+     *   If <i>false</i>, add the parameter to the URL.  If <i>true</i> then
+     *   instead the parameters added by calls to this method will be combined
+     *   into a string added as the request data, as if the entire set of
+     *   parameters had been pre-build and passed to setData().
+     *
+     * Note: Parameters requested to be sent as data will be silently dropped
+     *       if data is manually added via a call to setData().
+     *
+     * Note: Some transports, e.g. Script, do not support passing parameters
+     *       as data.
+     *
      * @return {void}
      */
-    setParameter : function(vId, vValue) {
-      this.__parameters[vId] = vValue;
+    setParameter : function(vId, vValue, bAsData)
+    {
+      if (bAsData)
+      {
+        this.__dataParameters[vId] = vValue;
+      }
+      else
+      {
+        this.__urlParameters[vId] = vValue;
+      }
     },
 
 
     /**
      * Remove a parameter from the request.
      *
-     * @param vId {String} Identifier of the parameter to remove.
+     * @param vId {String}
+     *   Identifier of the parameter to remove.
+     *
+     * @param bFromData {Boolean}
+     *   If <i>false</i> then remove the parameter of the URL parameter list.
+     *   If <i>true</i> then remove it from the list of parameters to be sent
+     *   as request data.
+     *
      * @return {void}
      */
-    removeParameter : function(vId) {
-      delete this.__parameters[vId];
+    removeParameter : function(vId, bFromData)
+    {
+      if (bFromData)
+      {
+        delete this.__dataParameters[vId];
+      }
+      else
+      {
+        delete this.__urlParameters[vId];
+      }
     },
 
 
     /**
      * Get a parameter in the request.
      *
-     * @param vId {String} Identifier of the parameter to get.
-     * @return {var} TODOC
+     * @param vId {String}
+     *   Identifier of the parameter to get.
+     *
+     * @param bFromData {Boolean}
+     *   If <i>false</i> then retrieve the parameter from the URL parameter
+     *   list. If <i>true</i> then retrieve it from the list of parameters to
+     *   be sent as request data.
+     *
+     * @return {var}
+     *   The requested parameter value
+     *
      */
-    getParameter : function(vId) {
-      return this.__parameters[vId] || null;
+    getParameter : function(vId, bFromData)
+    {
+      if (bFromData)
+      {
+        return this.__dataParameters[vId] || null;
+      }
+      else
+      {
+        return this.__urlParameters[vId] || null;
+      }
     },
 
 
     /**
      * Returns the object containg all parameters for the request.
      *
-     * @return {Object} The returned object has as its property names each of the ids of
-     *     parameters which have been added, and as each property value, the value
-     *     of the property corresponding to that id.
+     * @param bFromData {Boolean}
+     *   If <i>false</i> then retrieve the URL parameter list.
+     *   If <i>true</i> then retrieve the data parameter list.
+     *
+     * @return {Object}
+     *   The returned object has as its property names each of the ids of
+     *   parameters which have been added, and as each property value, the
+     *   value of the property corresponding to that id.
      */
-    getParameters : function() {
-      return this.__parameters;
+    getParameters : function(bFromData)
+    {
+      return (bFromData ? this.__dataParameters : this.__urlParameters);
     },
 
 
@@ -919,6 +983,8 @@ qx.Class.define("qx.io.remote.Request",
   destruct : function()
   {
     this.setTransport(null);
-    this._disposeFields("__requestHeaders", "__parameters", "__formFields");
+    this._disposeFields("__requestHeaders",
+                        "__urlParameters",
+                        "__formFields");
   }
 });
diff --git a/qooxdoo/framework/source/class/qx/io/remote/transport/Iframe.js b/qooxdoo/framework/source/class/qx/io/remote/transport/Iframe.js
index be167d7..7fa5c39 100644
--- a/qooxdoo/framework/source/class/qx/io/remote/transport/Iframe.js
+++ b/qooxdoo/framework/source/class/qx/io/remote/transport/Iframe.js
@@ -174,7 +174,7 @@ qx.Class.define("qx.io.remote.transport.Iframe",
       // --------------------------------------
       //   Adding parameters
       // --------------------------------------
-      var vParameters = this.getParameters();
+      var vParameters = this.getParameters(false);
       var vParametersList = [];
 
       for (var vId in vParameters)
@@ -197,6 +197,41 @@ qx.Class.define("qx.io.remote.transport.Iframe",
         vUrl += (vUrl.indexOf("?") >= 0 ? "&" : "?") + vParametersList.join("&");
       }
 
+      // --------------------------------------------------------
+      //   Adding data parameters (if no data is already present)
+      // --------------------------------------------------------
+      if (this.getData() === null)
+      {
+        var vParameters = this.getParameters(true);
+        var vParametersList = [];
+
+        for (var vId in vParameters)
+        {
+          var value = vParameters[vId];
+
+          if (value instanceof Array)
+          {
+            for (var i=0; i<value.length; i++)
+            {
+              vParametersList.push(encodeURIComponent(vId) +
+                                   "=" +
+                                   encodeURIComponent(value[i]));
+            }
+          }
+          else
+          {
+            vParametersList.push(encodeURIComponent(vId) +
+                                 "=" +
+                                 encodeURIComponent(value));
+          }
+        }
+
+        if (vParametersList.length > 0)
+        {
+          this.setData(vParametersList.join("&"));
+        }
+      }
+
       // --------------------------------------
       //   Adding form fields
       // --------------------------------------
diff --git a/qooxdoo/framework/source/class/qx/io/remote/transport/XmlHttp.js b/qooxdoo/framework/source/class/qx/io/remote/transport/XmlHttp.js
index ff45b71..f8dffd3 100644
--- a/qooxdoo/framework/source/class/qx/io/remote/transport/XmlHttp.js
+++ b/qooxdoo/framework/source/class/qx/io/remote/transport/XmlHttp.js
@@ -181,9 +181,9 @@ qx.Class.define("qx.io.remote.transport.XmlHttp",
       this.__localRequest = vLocalRequest;
 
       // --------------------------------------
-      //   Adding parameters
+      //   Adding URL parameters
       // --------------------------------------
-      var vParameters = this.getParameters();
+      var vParameters = this.getParameters(false);
       var vParametersList = [];
 
       for (var vId in vParameters)
@@ -206,6 +206,41 @@ qx.Class.define("qx.io.remote.transport.XmlHttp",
         vUrl += (vUrl.indexOf("?") >= 0 ? "&" : "?") + vParametersList.join("&");
       }
 
+      // --------------------------------------------------------
+      //   Adding data parameters (if no data is already present)
+      // --------------------------------------------------------
+      if (this.getData() === null)
+      {
+        var vParameters = this.getParameters(true);
+        var vParametersList = [];
+
+        for (var vId in vParameters)
+        {
+          var value = vParameters[vId];
+
+          if (value instanceof Array)
+          {
+            for (var i=0; i<value.length; i++)
+            {
+              vParametersList.push(encodeURIComponent(vId) +
+                                   "=" +
+                                   encodeURIComponent(value[i]));
+            }
+          }
+          else
+          {
+            vParametersList.push(encodeURIComponent(vId) +
+                                 "=" +
+                                 encodeURIComponent(value));
+          }
+        }
+
+        if (vParametersList.length > 0)
+        {
+          this.setData(vParametersList.join("&"));
+        }
+      }
+
       var encode64 = function(input)
       {
         var keyStr = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/=";

---

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Jean-Baptiste BRIAUD -- Novlog]

Hi Derrell,

Thanks a lot, that's very kind !

Once again, I'd like to hightlight another good point of qooxdoo : the community.

Now, about the patch itself, could you confirm it patch the io.remote.Request class ?

I never have to deal with qooxdoo patch, but what should I do then ?

I'm afraid I need to be educated on that point. This is not lost since I'll be able to help on testing other patches after that :-)

I think the simplest thing will be to :

* checkout the HEAD from SVN,

* use the qooxdoo build to produce that qooxdoo in one file with Petr json config file

* test against my code.

I have a big company meeting now, but I'll  check all that tomorow.

JBB.

On 19 Nov 2008, at 16:02, Derrell Lipman wrote:

On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:

On 18 Nov 2008, at 14:23, Derrell Lipman wrote:

On Tue, Nov 18, 2008 at 8:14 AM, thron7 <thron7@...> wrote:

>> Using setParameter() specifically tells it to encode the parameters in the
>> URL.  I believe you're looking for setFormField().
>>

> If you have form fields, then a different transport will be used.

This is true, but I strongly object against the XmlHttp transport being
restricted to GET and URL parameters. If this is really the case,
somebody has to open up a bug for it. XmlHttp transport has to support
POST and setParameters() working on the request body!

XmlHttp transport _does_ support POST.  That's not the issue.  The issue which has been discussed in depth in the past is that even with POST, it must be possible to add parameters to the URL.  You (and the reset of those in this discussion) are right that there *should* be a way to add parameters to the POST request body.  There's just no way to explicitly specify that currently.   This is just one of many issues that have been addressed in the past, that should be addressed in a rewrite of qx.io.remote.*

I didn't know it was discussed before, sorry ...

So, I do agree with you : parameter to the POST request body is a need.

Jean-Baptiste, would you please test the attached patch (or pull from SVN; I've checked it in).  Note the new parameter available to setParameter() which specifies whether you want the parameter to be in the URL or as data.  This should do exactly what you're looking for.  Let me know whether this works properly for you.

Cheers,

Derrell

<y.patch>-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Wed, Nov 19, 2008 at 10:44 AM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:

Hi Derrell,

Thanks a lot, that's very kind !

Once again, I'd like to hightlight another good point of qooxdoo : the community.

Now, about the patch itself, could you confirm it patch the io.remote.Request class ?

Not only to Request, but to a few of the other classes in qx.io.remote as well.
 

I never have to deal with qooxdoo patch, but what should I do then ?

I don't recall your development environment.  If you are using Unix or Linux, or one of the Unix emulation packages on Windows, you'll have the utility "patch" which reads a patch file like I provided and applies it to the appropriate source files.  You usually need to provide the -p option to tell it how many path components to strip off of the beginning of the path.  If you need help with that let me know.  I suspect, however, that you'll find it easier to use your other option:

I think the simplest thing will be to :

* checkout the HEAD from SVN,

* use the qooxdoo build to produce that qooxdoo in one file with Petr json config file

* test against my code.

Sounds entirely reasonable.

Cheers,

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Nathan Hadley]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hello all,

 

Bit of a basic question, I’m trying to set the width a SplitButton and I’m finding that although the space is given, the button itself doesn’t fill it up.

 

In this example I wanted the button to take up all of the room under the group box;

 

 

Is this a bug or intentional?

 

--
Nathan Hadley
www.celcat.com
Tel: [phone]

CELCAT is the trading name of Corbett Engineering Ltd,
a limited company registered in England and Wales with
company number 1448722. VAT number: 418696219.
Registered office: 21-23 Mercia Business Village,
Torwood Close, Coventry, CV4 8HX, United Kingdom

 

---

From: Jean-Baptiste BRIAUD -- Novlog [mailto:j-b.briaud@...]
Sent: 19 November 2008 15:44
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Passing named parameter without the URL

 

Hi Derrell,

 

Thanks a lot, that's very kind !

Once again, I'd like to hightlight another good point of qooxdoo : the community.

 

Now, about the patch itself, could you confirm it patch the io.remote.Request class ?

I never have to deal with qooxdoo patch, but what should I do then ?

I'm afraid I need to be educated on that point. This is not lost since I'll be able to help on testing other patches after that :-)

 

I think the simplest thing will be to :

* checkout the HEAD from SVN,

* use the qooxdoo build to produce that qooxdoo in one file with Petr json config file

* test against my code.

 

I have a big company meeting now, but I'll  check all that tomorow.

 

JBB.

 

On 19 Nov 2008, at 16:02, Derrell Lipman wrote:

 

On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:

 

On 18 Nov 2008, at 14:23, Derrell Lipman wrote:

 

On Tue, Nov 18, 2008 at 8:14 AM, thron7 <thron7@...> wrote:

>> Using setParameter() specifically tells it to encode the parameters in the
>> URL.  I believe you're looking for setFormField().
>>

> If you have form fields, then a different transport will be used.

This is true, but I strongly object against the XmlHttp transport being
restricted to GET and URL parameters. If this is really the case,
somebody has to open up a bug for it. XmlHttp transport has to support
POST and setParameters() working on the request body!

XmlHttp transport _does_ support POST.  That's not the issue.  The issue which has been discussed in depth in the past is that even with POST, it must be possible to add parameters to the URL.  You (and the reset of those in this discussion) are right that there *should* be a way to add parameters to the POST request body.  There's just no way to explicitly specify that currently.   This is just one of many issues that have been addressed in the past, that should be addressed in a rewrite of qx.io.remote.*

I didn't know it was discussed before, sorry ...

So, I do agree with you : parameter to the POST request body is a need.

Jean-Baptiste, would you please test the attached patch (or pull from SVN; I've checked it in).  Note the new parameter available to setParameter() which specifies whether you want the parameter to be in the URL or as data.  This should do exactly what you're looking for.  Let me know whether this works properly for you.

Cheers,

Derrell

<y.patch>-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Christian Schmidt-18]

Hi Nathan,

yes, this is a bug. This bug is fixed in the SVN trunk.
(http://bugzilla.qooxdoo.org/show_bug.cgi?id=1441)

Regards
Chris

Nathan Hadley schrieb:

>
> Hello all,
>
> Bit of a basic question, I’m trying to set the width a SplitButton and
> I’m finding that although the space is given, the button itself
> doesn’t fill it up.
>
> In this example I wanted the button to take up all of the room under
> the group box;
>
> Is this a bug or intentional?
>
> --
> **Nathan Hadley**
> www.celcat.com
> Tel: [phone]
>
> CELCAT is the trading name of Corbett Engineering Ltd,
> a limited company registered in England and Wales with
> company number 1448722. VAT number: 418696219.
> Registered office: 21-23 Mercia Business Village,
> Torwood Close, Coventry, CV4 8HX, United Kingdom
>
> ------------------------------------------------------------------------
>
> *From:* Jean-Baptiste BRIAUD -- Novlog [mailto:j-b.briaud@...]
> *Sent:* 19 November 2008 15:44
> *To:* qooxdoo Development
> *Subject:* Re: [qooxdoo-devel] Passing named parameter without the URL
>
> Hi Derrell,
>
> Thanks a lot, that's very kind !
>
> Once again, I'd like to hightlight another good point of qooxdoo : the
> community.
>
> Now, about the patch itself, could you confirm it patch the
> io.remote.Request class ?
>
> I never have to deal with qooxdoo patch, but what should I do then ?
>
> I'm afraid I need to be educated on that point. This is not lost since
> I'll be able to help on testing other patches after that :-)
>
> I think the simplest thing will be to :
>
> * checkout the HEAD from SVN,
>
> * use the qooxdoo build to produce that qooxdoo in one file with Petr
> json config file
>
> * test against my code.
>
> I have a big company meeting now, but I'll check all that tomorow.
>
> JBB.
>
> On 19 Nov 2008, at 16:02, Derrell Lipman wrote:
>
>     On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog
>     <j-b.briaud@... <mailto:j-b.briaud@...>> wrote:
>
>     On 18 Nov 2008, at 14:23, Derrell Lipman wrote:
>
>         On Tue, Nov 18, 2008 at 8:14 AM, thron7
>         <thron7@...
>         <mailto:thron7@...>> wrote:
>
>
>         >> Using setParameter() specifically tells it to encode the
>         parameters in the
>         >> URL. I believe you're looking for setFormField().
>         >>
>
>         > If you have form fields, then a different transport will be used.
>
>         This is true, but I strongly object against the XmlHttp
>         transport being
>         restricted to GET and URL parameters. If this is really the case,
>         somebody has to open up a bug for it. XmlHttp transport has to
>         support
>         POST and setParameters() working on the request body!
>
>
>         XmlHttp transport _does_ support POST. That's not the issue.
>         The issue which has been discussed in depth in the past is
>         that even with POST, it must be possible to add parameters to
>         the URL. You (and the reset of those in this discussion) are
>         right that there *should* be a way to add parameters to the
>         POST request body. There's just no way to explicitly specify
>         that currently. This is just one of many issues that have been
>         addressed in the past, that should be addressed in a rewrite
>         of qx.io.remote.*
>
>     I didn't know it was discussed before, sorry ...
>
>     So, I do agree with you : parameter to the POST request body is a
>     need.
>
>
>     Jean-Baptiste, would you please test the attached patch (or pull
>     from SVN; I've checked it in). Note the new parameter available to
>     setParameter() which specifies whether you want the parameter to
>     be in the URL or as data. This should do exactly what you're
>     looking for. Let me know whether this works properly for you.
>
>     Cheers,
>
>     Derrell
>
>     <y.patch>-------------------------------------------------------------------------
>     This SF.Net email is sponsored by the Moblin Your Move Developer's
>     challenge
>     Build the coolest Linux based applications with Moblin SDK & win
>     great prizes
>     Grand prize is a trip for two to an Open Source event anywhere in
>     the world
>     http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
>     <http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________>
>     qooxdoo-devel mailing list
>     qooxdoo-devel@...
>     https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  

--
Christian Schmidt
Software Engineer
Core Development :: Web Technologies

1&1 Internet AG
Ernst-Frey-Str. 9
76135 Karlsruhe, Germany
http://www.1und1.de 

Amtsgericht Montabaur / HRB 6484
                                                       
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen

Aufsichtsratsvorsitzender: Michael Scheeren


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Nathan Hadley]

Ah was looking to see if it had already been reported,

Thanks Chris

--
Nathan Hadley
www.celcat.com
Tel: [phone]
CELCAT is the trading name of Corbett Engineering Ltd,
a limited company registered in England and Wales with
company number 1448722. VAT number: 418696219.
Registered office: 21-23 Mercia Business Village,
Torwood Close, Coventry, CV4 8HX, United Kingdom
 
-----Original Message-----
From: Christian Schmidt [mailto:schmidt.christian@...]
Sent: 19 November 2008 16:47
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] Split button not taking up set Width

Hi Nathan,

yes, this is a bug. This bug is fixed in the SVN trunk.
(http://bugzilla.qooxdoo.org/show_bug.cgi?id=1441)

Regards
Chris

Nathan Hadley schrieb:

>
> Hello all,
>
> Bit of a basic question, I'm trying to set the width a SplitButton and
> I'm finding that although the space is given, the button itself
> doesn't fill it up.
>
> In this example I wanted the button to take up all of the room under
> the group box;
>
> Is this a bug or intentional?
>
> --
> **Nathan Hadley**
> www.celcat.com
> Tel: [phone]
>
> CELCAT is the trading name of Corbett Engineering Ltd,
> a limited company registered in England and Wales with
> company number 1448722. VAT number: 418696219.
> Registered office: 21-23 Mercia Business Village,
> Torwood Close, Coventry, CV4 8HX, United Kingdom
>
> ------------------------------------------------------------------------
>
> *From:* Jean-Baptiste BRIAUD -- Novlog [mailto:j-b.briaud@...]
> *Sent:* 19 November 2008 15:44
> *To:* qooxdoo Development
> *Subject:* Re: [qooxdoo-devel] Passing named parameter without the URL
>
> Hi Derrell,
>
> Thanks a lot, that's very kind !
>
> Once again, I'd like to hightlight another good point of qooxdoo : the
> community.
>
> Now, about the patch itself, could you confirm it patch the
> io.remote.Request class ?
>
> I never have to deal with qooxdoo patch, but what should I do then ?
>
> I'm afraid I need to be educated on that point. This is not lost since
> I'll be able to help on testing other patches after that :-)
>
> I think the simplest thing will be to :
>
> * checkout the HEAD from SVN,
>
> * use the qooxdoo build to produce that qooxdoo in one file with Petr
> json config file
>
> * test against my code.
>
> I have a big company meeting now, but I'll check all that tomorow.
>
> JBB.
>
> On 19 Nov 2008, at 16:02, Derrell Lipman wrote:
>
>     On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog
>     <j-b.briaud@... <mailto:j-b.briaud@...>> wrote:
>
>     On 18 Nov 2008, at 14:23, Derrell Lipman wrote:
>
>         On Tue, Nov 18, 2008 at 8:14 AM, thron7
>         <thron7@...
>         <mailto:thron7@...>> wrote:
>
>
>         >> Using setParameter() specifically tells it to encode the
>         parameters in the
>         >> URL. I believe you're looking for setFormField().
>         >>
>
>         > If you have form fields, then a different transport will be used.
>
>         This is true, but I strongly object against the XmlHttp
>         transport being
>         restricted to GET and URL parameters. If this is really the case,
>         somebody has to open up a bug for it. XmlHttp transport has to
>         support
>         POST and setParameters() working on the request body!
>
>
>         XmlHttp transport _does_ support POST. That's not the issue.
>         The issue which has been discussed in depth in the past is
>         that even with POST, it must be possible to add parameters to
>         the URL. You (and the reset of those in this discussion) are
>         right that there *should* be a way to add parameters to the
>         POST request body. There's just no way to explicitly specify
>         that currently. This is just one of many issues that have been
>         addressed in the past, that should be addressed in a rewrite
>         of qx.io.remote.*
>
>     I didn't know it was discussed before, sorry ...
>
>     So, I do agree with you : parameter to the POST request body is a
>     need.
>
>
>     Jean-Baptiste, would you please test the attached patch (or pull
>     from SVN; I've checked it in). Note the new parameter available to
>     setParameter() which specifies whether you want the parameter to
>     be in the URL or as data. This should do exactly what you're
>     looking for. Let me know whether this works properly for you.
>
>     Cheers,
>
>     Derrell
>
>     <y.patch>-------------------------------------------------------------------------
>     This SF.Net email is sponsored by the Moblin Your Move Developer's
>     challenge
>     Build the coolest Linux based applications with Moblin SDK & win
>     great prizes
>     Grand prize is a trip for two to an Open Source event anywhere in
>     the world
>     http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
>     <http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________>
>     qooxdoo-devel mailing list
>     qooxdoo-devel@...
>     https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>  

--
Christian Schmidt
Software Engineer
Core Development :: Web Technologies

1&1 Internet AG
Ernst-Frey-Str. 9
76135 Karlsruhe, Germany
http://www.1und1.de 

Amtsgericht Montabaur / HRB 6484
                                                       
Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen

Aufsichtsratsvorsitzender: Michael Scheeren


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Kenny Tilton-2]

Woohoo, getting close: I have a subclass of the remote table model at
least getting its rowcount back from Lisp and being reported accurately
by the table view, but that's it no rows. And I do not see Lisp being
hit for the rowdata URL, so I guess no one is asking.

The example:

 
http://demo.qooxdoo.org/current/demobrowser/#table~Table_Remote_Model.html

...seems unfinished. It uses a Simple model and generates random data.
Is there a better example anywhere? I searched the entire qx source tree
for qx.ui.table.model.Remote and just found its definition.

I'll start digging around in the source of Table now to see what makes
it ask for data, but any hints are welcome.

kt

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Wed, Nov 19, 2008 at 3:48 PM, Kenny Tilton <kennytilton@...> wrote:

Woohoo, getting close: I have a subclass of the remote table model at
least getting its rowcount back from Lisp and being reported accurately
by the table view, but that's it no rows. And I do not see Lisp being
hit for the rowdata URL, so I guess no one is asking.

The example:


http://demo.qooxdoo.org/current/demobrowser/#table~Table_Remote_Model.html

...seems unfinished. It uses a Simple model and generates random data.
Is there a better example anywhere? I searched the entire qx source tree
for qx.ui.table.model.Remote and just found its definition.

I'll start digging around in the source of Table now to see what makes
it ask for data, but any hints are welcome.

There's an actual working example of the Remote data model in qooxdoo-contrib.  You'll likely find that much more useful.

Cheers,

Derrell
 

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Kenny Tilton-2]

Derrell Lipman wrote:

>
> On Wed, Nov 19, 2008 at 3:48 PM, Kenny Tilton <kennytilton@...
> <mailto:kennytilton@...>> wrote:
>
>     Woohoo, getting close: I have a subclass of the remote table model at
>     least getting its rowcount back from Lisp and being reported accurately
>     by the table view, but that's it no rows. And I do not see Lisp being
>     hit for the rowdata URL, so I guess no one is asking.
>
>     The example:
>
>
>     http://demo.qooxdoo.org/current/demobrowser/#table~Table_Remote_Model.html
>     <http://demo.qooxdoo.org/current/demobrowser/#table%7ETable_Remote_Model.html>
>
>     ...seems unfinished. It uses a Simple model and generates random data.
>     Is there a better example anywhere? I searched the entire qx source tree
>     for qx.ui.table.model.Remote and just found its definition.
>
>     I'll start digging around in the source of Table now to see what makes
>     it ask for data, but any hints are welcome.
>
>
> There's an actual working example of the Remote data model in
> qooxdoo-contrib.  You'll likely find that much more useful.

Do you mean your example in the context of an RPC demo? I did not see
anything related to a qx.ui.table.Table being connected to a
qx.ui.table.model.Remote, and I think my problem is with the Table, not
the model.Remote.

I do see the Table asking for and correctly displaying the row count
(30k or so) and the scroll bar looks like it knows it has a ton of data,
I just do not see the Table asking the model.Remote for data.

I will poke around the Table doc and code, I must me missing something
simple.

cheers, kenny

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Wed, Nov 19, 2008 at 4:44 PM, Kenny Tilton <kennytilton@...> wrote:

> There's an actual working example of the Remote data model in
> qooxdoo-contrib.  You'll likely find that much more useful.

Do you mean your example in the context of an RPC demo? I did not see
anything related to a qx.ui.table.Table being connected to a
qx.ui.table.model.Remote, and I think my problem is with the Table, not
the model.Remote.

I'm not at my computer with access to qooxdoo-contrib, but I'm almost certain I created a qooxdoo-contrib project that demonstrated qx.ui.table.model.Remote.  I'll find it for you when I get home.

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Petr Kobalíček]

Hi Kenny,

maybe you should start with simple model and try write some
editing/deleting stuff. My experiences are that you will need remote
table model in minimal cases (usually 1 or 2 big sql tables depending
on what you are doing) and all other models simple.

I'm guessing, actualy i'm not using remote model, I load for example
1000 items, no problem:)

Cheers
- Petr

2008/11/19 Kenny Tilton <kennytilton@...>:

> Derrell Lipman wrote:
>>
>> On Wed, Nov 19, 2008 at 3:48 PM, Kenny Tilton <kennytilton@...
>> <mailto:kennytilton@...>> wrote:
>>
>>     Woohoo, getting close: I have a subclass of the remote table model at
>>     least getting its rowcount back from Lisp and being reported accurately
>>     by the table view, but that's it no rows. And I do not see Lisp being
>>     hit for the rowdata URL, so I guess no one is asking.
>>
>>     The example:
>>
>>
>>     http://demo.qooxdoo.org/current/demobrowser/#table~Table_Remote_Model.html
>>     <http://demo.qooxdoo.org/current/demobrowser/#table%7ETable_Remote_Model.html>
>>
>>     ...seems unfinished. It uses a Simple model and generates random data.
>>     Is there a better example anywhere? I searched the entire qx source tree
>>     for qx.ui.table.model.Remote and just found its definition.
>>
>>     I'll start digging around in the source of Table now to see what makes
>>     it ask for data, but any hints are welcome.
>>
>>
>> There's an actual working example of the Remote data model in
>> qooxdoo-contrib.  You'll likely find that much more useful.
>
> Do you mean your example in the context of an RPC demo? I did not see
> anything related to a qx.ui.table.Table being connected to a
> qx.ui.table.model.Remote, and I think my problem is with the Table, not
> the model.Remote.
>
> I do see the Table asking for and correctly displaying the row count
> (30k or so) and the scroll bar looks like it knows it has a ton of data,
> I just do not see the Table asking the model.Remote for data.
>
> I will poke around the Table doc and code, I must me missing something
> simple.
>
> cheers, kenny
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Kenny Tilton-2]

Petr Kobalíček wrote:
> Hi Kenny,
>
> maybe you should start with simple model and try write some
> editing/deleting stuff.

Sage advice and I did consider that as a stepping stone when things got
rough -- in fact, I was getting ready to set some break points in one of
the demos just to find out where getRowData got called when it all
started working. (Yeah!!!!)

My app does nothing /but/ read huge datasets so I went right for the
jugular, and was happy to see the row count working right off the bat,
figured I was not too far out from getting the whole thing working.

And I have implemented the same already in jQuery, Dojo, and YUI -- yes,
this is getting old, but I think I have found the promised land and it
is called qooxdoo -- so I figured how hard could it be.

I have no clue why it started working, but I think it is simply that
Chrome is not as helpful as FireFox in announcing errors -- I /think/ a
simple JS bug was killing the data load. Could have sworn I had tried
the thing in FF during this firefight, but probably not, it was a solid bug.

> My experiences are that you will need remote
> table model in minimal cases (usually 1 or 2 big sql tables depending
> on what you are doing) and all other models simple.

My first test serves 30,880 rows. It's a datamining app, later on I'll
have millions.

Thx,

kenny


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Kenny Tilton-2]

Looks like we'll be adopting qooxdoo. First impressions are really over
the top. Anywho...

Now that I am getting serious about qooxdoo I want to start getting my
code base organized. One easy way to divide it up comes from the app
itself being eally multiple browsers in one, with a tabview just under
the page banner, one tab per browser.

In my code, I have this:

                var tabView = new qx.ui.tabview.TabView();
                var tab = new qx.ui.tabview.Page("XYZ Browser");
                tab.setLayout(new qx.ui.layout.Grow());
                tab.add(this.buildXYZ());
                tabView.add(tab);

Now I guess what I do is subclass....tabView.Page?! Sounds wrong.

What would you do? I could just make up a new class nova.xyz (where nova
is my top-level application) and then:

                var tabView = new qx.ui.tabview.TabView();
                var xyz = new nova.xyz;
                var tab = new qx.ui.tabview.Page(xyz.view.title);
                tab.setLayout(new qx.ui.layout.Grow());
                tab.add(xyz.view);
                tabView.add(tab);

That way the view does not know about being in a tabView.

I'm not really asking about OO design -- I am pretty comfortable with
that -- I guess I am just wondering if my usual thinking needs
adjustment under the qooxdoo model.

cheers, kenny



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Derrell Lipman]

On Wed, Nov 19, 2008 at 4:57 PM, Derrell Lipman <derrell.lipman@...> wrote:

On Wed, Nov 19, 2008 at 4:44 PM, Kenny Tilton <kennytilton@...> wrote:

> There's an actual working example of the Remote data model in
> qooxdoo-contrib.  You'll likely find that much more useful.

Do you mean your example in the context of an RPC demo? I did not see
anything related to a qx.ui.table.Table being connected to a
qx.ui.table.model.Remote, and I think my problem is with the Table, not
the model.Remote.

I'm not at my computer with access to qooxdoo-contrib, but I'm almost certain I created a qooxdoo-contrib project that demonstrated qx.ui.table.model.Remote.  I'll find it for you when I get home.

Yup, you're looking at the correct demo.  In qooxdoo-contrib, it's called RpcExample.  If you look near the bottom of source/class/rpcexample/Application.js, you'll see the method remoteTable() which is currently all you care about.  You'll see that it instantiates a new rpcexample.RemoteDataModel for use with the table it creates.  You'll find rpcexaple.RemoteDataModel in the same directory as Application.js.  rpcexample.RemoteDataModel extends the abstract class qx.ui.table.model.Remote.  Of particular interst is the setting of column ids in the constructor.  Your backend either needs to return an array of maps as I demonstrated here, or you need to convert the returned array of arrays of values into an array of maps.  Also of particular interest is the implementation of the two methods which are abstract in qx.ui.model.Remote: _loadRowCount() and _loadRowData().  You can look at qooxdoo-contrib/RpcPhp/trunk/services/qooxdoo/remoteTableTest.php to see what the backend for this example does.  It's VERY simple for this example.  You can implement client/server communication with remote procedure calls as I did, or however else you'd like.  You just need to ensure that you pass back data in the form required for the remote data model.

Cheers,

Derrell

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

[Alexander Back]

Hi Kenny,

just for completion (and for all other users out there using the Remote
Table Model): I wrote a basic tutorial on how to implement it (client-
and server-side). And of course, Derrell's demos is mentioned as well.

-> http://qooxdoo.org/documentation/0.8/remote_table_model

Any feedback welcome ;-)

cheers,
   Alex

Kenny Tilton wrote:

> Woohoo, getting close: I have a subclass of the remote table model at
> least getting its rowcount back from Lisp and being reported accurately
> by the table view, but that's it no rows. And I do not see Lisp being
> hit for the rowdata URL, so I guess no one is asking.
>
> The example:
>
>  
> http://demo.qooxdoo.org/current/demobrowser/#table~Table_Remote_Model.html
>
> ...seems unfinished. It uses a Simple model and generates random data.
> Is there a better example anywhere? I searched the entire qx source tree
> for qx.ui.table.model.Remote and just found its definition.
>
> I'll start digging around in the source of Table now to see what makes
> it ask for data, but any hints are welcome.
>
> kt

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel