Recently, while working on a new JavaScript mockup I’ve noticed that JavaScript lacks a decent support for retrieving values of object properties. Constantly checking whether both object and property makes the code almost unreadable. But isn’t there a better to get the values of object properties and keep the JavaScript code to the minimum?

For the last couple of weeks we’ve been thinking here at Imtech ICT Velocity about how we could improve our SharePoint development process. During the last year we have gathered a lot of different tools which help us to automate the routine. And while they all are definitely very useful, they make the development environment quite complex. Maybe even too complex. One of the improvements we thought about was integrating all these different tools we have made into Visual Studio. Imtech Fields Explorer is the first one to go.

Via Jaap Vossers: Recently I’ve been pinged about a new SharePoint project on CodePlex called SharePoint InlineSiteSettings. What is does is to display the links to all Site Settings on the front-end saving you at least two clicks:

While working on SharePoint solutions once in a while you need to create custom Site Definitions. It’s not easy to work with Site Definitions: they can easily get very complex and are almost impossible to debug. Unfortunately there are situations when you cannot avoid using custom Site Definitions. Is there anything we could do to make it easier to work with Site Definitions?

Via EndUserSharePoint.com: The ability to print web pages has been available for years. Comparing it to the transition that most browsers have gone through, there is very little that has changed about how web pages are printed. While moving the digital version of a page to its paper equivalent, important information is not accessible to the print job. Luckily you can quite easily provide your visitors with a richer printing experience using no more than a couple of lines of JavaScript.