Where does CB load jQuery

Hi,
I tried to search for an answer to this question on the forum , but I was unable to find a clear cut answer. Can anyone please let me know where does CB load the jQuery 1.5.0 file (the PHP code location).

This is pretty important, I have tried to go through the code w/o success please please let me know the location.

Thanks a lot in advance.
-Sushant

We can't advise you on core edits, which is likely why you never found results. CB needs to load its library as necessary when something calls the jQuery API. You can not remove or change this, sorry.

Hi Kyle,
I am not trying to edit the core files neither am I seeking advice/support for it, I just want to understand the program structure better so that I can modify my own files accordingly.

If I know where the CB loads its jQuery, or how it loads it, I can organise the loading of my JS scripts (in my own component accordingly).

In the true spirit of an open source system, there should be no problem in giving me what I seek, a little hint into the source code.

Thanks again,
Sushant

I am not trying to edit the core files neither am I seeking advice/support for it, I just want to understand the program structure better so that I can modify my own files accordingly.

Well then I see absolutely no reason not to tell you.

administrator/components/com_comprofiler/plugin.foundation.php

In class "CBframework" as function "outputCbJQuery".

If I know where the CB loads its jQuery, or how it loads it, I can organise the loading of my JS scripts (in my own component accordingly).

I see, CB does not output static jQuery. It's all done dynamically and added to the head by integrations. If going to load your own jQuery it's best to check if jQuery already exists before adding it. This can all be done with a relatively small amount of JS as follows.

With the above you'd just adjust the SRC accordingly.

In the true spirit of an open source system, there should be no problem in giving me what I seek, a little hint into the source code.

Certainly, it's not a problem at at all depending on the intentions. We don't advise users on core edits because it's counter productive to advise them on how to break our own software then they come back needing help because XYZ doesn't work anymore.