Jquery and ViaMichelin Maps Api Problem

[Adriano-17]

Hi all, I'm a new member so... nice to be here, I'm Adriano from Rome
(Italy).

My problem is the following: I have to use the ViaMichelin maps APIs,
but when i include together the two library, the jquery plus the
viamichelin, firebug gives me this error "tF.call is not a function".
The maps work, but jquery doesn't any more...
Trying to isolate the error cause I simply set up an html document
that simply import the two scripts:

<script type="text/javascript" src="jquery.js"></script>
<script src="http://api.viamichelin.com/apijs/js/api.js"></script>

and this, alone, trigger the firebug error warning. "tF.call is not a
function".

If is there anyone that have any glimpse of the cause of this strange
behaviour I'll be glad and... grateful!!

Thank you

Adriano

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Yoan Blanc-2]

// http://www2.viamichelin.com/vmw2/fwk/cmn/VMPrototypes.jsp?charset=UTF-8

Object.prototype.ci = function(tF)
{
        tF.call(this);
};

This is so wrong.

-- Yoan

On Wed, Jun 4, 2008 at 10:01 AM, Adriano <adrianomassi@...> wrote:

>
> Hi all, I'm a new member so... nice to be here, I'm Adriano from Rome
> (Italy).
>
> My problem is the following: I have to use the ViaMichelin maps APIs,
> but when i include together the two library, the jquery plus the
> viamichelin, firebug gives me this error "tF.call is not a function".
> The maps work, but jquery doesn't any more...
> Trying to isolate the error cause I simply set up an html document
> that simply import the two scripts:
>
> <script type="text/javascript" src="jquery.js"></script>
> <script src="http://api.viamichelin.com/apijs/js/api.js"></script>
>
> and this, alone, trigger the firebug error warning. "tF.call is not a
> function".
>
> If is there anyone that have any glimpse of the cause of this strange
> behaviour I'll be glad and... grateful!!
>
> Thank you
>
> Adriano
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Godmar Back]

It seems to indicate that jQuery assumes that no properties have been
added to Object.prototype?
Is it possible that jQuery should be using hasOwnProperty in "for ... in" loops?

 - Godmar

On Wed, Jun 4, 2008 at 8:18 AM, Yoan Blanc <yoan.blanc@...> wrote:

>
> // http://www2.viamichelin.com/vmw2/fwk/cmn/VMPrototypes.jsp?charset=UTF-8
>
> Object.prototype.ci = function(tF)
> {
>        tF.call(this);
> };
>
> This is so wrong.
>
> -- Yoan
>
> On Wed, Jun 4, 2008 at 10:01 AM, Adriano <adrianomassi@...> wrote:
>>
>> Hi all, I'm a new member so... nice to be here, I'm Adriano from Rome
>> (Italy).
>>
>> My problem is the following: I have to use the ViaMichelin maps APIs,
>> but when i include together the two library, the jquery plus the
>> viamichelin, firebug gives me this error "tF.call is not a function".
>> The maps work, but jquery doesn't any more...
>> Trying to isolate the error cause I simply set up an html document
>> that simply import the two scripts:
>>
>> <script type="text/javascript" src="jquery.js"></script>
>> <script src="http://api.viamichelin.com/apijs/js/api.js"></script>
>>
>> and this, alone, trigger the firebug error warning. "tF.call is not a
>> function".
>>
>> If is there anyone that have any glimpse of the cause of this strange
>> behaviour I'll be glad and... grateful!!
>>
>> Thank you
>>
>> Adriano
>>
>> >
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[John Resig]

> It seems to indicate that jQuery assumes that no properties have been
> added to Object.prototype?
> Is it possible that jQuery should be using hasOwnProperty in "for ... in" loops?

That is certainly an option - but at the cost of performance. We've
done testing of this in the past and have, for now, opted to err on
the side of performance instead of ubiquitous compatibility. We may
change this eventually but that's our reasoning, for now.

--John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Sam Collett]

Could this somehow be reported to the authors of these libraries that practice this bad habit?
jQuery could be modified, but sacrificing performance just for one or two scripts that do this seems detrimental (especially if it affects very few users).

Maybe there should be a list of libraries that do this, stating that they are incompatible with jQuery (and I expect other libraries as well)?

ViaMichelin have a developer blog, so I expect that this can be reported to them (and maybe someone who can figure out the API can suggest a fix)?
http://dev-blog.viamichelin.com/

They also have a developer network:
http://dev.viamichelin.com/

2008/6/4 John Resig <jeresig@...>:

> It seems to indicate that jQuery assumes that no properties have been
> added to Object.prototype?
> Is it possible that jQuery should be using hasOwnProperty in "for ... in" loops?

That is certainly an option - but at the cost of performance. We've
done testing of this in the past and have, for now, opted to err on
the side of performance instead of ubiquitous compatibility. We may
change this eventually but that's our reasoning, for now.

--John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jörn Zaefferer-2]

Could you run the map component in an iframe, to sandbox the JS, while
using jQuery for the embedding page?

Jörn

On Wed, Jun 4, 2008 at 5:09 PM, Sam Collett <sam.collett@...> wrote:

> Could this somehow be reported to the authors of these libraries that
> practice this bad habit?
> jQuery could be modified, but sacrificing performance just for one or two
> scripts that do this seems detrimental (especially if it affects very few
> users).
>
> Maybe there should be a list of libraries that do this, stating that they
> are incompatible with jQuery (and I expect other libraries as well)?
>
> ViaMichelin have a developer blog, so I expect that this can be reported to
> them (and maybe someone who can figure out the API can suggest a fix)?
> http://dev-blog.viamichelin.com/
>
> They also have a developer network:
> http://dev.viamichelin.com/
>
> 2008/6/4 John Resig <jeresig@...>:
>>
>> > It seems to indicate that jQuery assumes that no properties have been
>> > added to Object.prototype?
>> > Is it possible that jQuery should be using hasOwnProperty in "for ...
>> > in" loops?
>>
>> That is certainly an option - but at the cost of performance. We've
>> done testing of this in the past and have, for now, opted to err on
>> the side of performance instead of ubiquitous compatibility. We may
>> change this eventually but that's our reasoning, for now.
>>
>> --John
>>
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Adriano-17]

Thank to you all for your kind replies...

unfortunately it looks that the ViaMichelin developer blog isn't
working very well... the form for signaling problems doesn't work....

To Jorn: we coud, but whe have to set up a three panes layout so we
are looking for a more simple solution, in the worst case we would be
trying something similar to what you said... Thanx!

it looks I'll have to switch to another framework, even if EXT also
gives a similar error... It's too bad since we where already utilising
jQuery for other things...

Ok, again, thank you all

Best regards

Adriano

On 4 Giu, 17:17, "Jörn Zaefferer" <joern.zaeffe...@...>
wrote:

> Could you run the map component in an iframe, to sandbox the JS, while
> using jQuery for the embedding page?
>
> Jörn
>
> On Wed, Jun 4, 2008 at 5:09 PM, Sam Collett <sam.coll...@...> wrote:
> > Could this somehow be reported to the authors of these libraries that
> > practice this bad habit?
> > jQuery could be modified, but sacrificing performance just for one or two
> > scripts that do this seems detrimental (especially if it affects very few
> > users).
>
> > Maybe there should be a list of libraries that do this, stating that they
> > are incompatible with jQuery (and I expect other libraries as well)?
>
> > ViaMichelin have a developer blog, so I expect that this can be reported to
> > them (and maybe someone who can figure out the API can suggest a fix)?
> >http://dev-blog.viamichelin.com/
>
> > They also have a developer network:
> >http://dev.viamichelin.com/
>
> > 2008/6/4 John Resig <jere...@...>:
>
> >> > It seems to indicate that jQuery assumes that no properties have been
> >> > added to Object.prototype?
> >> > Is it possible that jQuery should be using hasOwnProperty in "for ...
> >> > in" loops?
>
> >> That is certainly an option - but at the cost of performance. We've
> >> done testing of this in the past and have, for now, opted to err on
> >> the side of performance instead of ubiquitous compatibility. We may
> >> change this eventually but that's our reasoning, for now.
>
> >> --John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Yoan Blanc-2]

I sent an email to Renaud Euvrard (http://renaud.euvrard.com/) who is
working at ViaMichelin. I found his name on this article (in French):
http://www.journaldunet.com/developpeur/itws/071031-itw-viamichelin.shtml
where they are saying how good their API is. Guillaume Macaigne, the
first name doesn't work at ViaMichelin anymore according to LinkedIn.

Hoping he (or someone of the ViaMichelin team) will join this thread very soon.

-- Yoan

On Thu, Jun 5, 2008 at 10:46 AM, Adriano <adrianomassi@...> wrote:

>
> Thank to you all for your kind replies...
>
> unfortunately it looks that the ViaMichelin developer blog isn't
> working very well... the form for signaling problems doesn't work....
>
> To Jorn: we coud, but whe have to set up a three panes layout so we
> are looking for a more simple solution, in the worst case we would be
> trying something similar to what you said... Thanx!
>
> it looks I'll have to switch to another framework, even if EXT also
> gives a similar error... It's too bad since we where already utilising
> jQuery for other things...
>
> Ok, again, thank you all
>
> Best regards
>
> Adriano
>
> On 4 Giu, 17:17, "Jörn Zaefferer" <joern.zaeffe...@...>
> wrote:
>> Could you run the map component in an iframe, to sandbox the JS, while
>> using jQuery for the embedding page?
>>
>> Jörn
>>
>> On Wed, Jun 4, 2008 at 5:09 PM, Sam Collett <sam.coll...@...> wrote:
>> > Could this somehow be reported to the authors of these libraries that
>> > practice this bad habit?
>> > jQuery could be modified, but sacrificing performance just for one or two
>> > scripts that do this seems detrimental (especially if it affects very few
>> > users).
>>
>> > Maybe there should be a list of libraries that do this, stating that they
>> > are incompatible with jQuery (and I expect other libraries as well)?
>>
>> > ViaMichelin have a developer blog, so I expect that this can be reported to
>> > them (and maybe someone who can figure out the API can suggest a fix)?
>> >http://dev-blog.viamichelin.com/
>>
>> > They also have a developer network:
>> >http://dev.viamichelin.com/
>>
>> > 2008/6/4 John Resig <jere...@...>:
>>
>> >> > It seems to indicate that jQuery assumes that no properties have been
>> >> > added to Object.prototype?
>> >> > Is it possible that jQuery should be using hasOwnProperty in "for ...
>> >> > in" loops?
>>
>> >> That is certainly an option - but at the cost of performance. We've
>> >> done testing of this in the past and have, for now, opted to err on
>> >> the side of performance instead of ubiquitous compatibility. We may
>> >> change this eventually but that's our reasoning, for now.
>>
>> >> --John
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Adriano-17]

Yes, it would be great if somebody in Michelin would realize that
their API's are not compatible with one of the most widely used JS
framework and rush to fix the problem...

Let's hope...

Adriano

On Jun 5, 3:56 pm, "Yoan Blanc" <yoan.bl...@...> wrote:

> I sent an email to Renaud Euvrard (http://renaud.euvrard.com/) who is
> working at ViaMichelin. I found his name on this article (in French):http://www.journaldunet.com/developpeur/itws/071031-itw-viamichelin.s...
> where they are saying how good their API is. Guillaume Macaigne, the
> first name doesn't work at ViaMichelin anymore according to LinkedIn.
>
> Hoping he (or someone of the ViaMichelin team) will join this thread very soon.
>
> -- Yoan
>
> On Thu, Jun 5, 2008 at 10:46 AM, Adriano <adrianoma...@...> wrote:
>
> > Thank to you all for your kind replies...
>
> > unfortunately it looks that the ViaMichelin developer blog isn't
> > working very well... the form for signaling problems doesn't work....
>
> > To Jorn: we coud, but whe have to set up a three panes layout so we
> > are looking for a more simple solution, in the worst case we would be
> > trying something similar to what you said... Thanx!
>
> > it looks I'll have to switch to another framework, even if EXT also
> > gives a similar error... It's too bad since we where already utilising
> > jQuery for other things...
>
> > Ok, again, thank you all
>
> > Best regards
>
> > Adriano
>
> > On 4 Giu, 17:17, "Jörn Zaefferer" <joern.zaeffe...@...>
> > wrote:
> >> Could you run the map component in an iframe, to sandbox the JS, while
> >> using jQuery for the embedding page?
>
> >> Jörn
>
> >> On Wed, Jun 4, 2008 at 5:09 PM, Sam Collett <sam.coll...@...> wrote:
> >> > Could this somehow be reported to the authors of these libraries that
> >> > practice this bad habit?
> >> > jQuery could be modified, but sacrificing performance just for one or two
> >> > scripts that do this seems detrimental (especially if it affects very few
> >> > users).
>
> >> > Maybe there should be a list of libraries that do this, stating that they
> >> > are incompatible with jQuery (and I expect other libraries as well)?
>
> >> > ViaMichelin have a developer blog, so I expect that this can be reported to
> >> > them (and maybe someone who can figure out the API can suggest a fix)?
> >> >http://dev-blog.viamichelin.com/
>
> >> > They also have a developer network:
> >> >http://dev.viamichelin.com/
>
> >> > 2008/6/4 John Resig <jere...@...>:
>
> >> >> > It seems to indicate that jQuery assumes that no properties have been
> >> >> > added to Object.prototype?
> >> >> > Is it possible that jQuery should be using hasOwnProperty in "for ...
> >> >> > in" loops?
>
> >> >> That is certainly an option - but at the cost of performance. We've
> >> >> done testing of this in the past and have, for now, opted to err on
> >> >> the side of performance instead of ubiquitous compatibility. We may
> >> >> change this eventually but that's our reasoning, for now.
>
> >> >> --John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Godmar Back]

One idea would be to write a compatibility check script
"jquery-compatibility.js" that collects and stores the experience
gained from debugging such compatibility issues in the form of
JavaScript code. (If I recall, in a separate thread, a version of
prototype was found incompatible because it changed Array.prototype in
some way).

This script, when included in the place at which otherwise jquery.js
would be included, could check the environment for such conditions as
whether properties have been added to the prototype of essential
objects by already included scripts. It could also contain specific
checks for properties added by libraries known to be incompatible.
Since much JavaScript code is copied between sites, the same issues
may reoccur. You could then point users to include the compatibility
check script and if it flags anything, follow the instructions given.

 - Godmar

On Fri, Jun 6, 2008 at 4:28 AM, Adriano <adrianomassi@...> wrote:
>
> Yes, it would be great if somebody in Michelin would realize that
> their API's are not compatible with one of the most widely used JS
> framework and rush to fix the problem...
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

[Godmar Back]

Draft in case any jQuery developer wants to add that to their blog/plugins.

---
//
// Check for known compatibility issues.
//
(function () {
    function reportIncompatibility(msg, link) {
        document.write('<span style="color: red">Incompatibility
detected.</span><br />' + msg + '<br />');
        if (link)
            document.write('For more information, see <a href="' +
link + '">here.</a>');
    }

    // test if Object.prototype was extended.
    var emptyobj = {};
    for (var p in emptyobj) {
        reportIncompatibility(
              "Found property " + p + " in Object.prototype. "
            + "jQuery is not compatible with scripts that augment
Object.prototype.",
               "http://dev.jquery.com/ticket/262");
    }

    // add more here
})();

---

On Fri, Jun 6, 2008 at 8:36 AM, Godmar Back <godmar@...> wrote:

> One idea would be to write a compatibility check script
> "jquery-compatibility.js" that collects and stores the experience
> gained from debugging such compatibility issues in the form of
> JavaScript code. (If I recall, in a separate thread, a version of
> prototype was found incompatible because it changed Array.prototype in
> some way).
>
> This script, when included in the place at which otherwise jquery.js
> would be included, could check the environment for such conditions as
> whether properties have been added to the prototype of essential
> objects by already included scripts. It could also contain specific
> checks for properties added by libraries known to be incompatible.
> Since much JavaScript code is copied between sites, the same issues
> may reoccur. You could then point users to include the compatibility
> check script and if it flags anything, follow the instructions given.
>
>  - Godmar
>
> On Fri, Jun 6, 2008 at 4:28 AM, Adriano <adrianomassi@...> wrote:
>>
>> Yes, it would be great if somebody in Michelin would realize that
>> their API's are not compatible with one of the most widely used JS
>> framework and rush to fix the problem...
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-dev@...
To unsubscribe from this group, send email to jquery-dev-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---