Changes between Version 5 and Version 6 of DevNotes/Obsolete/Development


Ignore:
Timestamp:
Apr 26, 2015 1:45:13 PM (4 years ago)
Author:
butler
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • DevNotes/Obsolete/Development

    v5 v6  
    3030doubt, contact your IT Support. 
    3131 
    32 === Installing PyDev ===  
     32=== Installing !PyDev ===  
    3333Start Eclipse and open: File -> Switch Workspace -> Other... -> Select a workspace (the default is drive:\path\Eclipse_workspace) 
    3434 
    35 Window -> Open Perspective -> Other -> PyDev 
    36  
    37 If PyDev is not listed as a perspective it will be necessary to install it: 
     35Window -> Open Perspective -> Other -> !PyDev 
     36 
     37If !PyDev is not listed as a perspective it will be necessary to install it: 
    3838 
    3939Help -> Install New Software... and in the Work With: drop-down select the PyDev Update Site. Let the list of available software refresh. 
    4040 
    41 Check the box next to PyDev and click Next. The plug-in will install. 
     41Check the box next to !PyDev and click Next. The plug-in will install. 
    4242 
    4343If this doesn’t work: 
    4444 
    45 Download the PyDev certificate from http://pydev.org/pydev_certificate.cer and install it (in Windows, just right-click and select Install certificate) 
    46  
    47 Now get PyDev from http://sourceforge.net/projects/pydev/files/ 
    48  
    49 If you have Java 7 installed, you must install PyDev 3.4.1 or later. 
     45Download the !PyDev certificate from http://pydev.org/pydev_certificate.cer and install it (in Windows, just right-click and select Install certificate) 
     46 
     47Now get !PyDev from http://sourceforge.net/projects/pydev/files/ 
     48 
     49If you have Java 7 installed, you must install !PyDev 3.4.1 or later. 
    5050Extract the zip file to the Eclipse dropins folder and re-start Eclipse 
    5151 
     
    8989Check ‘Use existing repository location’ -> Select a SVN repository from the list shown -> Next 
    9090 
    91 The SasView SVN repository is hosted by SourceForge at: https://svn.code.sf.net/p/sasview/code 
     91The SasView SVN repository is hosted by !SourceForge at: https://svn.code.sf.net/p/sasview/code 
    9292 
    9393For commit access aspiring developers need (read-only checkout is public): 
     
    129129The official version of Python for building SasView is 2.7 
    130130 
    131 Install NumPy, SciPy, and the additional Python site packages for building SasView 
     131Install !NumPy, !SciPy, and the additional Python site packages for building !SasView 
    132132 
    133133NB: if you are using a Win64 version of Python ensure you also download and install a Win64 
    134134version of wxPython compatible with your Python 2.x installation! 
    135135 
    136 Window -> Preferences -> PyDev -> Interpreter – Python 
     136Window -> Preferences -> !PyDev -> Interpreter – Python 
    137137 
    138138If no Python interpreter is shown, click ‘New...’, enter a name for your Python installation and 
     
    141141Click OK 
    142142 
    143 In the PyDev Package Explorer pane: 
     143In the !PyDev Package Explorer pane: 
    144144 
    145145Navigate to the sansview folder within the trunk 
     
    147147Right-click on sansview.py -> Run As -> Python Run 
    148148 
    149 If this fails with an error message in the console pane it means that there is no existing SasView build 
    150 – which is what you want! If, on the other hand, SasView starts up, search for a sasview .egg file! 
     149If this fails with an error message in the console pane it means that there is no existing !SasView build 
     150– which is what you want! If, on the other hand, !SasView starts up, search for a sasview .egg file! 
    151151 
    152152Then repeat this test. 
     
    154154Locate setup.py in the top level of the trunk 
    155155 
    156 Right-click on run.py -> Properties -> Run/Debug Settings 
     156Right-click on run.py -> Properties -> !Run/Debug Settings 
    157157 
    158158IF no_launch_configuration shown: 
     
    168168Or highlight your_trunk_project setup.py and then choose Run -> Run As -> Python Run 
    169169 
    170 SasView should build from your local trunk. If the build fails it will most likely be because a Python 
     170!SasView should build from your local trunk. If the build fails it will most likely be because a Python 
    171171package has not installed, in which case install it manually (eg, using easy_install) 
    172172 
     
    181181Right-click on setup.py -> Run As -> Python Run 
    182182 
    183 SasView should build! 
    184  
    185 The locally-built version of SasView should appear in 
     183!SasView should build! 
     184 
     185The locally-built version of !SasView should appear in 
    186186drive:\path\Eclipse_workspace\workspace_location\dist as something similar to 
    187187sasview-3.0.0_r0-py2.7-win32.egg 
     
    193193Right-click on run.py -> Run As -> Python Run 
    194194 
    195 SasView should start up! 
    196  
    197 NB: This is running SasView from compiling and building the Python/C/C++, it is not installing 
    198 SasView 
    199  
    200 NB: If you run SasView at this point it may stop an Installer application from building, so if you want 
     195!SasView should start up! 
     196 
     197NB: This is running !SasView from compiling and building the Python/C/C++, it is not installing 
     198!SasView 
     199 
     200NB: If you run !SasView at this point it may stop an Installer application from building, so if you want 
    201201an Installer application, create that first (see below)! 
    202202 
    203 === Creating a SasView Installer Package === 
     203=== Creating a !SasView Installer Package === 
    204204NB: You would not normally need to do this because that is the function of the Build Server! 
    205205Navigate to the sansview folder within the trunk 
     
    207207Right-click on setup_exe.py -> Run As -> Python Run 
    208208 
    209 This should create a file SasView.exe in the sansview\dist folder of the trunk 
     209This should create a file !SasView.exe in the sansview\dist folder of the trunk 
    210210 
    211211Double-click on installer.iss to bring up the Inno Setup Compiler 
    212212 
    213 Click the green ‘play’ button to build a SasView installer 
     213Click the green ‘play’ button to build a !SasView installer 
    214214 
    215215This should create a file setupSasView.exe in the sansview\Output folder of the trunk 
     
    221221Right-click on the utest_test-name.py file -> Run As -> Python unit-test 
    222222 
    223 NB: unit tests operate on the last built version of SasView, so if you have modified any modules or 
    224 unit tests you must re-build SasView first! 
     223NB: unit tests operate on the last built version of !SasView, so if you have modified any modules or 
     224unit tests you must re-build !SasView first! 
    225225 
    226226The unit test your_trunk_project\test\utest_sansview.py executes all the unit tests 
     
    242242Add a comment to describe your changes 
    243243 
    244 ==== To See/Compare Code Changes ==== 
     244==== To !See/Compare Code Changes ==== 
    245245Either: 
    246246 
     
    253253Login 
    254254 
    255 Projects -> SasView -> Code 
     255Projects -> !SasView -> Code 
    256256 
    257257NB: if you haven’t been coding for a while, right-click on the top level of the trunk and do Team -> Update 
     
    277277Note that a branch is not simply a sub-folder of trunk 
    278278 
    279 The top-level of the SasView code repository contains: 
     279The top-level of the !SasView code repository contains: 
    280280 Web:: the sasview.org web pages 
    281281 Trunk:: the code in the current development build 
     
    290290To create a branch in Eclipse: 
    291291 
    292  * Right-click on your_trunk_project -> Team -> Branch/Tag 
     292 * Right-click on your_trunk_project -> Team -> !Branch/Tag 
    293293 * Modify the URL shown by adding /branches/name_of_branch 
    294294 * Click Next 
     
    300300 
    301301To work with a different branch: 
    302  * In PyDev view, right-click on the top-level of the current trunk -> Team -> Switch to another 
    303  * Branch/Tag/Revision... 
     302 * In !PyDev view, right-click on the top-level of the current trunk -> Team -> Switch to another 
     303 * !Branch/Tag/Revision... 
    304304 * Modify the URL shown to point to the appropriate branch 
    305305 * Click OK