So you compile it all in it's own shared library (dll / so / dylib) and stick it in a plugins directory.
The main app will load whatever plugins it is configured to (either search for all or some specific ones). Or you might just compile it straight into your main app.
The plugin provides a registration function, that gets passed a pointer to WApp.
URL hookins
The plugin tells the url2action.hpp system that it's interested in /article/* urls. The plugin has its own url2action that is based off a generic restful system.
Base Plugin
There could be a base template like system that you could base plugins off of. Perhaps generating / hooking up widgets to fields.
Shared plugins
There could be a Web site where people could upload their plugins. Perhaps even a build machine on it, so you can just upload the source code.
For example
For example, you make some content type, lets say 'article' .. it has some urls that it likes:
/article/new /article/1 /article/1/edit /article/1/delete /article/list
DLL plugins
So you compile it all in it's own shared library (dll / so / dylib) and stick it in a plugins directory.
The main app will load whatever plugins it is configured to (either search for all or some specific ones). Or you might just compile it straight into your main app.
The plugin provides a registration function, that gets passed a pointer to WApp.
URL hookins
The plugin tells the url2action.hpp system that it's interested in /article/* urls. The plugin has its own url2action that is based off a generic restful system.
Base Plugin
There could be a base template like system that you could base plugins off of. Perhaps generating / hooking up widgets to fields.
Shared plugins
There could be a Web site where people could upload their plugins. Perhaps even a build machine on it, so you can just upload the source code.