- Timestamp:
-
04/07/13 03:49:50 (11 years ago)
- Author:
-
C Rempel
- Comment:
-
/* Required / Suggested Methodology */
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v18
|
v19
|
|
58 | 58 | == Required / Suggested Methodology == |
59 | 59 | |
60 | | # (Suggested) Start with an '''existing''' open source project that generates configurations, for example: [http://xpresser.com/ xpresser], [http://cyberelk.net/tim/data/system-config-printer/ system config printer], or [http://koti.kapsi.fi/ighea/wbarconf/ wbarconf]. '''Note:''' these are just examples that illustrate there are already projects out there, but if another project has a preferred configuration GUI written in Python it can be used as a starting point as well. |
| 60 | # (Suggested) Start with an '''existing''' open source project that generates configurations, for example: [http://invisible-island.net/dialog/ dialog], [http://xpresser.com/ xpresser], [http://cyberelk.net/tim/data/system-config-printer/ system config printer], or [http://koti.kapsi.fi/ighea/wbarconf/ wbarconf]. '''Note:''' these are just examples that illustrate there are already projects out there, but if another project has a preferred configuration GUI written in Python it can be used as a starting point as well. |
61 | 61 | # (Suggested) Identify patterns in the open source project for how it writes configurations |
62 | 62 | # (Required) Rewrite http://git.rtems.org/rtems/tree/doc/user/conf.t so it's trivial to use textual substitution to generate parts of the configuration GUI from them, and thus the trivial textual substitution will be easier to maintain |