SilverLight: Microsoft’s labs back on track?

June 2, 2007

Microsoft is coming with a video media player for the web, called SilverLight. Looks very much like flash but with lots of vitamins for 3D animations mixed with videos.. :

“Microsoft® Silverlight™ is a cross-browser, cross-platform plug-in for delivering the next generation of .NET based media experiences and rich interactive applications for the Web. Silverlight offers a flexible programming model that supports AJAX, VB, C#, Python, and Ruby, and integrates with existing Web applications. Silverlight supports fast, cost-effective delivery of high-quality video to all major browsers running on the Mac OS or Windows.”

Some thoughts about this technology:


  • really cool, amazing user experience (better than flash)
  • runs in all  browsers (like flash)
  • 3D
  • runs server side on IIS and Apache…


  • .NET development… How are they going to convert all the creative guys who already work with Flash? They rarely know much about server side development and C# is unlikely to be their favourite language… But let’s wait and see what Microsoft has put in the box for them…
  • doesn’t seem possible to do much with php with this environment… Microsoft closed box again…

May 15, 2007

interesting post about widgets and mashups.

Looks like the time of the “standardised widget” is slowly coming, with the W3C spec . Let’s hope platforms developers soon agree on  a common format. This will not only have an impact on the widget world but on all client side developments, as it will be a kind of application level HTTP ORB…

Apollo and Flex

March 26, 2007

Just started the evaluation of flex and Apollo…


Flex is an application layer on top of flash. Provides an API for building RIA type of applications and a builder transforming xml descriptors to flash. Includes a network layer enabling very easy communication with server backend (almost any type of server).

Apollo is an application allowing html/js or flex applications to live on the desktop. Manages connexion status to server and provides way to launch even websites such as GMAIL as a desktop application. Seems very easy to use and quite powerful. Cross plateform way to create applications.

First reaction:

Flex is really cool. I already evaluated Flash in 2004 and found at that time that it had probably the best foundation for creating networked applications: excellent APIs and debugger:

  • Object oriented javascript (with classes etc.)
  • excellent network layer supporting various protocols such as SOAP, AMF, XML/Rest, text files, etc.

Flex adds another level by providing a set of controls (radio boxes, text areas, etc.) and widgets (layout widgets, tables etc.).

Only point to check out: drag/drop and integration with OS.

Apollo: like widget engines, a cool way to write cross browser networked applications. And supporting html/js + Flex => cool and easy!


Watch this space! I hope Adobe will win a market share in the RIA space. I’ll start evaluating it soon for enterprise types of applications because it seems to be able to bring in the browser web 2.0 type of applications that are stronger and faster than DHTML ones (which I use now)….

Yahoo RSS Pipes, etc.

February 20, 2007

Just heard about Yahoo pipes. Thank you Jean-Christophe.

Summary: Yahoo pipes is cool stuff for RSS addicts. Some related thoughts about RSS as a multi purpose protocol…

Yahoo pipes is a very interesting system for managing RSS feeds including:

  • content filtering
  • adding a user interface (a search form dedicated to a feed)
  • aggregating several feed together.

The system is a little bit complex to setup but looks very powerful. A very useful brick in the RSS layer… When Web 2.0 empowers Web 3.0 🙂

RSS has the potential to be used widely in the information chain. We currently are using only a fraction of this potential, mainly for news… I mean, we have with RSS an information protocol that is categorised, has meta data we can read, search and organise in various ways.

The protocol could be used to replace site maps (Google site maps or other), navigation panels in websites, monitoring events in enterprises (hardware, system, organisation, teams). Probably some other application too…

So what is missing in the layer for achieving these results (applications):

1) better categorisation of RSS items (server side): currently under used because of the lack of intelligent RSS clients able to render them..

2) start using RSS “channels” (most RSS feeds have only one channel…): channels are a great way to offer different views on the same information space, or related ones..

3) having RSS readers that make better use of RSS item categories: I haven’t found yet a RSS reader that can display more than a single view on a RSS item list, or that can display them in a tree view (assuming category namespaces are tree based of course).

4) implementing HTTP security (basic, digest, etc.) in all RSS readers: security enabled RSS readers allow RSS Applications in intranet or extranet spaces.
For example: Mr MD can follow his company events (commercial/project/hardware events) whilst he is on a business trip somewhere..
Mr Network Mgr can check his server health when offsite.
Mr Everybody could safely check his emails through a RSS feed (some are already doing it…).

5) having mobile phone/PDA RSS readers: RSS feeds are smaller in size than full web pages and easier to write than WAP pages. Would be useful to follow RSS events on phones/ Blackberry etc.

example of RSS feed with categories (only one level shown in rss reader):

About Ajax toolkits…

December 13, 2006

lots of toolkits are available today. They are cool but what we need is not necessarly cool effects (although some could help) but a framework that allows us to create our own widgets. So the question is not which toolkit to use but more which kind of design patterns or standard in writing a widget.  There are a few basic issues that are solved in these toolkits (like how to load libraries, how to link a html element and a JS class, what format to use for a class etc.) and the community should focus first on these points instead of trying to offer toolkits thaht have been writing for a specific context (i can’t see any that I can apply in my applications). We need design patterns and widget coding guidelines, not toolkits.. In the meantime, the only library I find useful – as a standard – is prototype.js … 🙂

IE7 and Firefox 2 : headaches for web developers

December 3, 2006

IE7 and Firefox 2 are now released and begin to spread in the world thanks to auto-updates and the cool factor driving technology.. What does this bring us? Well.. happiness and sleepless nights..

Happiness: IE7 is coming with a bunch of features and bug fixes that allow us to think of a bright future where browsers co-exist in peace without making web developers struggle too much for delivering their cool web pages..

Sleepless nights: as described in previous post about CSS design patterns, a lot of websites rely on web browsers bugs for writing browser dependent rules in CSS. As there are (were?) still differences in browser rendering, CSS cant yet be written in independent manner. But with IE7 supporting fixing bugs and supporting CSS 2, all these rules become obsolete and rules written for firefox are now going to be applied to IE7. In some case it will work but we can expect a whole lot of websites designs that will break in the following weeks and months..

The second issue comes from the support of SSL in IE7 and FF2: they only support SSL version 2, which means that servers implementing SSL V1 wont work.. It sure going to involve some time fixing this issue..

But well, crises are meant to make us humain being evolve for the better, arent  they 🙂 Good luck for everyone involved in web development and enjoy the new tools…

PS. for a solution on how to safely manage browser dependent rules in CSS, check previous post…

CSS design patterns for web 2.0

November 26, 2006


Summary: web 2.0 has seen dramatic changes in the way pages are developed. CSS standards are evolving to cope with the demand but in todays browsers web 2.0 requirements have outgrown CSS features and very few strategies are either defined or applied by CSS developers in the web industry. This makes web page creation a kind of black magic that is both expensive and risky as magic tricks might not work in next versions of browsers. This article describes the situation and provides 2 design patterns that make a significant change in developing web pages with direct returns on

  • css code reuse
  • quality,
  • safety of investments
  • ease of development and support of browsers.



As the web technology progresses on the client side with Web 2.0 being spread in the industry, we rely more often on both javascript and CSS for building websites and web applications. Whilst the javascript side is fairly well covered on the design side, with the knowledge derived from JS libraries (prototype.js, dojo, Y! UI, G! UI, etc.), we still don’t see enough efforts to rationalise CSS development (yes I know it’s a bold statement, but well just a view from my little corner, and anyway, I like bold statements :-).

We know that browsers are getting closer to each others in terms of CSS support. Thanks to Mozilla, we now have a decent cross platform browser that we can spot on our traffic analysis graphs without a magnifier. That means we now need to support more than one browser and it is a lot easier than it was with the evil Netscape 4 or Mac IE. But there are still some issues CSS developers (yet another title to put on already heavy CV in the industry) have to face nowadays…

First issue: font sizes and accessibility

By law, respect or any other reason, fonts in web pages that are written these days should scale well so that everybody can read them. To have fonts that scale well in all browsers, we should use units such as “em”, “%”, or “small/medium/large”, instead of “px” (pixels). However it is very difficult to use these units because:

  • “em” or “%” units are dependent on their context (what is the current font size), so any change in html or css can (and does) have side effects on other parts of the page. I know  it is possible to write pages like that but it is not easy and it is risky.
  • “small/medium/large” are the easiest and natural way of writing fonts that will scale well in any browser/device. However Mozilla, for probably a very good reason (what is it ?), displays fonts that are smaller than on any other browser. This breaks the design..

Conclusion: we can’t write accessible web pages with only a clean cross-browser CSS sheet.

Second issue: managing z-index

A lot of web applications now use drop-down menus or other widgets that display on top of others. In CSS, z-index property defines which layer should go on top of the other. Well, not always as IE has a bug for elements that are relatively positioned. It then breaks the rules and we have to apply special tricks well described in .

“height” matter

Not all browser support height properties the same way. IE6 allows to use the CSS “height” property for most html tags, whist in Firefox, the “height” is only supported (as defined in CSS standard) for block elements, and in any case, most of the time it is “min-height” that is equivalent to IE’s height .

Conclusion : getting the right height in CSS involves some kind of trickery to make every browser happy, and to play with “height”, “min-height”, line-height”, “padding” etc. until we get the right result in all browsers (whatever “all” means for you :-).

Lack of CSS reusability

HTML and CSS is often used beyond their limits and new de facto standards are created in this outland area. Examples are:

  • transforming ul/li lists into menus
  • creating side areas with floating divs (replacing tables).

Achieving these effects is not very easy because they use html/css features that were not designed for these purpose. The “float” property was mainly used to have floating text around images, not for replacing tables or create css menus. Although this works fine, CSS development is then quite difficult to write and then is more expensive. Also, because design pattern for reusability are not well known for CSS (apart from reading tutorials and rewriting things from scratch), we haven’t much CSS libraries on the market. Web development tools can help in some cases but not enough for making things any better.

Conclusion: CSS development is tedious and expensive because of lack of reusability and skill levels required.

Lack of common support for javascript behaviors in CSS

One design pattern that provides a direct impact on programming quality, time/money spent on projects of medium size is the “Model-View-Controller” or “MVC”. The basic idea is to separate things so that development can be done in parallel by different people (ex. graphic designer/html developer/javascript specialist/PHP developer/etc.). There are many other quality factors brought by this model (reusability, testing, maintenance, etc.).

In web2.0 applications, we can see components being implemented in web pages (ex. calendars, menus, other widgets, etc.). Modular Javascript libraries are available for helping in the development of such components, however it is still difficult to truly separate html from javascript the way html and css can be separated. The reason for that is we often need to attach a “behaviour” (such as opening a new window, adding a visual effect, etc.) to a piece of html and/or add html fragments in some specific parts of pages. To do so, we need to add <script> tags in the code. This solution is not very effective because html/css developers can’t write the page without either knowing javascript or work with javascript developers. This costs time and money and makes pages difficult to modify.

One excellent way to attach javascript behaviour to html is to put the attachment in a css rule. ex. { behavior: } . This example use IE syntax for attaching a javascript component (HTC) to html. Mozilla has another syntax for behaviours. The main issue is that we can’t use them because they are browser specific (and also some browsers have no support at all for behaviours).

Several workarounds have been added to js libraries but they are cumbersome, fairly slow and/or break the (x)html standard:

  • parsing the DOM and add behaviours to html elements with a specific css selector: cf. “behaviour.js” or “prototype.js javascript libraries.
  • parsing the DOM and add behaviours to html elements with a specific attribute. ex. dojo library with its “dojoType” attribute.
  • add XML tags in the html code and transform by js into components (ex. dojo tags <dojo:widget />)

These solutions are good enough and the best ones we have available but they can make page loading a bit slow. If a standard for web components was defined and supported in browsers, we would probably see a lot more reusable components on the market…

No Support in CSS for selecting rules by user agent

Because of several cross browser differences, CSS sheets have to be written in browser dependent manner.  How can this be achieved? As nothing in CSS currently helps in writing CSS rules dependent on the browser application (apart from “screen”, “print”, “tv” devices selectors for <link> tag), developers are using black magic based on application bugs or CSS level support:

  • some funny sequences of characters make a rule or part of the rule work in some browsers and not in others (ex. \*//*/ for IE/Mac)
  • conditional compilation in html is supported in IE (in html only)
  • IE6 doesn’t support the “>” parent syntax (as in ul > li), so rules written with this syntax wont be used by IE.

The fact we have to rely on bugs in internet browsers makes the development of pages both difficult and risky. Difficult because these tricks are not easy to achieve and are poorly documented. Risky because bugs could be fixed (we have seen these things happening, even in IE). So in next versions of IE or Firefox we could see a lot broken designs in websites… This could lead to some decent amount of money spent in fixing these websites. It actually reminds me of the huge work involved in fixing applications in year 1999 for supporting Y2K. Or business applications when the euro currency was launched in Europe…

Proposed solutions and design patterns

Solution 1: adapting standards and browsers to the reality of web 2.0 development.

The ideal situation would be to have CSS standard following the development reality by:

  • adding CSS selectors based on the user agent and/or browser application. It could be for example:
    gecko: body {font-size:small;} ie.5+ {font-size:x-small;}
  • or have CSS selectors based on supported features (css2: ul>li {})
  • create standard JS components via css behaviors.


Design Pattern 1: add support for browser dependent rules (without relying on browser bugs)

One way to distinguish rules supported by a specific browser is to add a class selector of the form: li { position:relative;z-index:100; }, body.ie_mac {position:static }.

Classes derived from the user agent can be added to the body tag at load time.

example (dependent on prototype.js):

// add support for user agent detection in document
Object.extend(document, {
getUserAgentClass:function() {
if (window.opera)
return “opera”

if (/MSIE/.test(navigator.userAgent)) {
if (/Mac/.test(navigator.platform))
return “ie ie_mac mac”
return “ie ie_win win”
if (/Gecko/.test(navigator.userAgent)) {
return “mozilla”
if (/Safari/.test(navigator.userAgent)) {
return “safari mac”
return “”

setBrowserClasses: function() {
// add user agent to body class

// add UA classes to body
Event.observe(window, ‘load’,document.setBrowserClasses);

NB. by applying this method, we make sure that CSS rules will be safely applied to a specific browsers and that these pages won’t break when browser bugs are fixed or when a new version is launched… This also makes CSS development easier and faster, in the short and long terms…

Design Pattern 2: use an modular/OO approach to CSS

CSS libraries can be implemented by using two interesting features in CSS:

  1. the ability to add several classes to an html tag. ex. <ul class=”horiz_list menu”><li>etc.. </ul>
  2. filtering CSS rules by a selector: ex. .horiz_list ul li {float: left;}. This feature limits the impact of defined rules to only a part of the DOM, thus avoiding side effects to other html parts in the page.

Combining these 2 features allow HTML/CSS developers to create CSS libraries that can be directly reused with less risks of having side effects. In the example above, the horiz_list class is applied to a <ul><li> to make it a flat list. The actual design for the menu (colors, fonts etc.) can then be defined in “menu” class, thus making it very easy to develop horizontal menus…

This example can be applied also to javascript components: separating the design of components (colors etc.) from their function (horizontal menu). We can then share CSS libraries across projects and people and make the creation of web page less tedious and expensive…


Developing CSS based pages is still difficult, expensive and risky because no actual design patterns or development standards are widely available or used by web developers. This could be easily improved by sharing the knowledge of CSS gurus (such as the guys at Zen garden and many others) into reusable CSS libraries or design patterns. This would help the web industry in getting better development quality at lower costs. The 2 design patterns described above could help achieving this objective and I hope that others will be available and applied in a near future…

Windows Live toolbar

October 24, 2006

Thanks JC for the link to the Windows Live toolbar. This is the first post I try with this software. It is also the opportunity to have a quick look on this toolbar and see how it fits  in  the “gadgetisation” of the web through our desktops..

The software is made of a toolbar with nice features such as a blog writer, link to RSS feeds, tabbed browsing, a synchronisation tool with server for favourite links (overlap with delicious?), popup blocker (yet another one?), desktop search (overlap with Google desktop) and also the ability to create new menus.

This is similar to other gadget engines in the sense as it provides an interface to web resources. It is still in beta so we’ll have to wait until the end of the program to see what can actually be done with the system (the button gallery is not yet very large)…

Adding new applications/buttons seems to be done as a standard MSI download.. This probably means applications and smart buttons in the toolbar require .NET development. Huh! Compared to other systems based on html/js/css, this could be quite complex to develop a simple menu and this is likely to deter a lot of people from adding their own gadget/menu.. However this toolbar seems a bit more useful than tabs we find in the messenger (which are pure marketing tools and related to a young audience). It then looks like the toolbar could be more targeting a professional audience and/or bloggers.

Microsoft Gadgets

October 19, 2006

Please ignore the last part of the previous post: Microsoft DOES provide a widget engine and is actually providing the right model for it… Just found their developer blog:

But as many features as we are adding to, the site is still very much a Gadget platform for you developers out there to build on. We rely on you to build rich and interesting Live Gadgets that we haven’t thought of, and to build a strong ecosystem around this platform. is still in Beta today, but it promises to be one of the most popular Internet destinations when we launch later this year. You can leverage on the high traffic site to extend services beyond your web site by building Gadgets that live on”

and their todo list seems promising:

Some of the things that we know we need to work on are:

  1. Unified Gadget model – we want to enable developers to write a Gadget once and have it run on both Vista Sidebar and on the web, maybe even in other environments.
  2. Allow 3rd party gadgets to change header and footer – today, all 3rd party Gadgets are hosted within and iframe and do not have access to the title, title icon and footer.
  3. Make calling web services easier – this is self-explanatory.
  4. Better Settings model – there is no standard way to do settings today for 3rd party Gadgets. We would like to move to a more declarative model.
  5. Better Localization model – we provide API for you to find out the query the current locale but we don’t provide much other support otherwise. This is not a big problem for most Gadgets, but it would be nice for more advanced Gadgets.

Looks like we’ll see Vista with a widget system intergrated in side bars… Anyone having tested Vista yet?

But will that support other platforms? Y! and G! widget engines work on PC and Macs…

Widget engine: a bridge between web and desktop applications

October 18, 2006

(sometimes I hate WordPress… Second time it loses all the post content and I have to write again… A summary will do I hope…)

Widget engines again… Google, Yahoo and other are creating an interest by adding small applications that link users’ desktops to online applications or websites.

The interest as described in previous post could be very strong once a business application of these system is in place.

If that happens how could other actors react? and who are these potential actors?

Given the fact widgets create a new link from users to (potentially) branded content, it is likely the technology will create an interest from others such as Microsoft…

And M! has already in place most of the required technology within M! Live Messenger: an application which supports authentication, multi channels and a notification engine. And this piece of software already runs on a lot of computers of the planet!!

So the only missing bit is the ability for M! engineers to integrate a widget engine based on html+css+js+ajax and to integrate it in Messenger. Given the development resources they have it doesn’t seem out of reach..

So maybe we could see M! playing as well with this technology in a near future, we never know.. Probably all will depend on the success of G! as M! seems more like a follower on the web these days (personal view:-)…

I’d be interested in your comments on the subject…