scott's "siteexperts" place
scott's "siteexperts" place
.containerpadding, .containerpadding td, .containerpadding th, ul.subnav, ul.list, .containerfullview, .containerfullview td, .containerfullview th {}
.containerheader, .containerheader td, .containerheader th {}
windows live™windows live serviceshomecalendarcontactsfamily safetygalleryhotmailonecareskydrivespacesall servicesother live serviceslive searchoffice livexbox live msn accountfeedbackhelp centralhomehotmailspacesonecare
search sign in
spaces home sign upspaces home your spacefriendsphotos skydriveevents scott's "siteexperts" pl...photosprofilefriendsmore bloglists tools send a messagesubscribe to rss feedtell a friendadd to my msnadd to live.cominvite as friendsign up for alertsexplore spaces
scott's "siteexperts" placemy little place away from home...
blog
8/1/2006talking about gadget devs, come out and play!i know it has been awhile since i posted. tonight we have big news! msn spaces is now windows live spaces. the windows live vision is taking shape! in addition to tons of cool improvements (themes, social networking, and more), now gadgets can be built for spaces as well as live.com. stay on top of developing for spaces at the spaces platform blog.
one of the best aspects of gadgets on spaces is their viral nature. see a cool gadget on someones space - just click on the + sign and you can quickly add it to your space. let the fun begin!
quote
gadget devs, come out and play!
admit it.
you've always thought msn spaces was pretty cool -- that we did some things right and would work hard to smooth out any rough edges over time. but, you weren't sure if the spaces team would ever let developers outside the company party in someone else's space. well, a big part of joining the windows live family today is support for web gadgets written by anyone including you! thanks to the great work done on gadgets to date, you can now write a gadget that works both in live.com (personalized portal) and spaces (online expression/identity). and, it only takes one person adding it to their space for your gadget to become popular -- visitors to that space can choose "add to your space" or "add to live.com" right from the header of the gadget, then visitors to that space can add to their spaces, and it's off to the races!
what kind of gadget makes sense in a space?
remember that the live.com portal is about you catching up on the world. spaces is about the world (however big or small you define it with the permissions you set) catching up on you. users will decide which gadgets are worthy of adding to their space or not, and given our experience with spaces features to date, the ones that will be the most successfull will be:
customizable -- let the space author personalize the gadget so their instance of it is different than another spaces user's instance. this could be as simple as letting the space author select the city they want to show weather for or as complicated as pulling the user's account data in from another service (ie, his/her netflix queue).
reflective of the author's personality -- a gadget that helps the author to be creative with little or no work is more relevant than one that lets a visitor come to a space and check their mail account or convert their currency. all of those gadgets are killer apps; it's just the ones that are more like sharing your photos or music tastes will probably be more popular.
adaptive to our rich themes/layouts -- after adding your gadget to your own space for testing, try selecting a bunch of dark and light themes and moving the gadget between our narrowest and widest columns to make sure it works well in all scenarios. you want that puppy to shine!
how do i get started?
1. build a windows live web gadget according to the sdk available at the windows live dev site.
2. if your gadget has any settings/edit ui that visitors shouldn't see, then use the following code to detect whether spaces is running the gadget in author mode and show/hide the ui accordingly. there is a p_args argument outlined in the gadgets sdk and we've added a new method off of that called getmode(). you can do a simple comparison of the value returned from that method call to determine author vs. visitor mode.
something like the following:
foo = function(p_elsource, p_args, p_namespace)
p_args.module.getmode() == web.gadget.mode.author
3. add the gadget to your own space using the following spaces api:
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=urlencodedpathtoyourh ostedgadgetmanifesturl
switch between "edit your space" and "view your space" to see how it behaves in both author and visitor modes. if your manifest file, javascript, and css are hosted anywhere but windows live gallery (gallery.live.com), the gadget can only be added for editing/viewing by the space owner. it will be hidden to visitors.
4. zip up your manifest file and supporting javascript/css files and submit that gadget package to the windows live gallery so other visitors can add it to their space by going to customize --> modules --> "add gadgets from windows live gallery". once it has been verified to work in each service, it will appear in the gallery for users to add to live.com or spaces. make sure you use relative urls (mygadget.css instead of http://foogadgetdeveloper.com/mygadget.css) in your manifest xml to point to the scripts/css or the gadget will be rejected during verification.
5. if you upload a cool gadget to gallery that you think will be a hit with spaces users, comment on this post or send mail to spgadget@microsoft.com. same thing applies if you have feedback or feature requests for making gadget development for spaces better.
we'll be updating the gadgets sdk and sample code on dev.live.com very soon to reflect the additional spaces items. in the meantime, you have everything you need above.
good luck stormin' the castle!
-- jay fluegel11:48 pm | add a comment | read comments (8) | send a message | permalink | view trackbacks (0)5/4/2006watch my engineering great ajax experiences talk...my presentation from the mix06 conference, lessons from the trenches: engineering great ajax experiences is now online:
ngw020 - lessons from the trenches: engineering great ajax experiences
description:explore the challenges and lessons learned developing the windows live and gadgets web client frameworks powering windows live, hotmail (kahuna beta), spaces, and more. this technical talk presents design and architectural considerations for building interactive ajax-like sites. see how componentization, network management, accessibility, page composition, and more impact the design and engineering of your web application.
(to find other talks, go to the main mix06 sessions page).
3:59 am | add a comment | read comments (8) | send a message | permalink | view trackbacks (0)4/26/2006gadgets and cross-browser development
we are working hard to improve the gadget framework documentation. in the meantime (and as we improve documentation), i am working on a series of short tutorials, tips, and highlights introducing how to use the gadget framework and the underlying apis.
i am going to start with our compatibility layer. after exploring various third-party gadgets being developed for live.com, i discovered that many developers are still struggling with the api differences between firefox and internet explorer. most common, i see various tricks to handle the event model differences where ie uses a global event object and firefox passes the event object as an argument to your handler.
this is not necessary when you build gadgets. instead, you should be leveraging the underlying compatibility layer that is part of the overall gadget framework.
as i posted last september, as we develop our properties, almost none of our application logic contains browser specific code. instead, we develop once to the internet explorer api and our code runs without modification in firefox. this occurs because we download a special script that emulates the most useful ie’isms inside of firefox and in a few cases, firefox/w3c’isms in internet explorer. in this article i highlight the most useful methods and properties of this layer (i promise we will develop a full reference in the near future).
event model
this is easy – always attach events using attachevent and detachevent. do not assign event handlers using function references (e.g., myelement.onclick = dothis) nor use the addeventlistener approach.
in your event handlers, don’t worry – you will always get the global event object. for example: function doclick()
{
alert("you clicked on a " + event.srcelement.tagname + " element");
}
document.body.attachevent(“onclick”,doclick);
also, as a general practice (i will cover this more in later articles but this is extremely important), when writing gadgets, be sure to detach any event handlers in your dispose handler. otherwise, your gadget will leak memory due to known browser issues.
what can you do with this event object? you can check out the msdn reference as most properties are exposed. in addition to the standard properties, below are the list of properties we added to firefox:
srcelement
cancelbubble
offsetx
offsety
x
y
returnvalue
button (few issues as firefox does not properly distinguish between the left button and no button)
fromelement
toelement
we have also gone further and extended firefox with the very useful mouseenter and mouseleave events. as long as you attach these events using the attachevent and detachevent methods, these events fire just as they do in internet explorer. these events are very useful for quickly and easily detecting when a mouse enters or leaves a specific element. again, check out the msdn reference for more details.
we even have a reasonable emulation of mouse capturing. however, this is most useful in the context of an entire web-page not within a simple gadget. this is because mouse capturing in firefox only fires within the context of the browser client area. regardless, when using mouse capturing (setcapture and releasecapture methods), the mouse events fire properly on the correct elements.
we also fixed the firefox onclick event to only fire for the left mouse button (firefox fired for all mouse buttons). this little difference could cause you grief in your application. (for those of you who noticed that we also accidentally prevented the ability to open pages in new tabs via the middle button, that will be fixed real soon).
useful element methods
internet explorer also supports a number of very helpful methods and properties on every element. these apis simplify day-to-day programming and are very useful for building your application. below are the list of element functions we added to firefox. again, check out msdn for the details (linked for each item below) on how they work.
click()
setcapture(), releasecapture()
insertadjacentelement()
children collection
parentelement property
innertext property
currentstyle property (see below)
swapnode()
replacenode()
removenode()
contains()
the currentstyle property returns the value actually being applied to the element. we currently support a subset of css attributes that we have found useful: border, margin, padding for top, left, right, and bottom; position; height; width; zindex; color; and direction. we will most likely extend this list over time.
useful style properties
we also extended the properties available on the style object with the extremely useful pixel* properties. these allow you to easily manipulate the dimensions of the element (assuming you are working with pixels). we also added the csstext property which gives you a serialized representation inline style.
xpath expressions
when dealing with xml documents the ability to query for specific nodes is especially useful. trying to decipher the difference between ie and firefox for querying xml can be extremely painful. so, we provided support for two very straighforward ie methods, selectsinglenode and selectnodes.
creating xmlhttp objects
when you need to create a new xml http object, you can now simply use the standard approach, var y = new xmlhttprequest(). however, as i will cover in future articles, i highly recommend you leverage our built-in network stack for all your network requests.
parsing xml
last, but not least, you have a string that you want to load into an xml dom - just use the standard dom parser object: var dp = new domparser();
var xmldom = dp.parsefromstring(yourxmlstring);
this concludes my very brief and fast introduction to our compatibility layer. we are continually expanding the functionality. for example, we have basic ie filter support (alpha filters assigned via script will also apply in firefox). i will cover these in later posts. for now, resist the urge in your gadgets to author code differently for each browser. instead, take the easy road and let our compatibility layer do all your heavy lifting.
last, since it will inevitably come up, see the following post on why we support or don't support other browsers (while the post talks about start.com it is relevant to all properties on our framework).11:35 pm | add a comment | read comments (3) | send a message | permalink | view trackbacks (0)4/25/2006what we learned building live.com (or why are we slow)?
over the last 18 months, we have explored how to build a highly-interactive, customizable, and extensible portal. the first iteration was a simple portal on start.com. we created various iterations (start.com/1, start.com/2, start.com/3) which have evolved into the first fully extensible portal on live.com. today, from live.com to the kahuna (hotmail) beta to msn spaces, and so-on, we are investing heavily in building very rich, interactive experiences. with these investments, we are learning a great deal on the right and wrong ways to engineer rich, interactive web-sites.
underneath all our windows live properties, we share a common framework for how we engineer our client experiences. the framework is very client-centric where we composite most of the page client-side. for example, if you were to view live.com’s html, you will notice that it serves a web-page “shell” and meta-data that describes the content. this meta-data is interpreted by the live.com application and then rendered. this approach is extraordinarily flexible as we can quickly enhance and extend the application without any heavy server lifting. however, as we have learned and is being evidenced by our customers, without care, performance degradation can quickly outweigh all other benefits.
as you examine live.com, and for the technically savvy, explore the underlying browser technology, it is easy to question whether we as microsoft and the industry as a whole are pushing the browser too far. the current crop of rich applications while cool and interactive are starting to fare poorly performance-wise against their traditional brethren. so much so that an often posed question is, where do we go from here? and is it time to reexamine building rich applications?
first, let’s step back and very briefly look at the web versus traditional software. with traditional software, you would go through various design phases starting from specifications, to architecture documentation, to development, to usability testing, to testing, and eventually to ship. the entire approach had a fairly long lead time (up to years). once released, updating the software was difficult and many times very cost prohibitive. this created a very high-bar. the web has removed almost all those barriers. on the web, we can now experiment and develop software with near real-time feedback and very fast release cycles.
i view the web 2.0 phenomena as being very early in the development lifecycle. i am not prepared to dismiss any approach, pattern, or methodology as we are still in the learning phases. in the case of windows live, as we push the browser, we are also learning a great deal. examining performance specifically - when i look at live.com today, i see incredible innovation. we are pushing the limits of extensibility (gadgets), reuse (shared frameworks across all our properties), and are taking chances to drive new user-experience standards (look at how we present search results). on the contrary, i also see an application whose performance is starting to become painful to use. the page currently takes a long time to load, especially on the first visit. beyond our user’s feedback (we do read all messages), broader industry pundits are quick to throw in the towel on the entire technology.
we are taking a different approach to this problem. we are challenging ourselves to prove that we can architect a performance driven, rich extensible experience. we are leveraging our gained knowledge shipping the many iterations of start.com and all the beta products we are developing to improve our shared architecture and drive best patterns. using the current live.com as a simple case study, below i illustrate a few of the performance-oriented technical issues that we are working on quickly addressing:
manage your connections carefully
if you were to examine live.com at the network level, a reasonable person would quickly conclude that we are making too many connections. we decomposed this issue as follows: first, we are hitting an ie 6 issue that causes un-cached images applied dynamically via script to download on each reference. this issue typically manifests itself on slower connections – the time when bandwidth is most at a premium. we are baking a solution to this problem directly into our frameworks so that we pre-cache dynamically applied images before reuse. next, every rss feed and gadget manifest is a unique request. this creates a web-page that is very “chatty” – an ajax characteristic that you should work to avoid. we will solve this by intelligently batching multiple requests into a single request (and are exploring even more efficient means for the longer-term)
parsing xml is slow
we have also learned that merely parsing the rss xml can be expensive in the browser. when we parse rss, we are merely translating it into javascript structures to be further manipulated. since our server’s are already normalizing feeds to a standard format, instead of serving the rss feed directly, we are going to translate the feed directly to json (javascript structures). as a simple benchmark, on my fast developer machine we went from 400ms to parse 150k of rss to 15ms to “execute” the json response.
caching and connection management is essential
network bandwidth and connections are a scarce resource. managing them is essential to providing fast experiences (especially for subsequent loads). we are evaluating the optimal approaches for splitting resources across multiple servers to leverage as many simultaneous connections at once (the browser is limited to 2 active connections per domain). we are also reviewing all resources to make sure they are set with appropriate expirations. in general, almost all content should have expiration, even a very short one (e.g., if the user leaves the page and hits the back button, the page should be re-rendered entirely from the cache).
staging the application
one of the biggest challenges with a very rich web-application is deploying the code. the richer the site, the more code that is needed. in the case of live.com today, the entire application deploys before anything renders. however, our underlying framework supports dynamic and prioritized deployment – we just were not properly leveraging it. we are now focusing leveraging this pattern so that we can “stage” the application. we will be able to deploy the minimal code necessary to retrieve content and render the page and subsequently download features in priority order (e.g., render, then get drag-drop code, then get the rss image rotator code, etc). for features not yet in use or visible, we can deploy those last or even on demand. staging an application is fundamental to maintaining high-degrees of perceived performance.
server versus client rendering
traditional web-pages are generated via the server. live.com and many of our properties are very client-centric where the client constructs the web-page from the user’s meta-data. in general, the first time a web-page loads, a server-generated page will almost always be faster. however, with a properly architected web application, we are discovering that our subsequent loads on a client-side generated page (especially when we stage the application) can be much faster than a server-oriented page. this occurs because our client-oriented approach is highly cacheable and loads asynchronously, even off the cache. the only content we need to download is the user’s meta-data. the rest of the page, scripts, and behaviors are cached indefinitely.
this summarizes a few of the performance-driven challenges we are addressing. internally, we have developed a complete prototype that validates we can build a high-performance, scalable version of live.com that load and run near-instantly to within seconds (on broadband). we are working on integrating these improvements into the shipping site as quickly as possible. over the coming weeks and months, expect to see continuous noticeable improvements.
update: beyond performance, the live.com team just posted the goals for the live.com page. 4:29 pm | add a comment | read comments (21) | send a message | permalink | view trackbacks (2)4/9/2006this deserves a link...i've been called lots of things, but this is the first time i believe i was called a treasure... thanks scoble :-)
6:31 pm | add a comment | read comments (5) | send a message | permalink | view trackbacks (0)talking about "hack day" is creative play at workin saturday's seattle times, there was a short article about microsoft's hack day. i was part of the virtual team that helped kick off and organize the first two hack day events. they serve as a great venue to experiment and meet others. the first two focused on hacking spaces modules and building unique gadgets. we typically give a few short presentations, and then let everyone loose on the code base to experiment and innovate. check this article out to get a little glimpse into the windows live culture...
quote
"hack day" is creative play at work
...
and that's how a group of 75 microsoft developers set out thursday to brainstorm at an internal event called "hack day."
...6:28 pm | add a comment | send a message | permalink | view trackbacks (0)4/4/2006talking about: ric merrifield on the motion initiativeprior to rejoining msn/ windows live, i spent a few years trying something completely different. i was an architect on an incubation project (virtual enterprise team) exploring and bringing together soa with how businesses work. ric continues driving this work. i guarantee you will learn something new and different in this channel 9 video.
ric merrifield - microsoft gets down to business with motion initiative
"ric, director of strategy on the top secret motion incubation team, runs the motion initiative. what's that? it's a group at microsoft that studies how businesses work and looks for opportunities to help them do their business better. they made an entire map of how business works.motion's research led to the acquisition of great plains, too (which led to the dynamics suite of services/applications).enjoy this look into a team you've never heard of before today and see how microsoft approaches new markets and new acquisitions, and how it learns from other businesses."2:31 pm | add a comment | send a message | permalink | view trackbacks (1)3/21/2006presentation: lessons from the trenchesi just gave my lessons from the trenches talk at the mix06 conference. as requested, i uploaded my slide deck and you can find it at http://www.weblogging.com/decks/lessons.ppt. i believe the talk was also videotaped as a webcast and will hopefully be able to make that available.
update: if you attended the talk, be sure to provide feedback at http://content.mix06.com. also, i expect a webcast of the talk to be available within 3-4 weeks.
3:22 pm | add a comment | read comments (2) | send a message | permalink | view trackbacks (3)3/8/2006the live.com team has outdone themselves...
go check out http://www.live.com.
i expect to see more posts from the team after they get back from some much needed rest.
the experience and features have been heavily updated. a few highlights to check out:
heavily updated look and feel.
multiple pages to help organize your content. quickly rename and rearrange your pages (drag and drop them)
adding content is much easier (and again, just drag an item from the list onto your page)
the coolest updated feature: search (including extensible macros). try the infinite scroller to move through the lists, click on the drop-down to find macros to extend your search experience.
built in gadgets have an enhanced look and feel.
explore. i am sure you will find more great stuff.
12:10 am | add a comment | read comments (12) | send a message | permalink | view trackbacks (0)2/20/2006talking about "the real ajax upside"naming was never my specialty. very little known tidbit. when i wrote the first dhtml draft specification, i named it "active html" (i will leave it up to you to figure out why this is a bad name back in 1997). how did it change to "dynamic" - from looking up active in a thesaurus.
however, dynamic html as a name served its purpose well in the late 90's. i do believe remarketing the existing technology as ajax was a necessity for the community/ industry. can you imagine all the new startups going for vc capital having to explain their cool new web innovations is based on 8 year old technology :-)?
quote from tim bray's blog...
ongoing the real ajax upside"you know, i (tim) could be excused for being a little bitter here. everybody’s all gaga these days about ajax as meme-ified by jesse james garrett. check out taxi to the future, a piece i (tim) wrote for xml.com in 2001, talking about how to improve user experience and system performance with a transform-aggregate-send xml-interact architecture. remind you of anything?
but you know, i’m actually not crying in my beer because first, garrett was in the right place at the right time with the right acronym, and secondly, scott isaacs has been talking about this stuff since 1998 and helped invent most of the underlying technology, but dammit scott, how could you ever expect to hit the memescape big-time with a dorky name like “dynamic html”?"9:26 pm | add a comment | read comments (5) | send a message | permalink | view trackbacks (0)2/6/2006presentation: creating rich interactive web applications using ajax
about 2 weeks ago (on january 25th), i gave a presentation on creating rich interactive web applications using ajax. i just posted the deck at http://www.weblogging.com/decks/ajax.ppt. the deck is mostly intended for the attendees as the slides by themselves do not convey the full intent of the talk.
for those that missed the talk, i will be giving a similar talk at the mix06 conference in march:
lessons from the trenches: engineering great ajax experiences
explore the challenges and lessons learned developing the windows live and gadgets web client frameworks powering windows live, hotmail (kahuna beta), spaces, and more. this technical talk presents design and architectural considerations for building interactive ajax-like sites. see how componentization, network management, accessibility, page composition, and more impact the design and engineering of your web application.
the focus of the talk is to look well beyond ajax to explore challenges in designing and engineering your web application. i believe the paradigm shift is not so much focused on ajax (which is merely a development pattern) but rather around the ability to remix and mashup the web. the remix concept is fundamental to how we are architecting our experiences across windows live. this talk explores the web client technical issues that need to be considered when building a rich (remixable) web-experience.
11:05 pm | add a comment | send a message | permalink | view trackbacks (1)going on the road again...
below is my schedule of upcoming conferences and talks.
mashup camp
febuary 20th-21st
computer history museum in mountain view, ca
to hang out, network, listen, and have fun :-)
o'reilly emerging technology conference
march 6th-9th
san diego, ca
presenting "remixing the web with the windows live™ platform" (march 8th)
mix06
march 20th-22nd
las vegas, nv
presenting "lessons from the trenches: engineering great ajax experiences" (tbd)11:03 pm | add a comment | read comments (2) | send a message | permalink | view trackbacks (0)retiring the spaces cleanup tooljust as we were able to eliminate the edit it tool!, with the recent update to spaces we can now retire the spaces cleanup tool. the spaces cleanup tool made it easy to quickly delete multiple comments and trackbacks from your blog. this feature is now natively supported by spaces by selecting "blog" when you are in author mode on your space.
10:57 pm | add a comment | send a message | permalink | view trackbacks (0)1/21/2006i am presenting at the webguild user group next weekif you are in the valley, feel free to join me wednesday, january 25th, at the webguild user group (http://www.webguild.org). i am giving a talk on building rich interactive web aapplications using ajax. i will share design and engineering challenges that should be considered when building ajax-like sites.
11:15 am | add a comment | read comments (1) | send a message | permalink | view trackbacks (0)12/16/2005other msn/ live developer developments
two more interesting links...
live.com
steve rider saved me a long post by posting the long list of enhancements with the latest windows live update. i suggest checking it out (http://microsoftgadgets.com/forums/1813/showpost.aspx)
also, slightly old news, but spaces released metaweblog api support earlier this month. you can find some details at dare's blog and there is a msdn discussion forum (http://forums.microsoft.com/msdn/showforum.aspx?forumid=198&siteid=1).10:48 am | add a comment | send a message | permalink | view trackbacks (0)view more entries
profile
scott isaacs
send a messageinvite as friend
occupation:microsoft windows live architect
view profile details
other sites
weblogging
if you can't remember my url and need to get back - just remember weblogging. http://weblogging.com!
siteexperts.com
a web developer community i have been hosting for 8 years.
scott on wikipedia
a short bio about my inolvement helping define and create web technologies.
photos
whistler (4)
updated 1/26/2007
hawaii (9)
updated 9/14/2007
© 2007 microsoft
privacy
legal
code of conduct
report abuse
safety
help central
account
feedback
Acceuil
suivante
scott's "siteexperts" place scottberkun.com Home scottberkun.com About Scott HELLO, my name is Scott! Welcome to the Official Website of the City of Scott, Louisiana Scott Speedman, DVD & Vidos sur Fnac.com PapaScott Les Freres Scott scott westerfeld Scott Glenn Scott SPEED fiche joueur de Formule1 news, photos, statistiques ... scott.com Ridley Scott Tom Scott (I) Scott original Vetement sportswear pour la mode Homme, Femme et ... Scott Sports - vybaven pro sport - kolo, lye, snowbord, oblečen Laughing Squid Les Frres Scott - Saison 3 Bienvenue sur le site d'Arthur Scott Consulting Les frres Scott - Le dossier de la srie sur Yahoo! Tl Jacqueline Scott-Lemoine Biographies - Frres Scott Les frres scott UNESCO - Momaday, N. Scott Essai exclusif du cadre Photo SCOTT PFX7 Joan W. SCOTT, La citoyenne paradoxale : les fministes franaises ... The creative and technical vents of Scott Schiller plaintxt.org Minimalism in blogging: an experiment out of control Les Restaurants Country Oncle Scott's Cherbourg, Tourlaville et ... Les Freres Scott : Dossier Les frres Scott Ados.fr SCOTTLAND - A Tribute to Bon Scott ACDC Scott Ross Photos Emily Scott sexy en bikini - Bikini, Emily Scott, Photo ... Scott SWM5 - Radios CD (Lecteur audio portable) - Audio portable ... Computers, blogging, education, martial arts and liberal politics. Cecilia PARODY SCOTT M-AUDIO - Tom Scott scottmccloud.com Scott Walter Broken Toys Actualit - Francis Scott Fitzgerald Ridley Scott - Wikipedia, the free encyclopedia Actualit - Scott Free Home of the Clan Scott Society Acheter LES FRRES SCOTT / SAISON 4 - Comparateur de Prix et Avis ... Scott-O-Rama - Smart, snarky, sarcastic, irreverent, and queer as ... FuzzyBlog eBay.be - scott, Acheter et vendre: scott Sports Vlos, Vlos ... Scott Heiferman`s Daily Fotolog - photos from heif - Fotolog Reporter Monde: Michel Scott Les frres Scott / saison 1 : Comparer les prix avec Clubic Les frres Scott / saison 4 : Comparer les prix avec Clubic SCOTT autoradio cd/dvd - scott drx i800 t (ref : SCOTT-DRXi800T ... Adams, Scott - The Dilbert Blog Scott County Public Schools Les Frres Scott Blankbaby Box-office amricain - Ridley Scott fait remonter les chiffres ... SCOTT Poland :: www.scott.pl :: AnnuSeries.com : Frres Scott (Les) - Fiche, guide des pisodes et ... Scott Janousek