Re: Transition to Wolfram Workbench
- To: mathgroup at smc.vnet.net
- Subject: [mg107724] Re: [mg107707] Transition to Wolfram Workbench
- From: Adam Berry <adamb at wolfram.com>
- Date: Thu, 25 Feb 2010 01:49:32 -0500 (EST)
- References: <201002241118.GAA22676@smc.vnet.net>
On 2/24/10 5:18 AM, Hannes Kessler wrote: > Hello, > > could you give some recommendations for a smooth transition to the > workbench for packages developed in a standard mathematica notebook > environment? Starting a completely new project in the workbench is > one thing, but at least as important is the question how to continue > to work on existing packages created previously by other means. Up to > now I wrote code in input cells of a mathematica notebook, added > explanations in text cells, marked the input cells with package code > as initialization cells to create the .m file automatically upon > saving the notebook. I never looked into the .m files themselves. > Should one / could one import the notebook (or the .m file) to a > workbench project, or copy it to a work space directory, or work > directly on the files in the user base directory, or what else ... ? > > Are there tutorials deeling with this problem? > > Best regards, > Hannes Kessler > > > Hello, the best approach is to create a project in the workbench, and then copy the .m package file into that project. Once you have done that you will edit the file using the workbench, and will no longer need the notebook with its generated .m file. See; http://reference.wolfram.com/workbench/topic/com.wolfram.eclipse.help/html/tasks/applications/mathematicaapps.html for ideas on how to structure the project. Adam Berry Wolfram Workbench Development Team Wolfram Research, Inc
- References:
- Transition to Wolfram Workbench
- From: Hannes Kessler <HannesKessler@hushmail.com>
- Transition to Wolfram Workbench