Comments for TeamSite Tuesday

Comment on TeamSite Toolbar available for download by loz

loz — Thu, 28 Jan 2010 10:08:50 +0000

Thanks Alun. It’s not in production use yet, but it’ll be introduced with the project we’re currently working on. I’ve given demos to some key users, and the response has been a resounding “Ooooh!”… a noise seldom heard by TeamSite developers

Comment on TeamSite Toolbar available for download by Alun

Alun — Tue, 26 Jan 2010 08:00:47 +0000

Look nice Loz – gives a nice solution to a common problem; teamsite navigation. How widely is it being used? Have you had some good user feedback?

Comment on TeamSite Toolbar by ddddd

ddddd — Wed, 20 Jan 2010 15:59:18 +0000

So how do we get it?

Comment on TeamSite Toolbar by Ronald

Ronald — Mon, 09 Nov 2009 15:15:00 +0000

Loz, thank you for your answer. I think this is a VERY elegant solution for a problem that shows it ugly head at every teamsite project I’ve done so far.

Comment on TeamSite Toolbar by loz

loz — Mon, 09 Nov 2009 13:52:43 +0000

Hi Ronald, It’s done client-side.

Greasemonkey is installed onto the site editor’s PC. It is configured with a list of sites to look for, e.g. http://www.channel4.com/*. When the editor browses to a URL which matches, Greasemonkey is configured to run a few lines of JavaScript:

var s = document.createElement('script'); s.setAttribute("src", "http://teamsite.channel4.com/iw/greasemonkey-include.js"); s.setAttribute("type", "text/javascript"); document.body.appendChild(s);

This has the effect of injecting some more JavaScript into the page that they’re currently viewing.

Therefore only the site editors will get the JavaScript which creates the toolbar. The original page that the public see is completely untouched, with no toolbar code in it at all.

Does that answer your question?

Comment on TeamSite Toolbar by Ronald

Ronald — Mon, 09 Nov 2009 11:13:41 +0000

Hi, this looks very good. 1 thing I like to know is how does the webserver or the browser ‘know’ that is should show the toolbar? Is this does server or client side? And how?

Comment on Solving the Environment Problem at Channel 4 by loz

loz — Fri, 23 Oct 2009 11:29:38 +0000

For code common across branches, it can be stored in the level above. The search path starts in the current branch, and then hops up the tree. Finally, the standard locations are used for fallback.

Project 1 – /default/main/Channel4/dev/Project1/STAGING/iw_admin/perl/lib/
Project 2 – /default/main/Channel4/dev/Project1/STAGING/iw_admin/perl/lib/
Common Code – /default/main/Channel4/dev/STAGING/iw_admin/perl/lib/
Fallback – $IWHOME/iw-perl/site/lib/

Good point regarding security. I think that particular story card got lost in the deck! We should have restricted write access to a specific TeamSite group.

Comment on Solving the Environment Problem at Channel 4 by Darren Ferguson

Darren Ferguson — Mon, 12 Oct 2009 10:54:44 +0000

Interesting read.

Were there any security concerns around storing code in a branch or did you just use submit.cfg to restrict them accordingly?

How about code that was common across branches. Were those files still stored in iw-home/site/lib or did you create a common code branch for versioning purposes?