|
|
||||||||||||
|
Welcome to Digitool!Digitool is the maker of Macintosh Common Lisp (MCL) and CLIM: tools for developing intelligent applications on the Macintosh platform. What's New?May 2005MCL 5.1 is shipping. The latest version of MacOSX native MCL (MCL 5.1) is available for purchase. See here for purchasing details and here for the release notes. May 20045/24/04: The new info-mcl mailing list is now up again. 5/23/04: We have switched hosting services and the web site and company email addresses are back online. We are in the process of migrating the info-mcl mailing list and it should be running again soon. June 2003The release version of MacOSX native MCL (MCL 5.0) is available for purchase. See here for the details and here for the release notes. Customers who purchased the beta version automatically receive the release version. February 2003The MCL Software Directory is now available. combines growing number of MCL contributions, commercial applications, and demos. Also includes a directory of MCL/Lisp consultants. If you wish to be participate, check here. November 2002The beta version of MacOSX native MCL (MCL 5.0) is available for purchase. Beta customers will automatically receive the release version which is expected to ship in January 2003. See here for the details, here for the release notes, and here for patches. October 2002Digitool ships MCL 4.3.5, a CarbonLib based version that is intended to allow users to begin migrating their code to Carbon and ultimately native Mac OS X compatibility. Though MCL 4.3.5 is not the Mac OS X native version (it will run in Mac OS Classic compatibility mode), it includes many of the improvements added in the course of working on the native Mac OSX port. MCL 4.3.5 is available for electronic download to: April 2002MCL 4.3.1 is available for only $95! The MCL subscription has been discontinued and the single license price has been reduced from $375 to $95! Check here for how to purchase. Technical support is available direct from Digitool engineers on either a per-incident or annual support basis. March 2002MCL 4.4 (Mac OS X native) is still undergoing development and testing. We are working with Apple engineers on getting it to work with recent releases of the operating system. August 2001MCL 4.3.1 has now shipped; if you are expecting it and have not yet received it, please contact Jennifer. Please check the patches README page for information on post-release patches you may want to install. Please note: The "ReadMe" file on the MCL 4.3.1 CD is an out of date version; the correct one is "MCL 4.3.1 Release Notes" in the "MCL 4.3.1" folder. July 2001MCL 4.4 (Mac OSX native) is now in preliminary testing. March 2001MCL 4.3.1 is currently undergoing beta-testing. MCL 4.3.1 runs under Mac OS X in "classic" mode. A Carbon-ized version of MCL intended to run in native mode is still under development. January 2000MCL 4.3/3.4 is now available. We've made changes and additions for ANSI Common Lisp compatibility. Read-sequence and write-sequence have very efficient implementations for many combinations of sequence and stream. Navigation Services are supported. The MCL color functionality for dialog items has been preserved in the presence of the Appearance Manager and Themes. New compiler optimizations increase speed and reduce consing. The online help file contains documentation for many additional functions including the process API. The release includes many more enhancements and numerous bug fixes. Please see the release notes for details. Current subscribers and licensees should receive the new release soon. If you're a new customer, please see the ordering information page. Thanks for your interest in MCL. Also...CLIM 2 is here for MCL. CLIM, the Common Lisp Interface Manager, is a cross-platform windowing system based upon Common Lisp and CLOS. All of the major Lisp vendors have either released their own CLIM implementation, or are planning to soon. Common Lisp has always been a smart choice for delivering complex systems that need portability across platforms. Now you'll be able to develop your GUI in the same familiar environment as the rest of your code.
|
|||||||||||
|
||||||||||||