Hey,
I wanted to add my two cent's as well. At first, this is not the first time
that we thought about a move to another medium than the mailing list. We talked
about a forum, we talked about stackoverflow and so on. In the end, it always
came back to "I want to have email notifications" (like F
Hi Scott,
I don't believe so. Resetting the state will not cancel the request, since
there is no apply routine associated. For store.Json, there can only be one
request at the time for each instance. How about disposing manually? Also note
that making a new request by changing the URL disposes
Just take a look at fireEvent and fireDataEvent on api.
Regards.
Von meinem iPhone gesendet
Am 04.01.2012 um 21:49 schrieb Scott Chapman :
> qx.Class.define("test1.KioskFinder",
> {
> extend : qx.ui.container.Composite,
> construct : function()
> {
> this.base(arguments);
>
qx.Class.define("test1.KioskFinder",
{
extend : qx.ui.container.Composite,
construct : function()
{
this.base(arguments);
this.setLayout(new qx.ui.layout.VBox(5));
this.__textField = new qx.ui.form.TextField;
this.__hostTable = new qx.ui.table.Table;
this.add
Is resetState() the correct way to cancel any current AJAX request on this?
Thanks!
Scott
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless
Hi
If you want to give it a try by all means do it. I am not opposed to it.
Simon
On 03/01/2012 11:34 AM, Mehrez KRISTOU wrote:
> Do you mind if I give it a try?
>
> Kristou
>
>
>
> On Wed, Jan 4, 2012 at 1:30 AM, Simon White
> wrote:
>> I just use the search feature of my news reader so I h
On Wed, Jan 4, 2012 at 12:42, Scott Chapman wrote:
> I'm going to be hitting a URL from qx.data.store.JSON. It will have spaces
> and other "unsavory" characters in it.
>
> var jsonLateKioskFetcher = new qx.data.store.Json(null);
> this.__jsonHostFetcher.setUrl("/kiosk_find/" + search
I'm going to be hitting a URL from qx.data.store.JSON. It will have spaces
and other "unsavory" characters in it.
var jsonLateKioskFetcher = new qx.data.store.Json(null);
this.__jsonHostFetcher.setUrl("/kiosk_find/" + search_for);
Does qooxdoo have a routine to URL-encode the "search_
It's a little hard to debug on Firefox but it's just a function. AIUI
it's quicker to push strings into an array and then join them, e.g.
var lcTxt=[];
for (i=0; i0)
lcTxt.push("+");
lcTxt.push("mRecord.get('");
lcTxt.push(tmSearch.key[i]);
lcTxt.push("')");
}
var Search = new Function(lcTx
On 01/04/2012 03:28 PM, Stefan Andersson wrote:
Why hasn't a link to the book been put on the frontpage of qooxdoo.org?
I think it will fit nicely in the next 'weekly' blog post (which might
not be issued before next week). I'm not so sure about the front page of
qooxdoo.org, though, that w
Hi
Yes I thought about building a AVL binary tree and attaching it to the
store but I am not sure I need to as most of the data will be sorted on
the server as part of an SQL statement so I only needed a method to
lookup keys from a Data Dictionary where some of the widget properties
are store
Patience, Thomas ...
On Wed, 4 Jan 2012, Stefan Andersson wrote:
>
> Why hasn't a link to the book been put on the frontpage of qooxdoo.org?
> a short summary and comments from the core team would also be good...
>
> I think that the best promoter of the book is qooxdoo itself...
> ...joint press
Why hasn't a link to the book been put on the frontpage of qooxdoo.org?
a short summary and comments from the core team would also be good...
I think that the best promoter of the book is qooxdoo itself...
...joint pressrelease
When is it coming?
Stefan
Kristou!
I think that the list has shown you "exaggerated" resistance to your suggestion
so far, though they have come with suggestions for you to work differently.
You tell that qooxdoo should learn from Sencha and setup a structured forum.
This suggestion has some good points:
1. better topi
I personally don't like checking websites (or newsgroups or whatever) all
the time for new messages.
One problem with a hierarchically organized forum is, that I must beforehand
know, in which category to look (or post) if it's not obvious. And sometimes
it's not even clear because the topics aren
Sure there are reasons behind choosing a mailing list as communication
medium. However, I think a forum is more sophisticated and easy to
follow.
for example, i like the organization of this forum.
http://www.sencha.com/forum/
Kristou
On Wed, Jan 4, 2012 at 10:36 PM, Mehrez KRISTOU wrote:
> So
Sorry I did not define correctly the inconveniences.
A forum like mentioned shows exactly what I mean.
kristou
On Wed, Jan 4, 2012 at 9:49 PM, thron7 wrote:
>
>
> On 01/04/2012 12:03 PM, Mehrez KRISTOU wrote:
>> Yes I gave it a try. still it is an archive of the mailing list.
>> I don't see any
On 01/04/2012 12:03 PM, Mehrez KRISTOU wrote:
> Yes I gave it a try. still it is an archive of the mailing list.
> I don't see any hierarchy of the topics. I can not figure out what is
> new about contribution. It needs an effort to find out what need if I
> don't know in advance that it exists.
On 01/04/2012 02:46 AM, Marc Puts wrote:
> As for selecting a shape by clicking on it, I think that requires a tiny bit
> of qooxdoo magic that I'll post tomorrow, when I'm back at my development
> pc.
>
And here's the promised example of how to get back the shape that you
clicked on:
var elem
Yes I gave it a try. still it is an archive of the mailing list.
I don't see any hierarchy of the topics. I can not figure out what is
new about contribution. It needs an effort to find out what need if I
don't know in advance that it exists. Any way it was a proposition, if
everybody is satisfied,
Have you tried http://qooxdoo.678.n2.nabble.com/
http://qooxdoo.678.n2.nabble.com/ ? Works a treat for me.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/A-forum-for-qooxdoo-tp7145560p7149954.html
Sent from the qooxdoo mailing list archive at Nabble.com.
-
Hi Deech,
by headers I assume you mean the request body?
With qooxdoo 1.6, and if your server expects JSON, you can set the Content-Type
of the request’s body to "application/json" and provide the data as part of the
parameters hash. Parameters with placeholders associated end up in the URL, th
22 matches
Mail list logo
