python - How to design an application in a modular way? -


I'm looking at indicators, suggestions, links, warnings, ideas and even ectotal accounts "How to design an app in a modular way" I am going to use Python for this project, but advice does not have to be considered necessary in this language, although I only I'm ready to implement a design based on OOP.

Here are some references to understand where I came from and what I am trying to achieve ...


My project is a little bit Applications that will use web services and display results in various ways, including: / P>

  • Notifications popups resulting from calls
  • Retrieved raw- Tabs in the main window of the application with graphics plotted from the data
  • The buffer message (visible on the domand) where the results of various services will stack

The application will be released as free (as speech) software, and this The reason I make it easier for other developers to write plugins / modules which will increase the functionality of the main application without the need to change the main code.

At this point, By defining the provider to the plugins, data manipulation (if any) and the way the data will be presented to the user

P> I have extensive experience in developing which has a powerful modular approach, but it also follows a non-object-oriented design, so I suspect that Python For, the drupal design can not be the optimal solution.

If it is of any importance - basically it will be developed for GNU / Linux.

Thank you in advance for your time!

Try to keep things coherently, and use the interface generously for assistance.

I the separation of problems . The major architectural layers are:

  • Problem domains (aka engine, back-end): domain class, which do all the actual work, domain domain implement domain behavior
  • < Li> Persistence: storage management for domain classes, database / file system layer
  • User Interface: GUI, which talks to domain classes
  • System interfaces: talking to other systems , E.g. Networking, Web Services

Domain classes work, but do not know about the firm knows the level of level domain classes, which is necessary / enough to save the system interface layer The external system is removed, so that you can run in a simulator plug during the test. The UI should ideally use MVC for maximum flexibility.

Without fixing a point on it, generally Doppl will not be seen as an example of a good architectural design. Instead, systematically increased, and there are many entanglements of the design, as explained about the regular plugin breakdown on system upgrades.

What do I also rekindle about Microsimm, which many different plugins about designing and writing plugin interfaces to exercise it The way the app and plugins interact, the issue is actually the only way to meat.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

jquery - SimpleModal Confirm fails to submit form -