Comments for BinaryJam

Comment on Embracing the dark side – Part 2, Customising a List Form by Sharepoint Updates December-15-2011 | SDavara's Sharepoint Knowledge Center

Sharepoint Updates December-15-2011 | SDavara's Sharepoint Knowledge Center — Mon, 26 Dec 2011 05:48:02 +0000

[...] Embracing the dark side – Part 2, Customising a List Form [...]

Comment on Embracing the dark side – Part 3, Image browser enhancement to a form by Sharepoint Updates December-20-2011 | SDavara's Sharepoint Knowledge Center

Sharepoint Updates December-20-2011 | SDavara's Sharepoint Knowledge Center — Wed, 21 Dec 2011 19:19:31 +0000

[...] Embracing the dark side – Part 3, Image browser enhancement to a form [...]

Comment on Embracing the dark side – Part 3, Image browser enhancement to a form by Sharepoint Updates December-22-2011 | SDavara's Sharepoint Knowledge Center

Sharepoint Updates December-22-2011 | SDavara's Sharepoint Knowledge Center — Wed, 21 Dec 2011 19:00:17 +0000

[...] Embracing the dark side – Part 3, Image browser enhancement to a form [...]

Comment on Embracing the dark side – Part 1 by Sharepoint Updates December-17-2011 | SDavara's Sharepoint Knowledge Center

Sharepoint Updates December-17-2011 | SDavara's Sharepoint Knowledge Center — Fri, 16 Dec 2011 18:37:45 +0000

[...] Embracing the dark side – Part 1 [...]

Comment on jQuery autocomplete for SharePoint Search Box by BinaryJam

BinaryJam — Wed, 09 Nov 2011 09:22:35 +0000

As Marc discusses in his blog post here

http://sympmarc.com/2011/11/08/problem-with-jquery-1-7-and-spservices/

Unfortunately the “[nodeName=z:row]” syntax is no longer valid in the jQuery 1.7 library.

Read Marc’s articles for more info.

Comment on Upgrading SharePoint 2007 to 2010 – Find those missing EventReceivers / Features / SiteDefs by Binaryjam

Binaryjam — Fri, 05 Aug 2011 10:04:10 +0000

Glad to help, although not being the main dev behind each individual search type, I thought by posting this, it would certainly expand the chances of someone trying to fix the problem finding a solution

Comment on Upgrading SharePoint 2007 to 2010 – Find those missing EventReceivers / Features / SiteDefs by Ashraf

Ashraf — Fri, 05 Aug 2011 05:29:01 +0000

I am working in a sharepoint 2010 migrated farm to fix this sort of issue while saving site as site template and here find the clue for solution.

Thanks for your post.

-Ashraf

Comment on Multiple jQuery on a page by Binaryjam

Binaryjam — Fri, 24 Jun 2011 09:41:26 +0000

I was aware that noConflict existed, however I had not investigated too much time in it, so I didnt know that you could “unhook” both $ and jQuery and assign your own.

I will do some more playing with this, it may be preferable for a solution vendor to include extra jQuery in the solution even if the customer has it in their masterpage, but decouple the window.$/jQuery refs and run in context of some namespaced version. If this is possible, certainly with the CustomAction script link you have no control on the order that same sequence links are applied. Definately more playing required.

In a webpart of course I can control when I output things, so I can also add a bunch of checkboxes on the part to say load jQuery/or not handle it in page etc

Like I say lots more effort required

Comment on Multiple jQuery on a page by Binaryjam

Binaryjam — Fri, 24 Jun 2011 09:34:44 +0000

I think your right for the forseeable future, we just have to cope. jQuery in the masterpage and communication to your devs is the best way forward.

I Still feel that for sandbox solution vendors people you can’t inform; that some central way provided in the product is the best solution. However I think I’m alone in the wilderness on that one though

Comment on Multiple jQuery on a page by Marc D Anderson

Marc D Anderson — Thu, 23 Jun 2011 19:10:14 +0000

I see your points, but I think for the forseeable future, code management is the responsibility of the developers, whatever type of developers they are. jQuery is one of the current popular flavors, and there will always be new ones.

Many times IT sees that this can get out of hand, and the response is to shut everyone off. A better answer is to work with the people who are using things like jQuery to come up with better ways to manage things. Simply adding a jQuery reference to the master page and letting everyone know it’s there goes a long way toward reducing issues.