[OpenLayers-Dev] {} or new Object()

[John Cole]

I'll second the caution about prototyping basic items.  I've found that you
cannot use M$ ajax framework with some prototype.net based kits because they
define the same thing differently.

I don't think OL should assume that it's the only JavaScript kit on the page
and would prefer it to use standard JS when possible.

My $.02

John

-----Original Message-----
From: dev-bounces at openlayers.org [mailto:dev-bounces at openlayers.org] On
Behalf Of Jeff Dege
Sent: Tuesday, July 24, 2007 2:51 PM
To: dev at openlayers
Subject: Re: [OpenLayers-Dev] {} or new Object()

Which is more likely to cause conflicts with other javascript class
frameworks?

Everybody and his brother seems to override $(), which causes no end of
headaches. 

> -----Original Message-----
> From: dev-bounces at openlayers.org 
> [mailto:dev-bounces at openlayers.org] On Behalf Of Erik Uzureau
> Sent: Tuesday, July 24, 2007 2:43 PM
> To: dev at openlayers
> Subject: [OpenLayers-Dev] {} or new Object()
> 
> Paul has just gone vocal with his preference for using {} instead of
> "new Object()" for the instantantiation of a new object.
> 
> We do not currently have any policy for this. Do people feel strongly
> one way or the other?
> 
> Obviously it's not a big issue, but if there is broad support for
> doing it one way or the other, we might as well attempt to standardize
> a bit.
> 
> Erik
> _______________________________________________
> Dev mailing list
> Dev at openlayers.org
> http://openlayers.org/mailman/listinfo/dev
> 
_______________________________________________
Dev mailing list
Dev at openlayers.org
http://openlayers.org/mailman/listinfo/dev
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.