Skip to main content

Introduction

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.

Features

  • 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

Prerequirements

What you need to know before messing with this script

  • Basic Plone development and Eclipse usage knowledge

Installation

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.

Usage

  • 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

How it works

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.

For more information

Possible future features

  • Deploy as real Eclipse plug-in

  • paster integration: add view, content types directly from IDE

  • deployment integration

Author

mFabrik Research Oy - Python and Plone professionals for hire.

Metadata

Release files for collective.eclipsescripts 0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.eclipsescripts 0.1
File Size Uploaded
collective.eclipsescripts-0.1.tar.gz 13.1 kB Details

Release files / collective.eclipsescripts-0.1.tar.gz

Download URL collective.eclipsescripts-0.1.tar.gz
Size 13.1 kB
Tags Source
SHA-256 checksum
How to use checksums
d4738af7482db55760352f010e0b46e6bd0f86a3c753a2dd22051309b951d92a
BLAKE2b-256 checksum
How to use checksums
e7a0aacffb51a370b7d6047180fbb9971d9d5d952ef28b2a65e84732bd4d3f84
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release history Release notifications | RSS feed

This release

0.1 This release

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page