[Development] Switch Qt Remote Objects to a Tech Preview for Qt 5.9
Marc Mutz
marc.mutz at kdab.com
Wed Jan 11 10:43:43 CET 2017
Hi Brett,
On Wednesday 11 January 2017 01:42:38 Stottlemyer, Brett (B.S.) wrote:
> With this picture in mind, the key to getting it to work is to hook into
> qt_metacall and pass the invocations between processes. This takes custom
> code, so QtRO has repc (REPlica Compiler) for this. It reads a .rep file,
> a simple text format for describing the object’s API via Signals, Slot,
> Properties and Enums, and generates a Qt header file for the Source and
> Replica sides. The mkspecs then add these files for moc to process.
Speaking as someone who has almost no clue about QtRO, from an engineering
pov, it feels weird to have an easily-parsable representation of a
QMetaObject, then generate C++ code from it, and then use moc to parse the C++
code to generate a QMetaObject. Wouldn't it be much simpler to generate the
moc files directly from the rep files (maybe even at runtime, with
QMetaObjectBuilder)?
Thanks,
Marc
--
Marc Mutz <marc.mutz at kdab.com> | Senior Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts
More information about the Development
mailing list