|
1 | 1 | # TODOs |
2 | 2 |
|
3 | | -## Business logic, business features |
4 | | - - [ ] Issues guide for the GitHub (OS, content of the config, project tree, enable verbose) |
| 3 | +## Business logic, general features |
5 | 4 | - [ ] GitHub CHANGELOG - separate New, Fixed, Changed into paragraphs |
6 | 5 | - [ ] Middleware support (FreeRTOS, etc.) |
7 | 6 | - [ ] Arduino framework support (needs research to check if it is possible) |
8 | 7 | - [ ] Create VSCode plugin |
| 8 | + - [ ] UML diagrams (core, GUI back- and front-ends, thread flows, events, etc.) |
| 9 | + - [ ] CI is possible (Arch's AUR has the STM32CubeMX package, also there is a direct link). Deploy Docker one in Azure Pipelines, basic at Travis CI |
9 | 10 |
|
10 | 11 | ## GUI version |
11 | | - - [ ] Handle the initialization error (when boards are receiving) |
12 | | - - [ ] Maybe `data()` `QAbstractListModel` method can be used instead of custom `get()` |
| 12 | + - [ ] Obtain boards on demand (not at the startup) |
13 | 13 | - [ ] Can probably detect Ctrl and Shift clicks without moving the mouse first |
14 | | - - [ ] Notify the user that the 'board' parameter is empty |
15 | 14 | - [ ] Mac: sometimes auto turned off shift highlighting after action (hide-restore helps) |
16 | 15 | - [ ] Some visual flaws when the window have got resized (e.g. 'Add' button position doesn't change until the list gets focus, 'Log' area crawls onto the status bar) |
17 | | - - [ ] Gray out "stage" line in all projects except current |
18 | 16 | - [ ] Tests (research approaches and patterns) |
19 | | - - [ ] Test performance with a large number of projects in the model. First test was made: |
20 | | - 1. Some projects occasionally change `initLoading` by itself (probably Loader unloads the content) (hence cannot click on them, busy indicator appearing) |
| 17 | + - [ ] Remade the list item to use States, too. Probably, such properties need to be implemented: |
| 18 | + ``` |
| 19 | + state: { |
| 20 | + loaded, |
21 | 21 |
|
22 | | - Note: Delegates are instantiated as needed and may be destroyed at any time. They are parented to ListView's contentItem, not to the view itself. State should never be stored in a delegate. |
| 22 | + visitedAfterInstantiating, |
23 | 23 |
|
24 | | - Use `id()` in `setInitInfo()`. Or do not use ListView at all (replace by Repeater, for example) as it can reset our "notifications" |
25 | | - 2. Some projects show OK even after its deletion (only the app restart helps) |
| 24 | + actionRunning, |
| 25 | + lastActionStatus, |
| 26 | + visitedAfterAction, |
| 27 | + ... |
| 28 | + } |
| 29 | + ``` |
26 | 30 | - [ ] Test with different timings |
27 | 31 | - [ ] Divide on multiple modules (both Python and QML) |
28 | 32 | - [ ] Implement other methods for Qt abstract models |
29 | 33 | - [ ] Warning on 'Clean' action (maybe the window with a checkbox "Do not ask in the future" (QSettings parameter)) |
30 | | - - [ ] 2 types of logging formatters for 2 verbosity levels |
31 | | - - [ ] `TypeError: Cannot read property 'actionRunning' of null` (deconstruction order) (on project deletion only) |
32 | 34 | - [ ] QML logging - pass to Python' `logging` and establish a similar format. Distinguish between `console.log()`, `console.error()` and so on |
33 | 35 | - [ ] Lost log box autoscroll when manually scrolling between the actions |
34 | 36 | - [ ] Crash on shutdown in Win and Linux (errors such as `[QML] CRITICAL QThread: Destroyed while thread is still running Process finished with exit code 1073741845`) |
35 | | - - [ ] Start with a folder opened if it was provided on CLI (for example, `stm32pio_gui .`) |
36 | | - - [ ] Linux: |
37 | | - - Not a monospace font in the log area |
| 37 | + - [ ] Linux: Not a monospaced font in the log area |
| 38 | + - [ ] Temporarily pin projects with currently running actions to the top (and stay there on scrolling). See QML Package type |
38 | 39 |
|
39 | 40 | ## Core library |
40 | | - - [ ] Add more checks, for example when updating the project (`generate` command), check for boards matching and so on... |
41 | | - - [x] Remove casts to string where we can use path-like objects (related to Python version as new ones receive path-like objects arguments while old ones aren't) |
| 41 | + - [ ] when updating the project (`generate` command), check for boards match |
| 42 | + - [ ] Remove casts to string where we can use path-like objects (related to a Python version as new ones receives path-like objects arguments while old ones aren't) |
42 | 43 | - [ ] We look for some snippets of strings in logs and output for the testing code but we hard-code them and this is not good, probably (e.g. 'DEBUG') |
43 | | - - [ ] Store a folder initial content in .ini config and ignore it on clean-up process. Allow the user to modify such list (i.e. list of exclusion) in the config file. Mb some integration with `.gitignore` |
| 44 | + - [ ] Store an initial content of the folder in .ini config and ignore it on clean-up process. Allow the user to modify such list (i.e. list of exclusion) in the config file. Mb some integration with `.gitignore` |
44 | 45 | - [ ] at some point check for all tools (CubeMX, ...) to be present in the system (both CLI and GUI) (global `--check` command (as `--version`), also before execution of the full cycle (no sense to start if some tool doesn't exist)) |
45 | 46 | - [ ] generate code docs (help user to understand an internal mechanics, e.g. for embedding). Can be uploaded to the GitHub Wiki |
46 | | - - [ ] colored logs, maybe (brakes zero-dependency principle) |
47 | | - - [ ] check logging work when embed stm32pio lib in a third-party stuff (no logging setup at all) |
48 | | - - [ ] merge subprocess pipes to one where suitable (i.e. `stdout` and `stderr`) |
49 | | - - [ ] redirect subprocess pipes to `DEVNULL` where suitable to suppress output (tests) |
50 | | - - [ ] Two words about a synchronous nature of the lib and user's responsibility of async wrapping (if needed). Also, maybe migrate to async/await approach in the future |
| 47 | + - [ ] colored logs, maybe (breaks zero-dependency principle) |
| 48 | + - [ ] maybe migrate to async/await approach in the future (return some kind of a "remote controller" to control the running action) |
51 | 49 | - [ ] `__init__`' `parameters` dict argument schema (Python 3.8 feature). |
52 | | - - [ ] See https://docs.python.org/3/howto/logging-cookbook.html#context-info to maybe remade current logging schema (current is, perhaps, a cause of the strange error while testing (in the logging thread), also modifies global settings (log message factory)) |
53 | | - - [ ] UML diagrams (core, GUI back- and front-ends, thread flows, events, etc.) |
54 | | - - [ ] CI is possible (Arch's AUR has the STM32CubeMX package, also there is a direct link). Deploy Docker one in Azure Pipelines, basic at Travis CI |
55 | | - - [ ] Test preserving user files and folders on regeneration and mb other operations |
56 | | - - [ ] Move special formatters inside the library. It is an implementation detail actually that we use subprocesses and so on |
57 | | - - [ ] Mb store the last occurred exception traceback in .ini file and show on some CLI command (so we don't necessarily need to turn on the verbose mode). And, in general, we should show the error reason right off |
58 | | - - [ ] 'verbose' and 'non-verbose' tests as `subTest` (also `should_log_error_...`) |
| 50 | + - [ ] Mb store the last occurred exception traceback in .ini file and show on some CLI command (so we don't necessarily need to turn on the verbose mode and repeat this action). And, in general, we should show the error reason right off |
59 | 51 | - [ ] the lib sometimes raising, sometimes returning the code and it is not consistent. While the reasons behind such behavior are clear, would be great to always return a result code and raise the exceptions in the outer scope, if there is need to |
60 | 52 | - [ ] check board (no sense to go further on 'new' if the board in config.ini is not correct) |
61 | | - - [ ] check if `platformio.ini` config will be successfully parsed when there are interpolation and/or empty parameters |
62 | | - - [x] check if `.ioc` file is a text file on project initialization. Let `_find_ioc_file()` method to use explicitly provided file (useful for GUI). Maybe let user specify it via CLI |
63 | | - - [ ] mb add CLI command for starting the GUI version (for example, `stm32pio --gui`) |
64 | 53 | - [ ] test using virtualenv |
| 54 | + - [ ] test for different `.ioc` files (i.e. F0, F1, F4 and so on) as it is not the same actually |
| 55 | + - [ ] mb allow to use an arbitrary strings (arrays of str) to specify tools commands in stm32pio.ini (shell=True or a list of args (split a string)) |
| 56 | + - [ ] cache boards for a small interval of time |
| 57 | + - [ ] count another '-v' as '-v' for PlatformIO calls (slider in GUI settings window) |
| 58 | + - [ ] Project' name (path) can be reused so cannot be used as a unique identifier but so is id(self)? Probably it is better to use a path (human-readable) |
| 59 | + - [ ] Analyze `.ioc` file for the wrong framework/parameters |
0 commit comments