Atm, we still build with and depend on aidacc and sfidl.
Use of sfidl should be finally phased out, aidacc should be simplified to just
help with:
* interfaces, methods, enums, property accessors.
* meta data on properties and enum values.
* event delivery.
* support for an Any/Variant type for dynamic Event contents and a dynamic
property interface
* glue for method calls and event delivery between *threads*
* glue for C++ Iface objects on the one hand and Javascript Handle objects.
In particular *not* in current focus for aidacc should be:
- portability beyond Beast
- inter-process communication, using it across thread boundaries is good enough
for our uses
- sophisticated marshalling into serializable buffers, instead, packing
arguments into lambdas or similar idioms is sufficient for crossing thread
boundaries.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/94
_______________________________________________
beast mailing list
beast@gnome.org
https://mail.gnome.org/mailman/listinfo/beast
