After much persuasion, I’ve decided to fly in the face of public opinion and record one of the songs from my SharePoint show ![]()
Stop, Collaborate and Listen:
SharePoint’s Back with a Brand New Invention.
Subscribe
joelblogs.co.uk | joelj.co.uk | joeljeffery.co.uk | jfdiphoenix.co.uk
After much persuasion, I’ve decided to fly in the face of public opinion and record one of the songs from my SharePoint show ![]()
Stop, Collaborate and Listen:
SharePoint’s Back with a Brand New Invention.
I was recently asked how to remove the Editor Parts (Appearance, Layout, Advanced, etc) from custom Web Parts.
One strategy is to implement your own Editor Part and mark the built-in ones as not Visible.
Firstly, we need to create our Editor Part class:
class MyEditorPart : EditorPart { protected override void CreateChildControls() { // this line hides the default EditorParts Parent.Controls[2].Visible = false; base.CreateChildControls(); } public override bool ApplyChanges() { // do stuff here return true; } public override void SyncChanges() { // do stuff here } }
And here’s how we invoke our Editor Part from our Web Part:
public class MyWebPart : WebPart { public override EditorPartCollection CreateEditorParts() { ArrayList aryParts = new ArrayList(); MyEditorPart myEditor = new MyEditorPart(); myEditor.ID = this.ID + "_myEditorPart"; aryParts.Add(myEditor); return new EditorPartCollection(aryParts); } // do more stuff here... }
Hopefully, when you edit the Web Part it should look something like this:

The next step would be to extend CreateChildControls(), ApplyChanges() and SyncChanges() to get and set any properties you’d like to allow users to edit.
If you’re creating or editing a JavaScript file in Visual Studio and you would like some help creating Client Object Model code, you’re not alone.
It’s a little bit cryptic, but we can tell IntelliSense to include any JavaScript libraries you have on your development machine.
Simply place the following two lines at the top of your source code (watch out for line breaks!):
/// <reference path="C:\\Program Files\\Common Files\\Microsoft Shared\\Web Server Extensions\\14\\TEMPLATE\\LAYOUTS\\MicrosoftAjax.js" /> /// <reference path="C:\\Program Files\\Common Files\\Microsoft Shared\\Web Server Extensions\\14\\TEMPLATE\\LAYOUTS\\SP.debug.js" /> /// <reference path="C:\\Program Files\\Common Files\\Microsoft Shared\\Web Server Extensions\\14\\TEMPLATE\\LAYOUTS\\SP.Core.debug.js" />
Then, you can get IntelliSense when you need it the most!
Full article on MSDN available here.
Enjoy!
The Google Maps Web Part fir SharePoint 2010 and Office 365 is now free for download complete with source on CodePlex.
Our first product is a SharePoint 2010 Web Part that allows you to embed Google Maps in a SharePoint page.
You can use the Web Part in SharePoint Foundation, SharePoint Server (Standard and Enterprise) and even SharePoint Online (Office 365).
It lets you select a centre for the map, and then place a pushpin at a desired location. You can also add a title and label, and control the zoom level and a number of other settings. Not bad for under $20. ![]()
Come and read all about our Google Maps Web Part for SharePoint 2010 at JFDI Phoenix Ltd’s web site.
This year, I was very privileged to be asked to present the Cloud Hack event. In these videos we go behind the scenes and talk to the participants and to the API partners who kindly gave us access to their web APIs for the day.
We set the developers a challenge to build the most imaginative applications they could, using as many of the APIs as possible during the day.
In the second video, we meet the API partners. Thanks to Huddle, PayPal, Network Rail Enquiries and of course Microsoft Bing Maps.
In the third video, we catch up with some of the coders and see what they have managed to build on Azure in the cloud.