Difference between revisions of "Framework to develop simple Eclipse plugin using PHP"

Revision as of 15:19, 27 August 2007

Project lead, student:

• Toomas Römer (IRC: toomasr_) Blog: http://tom.jabber.ee

Mentor:

• Ahti Kitsik (IRC: AhtiK) Blog: http://ahtik.com/blog/

This project is one of the selected projects for Google's Summer of Code program in 2007.

About

Abstract Framework to develop simple Eclipse plugin using PHP. Create a framework that could support developing simple Eclipse plugin using a PHP To Java bridge (Like Caucho's Quercus and other JSR 223 engines). Develop and document a sample plugin in PHP, so that PHP developers could create simple plugins.

Getting the Plugin

Requirements

• Java 6 (http://java.sun.com/javase/6/)
• Eclipse 3.3

Update site

• http://tom.jabber.ee/phpengine/update-site

SVN access

• VIEWVC url: http://eclipse-incub.svn.sourceforge.net/viewvc/eclipse-incub/plugins_in_php/
• SVN url: https://eclipse-incub.svn.sourceforge.net/svnroot/eclipse-incub
  • Module org.eclipse.soc2007.phpscriptengine
  • Module org.eclipse.soc2007.scriptingbridge.core
    • ant dist
    • You have to manually set the eclipse directory, see build.xml file.
  • Module update-site
    • ant build
• Custom builds of Quercus http://sourceforge.net/projects/quercus-bundle

Using the Plugin

• Facilities Provided by the Plugin
• Mapping PHP Functions to Java Methods

Architecture

PHP today can be used for almost anything but it will be rather difficult to use it for building GUI's in Eclipse, extending existent Views/Editors or other Eclipse Widgets that is usually done in Eclipse plugins. Although it is possible to create Java objects in PHP code and interact with them, call arbitary methods on even preinitialized objects this should not be the case in getting aid from PHP from the Eclipse plugin development point of view. PHP should or can be used for the functional parts of the plugins. Either using a third party PHP library to do some work or writing functionality that one would not want to do in Java for some reason. Of course such an aspect is not a very appealing one.

General outline

• Mapping Java methods to PHP functions via annotations
  • Annotations enrich the Java method with the following information
    • PHP file name
    • Function name
    • Function parameters (from the list the Java method accepts)
    • Object name (if function not used)
    • Object method (if function not used)
    • Object method parameters (from the list the Java method accepts)
• PHP discovery system
  • By default searching PHP files from the project's workspace
  • Configurability to provide predefined locations to speedup the scanning
  • Provide plugins with the option of defining the PHP src folders in plugin.xml
• PHP reflection system
  • Provide an easy way of writing the annotations
  • Discovered PHP files are parsed and functions/objects/methods used for annotations' auto-completion
• PHP console for quick testing
  • Write/Eval loop
• General ScriptEngine support
  • Providing general ScriptEngine support for plugins
  • Working with Anton's project Write plugins using JRuby & Groovy
• PHP scripting support
  • Plugin with the needed libraries for parsing PHP

Deliverables

• Core plugin
  • Able to use scripting languages from Java as regular Java objects
• An Eclipse Plugin
  • Able to develop Eclipse plugins using scripting languages
• Update site
  • Install the Eclipse plugin
• Quercus Bundle
  • Standalone SVN trunk builds of Quercus (GPL)
  • [[SF project http://sourceforge.net/projects/quercus-bundle]