Comments on: Promoting Qt Kinetic and Animated Layouts

By: zchydem

zchydem — Wed, 23 Dec 2009 18:59:15 +0000

ciloman@ thanks for your comments. I agree, that ui and code (logic) should be separated. Personally I think that for example in QML I’d rather define the UI in QML, but the code is done in application code in C++. This is doable even right now. I can set QML component /object’s properties from C++ code, which is really nice feature. At the moment, I guess, Trolls would be happy to receive any kind of feedback of QML because it’s still under development.

What comes to your proposal of developing a new language “QCode”, it sounds an interesting idea. Maybe you should make a proposal directly to the Trolls or to the #qt-kinetic channel in freenode, but sadly I’m not one of them. I’m just a guy, who’s interested in Qt. Maybe some day if they decide to open an office to Finland I could try to apply there, but probably I’d need to have more competence even to get to the interview.

Oh yes.. Merry Christmas to you:)

By: ciloman

ciloman — Tue, 22 Dec 2009 22:39:04 +0000

I would also like to add, that I hope it also is in your future to target the web as well as the desktop with QML.

Adding to the previous brain storm.

Include QML.SomeFramework;
Alias SF = QTM.SomeFrameWork;
Alias SC = QTM.Framwork.SomeClass;

NameSpace MyFramework
{

Class MyClass Inherits SomeClass Use ISomeinterface
{}

}

By: ciloman

ciloman — Tue, 22 Dec 2009 22:14:28 +0000

This is a great addition to QT Development tools. But I must say, it would be best if separation of code and ui is employed. Rather than UI code and Javascript embedded. And to be honest, I hope QT moves forward and develops a true Object oriented language (not Java though) of its own. Along the lines of C#/Java/VB.Net, but more intuitive.

// use frameworks
Include QML.SomeClass;

//declare class

Class MyClass Inherits SomeClass Use ISomeinterface
{

// declare variables and constants etc..

Int myAttributes;

/* Constructor and Destructors
Public MyClass()
{

// some code here

}

Private ~MyClass()
{
//some code here
}

// Properties

Public Int MyAttribue
{
get{
return this.myAttribute;
}
set{
this.myAttribute = value;
}

}

// Methods

Public MyMethod ( Int args, …) Returns Int
{
// Some code here

}

This reads like English. It is intuitive, and simple. It Use the best approach of all languages. You don’t need to be a programmer to understand this. I hope I sparked a future thoughts for you guys. Hopefully a native compiled language. I call it QCode LOL.

I understand the value of c++ for maintaining legacy call and fan boys happy. But if you want to make a mark for the future. You need to approach the future, by looking into the future. Lessons learned in the past, move forward and improve on what was learned. You can cater to both C++ and the Future.

You have the most Multi-platform Gui framework. With the most Multi-platform language. But the language is a legacy.
It is not true Object Oriented, and complex to even look at. It is non-intuitive. It is a Hack of the past.

Seriously though, I hope you like my brainstorm and build on it.