On Saturday, February 04, 2017 07:05:41 AM Hamed Masafi wrote: > Why not using Q_PROPERTY instead of NUT_DECLARE_FIELD? > > A property im table is more thsn a just Qt property, that macro create > property and static field for query writing and class info about property > to add to database.
To achieve this I think it's possible to use the property system + a custom subclass of QObject. If you want to expose this objects to QML you will need to declare a Q_PROPERTY, so It's not convenient. > > And what's the reason to have a constructor as Q_INVOKABLE? > > Andre right about that, If you register the class as "MetaType" you will be able to create instances of the class using QMetaType::create(). > > Actually, there are more ORM solutions for Qt, e.g. QxOrm and QDjango > > Yes, there are, either other languages/frameworks like .net and java has. > But I really live Qt so I think it can be a good idea if prepare free one > of them to integrate into Qt. > > I think Nut is easy to use and feature rich (in alpha state for now) that > support much database manager. > > Some of them are complicated and some others are so simple to real using. > We can provide a full feature module with LGPL to community use. > > Excuses for my bad English, but I want give that tool to Qt community that > very helped me. I want suggest two of my libraries to playground area. > > After all of this, can I know your idea about an orm in playground area? -- Best regards, Jesus _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
