Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upRegistering new types dynamically (via Plugins) #89
Comments
The plugins containing the metadata must have seen the headers at some point or they couldn't generate the metadata. Once the metadata is compiled into the plugin, yes, it can be loaded without needing the headers. You can also unregister the types when the plugin is unloaded. See #21. |
|
I don't understand very well, both the host application and the plugin itself links to Ponder, the plugin new types has their respective headers to generate the needed metadata required by Ponder, but the host application doesn't know the new exported types in the C++ side, but should be known by the Host's Ponder API side when i load the DLL explicitly to the memory (via dlopen or LoadLibrary APIs). |
|
Needs docs and example. |
|
Just a little remark, make your users implement their own library loading strategies instead of Ponder do it so. Some projects have their own way to load their libraries, and maybe an already integrated plugin framework which is used for unrelated or specialized classes. |
|
Interesting idea. |
There's an way or what to modify from Ponder able to register new types via Plugins or dynamic/static plugins? where the core application doesn't have access to the headers of the new types?