On Tue, 29 Dec 2009 15:13:44 +0300, Joran Greef jorangr...@gmail.com
wrote:
Propose:
Http.get(uri, options) and Http.post(uri, options).
Where:
options = {
headers: {},
parameters: {},
body: '',
onSuccess: function(response) {},
onFailure: function(response) {},
onTimeout:
On Fri, 11 Dec 2009 21:02:52 +0300, Joran Greef jorangr...@gmail.com
wrote:
Thanks Artemy, 'set' vs 'put' took some consideration. Basically: many
Javascript APIs use 'get', 'set', 'unset' methods. I used to use POST
(as in 'create') but now find it's easier to deal with network failure
Using proposed interface, how do I do POST? How do I do OPTIONS or some
custom method? Why use `set` and not `put`? Why use 'representation' and
not 'body'?
I would say your proposal isn't much more memorable than existing.
On Fri, 11 Dec 2009 16:07:53 +0300, Joran Greef jorangr...@gmail.com
String#isEmpty checks not the length of a string, but absence of non-space
characters, which is quite useful i.e. in form validation.
On Sun, 04 Oct 2009 11:30:00 +0400, T.J. Crowder t...@crowdersoftware.com
wrote:
I'm with Robert, is there a good use case for these or should we just
Why don't you use element.onselectstart = Event.stop; ?
On Sat, 26 Sep 2009 07:04:22 +0400, kangax kan...@gmail.com wrote:
onselectstart
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Prototype: Core group.
To
Ah, i forgot that i used even more overkilling but working solution:
element.observe('selectstart', Event.stop);
Anyway i got your point.
On Sat, 26 Sep 2009 19:10:34 +0400, kangax kan...@gmail.com wrote:
On Sep 26, 6:30 am, artemy tregubenko m...@arty.name wrote:
Why don't you use
On Sun, 13 Sep 2009 01:39:43 +0400, kangax kan...@gmail.com wrote:
On Sep 12, 3:05 am, artemy tregubenko m...@arty.name wrote:
This may used to unobtrusively store in a hash some data associated
with dom nodes.
So DOM node would be a key? That doesn't really sound like a good
idea
This may used to unobtrusively store in a hash some data associated with
dom nodes.
On Fri, 11 Sep 2009 19:39:04 +0400, kangax kan...@gmail.com wrote:
On Sep 11, 7:08 am, T.J. Crowder t...@crowdersoftware.com wrote:
[...]
@Jim:
Yep, this is Java-esque but that doesn't *always* equal
On Thu, 28 May 2009 10:40:33 +0400, kangax kan...@gmail.com wrote:
On May 27, 8:37 pm, Luisgo lgo...@gmail.com wrote:
Hi all... I was about to submit a ticket (enhancement) but maybe this
has come up before so I ask here... what do you think about being able
to pass more than one event to
This is ok, because assignment also returns value. What happens here:
- seek for a match
- if match found, put match data to match and go to main branch
- if no match found, put undefined to match and go to else branch
On Tue, 06 Jan 2009 15:27:04 +0300, plattecoducks fliger.d...@gmail.com
On Fri, 14 Nov 2008 01:59:07 +0300, kangax [EMAIL PROTECTED] wrote:
My only concern about this pattern is memory usage. There are many
functions created during branching process, yet only one is returned/
assigned (and is then used throughout the rest of the application
life). Those
11 matches
Mail list logo
