Recommend this
on Google+

Recommend this
on Google+

Sunday, November 6, 2011

Nokia India - Nokia E7-00 : Smartphone with touch screen & QWERTY from Nokia

Nokia India - Nokia E7-00 : Smartphone with touch screen & QWERTY from Nokia

Friday, October 14, 2011

Web 2.0




My Google API Application




Loading...

Sunday, July 24, 2011

Automate browser testing…

I’m currently working on developing a very tiny framework to implmenet test-automation, using standard web technologies…..

Keep watching this space for updates, and source-code-host details.!

The mystery of the implementation releaved….

Basics of developing browser-based-IDE to develop web-applications:


1. Browser should handle IDE content as HTML, and the code being develped using it as a NON-HTML format. Otherwise, even that code would be considered to be part of the rendered page. cURL is a tool that is used by developers to test Google Data services, as it supports the HTTP functionality required to interact with the APIs at a low level.


2. Prepare a sandbox as part of IDE, that enables to debug code-being-writtetn, instead of  handling its parsing to Chrome-browser. Hence, the sandbox does parsing, and rendering UI of that without browser's default behaviour.


3. Cross-origin/unmatching domain requests handling.

As part of enhancing security of web-apps, browser does not allow any document to interact with other document served from a different domain. Ex: HDFC-Netbanking webpage, cannot be given access, to a webpage from twitter.com. Hence, atomicity of data access is ensured.


4. Asynchronous execution of several activities, while user does not feel slow performance while writing code. For example, a code written is being built, while user develops another document in the IDE. Hence, two activities run in parallel, and reduce hanging.


5. Authorization
     User should be able to develop a live-web-page for another website, while the IDE is running in a seperate domain. This requires a trust to be established for overcoming issues described in 3rd point.


6. Authentication
     Along with 5th need, a user may also try develop an application within a secure-application isolated from other apps hosted on the same domain. Example, Google search does not require you to login, while GMail mandates to login before granting access to its resources.


7. Token-based-session-handling….

Friends, so lets start gathering feedback from the community, meanwhile the project-code would be hosted at https://github.com/kcomkar/ inside “Pariksha” repository upon receiving enhancement of storage-quota. So this year, would gift you an opensource browser-based-IDE for new-year.

Happy new year 2012 in advance…!!!

Saturday, March 5, 2011

Rate your browser speed

Saturday, February 5, 2011

HP webOS

Advance in electronics ensured computers to be on diet and more fit. The result is mobile phones. Android, Symbian, Tablet PC, iOS, Windows Phone, Bada OS, BlackBerry, Meego, Maemo, …. Oh!! My god! Jargon ... Do these words leave you in mid of an ocean with no clue to reach shore? All these are Operating-Systems developed by various mobile-equipment manufacturers for their phones. They can easily be compared to Windows, Linux, Mac-OS that run on top of our PCs. But, the difference is you can install an OS of your choice on your PC. But, not on your mobile phones :(.

Afterall the bottom-line of mobiles, is to keep computers more portable, and make you feel omnipresent. But, what’s ensuring compatibility between these vendors? It’s the internet! These days it’s rare to see someone acquainted with using keyboard & mouse, not being on social networking. Social networking requires access to Internet. Accessing it requires a common set of protocols-&-formats to be understood by your mobile-phone. Those protocols-&-formats are called Web-Standards, that are governed by W3C.

It’s the Internet that is binding all these vendors to ensure compatibility. Computing capabilities made surfing cross the threshold of Browsers, and seamlessly integrate with OS.. Infact, a separate application called “Browser” is really not the only way to surf Internet. It’s being felt that Internet is synonymous with Mobiles.

“Web Runtime” is a framework coupled with the OS, enabling access to Internet as a Service. HP’s webOS, is one such implementation on it’s palm devices.

A webOS application is similar to a web application based on standard HTML, CSS, and JavaScript, but the application lifecycle is different. Applications are run within the UI System Manager, an application runtime built on standard browser technology, to render the display, assist with events, and handle JavaScript.

The webOS APIs are delivered as a JavaScript framework, called Mojo, which supports common application-level functions, UI widgets, access to built-in applications and their data, and native services. To build full-featured webOS applications, many developers will also leverage HTML5 features such as video/audio tagging and database functions. Although not formally part of the framework, the Prototype JavaScript framework is bundled with Mojo to assist with registering for events and DOM handling among many other great features.

The framework provides a specific structure for applications to follow based on the Model-View-Controller (MVC) architectural pattern. This allows for better separation of business logic, data, and presentation. Following the conventions reduces complexity; each component of an application has a defined format and location that the framework knows how to handle by default.

For now, you should know that the framework includes:
• Application structure, such as controllers, views, models, events, storage, notifications, logging and asserts;
• UI widgets, including simple single-function widgets, complex multi-function widgets and integrated media viewers;
• Services, including access to application data and cross-app launching, storage services, location services, cloud services, and accelerometer data;