|
Next revision
|
Previous revision
Next revision
Both sides next revision
|
dev:rg_qt4_action_management [2008/10/06 10:01]
cannam created |
dev:rg_qt4_action_management [2008/10/06 13:55]
cannam |
| There are three "developer roles" here which can readily be done by different people with very little interaction -- so I suggest we do that, unless we can't find three, erm, "volunteers". | There are three "developer roles" here which can readily be done by different people with very little interaction -- so I suggest we do that, unless we can't find three, erm, "volunteers". |
| |
| ===Developer A: Boilerplate code.=== | ====Developer A: Boilerplate code.==== |
| | |
| | **Currently handled by: Chris** (I think I can mostly script this, in fact) |
| | |
| | **This task is almost complete -- I'll look at the Developer C task and then return to tidy up some loose ends later** |
| |
| Go through the code, particularly RosegardenGUIApp, MatrixView and NotationView. Find all the cases where actions are constructed with fixed data (not the completely dynamic actions such as the note font menu -- those will need to continue having a full setup in the code). | Go through the code, particularly RosegardenGUIApp, MatrixView and NotationView. Find all the cases where actions are constructed with fixed data (not the completely dynamic actions such as the note font menu -- those will need to continue having a full setup in the code). |
| |
| |
| ===Developer B: GUI definition files.=== | ====Developer B: GUI definition files.==== |
| | |
| | **Currently handled by: Julie** |
| |
| For each of the .rc files in ''src/gui/ui'', but first and foremost ''rosegardenui.rc'', ''matrix.rc'' and ''notation.rc'', find the first occurrence of each named action, and add new XML attributes describing the label, icon name, shortcut, action (radio) group if necessary, and toggleable status if necessary, as follows: | For each of the .rc files in ''src/gui/ui'', but first and foremost ''rosegardenui.rc'', ''matrix.rc'' and ''notation.rc'', find the first occurrence of each named action, and add new XML attributes describing the label, icon name, shortcut, action (radio) group if necessary, and toggleable status if necessary, as follows: |
| |
| |
| ===Developer C: Action loading code.=== | ====Developer C: Action loading code.==== |
| | |
| | **Currently handled by: Chris** |
| |
| Implement the ''newAction'' and ''stateChanged'' functions for use by Developer A. | Implement the ''createAction'', ''enterActionState'' and ''leaveActionState'' functions for use by Developer A. |
| |
| Implement a new ''createGUI'' function that loads the XML and sets up the actions into menus and so on appropriately. | Implement a new ''createGUI'' function that loads the XML and sets up the actions into menus and so on appropriately. |
