Frequently Asked Questions


What is Maple IDE?

No matter if you want to create a small Maple application or you want to build large software system in Maple. With Maple IDE you can create your application in a snap. Also if you already have existing Maple packages, you can use Maple IDE to continue developing your application using the most professional and convenient Maple programming tools.

Who Uses Maple IDE?

Maple IDE can be used to develop Maple applications/packages for many different industries and is suitable for all levels of programming expirience.

Can I using Maple IDE without Maple?

Yes, you can. Without Maple, you still can use Maple Editor, create Maple projects etc. But you cannot build or launch your application inside the Maple IDE.

What Maple versions supported by Maple IDE?

Maple IDE supports all versions from Maple 12 and higher.


When should I use source folders within a Maple project?

Each Maple project locates its Maple source files via one or more source type entries on the project's build path. Use source folders to organize the files of a large project into useful grouping, or to keep source code separate from other files in the same project.

Can I use .lib Maple archive working with Maple IDE?

No. lib archive is old Maple library format and not supported by Maple IDE.
Maple IDE supports .mla Maple archives only.

What should I do if I encounter a Parsing Error in Maple Editor?

As suggested by the message, this is error is caused by a parsing problem. It has nothing to do with licensing. Your Eclipse ".log" file (found in your workspace /.metadata directory) should provide a hint as to the cause of the parsing error. Send the log file as well as a test case to support (ideally the window you are trying to edit). Including a test case that will help us reproduce the problem is very important. The faster we can reproduce the problem, the faster we can get you a fix. If we can't reproduce a problem, there is little we can do to help you.

Ideally, the test case you send should be the same window you were editing when the problem occurred (along with any supporting files needed to compile it). If that is not possible (possibly because you aren't allowed to send any code to a 3rd party), then you should try to create a new, standalone test case that illustrates the same problem. The best approach is to create a standalone test case by removing all of the code that isn't relevant to the problem at hand (e.g., keep deleting code until the problem goes away and then restore that last code that was last deleted).

Parsing problems can also be a side effect of the other problems described in the earlier FAQ entry here so check each of the suggestions there. Refreshing and rebuilding your project using the Project > Clean command can often help as can cleaning your Eclipse "configuration" directory.