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
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 g
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 ...
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
par
Hi,
I was just going through the forum to find some information about handling
resources in my qooxdoo application.
I wanted to point out that the URL given below in the posts
(http://qooxdoo.org/documentation/0.8/ui_overview?s=asset#resource_handling)
looks old and doesn't point to the correct p
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
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 th
On 18 Nov 2008, at 16:59, thron7 wrote:
> Jean-Baptiste BRIAUD -- Novlog wrote:
>> On 18 Nov 2008, at 14:54, thron7 wrote:
>>> Jean-Baptiste BRIAUD -- Novlog wrote:
>>>
Hi,
[CUT]
I'm a little bit scared to use a source version for a production
[CUT]
>>> No, you sh
Kenny,
>
> I agree 100%. "Python required" was quite scary. I thought Python was
> going to be preprocessing my source code and involved in every
> iteration. I passed on qooxdoo and went on to Dojo and then YUI, came
> back only because they came up short and because the original
> recommende
Jean-Baptiste BRIAUD -- Novlog wrote:
> On 18 Nov 2008, at 14:54, thron7 wrote:
>
>> Jean-Baptiste BRIAUD -- Novlog wrote:
>>
>>> Hi,
>>>
>>> [CUT]
>>>
>>> I'm a little bit scared to use a source version for a production
>>> [CUT]
>>>
>> No, you shouldn't be working against trunk f
Jean-Baptiste BRIAUD -- Novlog wrote:
> Even if I fully (I think) understand all the power and advantages of
> that qooxdoo build system, I have to say that this was the biggest
> negative thing I found in qoxdoo.
> Let me explain and be sure I really appreciate qooxdoo but we also
> have to
> Right, that is what I am doing. The good news is that the source version
> now loads OK even from my Lisp server (not sure what I did, but there
> may have been an error I just was not noticing and fixed while thrashing
> about),
Good :).
> the bad news is that it is a little slower than
On 18 Nov 2008, at 15:18, thron7 wrote:
> Jean-Baptiste BRIAUD -- Novlog wrote:
>> Hi,
>>
>> That one is about the fact some call to io.remote.Request are not log
>> in the debig console the same way other call are.
>>
>> [CUT]
>> I'm using a build version, the one that Petr kindly made for me.
>>
On 18 Nov 2008, at 14:54, thron7 wrote:
> Jean-Baptiste BRIAUD -- Novlog wrote:
>> Hi,
>>
>> [CUT]
>>
>> I'm a little bit scared to use a source version for a production
>> [CUT]
>
> No, you shouldn't be working against trunk for a production
> application,
> [CUT]
OK.
> Also, using a source vers
Alexander Back wrote:
> Hi Kenny,
>
> On Tuesday 18 November 2008 Kenny Tilton wrote:
>
>>I was having trouble loading my page using my Lisp server. I saw dozens
>>of separate requests pulling in bits of JS, and then nothing, just a
>>blank screen.
>
> The "source" version of qooxdoo uses a kin
Jean-Baptiste BRIAUD -- Novlog wrote:
> Hi,
>
> As we talked about several issues, I split them into several messages.
>
> That one is about the fact some call to io.remote.Request are not log
> in the debig console the same way other call are.
>
> I normaly use application/json but for testing
Jean-Baptiste BRIAUD -- Novlog wrote:
> Hi,
>
> As we talked about several issues, I split them into several messages.
> That one is about using SVN trunk of qooxdoo for developping a
> production application.
>
> I'm a little bit scared to use a source version for a production
> application bu
> 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
> So my question : how to have HTTP request parameter, not form field,
> using the body of the request, not URL ?
>
If POST and body parameter with setParameter() really fails (which I'm
not completely convinced of), as a fall-back, you can always construct
the parameter string yourself a
On 18 Nov 2008, at 14:23, Derrell Lipman wrote:
On Tue, Nov 18, 2008 at 8:14 AM, thron7
<[EMAIL PROTECTED]> 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 diffe
On 18 Nov 2008, at 14:14, 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 ag
On Tue, Nov 18, 2008 at 8:14 AM, thron7 <[EMAIL PROTECTED]>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,
>> 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 GE
Hi Darrell,
I'm not currently at home, but I have no problems with sharing my
transport layer (it's about 300 lines of code). I think that GET and
POST requests can work same way, it just differs where the parameters
are (in URL or in BODY).
My way is simple, for example JSON parameters:
{
id:
>
> You should use this class directly in your code. We may break the API
> without warning.
>
Fabian meant, "You shouldn't".
Thomas
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build t
thron7 wrote:
> Kenny,
>
> maybe a bit of background info regarding this topic, if you have the time.
>
> Within the qooxdoo world there are various different hierarchies where
> you have parent-child relations.
Yeah, I realized what was going on right away (been using/building
frameworks s
Kenny,
maybe a bit of background info regarding this topic, if you have the time.
Within the qooxdoo world there are various different hierarchies where
you have parent-child relations. The topic you are hinting at is the
structure of framework widgets like the SplitButton. While
getLayoutPare
Hi Sebastian,
Good to hear from you again and good to see that you want to try out the
TileView widget *grin*.
I haven't tested the TileView with the trunk yet only the 0.8 release.
It should work but please let me know if you have any teething problems
with it.
Thanks,
Matt
thron7 wrote:
>
Hi Sebastian!
Fixed with r16714. Thanks!
Thomas
Sebastian Werner wrote:
> Hi!
>
> I just tried to create a new qooxdoo application to check out the
> TileView :) Seems that the version of qooxdoo in SVN has some issues.
> See the attached log output. Any ideas?
>
> Sebastian
>
>
>
>
> sebast
Hi Kenny,
On Tuesday 18 November 2008 Kenny Tilton wrote:
> I was having trouble loading my page using my Lisp server. I saw dozens
> of separate requests pulling in bits of JS, and then nothing, just a
> blank screen.
The "source" version of qooxdoo uses a kind of "inlcude" script which includes
Amit Rana schrieb:
> Hi,
>
> I am porting my application from v0.7.3 to v0.8 based on SDK available
> to Qooxdoo site.
>
> I have a few queries :
>
>1. Do we always have to use the container
> (qx.ui.container.Composite) to add widgets and set their
> properties ?
>
There are a num
31 matches
Mail list logo
