Changes between Version 25 and Version 26 of ChimeraEclipse

Timestamp:

Sep 17, 2010, 1:31:30 PM (16 years ago)

Author:

Darren Weber

Comment:

--

ChimeraEclipse

@@ -21 +21 @@
 === Configure !PyDev Preferences ===
 
-See this neat [http://www.rose-hulman.edu/class/csse/resources/Eclipse/eclipse-python-configuration.htm step-by-step configuration].  Note especially the section on creating a new project and selecting the language version (2.7) and the interpreter (don't use the default, use the Chimera python install).
+Create a new workspace (e.g., Eclipse - File > Switch Workspace > Other) for the new Chimera workspace settings.  Then use Window > Preferences to locate the !PyDev panels to setup the "Interpreter - Python" to use the Chimera [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences.png python2.7 interpreter] (be sure to manually add {{{$CHIMERA/share}}} and {{{$CHIMERA/lib}}} to the "system PYTHONPATH" configuration).  Then set some [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-Env.png Chimera environment variables] (the $PATH and $CHIMERA syntax did not work, so these environment settings use full paths; the paths must point to hard-links in the file system, Chimera doesn't work with symbolic-links). Finally, an optional addition is to create a VirtualEnv for Chimera and add the pylint package, then configure the [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-PyLint.png pylint preferences].  It should be configured now to enable importing Chimera modules and [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Run.png running Chimera].
 
-Create a new workspace (e.g., Eclipse - File > Switch Workspace > Other) for the new Chimera workspace settings.  Then use Window > Preferences to locate the !PyDev panels to setup the "Interpreter - Python" to use the Chimera [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences.png python2.7 interpreter] (be sure to manually add {{{$CHIMERA/share}}} and {{{$CHIMERA/lib}}} to the "system PYTHONPATH" configuration).  Then set some [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-Env.png Chimera environment variables] (the $PATH and $CHIMERA syntax did not work, so these environment settings use full paths; the paths must point to hard-links in the file system, Chimera doesn't work with symbolic-links). Finally, an optional addition is to create a VirtualEnv for Chimera and add the pylint package, then configure the [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Preferences-PyLint.png pylint preferences].  It should be configured now to enable importing Chimera modules and [http://plato.cgl.ucsf.edu/trac/chimera/attachment/wiki/ChimeraEclipse/Chimera-Eclispe-PyDev-Run.png running Chimera].
+Also see this neat [http://www.rose-hulman.edu/class/csse/resources/Eclipse/eclipse-python-configuration.htm step-by-step configuration].  Note especially the section on creating a new project and selecting the language version (Chimera is using python 2.7, as of Sep 2010) and the interpreter (don't use the default, use the Chimera python install).
+
 
 Click on these thumbnails for the larger views: