Recently Flex 4.0 SDK is released. In this release Fx improve developer designer workflow. Not just import flash, Photoshop or AI files into flex builder but true Developer Designer workflow. It means thermo integration, new skin file (FXG) type included , and new name space “2009” will be in place to support new graphic rendering. I guess now every Fx component will have separate skin file which will describe look and feel and function behavior of the component.
When you think of list component in Fx 3.0 or older, what come to your mind?
Ammmm ….. list items can be display in a box with right hand scrollbar, Item can be rendering with itemrenderer and scrollbar can be skinup with .png or flash. Now take look this video and change your mind for list component. In Fx 4.0, every component will be reassemble easily with very less efforts. So, therefor it’s truly amazing Developer Designer workflow in FX 4.0.
Saturday, October 4, 2008
Wednesday, September 10, 2008
Monday, September 8, 2008
Google Chrome Overtakes Internet Explorer
Google has designed an almost completely new Web browser. In fact, other than the core rendering engine -- which is based on the open-source WebKit standard of Safari fame -- everything in google chrome constitutes a rethinking of how you engineer a browser application. For example, with the current versions of Mozilla Firefox and Internet Explorer, individual Web page tabs are hosted in a single process -- a model that is efficient (in terms of memory and resource consumption) but also prone to catastrophic failures: A single crashed tab can easily take down the entire browser application.
Chrome seeks to eliminate this problem by isolating each tab within its own application process and then leveraging the built in memory protection capabilities of modern, preemptively multitasking operating systems to keep code and data in a failing tab from stomping on other processes. So now, when that buggy Flash applet on your favorite humor site goes belly up, it won't necessarily take down the entire browser -- the processes running in other tabs will keep chugging along.
So i love Google Chrome and See this is the best browser in current scenario.
Chrome seeks to eliminate this problem by isolating each tab within its own application process and then leveraging the built in memory protection capabilities of modern, preemptively multitasking operating systems to keep code and data in a failing tab from stomping on other processes. So now, when that buggy Flash applet on your favorite humor site goes belly up, it won't necessarily take down the entire browser -- the processes running in other tabs will keep chugging along.
So i love Google Chrome and See this is the best browser in current scenario.
Friday, August 29, 2008
Subscribe to:
Posts (Atom)