[Windmill-dev] https; file uploads; extjs and click support

[Mikeal Rogers]

On Dec 16, 2007, at December 16, 200711:06 PM, Matthew Eernisse wrote:

> Adam,
>
> It might be worth considering allowing a preventDefault option to be  
> passed which would call that method immediately on our events before  
> they are actually dispatched, if it will work. It might not be that  
> hard to do, and would keep us from having to add new method calls to  
> the API.

+1 on adding options to existing API methods rather than writing new  
ones

>
>
> (With a wee bit of thought I realized how silly a stopPropagation  
> option would be -- you'd have an event that does absolutely nothing,  
> duh. :))
>
> On the other hand, if you're going to keep the current new method,  
> could you consider naming it something more descriptive? I can think  
> of two specific cases where the preventDefault option comes into  
> play a lot -- following links on a click, and the default submission  
> of forms with the onsubmit.
>
> Perhaps all we need is something like clickNoFollowLink, and  
> submitNoSubmitActualForm or something.

-1 on long annoying API method names.

>
>
> On the other hand, being able to call preventDefault preemptively on  
> all our actions might be more flexible.


I think this might be useful, it would be a huge pain in the ass to  
have to add the preventDefault option to every single one of your test  
calls.

If possible, I'd like to have an option on all current existing API  
that this makes sense for; {"preventDefault":true}, and in addition a  
command that would turn it on or off for all API calls coming in, but  
still allow override of the option if it's sent as an option to a  
method call.

-Mikeal