> 1) Add an configuration option what kind of response jEditable
expects.
> This requires less coding from end user. Bad thing is it adds bloat to
> jEditable since all different response types need their own handlers
> inside plugin code.
Yep, this doesn't sound right to me... Sometimes you j
2006/10/24, Mika Tuupola <[EMAIL PROTECTED]>:
>
> On Oct 24, 2006, at 17:54, Robert Wagner wrote:
>
> >> Just my $0.02: I find this odd. Imagine that you want some
> >> processing to be
> >> done based on the input (i.e. server side email address checking)
> >> (We all
> > that was my attempt too a
Mika
In order to keep the code as reusable as possible, i'd just go for the custom
callback method, and leave the way of handling the response to the user. That
way, i (and perhaps others) will be able to implement quick and dirty error
handling, and others can go with JSON or anything else.
T
On Oct 24, 2006, at 17:54, Robert Wagner wrote:
>> Just my $0.02: I find this odd. Imagine that you want some
>> processing to be
>> done based on the input (i.e. server side email address checking)
>> (We all
> that was my attempt too at first. error checking = application logic =
> write my
> that was my attempt too at first. error checking = application logic =
> write my own structures etc.
> but then think about error handling as a very basic thing that is
> already implementet in webserver, ajax functions etc. why not using
> this infrastructure? it's straightforward, ready to us
2006/10/24, Barry Nauta <[EMAIL PROTECTED]>:
> On Tuesday 24 October 2006 15:58, Mika Tuupola wrote:
> > On Oct 24, 2006, at 14:43, Robert Wagner wrote:
> > > how about that:
> > > if an error occours, let the server send a 500 header and the error
> > > message as a content.
> > >
> > > header("HT
On Tuesday 24 October 2006 15:58, Mika Tuupola wrote:
> On Oct 24, 2006, at 14:43, Robert Wagner wrote:
> > how about that:
> > if an error occours, let the server send a 500 header and the error
> > message as a content.
> >
> > header("HTTP/1.1 500 Internal Server Error");
> > print("this cannot
On Oct 24, 2006, at 14:43, Robert Wagner wrote:
> how about that:
> if an error occours, let the server send a 500 header and the error
> message as a content.
>
> header("HTTP/1.1 500 Internal Server Error");
> print("this cannot be done.");
Agreed. I find error headers to be more elegant and u
> 1.0.8 is already a bit old. Will downgrade from 1.5.x series and try
> it out.
It is indeed ;-) Nevertheless it would be great if this can be fixed.
By the way, you do not mention that it works with IE on your website. It does
work on XP SP2 with version 6.0.2900and some more version
On Oct 24, 2006, at 12:06, Barry Nauta wrote:
> - Using firefox 1.0.8 jeditable does not return.
> I can edit my text and the changes are saved in the database.
> However, after
> hitting the enter butting (and thus submitting the changes), the
> busy icon is
> show forever, it does not retur
2006/10/24, Miel Soeterbroek <[EMAIL PROTECTED]>:
> Barry,
>
> I've added some code to show an error message.
> Quite ugly solution though:
> I catch all returned text, and look for the following string '[error]',
> if it's found, I revert the form field text and alert the error.
>
> The trick is t
});
Cheers,
Miel
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Barry Nauta
Sent: dinsdag 24 oktober 2006 11:06
To: discuss@jquery.com
Subject: [jQuery] jEditable question
Hi all,
I have recently discovered jquery and jeditable.
When usi
Hi all,
I have recently discovered jquery and jeditable.
When using jeditable, I discovered two things:
- Using firefox 1.0.8 jeditable does not return.
I can edit my text and the changes are saved in the database. However, after
hitting the enter butting (and thus submitting the changes), th
13 matches
Mail list logo
