Hilarious internet musical… well worth the watch!
Pop quiz: Does it remind you of some people you know? ;-)
[via CollegeHumor]
Hilarious internet musical… well worth the watch!
Pop quiz: Does it remind you of some people you know? ;-)
[via CollegeHumor]
A discussion recently started by Harry Hübner and commented by Christopher Blum in OpenSocial Interest Group I’m moderating over at XING, led me to a conclusion:
Supporting various applications (either web 2.0 or headless server functionality) inside an OpenSocial container can create more traffic (and revenue if they’re commercial) for application’s developers.
Here’s my attempt to stand on Christopher’s shoulders and go into more detail. His proposition of “OpenSocial interoperability” by bringing various popular [web 2.0, headless] applications into OpenSocial containers is one of the ways to get more traction and traffic by using OpenSocial, which in turn could improve perceived interoperability.
This kind of interoperability can be best achieved using OpenSocial REST API which enables application’s home server to access selected OpenSocial container functionality. In this case, best-of-breed and widely adopted technologies are used: HTTP protocol for invoking container’s entry points and JSON for encoding data (read or written).
BTW, headless application can be any functionality on some server that runs or can run without a UI. For some examples of headless applications consider a Jabber or IRC server. You can let your imagination run free once you realize that this headless application can also be (almost) any application running in Amazon EC3, Google App Engine and other clouds. I’m wrote “almost” in parenthesis to include only those apps that understand REST, i.e. speak HTTP and understand JSON.
In more detail and related to OpenSocial, the scenario I’m supporting is the following:Note that either part of this scenario or both 1. and 2. can be used to improve application’s interoperability.
In using part 1 of this interoperability scenario, the initiative for improving social-awareness of a popular application by using REST API to connect to OpenSocial container is in the hands of the original application’s developers. In the case of open-source application projects, there are less impediments and objective reasons not to connect open-source applications to OpenSocial container and, through it, all the users using the app. This way, data is not only more socially-aware but also more pervasive when part 2 is used.
When using part 2, application data is embedded into a “personalized web panel” running inside OpenSocial container thanks to Gadget XML, Gadget API and different features-specific APIs that are optionally supported by the respective OpenSocial container. The most interesting feature (i.e. OpenSocial JavaScript API namespace) is RPC feature (which stands for remote procedure call) that an OpenSocial container may implement (since it’s an optional API) to provide gadget-to-container, container-to-gadget, and gadget-to-gadget communication.
The final result of this interoperability scenario is better data availability and more convenience to users which can lead to an increased [web 2.0, headless] application’s usage.
The most prominent example of increased usage thanks to implementing OpenSocial (albeit implementing the entire OpenSocial container is more work than previous scenario) is Plaxo Pulse which got an order of magnitude
Great stuff that your Google Chrome browser can do… most experiements won’t look as good or as fat in other web browsers.
Have in mind that everything is implemented in HTML, JavaScript and CSS. :-)
Verdict: this is one great viral marketing campaign!
Thanks to Raša for letting me know about this and bashing Tetris within a web browser as a bleak achievement. ;-)
Watch this comic explaining in detail features Google Chrome web browser.
On a sidenote, sometimes project managers are not the best people to present their product (at least not to the general public). That guy might be considered cool by geek standards (for what he does) but certainly is not to your neighbour Joe or Jane who’d like to surf the web on their mobiles as well. :-)
What’s particularly interesting is the concept of Opera Widgets among which there are some that will surely keep any Facebook addict relaxed and happy.
In my view, mobile widgets are a very viable solution for small-screened mobile devices. What’s a mobile widget? Well, isn’t that a regular application that can be downloaded from a widget library that can be browsed from your desktop web browser as well.
[via DailyMotion]
The brilliant people at Information Architects selected nearly 300 of the most influential and successful websites and layered them over the greater Tokyo-area train map. Looks great and it’s a great reference too.
All of you Web2.0 addicts may use this as your del.icio.us 2.0. ;-)
You can download a PDF (A3 format) or check out the clickable online version. Within a week, you will be able to obtain a huge poster (A0 format!) version of it. You can preview its prominent features in detail too.
[via informationarchitects.jp]
Here’s something for web developers out there.
If you wonder sometime why Flash is being used so much, you’re going to like this.
I guess you may have heard for GWT (Google Web Toolkit) allowing you to write AJAX application in Java. GWT allows web developers can save their valuable/expensive time by not messing with infinite intricacies of writing cross-browser DHTML pages. Instead, they can use Java programming language in design time, use their favorite IDE in debug time while seeing the visual aspect effects rendered in an applet. When all coding and debugging work is done you can have the Java application compiled it into cross-browser JavaScript and CSS (using its own Java-to-JavaScript compiler). Intriguied? Go try it out!
The main point of this article is the WVGL (Web Vector Graphics Library) that builds on top of GWT to produce pretty advanced results - 2D graphics in web browser. WVGL library offers the graphics primitives and support for the following features:
Click here to check out how it draws a Bezier curve in web browser esentially using Java programming language!
Cool, isn’t it?
Kudos to Nathan Matthews, the author of WVGL! Thanks to Miloš Malić for the link.