Try to keep things loosely coupled, and use interfaces liberally to help.

I d start the design with the Separation of Concerns. The major architectural layers are:

• Problem Domain (aka. Engine, Back-end): the domain classes, which do all the actual work, have domain knowledge implement domain behaviour
• Persistence: storage management for domain classes, database/filesystem layer
• User Interface: the GUI, which talks to the domain classes
• System Interfaces: talking to other systems, eg. networking, web services

The domain classes do the work, but don t know about the UI. The persistence layer knows about the domain classes, enough to save/load as required. The system interface layer abstracts away external systems, which lets you plug a simulator in behind while testing. The UI should ideally use MVC, for maximum flexibility.

Without putting too fine a point on it, one would not ordinarily look to Drupal as an exemplar of good architectural design. It has grown rather organically, and there have been many upheavals of the design, as evidenced by the regular plugin breakage upon system upgrades.

I would also echo what MicSim said, regarding carefully designing the plugin interface and writing multiple different plugins to exercise it. This is the only way to really flesh out the issues of how the app and plugins interact.

As you will deliver some basic functionality with your app, make sure that you code the part that should be extendable/replaceable already as a plugin by yourself. Then you ll best get a feeling about how your API should look like.

And to prove that the API is good, you should write a second and third plugin, because then you will discover that you made a lot of assumptions when writing the first one. Normally things clear up a bit after doing this 2nd and 3rd step.

Now, you should write one more plugin, because the last plugins you wrote resemble the first one in type, input data and presentation (maybe yet another weather webservice). Choose something total different, with absolutely different data, and you will see your API being still too tailored. (Else you did a good job!)

Well, probably the first place to start is to sit down and figure out what the plug-in might need to fulfill its purpose.

You d want to consider two main aspects in your design.

• How will your framework pass requests / receive responses from the plug-in?
• What helper classes or modules might be good to provide?

And probably also, since this sounds like a learning project.

• What do you want to write yourself, and what are you happy just to pick out of an existing library?

I d also recommend developing some basic plugins as you design the API. The experience of having to actually use what you design will allow you to see where a given approach might be making things harder than they need to be.

• design the api for your app, carefully (How To Design A Good API and Why it Matters)
• make everything, which could be used independently a module, then group and build larger parts out of the simple parts (KISS)
• don t repeat yourself (DRY)
• write/publish short documentation frequently, for yourself and others (open source mantra) ...

Look into the listener-subscriber pattern. Sooner or later, your app will be complex enough that you need to implement callbacks. When you hit that limit, use listener-subscriber (there s an implementation in wxPython).

For example, several modules will want to watch for new data from a number of feeds. Modules that link together might want to update themselves, based on new data.