- This morning one of our senior computer science students did their senior seminar on Silverlight, a new web technology developed by Microsoft to enable .NET client-side programming on the Web. Like the Flash player, Silverlight first requires the engine to be downloaded and installed. I got it to work just fine with Firefox (although I hate restarting my browser, especially when I have 20 different pages open). This technology looks promising, especially if Microsoft really pushes hard for adoption. I wonder why they don't include it along with Flash in Vista? Maybe they're afraid of another bundling lawsuit.
- One of the examples used in the Silverlight presentation was Microsoft's new search engine, Tafiti. Tafiti is powered by Live Search, but it uses Silverlight for it's interface. Tafiti is a perfect example of how a pretty interface does not necessarily make your application any more usable (see the tree of search results below for "Harding University").
P.S. I noticed today (3 days after this post) that the Tafiti tree view screen was eating 25% of my CPU cycles! I opened another tree view window to view different results, and 50% of my CPU cycles were being used! So not only is the screen useless, it will also cause your computer to waste time and energy. Booo. - Google has recently improved their date range functionality on the advanced search. These improvements allow you to do things like, find the pages Google crawled from my blog within the past week.
- And Google is offering $30 million to the first team able to send a robotic rover to the moon that is capable of roaming the surface and sending readings back to Earth. Of course accomplishing such a feat is going to cost much more than $30 million, but it's a nice gesture.
- And just for fun: Sidesplitting tech comics.
Showing posts with label web applications. Show all posts
Showing posts with label web applications. Show all posts
Saturday, September 15, 2007
Fav5
My pick of the week's top 5 items of interest:
Labels:
fav5,
google,
microsoft,
search engines,
web applications
Monday, April 23, 2007
Proposal: HTML 5
Mozilla, Opera, and Apple are pushing the W3C to recognize their proposal for HTML 5, the first large upgrade to HTML since 1999. You can read more about it here.
The HTML 5 specification includes some really cool stuff: Web Apps 1.0 and Web Forms 2.0. Web Applications 1.0 adds new elements to HTML and DOM to provide a richer environment in which to build on-line applications. For example, Web Apps 1.0 will allow you to present a context menu when the user right-clicks on an element, and you can draw a line connecting two points on the browser screen. Web Forms 2.0 (not to be confused with XForms) adds some powerful features to make controlling and processing user input from web forms a little easier. For example, you can more easily specify what types of characters are acceptable in a textbox or indicate that the form values are to be submitted as an XML document.
HTML 5 is designed to be backwards compatible, so the billions of pages which have been written with previous versions of HTML will still display correctly in newer browsers supporting HTML 5. This is a very important and positive development from a preservation standpoint, and it will likely help HTML 5 be adopted more readily by the development community.
Of course the most important player to get onboard is Microsoft who still controls around 75% of the browser market. Microsoft is busy right now promoting XAML, so it may not be in there best interest to devote many resources to HTML 5.
The HTML 5 specification includes some really cool stuff: Web Apps 1.0 and Web Forms 2.0. Web Applications 1.0 adds new elements to HTML and DOM to provide a richer environment in which to build on-line applications. For example, Web Apps 1.0 will allow you to present a context menu when the user right-clicks on an element, and you can draw a line connecting two points on the browser screen. Web Forms 2.0 (not to be confused with XForms) adds some powerful features to make controlling and processing user input from web forms a little easier. For example, you can more easily specify what types of characters are acceptable in a textbox or indicate that the form values are to be submitted as an XML document.
HTML 5 is designed to be backwards compatible, so the billions of pages which have been written with previous versions of HTML will still display correctly in newer browsers supporting HTML 5. This is a very important and positive development from a preservation standpoint, and it will likely help HTML 5 be adopted more readily by the development community.
Of course the most important player to get onboard is Microsoft who still controls around 75% of the browser market. Microsoft is busy right now promoting XAML, so it may not be in there best interest to devote many resources to HTML 5.
Subscribe to:
Posts (Atom)