A number of MaplePrimers have asked how one might use the section and subsections of a Maple worksheet to structure the source code of an extended Maple package. The usual answer is that it cannot be done; a module-based Maple package must be assigned in a single input region in a worksheet. A recommended alternative is to write the source in text files and use either command line tools or the Maple read command from a worksheet to assign the package. Because the read command handles Maple preprocessor macros, specifically the $include macro, the source can be conveniently split into smaller files.
I prefer this file-based method for development because text files are generally more robust than Maple worksheets, can be edited with the user's preferred editor, can be put under version control, and can be searched and modified by standard Unix-based tools. However, not everyone is familiar with this method of development. With that in mind, I wrote a small Maple package, CodeBuilder, that permits splitting the source of a Maple package (or any Maple code) into separate code edit regions in a standard Maple worksheet, using $include macros to include the source of other regions. To build the package, the code edit regions are written to external files, using the names of the regions as the local file name relative to a temporary directory.
The package includes a method to run mint on the source code. The result can be either printed in the worksheet or displayed in a pop-up maplet that allows selecting the infolevel and the region to check.
CodeBuilder includes help pages and a simple example (referenced from the top-level help page) demonstrating the usage. To install the package, unzip the attached zip file and follow the directions in the README file.
Errata Just noticed that a last minute change broke some of the code. Do not bother with the 1-0-1 version; I'll upload a new version shortly. The new version (1-0-2) is now available.