groundwork
groundwork copied to clipboard
useblocks
groundwork is a python based microframework for highly reusable applications and their components.
Current behaviour: If initialisation of a plugin fails, GW logs a 'WARNING: Plugin class could not be initialised.' , which does not provide any info about the cause of the...
The logging configuration might need improvement. **Current situation** Groundwork registers the following loggers: * groundwork * groundwork.signals * groundwork.pluginmanager * groundwork.patterns.gw_commands_pattern (from the commands pattern) * groundwork.patterns.gw_documents_pattern (from the documents...
The file configuration.py should be loaded by groundwork automatically during application startup. Therefore there must be some mechanism to get the location of configuration.py to the gw app: - Inside...
groundwork should setup its workspace during startup. The workspace location is defined by APP_PATH inside configuration.py Tasks to do: - Check permission - Create log folder - Create database folder
The plugin GwWebManager defines GwWeb as needed_plugin. But it looks like GwWeb gets never activated. I have added some log-outputs to the related signal-handler "_pre_activate_injection" in GwBasePattern, but none of...
Receives could be executed in parallel. We need to wrap a function around the receiver_function and create a thread for it. Maybe we get problems, if the return value is...
Log messages on debug level, if a receiver gets called
Scenario: Plugin A inherits from Pattern A Plugin A inherhits from Pattern B, which inherits from Pattern A Python will throw an exception, because it can not build a clean...
I stumbled upon the passage Plugin dependencies in plugins.rst. The following topics could make use of a more detailed documentation: - Plugin lifecylce 1. Plugin as class in my_app.plugins.classes -...