On Thu, Nov 13, 2008 at 10:04 AM, Jean-Baptiste BRIAUD -- Novlog <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> io.remote.Request :
> http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote.Request
>
> I'm wondering why the methods for adding things are nammed setThing.
> Explanation :
> say you want to add some form fields to the request, you'll have to
> use the method setFormField(String vId, String vValue)
> I would prefer addFormField(String vId, String vValue).
>
> The same for setParameter and setRequestHeader.
>
> In general, I'm using set/get for single value and for multiple value,
> like addListener(...) it is more complex :
> setXs(<the array>) : set the entire collection
> addX(<an element>) : add one element to the collection
> addXs(<a collection>) : add several elements on one shot to the
> collection
> getXs() : return the entire collection
> getX( <a find param like a unique id> ) : return, if any, one element
> that correcpond to that unique id.
>
>
> What do you think about that ?
I think there are more severe issues than just naming. That whole module is
not very clean and could use a rewrite. It's working, though, so none of us
have gotten up the motivation to rewrite it yet. Maybe some day. :-)
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
