Editing Python Scheduling Application
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
= Features = | = Features = | ||
− | |||
− | |||
* Python 3.6. | * Python 3.6. | ||
* Extensible. | * Extensible. | ||
Line 30: | Line 28: | ||
Reading the section on design as well may help understand this section. | Reading the section on design as well may help understand this section. | ||
− | |||
− | |||
− | + | The general parameter setup is explained in [[Configuration Files For Python]] and another example of its uses is discussed in [[Smart Terminal Parameter Examples]] The additional use of a global dict is different in this application. | |
− | |||
− | |||
− | |||
Each scheduling activity may have its own ( but sharable ) set of parameters for that activity. These are stored in a dictionary, which is in turn stored in a master dictionary of all activity parameters. It is set up in parameters.py and is called: AppGlobal.parameter_dicts. When an event related function is called it is passed the name of the dictionary ( a string ) in AppGlobal.parameter_dicts and it gets out the correct dictionary it needs as in: | Each scheduling activity may have its own ( but sharable ) set of parameters for that activity. These are stored in a dictionary, which is in turn stored in a master dictionary of all activity parameters. It is set up in parameters.py and is called: AppGlobal.parameter_dicts. When an event related function is called it is passed the name of the dictionary ( a string ) in AppGlobal.parameter_dicts and it gets out the correct dictionary it needs as in: | ||
Line 45: | Line 38: | ||
my_count = a_dict["failed_connect_count"] | my_count = a_dict["failed_connect_count"] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Install = | = Install = | ||
Line 82: | Line 44: | ||
= Design = | = Design = | ||
− | |||
− | |||
− | |||
− | |||
== Some Big Ideas == | == Some Big Ideas == | ||
Line 99: | Line 57: | ||
* A function that is run after the event is run that is intended to reschedule the event in some way. | * A function that is run after the event is run that is intended to reschedule the event in some way. | ||
* Most of the design is similar to [[Python Smart Terminal Technical]] except for the plug in processing modules. | * Most of the design is similar to [[Python Smart Terminal Technical]] except for the plug in processing modules. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== The GUI == | == The GUI == | ||
Line 125: | Line 73: | ||
− | + | [[Category:Arduino/RaspberryPi]] [[Category:Python]] |