The ApCoCoA 2.0 project is divided into two sub projects: The CoCoA Plugin and the CoCoA IDE based on IntelliJ.
The CoCoA IDE
The IDE is based on IntelliJ Community Edition. The source code of the IntelliJ Community Edition is available on Github. We cloned the original repository and modified some files in the python branch to make our own customized IDE (ApCoCoA). However the repository on which we are working now is available on Bitbucket: https://bitbucket.org/klausnguets/cocoa_ide/src/master/. We modified the following files in the IDE:
- In the folder python/resources we replaced the IDE logos with our own logo.
- In python/python-community-ide-resources/resources/tips you can find the files to modify the product name, the help page etc.
- In the same folder python/python-community-ide-resources/resources you can find the file /idea/PyCharmCoreApplicationInfo.xml to edit the IDE information.
Building the IDE
After the the IDE is customized as wanted, the last step is to build the sources in order to obtain the IDE for Windows, Linux and Mac as follows:
- Install Ant, the Java Development Kit and JavaFX.
- Increase the Java Heap size for ant:
export _JAVA_OPTIONS=-Xmx5000mto set a maximum heap size of for example 5G. To make those changes permanent, you have to add this command in your /etc/profile.
You can use the command
java -XshowSettings:vmto check whether the heap size has changed.
- Change to the folder python in the source and run the command
ant -f build.xml. You might get a
BUILD FAILEDerror message. You can ignore this message but need to make sure that in the directory out/pycharm-ce the three folders dist.mac, dist.unix and dist.win were created.
- To obtain the IDE for a given platform, for example unix, copy the contents of dist.unix/run into the folder dist.all/run.
- Make the files pycharm.sh, fsnotifier and fsnotifier64 executable:
chmod +x ./fsnotifier ./fsnotifier64 ./pycharm.sh.
- Now you should be able to start the IDE using
The CoCoA Plugin
The CoCoA plugin is the part of the project which addresses everything that is specific to the CoCoA language such as the syntax highlighting, the interpreter, the interactive window, the CoCoA files recognition... The plugin is developed as a normal IntelliJ Platform plugin, meaning it can be used in other IntelliJ IDEs to make them recognize and interpret a CoCoA file. IntelliJ platforms provides interesting tutorials on plugin creation: Getting Started, Creating a Plugin Project. Our plugin project is located in a Bitbucket repository at https://bitbucket.org/klausnguets/apcocoa_plugin/src/master/
The plugin implementation has 3 packages: com.cocoaplugin.ide, com.cocoaplugin.psi, com.cocoaplugin.run.
In this package you will find the logic about the CoCoA Parser for syntax highlighting, and all other logic related to the CoCoA language itself. For more information on this topic please refer to the IntelliJ Platform SDK DevGuide.
This package contains the logic to create a run configuration for CoCoA. It is not very important for the plugin to work but with a run configuration someone can send a CoCoA file to the interpreter without using the interactive windows or the CoCoA window. IMPORTANT: if you are building the plugin for windows or another OS please make sure the INTERPRETER_PATH in the class CocoaRunConfigurationProducer of this package is correct for that OS.
This package is the most important package of the project as here you have the logic for the interactive Window, the events “send to Cocoa”, “refresh cocoa” , as well as the multithreading used to separate the interpreter threads from the IDE thread in order to avoid blocking everything when cocoa is calculating. Let’s choose some important classes in this package and give a brief description of them:
This class is the class where we manage the cocoa interpreter process running in the background. Again make sure the right interpreter path for the targeted OS is given(line 32).
This class represents the thread which reads the results produced by CoCoA. It listens to the standard output of the CoCoA interpreter process and whenever there is a result available, it prints it back to the user in the CoCoA output window.
This class is an IntelliJ Action When the user starts the action “send to cocoa” we get the text selection and write it to the input of the cocoa interpreter process, and later the result will be read by the InterpreterThread as explained above.
This is the cocoa interactive window. It interacsts with the two other classes TerminalFilter and TerminalNavigationFilter.
This class is the window for the CoCoA Outputs. For more about IntelliJ ToolWindows, please refer again to the IntelliJ Platform SDK DevGuide
ApCoCoA can be distributed using the files generated during the building process. But the plugin also has to be integrated in the final distribution file. When ApCoCoA starts, we always check whether the user has a CoCoA interpreter in his or her system already. Otherwise we copy the CoCoA interpreter to the users home directory. This functionality is implemented in the files start.sh for Unix and start.bat for Windows.
You can create the final ApCoCoA by following the steps below. We assume that you built the IDE and that it is now in the folder dist.
- Clone the plugin project from the repository and open it in IntelliJ
- Choose the IntelliJ Platform SDK as SDK for the project. To do this follow the instructions described here: Setting Up a Development Environment
- Then you can build the plugin using the menu option “Build > Prepare module apcocoa_plugin for Deployment”.
- A jar file apcocoa_plugin.jar will be generated in the project directory. Move that plugin file to the folder dist/plugins/apcocoa/lib/
- copy the file start.sh for Unix or the file start.bat for Windows into the folder dist/bin/
- After making the start script executable you should then be able to run ApCoCoA
- Currently the file template and run configuration for CoCoA have to be added manually. To make these changes permanent you need to change the file bin/idea.properties (just copy it from a previous ApCoCoA version)