Editing MGED to Archer Command Migration
From BRL-CAD
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 1: | Line 1: | ||
| + | = MGED to Archer Command Migration= | ||
| + | |||
| + | {| border=1 align="right" | ||
| + | !Impact | ||
| + | !Difficulty | ||
| + | |- | ||
| + | |high | ||
| + | |medium | ||
| + | |} | ||
Archer is the next iteration of BRL-CAD's MGED model editing tool. We are currently in the process of migrating functionality from MGED to Archer, and there are many command-line commands that are currently not supported in Archer but should be. Proposals for this task should identify those commands, how to migrate them, how to test them, and any features needed but not implemented in Archer to support running them. The work over the course of the summer would be to perform the migrations, verify the results, and fix issues as needed along the way. | Archer is the next iteration of BRL-CAD's MGED model editing tool. We are currently in the process of migrating functionality from MGED to Archer, and there are many command-line commands that are currently not supported in Archer but should be. Proposals for this task should identify those commands, how to migrate them, how to test them, and any features needed but not implemented in Archer to support running them. The work over the course of the summer would be to perform the migrations, verify the results, and fix issues as needed along the way. | ||
| Line 4: | Line 13: | ||
A good proposal for this topic would include details on what commands would be migrated and how (not per command, some general techniques are in place), identify specifics needed to achieve full functionality in Archer, and factor in time required for testing - if it don't work it ain't migrated! Should also be looking to consolidate functionality where it is duplicated and clean up, rather than blindly copying - if there is a cleaner solution than the current setup for a particular task the preferred way forward is to implement the "right" way and support older commands as specific invocations of newer commands - for example, dbfind should be a call to the more powerful search command, and the graphical pattern tool in MGED needs to have its functionality merged into the command line tool clone. A student looking to submit a proposal for this task should do their homework and know what they're dealing with. | A good proposal for this topic would include details on what commands would be migrated and how (not per command, some general techniques are in place), identify specifics needed to achieve full functionality in Archer, and factor in time required for testing - if it don't work it ain't migrated! Should also be looking to consolidate functionality where it is duplicated and clean up, rather than blindly copying - if there is a cleaner solution than the current setup for a particular task the preferred way forward is to implement the "right" way and support older commands as specific invocations of newer commands - for example, dbfind should be a call to the more powerful search command, and the graphical pattern tool in MGED needs to have its functionality merged into the command line tool clone. A student looking to submit a proposal for this task should do their homework and know what they're dealing with. | ||
| − | =References= | + | ==References== |
* src/mged | * src/mged | ||
| Line 13: | Line 22: | ||
* src/librt | * src/librt | ||
| − | =Requirements= | + | ==Requirements== |
* Familiarity with C | * Familiarity with C | ||
| Line 19: | Line 28: | ||
* Knowledge of command handling in MGED, Archer, libged and possibly librt - scope of libraries and where functionality should live. | * Knowledge of command handling in MGED, Archer, libged and possibly librt - scope of libraries and where functionality should live. | ||
* Background knowledge of BRL-CAD will make a major difference! | * Background knowledge of BRL-CAD will make a major difference! | ||
| − | |||
| − | |||
| − | |||
