Skip to main content

Chrome Side tabs or Firefox Panorama?


Firefox Panorama has a unique way of organizing tabs into groups so that you can work with a loot of tabs (really lot of them). While the Side Tabs experiment is totally disjunct concept, The effective use of screen real estate is key measure in both. With just screen real estate, its still Panorama that wins the battle.

Side Tabs seems turned out to be a sore experiment. For one thing, it may be designed only for netbooks. There are other considerations for developers perspective. Many a time, the height is considered variable. The width, however is counted to be under standard 800, 1024, 1600 etc, those of the video resolutions. Many fixed layouts are drafted to work on these width numbers. Free flows however do not have this issue. Now, having Side tabs in picture, it creates two sets of fixed layouts to work with.


Firefox Panorama not only tackles width issue in question, also provides a organising benefit. So Which one is it? Most probably Chrome will eventually mimic Panorama.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>