Plone plug-in for Eclipse development
collective.eclipsescripts is an Eclipse integration plug-in for Plone development. It aims to provide effective way for novice developers to get started with Plone.
Create Eclipse workspace from buildout installation - all Python projects inside src/ folder structure are converted to Eclipse projects. You can keep your buildout in sync with your Eclipse workspace with one command.
Set Eclipse preferences suitable for Plone/Zope development
- Tab stops to 8 spaces
- File associations: .pt, .dtml, .zcml, etc.
- Version control ignores (do not commit egg-info folders)
- Text encoding settings to UTF-8
Different UI Run shortcuts are automatically created
- IDE compatible Zope launching script (retains console output by not making Zope to fork on start-up)
- Plone local instance
- Unit test runners for all projects
- Run buildout
- Open Zope debug shell
- Edit buildout.cfg
What you need to know before messing with this script
Note: Currently we can’t support installation as Python egg or Eclipse plug-in bundle. This is being worked out.
Install Aptana Studio with PyDev and Subclipse plug-ins. Standalone Aptana installation is recommended as it is the fastest way to get started - you do not need to manually gather and install plug-ins.
- Standard Eclipse standalone installation seems to have some componenent version compatibility issues. Aptana is recommended way to install Eclipse for Python development.
Install Python Monkey and restart Eclipse
Checkout this project using Subclipse/Subversive to Eclipse workspace as a project
- Repository URL: https://svn.plone.org/svn/collective
- Project path: collective.eclipsescripts/trunk
- Alternatively copy Python egg contents to script/ folders under some of your Eclipse projects
Immediately menu Scripts should appear in the top menu bar
Open scripts in Python editor to see comments what they do
Execute scripts by picking then from Scripts menubar
Open console to see possible sccript output
- Choose menu Window -> Show View -> Console. Then choose Eclipse Monkey Console from alternative console views. Note: console might not be available until you have run one of the scripts.
Create Plone 3 buildout - use your favorite buildout integrated tool to manage source code checkout under src/. E.g. ‘Mr. Developer <http://pypi.python.org/pypi/mr.developer>`_
Launch Eclipse - Switch workspace and choose src/ folder in buildout as the workspace location
Configure Python 2.4 (for Plone 3.x) in preferences
Set workspace settings - Choose Scripts -> Plone -> Set Plone Preferences
Choose Scripts -> Plone -> Import src folder as workspace to import all checked out projects under src/ as Eclipse projects. If you add new projects you can run this command without losing manual changes made to the projects.
- Plone instance and projects will have launchers created in Run configurations… menu
- Optionally, if you are using collective.recipe.omelette all Plone packages are added under PyDev builders and code autocompletion will work for the projects
Choose Scripts -> Plone -> Edit buildout.cfg if you wish to edit buildout.cfg
Python Monkey exposes Eclipse process to Python scripting environment through Jython run-time. Everything what can be done by Eclipse plug-ins and Java development can be now done with few lines of Python code. This makes the development of integration options for Eclipse real quick and dirty.
Also, you do not need to have a separate Eclipse project for your scripts. You can keep your scripts within any Eclipse project in scripts top level folder.
- Deploy as real Eclipse plug-in
- paster integration: add view, content types directly from IDE
- deployment integration
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size collective.eclipsescripts-0.1.tar.gz (13.1 kB)||File type Source||Python version None||Upload date||Hashes View hashes|
Hashes for collective.eclipsescripts-0.1.tar.gz