Over the past year, the use of jQuery to enhance the SharePoint interface has exploded. Maybe you were tempted to take the plunge, but as an end user you were intimidated by this technology you know little (or nothing) about?

Well, this coming Monday is your chance to get on the bandwagon. Mark Miller and I will be hosting a new workshop: Get Started with jQuery in SharePoint.

Your goal is of course not to become a jQuery expert. But still, by the end of the workshop:
- You’ll have written - and tested - your first jQuery script
- You’ll know the key domains in which jQuery shines
- You’ll be aware that jQuery is not always the best option, and that you should not grab every script you find on the Internet

As usual we’ll provide concrete examples that you’ll test live in your own sandbox.

For more information and to register:
http://series-jquery.eventbrite.com

An update for the Easy Tabs Lite – version 4.0 alpha – should be ready in a week or so.

The new version will handle cases when a Web Part has no title (it will simply ignore it, instead of triggering an error in the current version). Also I have ”widgetized” the script, which means that you won’t need to tweak the code anymore to get two Easy Tabs on a same page.

A couple options come with v4:
- Split (tabs spread across two rows)
- Display all/Expand all (make all the Web Parts visible)
- Autoplay: automatically switch to the next tab after a certain amount of time. This can be useful to build a simple slide show for example.

You can experiment with the Expand all and Autoplay (8 sec/tab) options on my home page:
http://www.pathtosharepoint.com

Like many other SharePoint consultants, I don’t expect to see a lot of SharePoint 2010 migrations this year. The majority of companies that have invested in an Office 2007 deployment will choose to wait and see. Technical constraints (server requirements, integration with client side applications) will reinforce this behavior.

That said, sticking with SharePoint 2007 for now doesn’t mean that you should not prepare for the future. And I am receiving more and more inquiries from readers worried that my scripts may not work in SharePoint 2010. So here is where I stand today.

First, it is clear that several scripts will need an upgrade to work in the next version. They rely on the standard page layout, which has evolved in SharePoint 2010: HTML tables replaced with div elements, new CSS class names, different calendar structure, etc.

From my first investigations, I am confident that only minor tweaks will be needed for most scripts, like the Easy Tabs. However, I’ll only be able to confirm this when the final release is out. Most of my scripts are at the very end of the page rendering chain, and any upstream modification might affect them. My big handicap is that, as an independent consultant having no direct contact with Microsoft, I don’t have any special privileges like access to information before the public release. I’ll keep you updated as I continue my investigations.

While my Easy Tabs work perfectly in SharePoint 2007 with OOTB Web Parts, I often hear complaints from users that their don’t work with third party Web Parts. Why is that?

The Easy Tabs rely on each Web Part following a standard pattern (see a simplified diagram on this page, “behind the scene” tab). This gives the Easy Tabs a straightforward way to scan a Web Part zone and identify for each Web Part:
- the title (will be converted into a tab)
- the content (will be displayed or hidden depending on the selected tab)

When the Easy Tabs come across a Web Part that doesn’t follow the standard structure, they don’t know how to deal with it.

How can we move forward on this issue? Tweaking my script will only help for a specific third party application. Here is my proposal:
- if your third party Web Parts work with the Easy Tabs,  use the comments section to let everybody know.
- if they don’t work, you could let the vendor know that their Web Parts don’t adhere to the standard structure. It may be an easy step for the vendor to fix it.

In the past two years, more and more SharePoint blogs have started sharing snippets of code. Some feature innovative ideas, and maybe you’ve wanted to apply them on your own sites. But did you first check if you’re allowed to do so?

Original content published on the internet is protected by copyright laws. It means that you cannot reuse it without the author’s consent. To be honest, I didn’t pay too much attention to this when I started a blog in 2008. It occured to me when I started reusing scripts from others, for example jQuery plugins. I was also alerted last year when Paul Grenier at endusersharepoint.com started including copyright notices. I contacted him, and he confirmed that his purpose was to give readers the freedom to reuse his scripts.

What does all of this have to do with you? Well, as it turns out, I have never precised under which conditions the content of my blog can be reused. I am not the only one btw, most of us bloggers are amateur publishers and started writing without being aware of the legal whereabouts. It may not have been an issue in the past, when code was limited to short snippets showing how to hide a button or change a background color. But today some scripts – like the Easy Tabs for example – are full blown solutions.

One of my top priorities today is to take the steps to clarify what readers can do with my content. I plan to include a copyright notice in my original scripts, and I need to choose a license or two under which I’ll make my work available. I have defined a few objectives:
1/ Make sure that end users can freely and legally use in their organizations the scripts I publish, without having to ask me first.
2/ Protect myself, so that I am not liable for any misuse of my scripts.
3/ keep some control on how my content is republished, or reused in other scripts.

How to do this in practice? Instead of trying to reinvent the wheel, the best is to leverage an existing license. However, there’s a bunch of them out there, so the choice is not easy. The MIT license is very open, so it seems like the right choice. But I don’t want to rush, and I’ll take the time to make an informed decision.

For the record, here are a few other important concepts associated with copyright.

Derivative work

Copyright extends to derivative work: works based or derived from copyrighted work require permission from the owner of the original work. So for example, my copyright would apply to a method that uses calculated columns to write HTML.

Fair use

The law allows “fair use” of copyrighted work. On the internet, it often means copying a short excerpt and linking to the original work.

I’ll add to this another principle, not derived from copyright but from collaborative systems: keep only one version of the truth. As a consultant, I am a strong defender of this principle – and this is actually one of the strengths of SharePoint: allowing the reuse of the same content in different views.
An issue I have been confronted with, for example, is that some people copied the content of my original post, “using calculated columns to write HTML”. 18 months later, the copies are still around, haven’t been updated and are not helpful anymore.

Obviously all of this is fairly new to me, so advice is welcome!

Additional reading: 10 Big Myths about copyright explained

In addition to live online workshops that I co-host with Mark Miller, I am now offering one-on-one sessions. The objective is to provide support to readers who need help to implement the customizations found on my blog.

If you are a frequent visitor of my blog, rest assured that I’ll continue answering comments and e-mails as before. The online sessions target people who want to benefit from a hands-on experience.

For more information on the upcoming workshops and the one-on-one sessions, please visit the home page of my SharePoint site.

You haven’t seen any update to my scripts in a while, and you’re wondering what the hell this guy is doing… Well, let me explain.

First, for the sake of transparency, I have decided to communicate on my action items. From now on, you’ll be able to follow my work in progress through my SharePoint To Do list. Hopefully this will give you a better idea of the workload behind the upcoming releases.
My top priority is version 4 of the Easy Tabs Lite. Because this is the most popular of my scripts, and also because…I plan to use it on my own sites!

Besides this, and the time spent responding to blog comments and e-mails, a couple things have kept me busy in the past weeks.

First, I’m back from a week in Beijing, where I celebrated the Chinese New Year. Before this, I was involved (or should I say dragged by Mark Miller?) in two SharePoint conferences: SharePoint Saturday EMEA (follow this link for the recordings, and see my previous post for the slides) and the San Francisco SPTechcon (more details here).

In January, I worked with Mark Miller on my sessions for the Spring 2010 live online workshops. I recommend that you check them out, and register for the free webinars that will start this month.

In addition to this, I have spent a significant amount of time investigating two issues: copyrights for my site content and scripts upgrades to SharePoint 2010. I’ll dedicate specific posts to these two important topics.

I wish you a Happy Year of the Golden Tiger!

I wanted to share this mosaic from the official SharePoint 2010 site, as an example of how Web design techniques are making their way into SharePoint 2010.

If you are familiar with Web design, you’ll recognize a CSS sprite. The principle: multiple images used throughout the Web page are combined into a “master image”. This reduces server requests and improves page load performance.

In the above example, the master image is used to populate the list ribbon (also a feature introduced in SP 2010):

Note that I already talked about CSS sprites a couple months ago, with this example designed to display inline pies in SharePoint lists: http://pathtosharepoint.com/Utilities/PieSprite50.png

Some references if you’d like to learn more and see other real life examples:
- CSS Sprites: Image Slicing’s Kiss of Death by Dave Shea March 2004
http://www.alistapart.com/articles/sprites 
Sprites are the extension of a technique called “sliding doors”, used to create button rollover effects.
- The Mystery Of CSS Sprites: Techniques, Tools And Tutorials
http://www.smashingmagazine.com/2009/04/27/the-mystery-of-css-sprites-techniques-tools-and-tutorials

Categories

I’m on Twitter!