20 | | * Modify coding style to match with Django's style |
21 | | * Adding row level permission editing to admin interface - Started. I have created an application that modifies row level permissions and will be adding this to the administration interface. |
22 | | * Adding checking of row level permissions (so they actually do something) |
23 | | |
24 | | == Proposal for Integrating into Administration Interface == |
25 | | |
26 | | === Inline Editing === |
27 | | |
28 | | Using the admin interface a user can edit Row Level Permissions (RLP) within the edit screen of a specific instance of a model. It will only be shown if RLPs are enabled for the model. |
29 | | |
30 | | The RLPs will be organized in a tabular form and using AJAX the user can add, delete or change RLPs related to the instance of the model. The page will also be set up to be backwards compatible incase the user is not able to use JavaScript. |
31 | | |
32 | | I am undecided as to whether the RLP form should be shown on the add form or not. The first priority is integrating it into the change form and then determine if it is needed in the add form. |
33 | | |
34 | | === Editing === |
35 | | |
36 | | There will probably be no capability for editing RLPs like a normal object with an add, change, and list view in the administration interface. There are a few reasons: |
37 | | * The number of RLPs could be quite high as there could possibly be one for every instance of a model. Editing this through the classic admin interface would be cumbersome. |
38 | | * Adding/Editing RLPs requires selecting the model, the instance of the model, the owner model and the instance of the owner model and the permissions related to the model. The form needed to do this would be quite elaborate and not very useful. |
| 20 | * Tidy up the admin interface and finish the AJAX interface |
| 21 | * Caching the row level permissions when checking |
| 136 | |
| 137 | == Proposal for Integrating into Administration Interface == |
| 138 | |
| 139 | === Inline Editing === |
| 140 | |
| 141 | Using the admin interface a user can edit Row Level Permissions (RLP) within the edit screen of a specific instance of a model. It will only be shown if RLPs are enabled for the model. |
| 142 | |
| 143 | The RLPs will be organized in a tabular form and using AJAX the user can add, delete or change RLPs related to the instance of the model. The page will also be set up to be backwards compatible incase the user is not able to use JavaScript. |
| 144 | |
| 145 | I am undecided as to whether the RLP form should be shown on the add form or not. The first priority is integrating it into the change form and then determine if it is needed in the add form. |
| 146 | |
| 147 | === Editing === |
| 148 | |
| 149 | There will probably be no capability for editing RLPs like a normal object with an add, change, and list view in the administration interface. There are a few reasons: |
| 150 | * The number of RLPs could be quite high as there could possibly be one for every instance of a model. Editing this through the classic admin interface would be cumbersome. |
| 151 | * Adding/Editing RLPs requires selecting the model, the instance of the model, the owner model and the instance of the owner model and the permissions related to the model. The form needed to do this would be quite elaborate and not very useful. |
| 152 | |