en:dev:drafts:plugins
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dev:drafts:plugins [2018/02/15 14:47] – +pyutilib code nerdoc | en:dev:drafts:plugins [2019/09/15 16:23] (current) – nerdoc | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| As MedUX needs to be completely modular, we need a plugin framework that has some capabilities: | As MedUX needs to be completely modular, we need a plugin framework that has some capabilities: | ||
| * **it must be easy** to understand and use | * **it must be easy** to understand and use | ||
| - | * **it must be maintained**. It must be a framework that will not vanish in half a year. | + | * **it must be maintained**. It must be a framework that will not vanish in half a year. |
| - | * **it must be thread safe**: Direct calls are not very nice when trying to make a responsive UI. Ideally based on a loosely-coupled signal/slot mechanism like the one in Qt. | + | |
| - | * **it should work with PyQt** | + | |
| There are several plugin systems that are available for python, | There are several plugin systems that are available for python, | ||
| Line 13: | Line 11: | ||
| that are taken into consideration for MedUX: | that are taken into consideration for MedUX: | ||
| + | * [[https:// | ||
| * [[http:// | * [[http:// | ||
| * [[http:// | * [[http:// | ||
| + | * [[https:// | ||
| + | |||
| + | Old ones (not taken into consideration further): | ||
| + | |||
| * [[http:// | * [[http:// | ||
| * [[https:// | * [[https:// | ||
| - | * [[https:// | ||
| * [[https:// | * [[https:// | ||
| + | * [[https:// | ||
| - | Maybe take the " | ||
| Brainstorming: | Brainstorming: | ||
en/dev/drafts/plugins.1518702478.txt.gz · Last modified: 2018/02/15 14:47 by nerdoc