Relative Content

Tag Archive for plugin-architecture

Application plugin interface design

I build a plugin based Qt application which currently lives entirely in a library. The app as well as the plugins link to the library. The ::main(…) is just a tiny two line bootstrapper calling a guarded run(…) in the library. Most of the interface classes are Pimpl or virtual interfaces, however there are loads of classes in the library that are not related to the interface but are simply part of the core app.

Is it possible to use PNaCl as a plugin framework?

I am looking to design an extremely modular game engine that allows for portable native plugins similar to the way PNaCl works with chrome. The biggest factors I need would be: cross platform, sandboxed, and the ability to launch an arbitrary number of these plugins based on what folder they reside in. I can’t have any internal code expecting a plugin to be there, all plugins will be added and will attach to my own custom API.

Is it possible to use PNaCl as a plugin framework?

I am looking to design an extremely modular game engine that allows for portable native plugins similar to the way PNaCl works with chrome. The biggest factors I need would be: cross platform, sandboxed, and the ability to launch an arbitrary number of these plugins based on what folder they reside in. I can’t have any internal code expecting a plugin to be there, all plugins will be added and will attach to my own custom API.

Is it possible to use PNaCl as a plugin framework?

I am looking to design an extremely modular game engine that allows for portable native plugins similar to the way PNaCl works with chrome. The biggest factors I need would be: cross platform, sandboxed, and the ability to launch an arbitrary number of these plugins based on what folder they reside in. I can’t have any internal code expecting a plugin to be there, all plugins will be added and will attach to my own custom API.

Is there a term for this coding practice?

One of the incidental complexities of introducing features to an existing system is that the programmer often has to touch several areas of code that are not immediately adjacent. Over the long haul it can be unclear when looking at a bit of code that it pertains to another bit found elsewhere. It’s both ugly design and a maintenance hazard. One of the properties of superior code, in my book, is its ability to keep a concept localized in one place. Sometimes this is built in to an architecture up front making it easy to plug new features into a system.

How to allow multiple plugins to provide data for multiple aggregation processes?

I’m working on a Java project in which we want to have data collection plugins that collect data to be processed by one or more data aggregation modules. The plugins will all written in-house. Say for example we have data collection plugins A, B and C and data aggegration module X. The modules A, B & C input data into tables that are different but have a few certain fields in common that X cares about. Sometimes the names of the fields are different, but as far as the algorithm is concerned they are “the same”.

How to allow multiple plugins to provide data for multiple aggregation processes?

I’m working on a Java project in which we want to have data collection plugins that collect data to be processed by one or more data aggregation modules. The plugins will all written in-house. Say for example we have data collection plugins A, B and C and data aggegration module X. The modules A, B & C input data into tables that are different but have a few certain fields in common that X cares about. Sometimes the names of the fields are different, but as far as the algorithm is concerned they are “the same”.

Pluggable UI Components in Java Web Applications

I will try to explain my question with an example. Let us say that we are writing a hotel reservation system which is web based using Java. We will have different payment methods, say Paypal, Master Card and Visa Card. Different customers of our product will use different payment methods only. (Hotel XYZ, who is our customer, will only want to use Paypal and hotel ABC will only want to show the Master Card and Visa options).

Would this be considered a plugin or template type architecture?

I would like to build a system that basically offers the option to make various APIs interchangeable for usage to the end user. For example, the person using the software would have the option of choosing a single existing supported Billing System at any one time. They could for example choose to use WHMCS, Host Bill or Blesta.