The DigiArea team is pleased to announce the first release of the Closure IDE - Eclipse toolkit for Google Closure Tools.
The IDE includes powerful tools to edit and compile Soy Templates, work with Closure Compiler and Closure Stylesheets, manage web projects which use Google Closure Tools.
You can read more about the tool here:
http://digi-area.com/ClosureIDE/
For those of you who have been waiting to try the Maple IDE, today’s your lucky day. Updated Maple IDE became available for purchase through the DigiArea website, and you can now download a 30-day free trial of the tool just to play around with the amazing features for Maple programming.
It’s now available for download at the Maple IDE Licenses page!
Today we released Maple IDE update version for Eclipse, Unix, Mac and Windows users, resolving the following bugs:
To get the update, from within Maple IDE choose Help > Check for Updates, causing the Update Manager to launch. Select Maple IDE and choose Update.
The integration of Maple projects with other Eclipse projects is designed for seamless development and building processes of your C, Fortran, or Java code for Maple using External Calling package.
Maple Project can be mixed with Eclipse JDT - Java Project, Eclipse CDT - C/C++ Project and Eclipse PTP - Fortran Project. In the tutorial we use Maple with Java language.
In this tutorial we develop a Java/Maple project consisting of:
public static double circleArea(double radius) {
return Math.PI * Math.pow(radius, 2);
}
public static double rectangleArea(double a, double b) {
return a * b;
}}
From the project's pop-up menu (right-click), select Maple > Add Maple Nature.
The project becomes a dual Maple Project (Maple/Java) with the default Libname/Build Path.
export circleArea, rectangleArea;
description "Maple External Call - Java - Geometry Module";
circleArea := define_external('circleArea', CLASS = "mapleide.extcall.java.GeometryUtil", CLASSPATH = "D:/workspaces/runtime-EclipseApplication/mapleide.extcall.java/bin", JAVA, radius::float[8], RETURN::float[8]);
rectangleArea := define_external('rectangleArea ', CLASS = "mapleide.extcall.java.GeometryUtil", CLASSPATH = "D:/workspaces/runtime-EclipseApplication/mapleide.extcall.java/bin", JAVA, a::float[8], b::float[8], RETURN::float[8]);end module;
Do not forget to replace CLASSPATH value with the actual output folder path of your Java project where compiled Java classes are located (by default is bin folder of your project).
From a project's pop-up menu (right-click), select Run as > Maple.
Maple runs in the Eclipse console and we can use our Java methods as normal Maple procedures defined in the module.
For the next update for the Maple IDE, we plan to add three export wizards for Java, C and Fortran projects. The wizards automatically generate a Maple module with external calling commands based on the selected Java class, C or Fortran shared library.
java.lang.UnsupportedClassVersionError: ... : Unsupported major.minor version 51.0
The error means you compiled the Java class with a newer version of Java and are trying to run with an older version, such as compiling with Java 7 but trying to run in Java 5 environment. Currently Maple uses Java 5 environment.
To fix the error, do the following:
java.lang.ClassNotFoundException: GeometryUtils
The error means the Java class cannot be found because of an incorrect name or a wrong path in the command.
To fix the error, check CLASS and CLASSPATH options of the define_external command.
The Maple IDE project team is pleased to announce the release of the standalone version of the Maple programming toolkit. Now Maple IDE is available for Windows, Unix and Mac OS as standalone tool.
For the information about new versions, please see Maple IDE page.
For the complete installation instructions see the following video:
Open Maple element (e.g.: a module, an procedure) without clicking through "infinite" list of source folders with Maple symbols and time-wasting manual search: Ctrl + Shift + F3. If you are looking for Maple elements such as modules, procedures, variables etc. which defined in your workspace, this shortcut will do it for you.
Go to a type declaration: F3. Alternatively, you can hold Ctrl down and click the hyperlinked variable or module.
Go directly to an element (module, variable) of a huge Maple file: Ctrl + O. Use Ctrl + O to get live list of matched elements and press Enter when you have finished.
Go to closing brace: Ctrl + Shift + P. If you have a big module or procedure, use this shortcut which brings you right to the end of the element (closing brace).
Find references: Ctrl + Shift + G. This shortcut helps you find all references of the selected Maple element in the workspace.
Go to a line in the Maple file: Ctrl + L. Enter line number and click Ok to go to the selected line.
We are proud to announce you about the new feature in the Maple IDE - Importing existing MPL files into a Maple Project.
You can update Maple IDE using Update Manager mechanism in the Eclipse.
The following article briefly introduces the migrating process using the new import wizard, and then provides the video for users who are considering to use MPE for theirs existing Maple applications.
Maple files with code can be very huge. Some Maple modules have more then 10000 lines of code. For instance, RegularChains module from RegularChains.mla library has more then 450 lines for locals and exports definitions only (without the module body). The standard solution for such a situation is the Maple preprocessor. The preprocessor implements some subset of the C preprocessor's capabilities such as include, define, ifdef and so on. A Maple programmer can split a module code into parts and use include directive to "compile" the pieces together.
It was hard decision for us to not support the preprocessor directives. On the one hand, we understand that Maple programmers has a lot of code with preprocessor directives, but on the other hand, we also understand that to go to the future we need to reject supporting such old technology as preprocessor directives.
We made the decision not to support the preprocessor directives but make an importing tool to import from *.mpl files to *.maple files.
MPL import wizard provides fast and super easy way to translate your existing MPL files into a Maple Project.
The main concepts of the MPL import wizard are:
Explore the following video to know how to import existing .mpl files:
The wizard was tested on a bunch of huge modules, and I can say that modules with up to 2500 lines of code can be imported and used without any problems. But what if you want to import more lines of code? Do we need to use preprocessor directives in that case? The answer is no! You still can import your code to *.maple files but the resulting files will be too huge to work with the code effectively in the editor.
It is obvious that we need some sort of further refactoring in general case of an importing. The main idea is do not do such a refactoring by hands, but use special wizard for that.
