[349] | 1 | SYSTEM REQUIREMENTS |
---|
[3492] | 2 | Pmesh requires many bits adn peices from the rest of the ANUGA code. |
---|
[349] | 3 | |
---|
[3492] | 4 | It's system requirements are the same as ANUGA |
---|
[349] | 5 | |
---|
[3492] | 6 | INSTALLATION COMMANDS |
---|
| 7 | To compile, do |
---|
| 8 | scones |
---|
[1926] | 9 | |
---|
[1476] | 10 | |
---|
[349] | 11 | GENERAL RUNNING |
---|
[3492] | 12 | To run all the unit tests; |
---|
| 13 | python test_all.py |
---|
[349] | 14 | |
---|
| 15 | To run pmesh; |
---|
[3492] | 16 | python graphical_mesh_generator.py |
---|
[349] | 17 | |
---|
| 18 | INSTRUCTIONS FOR USING PMESH |
---|
| 19 | |
---|
| 20 | Pmesh will let the user select various modes. The current |
---|
| 21 | allowable modes are vertex or segment. The mode describes what sort |
---|
| 22 | of object is added or selected in response to mouse clicks. When |
---|
| 23 | changing modes any prior selected objects become deselected. |
---|
| 24 | |
---|
| 25 | In general the left mouse button will add an object and the right |
---|
| 26 | mouse button will select an object. A selected object can de deleted |
---|
| 27 | by pressing the the middle mouse button (scroll bar). |
---|
| 28 | |
---|
| 29 | NOTES |
---|
| 30 | I have examples of running triangle in |
---|
| 31 | nautilus /home/duncan/MeshGen/triangle_old |
---|
| 32 | |
---|
| 33 | CREATING A PMESH EXECUTABLE |
---|
[3492] | 34 | Note, this has not been tried for about 2 years. |
---|
[349] | 35 | |
---|
| 36 | There is a package called py2exe which can take a Python script and |
---|
| 37 | package it up along with any other scripts it imports and a Python |
---|
| 38 | interpreter into a single .exe. It will also find any DLLs your script |
---|
| 39 | depends on and copy them too. |
---|
| 40 | |
---|
| 41 | The packaging process: |
---|
| 42 | |
---|
| 43 | |
---|
| 44 | 1)Install py2exe. This only needs to be done once on a machine. |
---|
| 45 | |
---|
| 46 | 2)Make a static version of Pmw. Pmesh uses a package called Pmw which |
---|
| 47 | normally dynamically loads pieces of itself as needed. This doesn't |
---|
| 48 | work with py2exe, so we need to fix it. You'll only need to do this |
---|
| 49 | once; if you make a change to your script and |
---|
| 50 | repackage you can skip this step. |
---|
| 51 | |
---|
| 52 | cd to c:\python22\lib\site-packages\Pmw\Pmw_1_1\bin. (Assuming python |
---|
| 53 | is installed in the default c:\python22; change the paths if you |
---|
| 54 | installed Python somewhere else. |
---|
| 55 | |
---|
| 56 | run "python bundlepmw.py |
---|
| 57 | c:\python22\lib\site-packages\Pmw\Pmw_1_1\lib". This will create a |
---|
| 58 | file called "Pmw.py" in the current directory. |
---|
| 59 | |
---|
| 60 | copy "Pmw.py" to your main script directory. |
---|
| 61 | |
---|
| 62 | copy "..\lib\PmwBlt.py" and "..\lib\PmwColor.py" to your main script |
---|
| 63 | directory, too. |
---|
| 64 | |
---|
| 65 | 3) Do the command "python exesetup.py py2exe" This will create a dist directory with the pmesh executable. |
---|