added to Qt.
Let me know your opinion on that.
BR
Hamed Masafi
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Sorry about pursuing an old thread. but I want to know what you think of
this old proposal.
Over the years, Nott has had many improvements:
- Macro mechanisms are removed and what remains is much like writing a
normal classroom.
- Many of the problems that have been resolved and used for our
Hi
I'd seen Qt Remote Objects. But is has not any document. I read wiki
and some information and compiled source and examples. I hope Berrit
add some information.
Overlas (as I understand)
- Share a QObject on server and clients can be access
Differences:
Noron can serv an object per peer
On
Project name: Noron
Project description:
This tool implements remote object sharing (Object Oriented RPC) in Qt.
>From a technical point of view, it can compare with Java RMI or similar
technologies. Noron has an advanced signaling mechanism. A property change
on a peer (server or client) will
> To achieve this I think it's possible to use the property system + a custom
> subclass
> of QObject. If you watnt to expose this objects to QML you will need to
> declare a
> Q_PROPERTY, so It's not convenient.
Nut macro declare a static method to helping query writing as
descripted in github
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.
And what's the reason to have a constructor as Q_INVOKABLE?
Andre right
> What are the advantages of NUT/ORM over existing, proven technologies like
> ODB?
Odb is other than QtSql module, but Nut use Qt so is familiar to Qt developers.
Odb has own compiler for pre-compiler declaratives and is hard to use
for beginners. But Nut use macro hack and no need another tool
Project Name: Nut (currently renamed to ORM)
Description: ORM is a project aimed to help users working with databases.
Developer will write his/her own classes and ORM will generates database
schema and corresponding tables. ORM can generate database migration code
(create, drop and alter table
> That shall complement Soroush Rabiei's work on the C++ side:
Yes, that's right. I'm trying to port Soroush's calendar mechanism to qml
side of Qt.
> If I understand Lars correctly, he prefers an API where the calendar
> object carries methods that act on a date and any further arguments it
>
I'm working on qml support of calendar system,
for porting this mechanism to qml we have two option:
1)
Add a global object to jsengine?
Somthing like that :
var date = new Date;
var cal = new JalaliCalendar;
var out = date.toString(cal, "-MM-dd");
In this case JalaliCalendar is a new
10 matches
Mail list logo
