exploring Qt

I have been experimenting with Qt for MCrux/Ubuntu port since last couple of days.. I found the Qt C++ APIs are much cleaner compared to the existing VC++/windows specific stuffs.

Current JavaScriptCore(JSC) APIs are native C APIs. This means that If we want to have Object Oriented design for all our extend-able modules then we need to have some dirty hack to make them work with static functions to actual object function call. I have taken a lot of pain to achieve this things in windows.

Qt Provides this functionality by default with QObject. We need to derive our class from QObject. Qt achieves this using "SIGNAL"s and "SLOT"s. This makes the design way cleaner. I will cover the fundamentals of them in a separate blog post.

Apart from having all these functionalities, I am not sure I can continue with QtWebKit (at-least for now). QtWebKit-JSC support is in a very primitive stage. They have exposed all the native data types but custom datatype support is in very primitive stage. This means that I can't play with my custom object and throw it back and forth from JavaScript to C++. I also can't set a custom QObject as property of any other QObject and expose them to JavaScript. The lack of these functionalities seems to be blocking me for using QtWebKit.

kicking off MCrux/ubuntu linux !!

hello guys..

Its after a long time that I am writing a new post. As many of you know I am starting off with MCrux ubuntu port. Here is a very first snapshot of MCrux/Ubuntu application. I hope the MCrux Ubuntu port will be fully functional in next few weeks.