Transition to Wolfram Workbench
Hannes Kessler
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
John Fultz
* File->Save As...
* Choose "Mathematica Package" under the file type
* Save as any .m file...but not using the same name as your .nb file (because
your .nb file is already writing a companion package, and so will keep
destroying and recreating the like-named package every time you save your
notebook).
You'll now end up with a package file which has some interesting properties.
* If you open it in Mathematica, it looks much like a notebook, even preserving
the cell structure and most of the properties of the notebook.
* If you open it in Workbench (or any text editor), it will be completely
readable, and all of that work you put into commenting your code in Text cells
will *still* be there in clearly readable comments.
* If you decide to make changes in Workbench (or any text editor), it will be
pretty clear how to do so without destroying any structure that would allow you
to reopen the package in the Mathematica front end and continue to see the same
structure.
When we designed the package editor in Mathematica (i.e., the mode you're put in
when you open a .m file), one of the chief goals was to have it stream out to a
file which is completely readable in any text editor, and which can be
co-developed using any combination of Mathematica, Workbench, and text editor.
By following this procedure, you'll be making absolutely no irreversible
commitment to Workbench, and this will allow you to transition as quickly or
slowly (or not at all) as you wish.
Incidentally, something else which you might wish to know...Mathematica has an
alternate evaluatable cell style known as "Code" (Alt+8 or Cmd+8). Code is like
Input, but with the following differences...
* Much less automatic formatting (e.g., auto-indent, auto-line-wrap)
* InitializationCell->True is set by default
* Differing background color so you can easily distinguish from Input cells
This can be a much easier and more visible way of tagging package code than
using the Initialization Cell menu item, and it's the style which is used by the
package editor for package code by default.
Sincerely,
John Fultz
jfu...@wolfram.com
User Interface Group
Wolfram Research, Inc.
Albert Retey
all this is possible, there is an import wizard that will import
notebooks and create package files from them but you can just as well
copy the notebook files to the project directory of a new project and
keep editing the notebook and create the package file automatically.
This approach might need some more work to get the configuration right
but you will need to learn only those features of the workbench that you
want to use. I would recommend to create a dummy application project to
see how the directory structure and configuration files need to be set
up for the workbench utilities to work alright. You could also crate a
new application project an then just replace the templates that are
generated with your already existing files, if these meet the suggested
conventions...
If you are only writing pure mathematica package files, the added value
of the workbench is IMHO limited, it really can help you to save a lot
of work only if you either plan to provide documentation that you want
to integrate into the Documentation Center or if you want to combine
mathematica code with java, webMathematica and/or probably
GridMathematica (which I have no experience with). It also is nice when
you are using or plan to use additional tools like a version control
system or a ticket/task repository which all can be integrated with
appropriate eclipse plugins.
Files will always be stored in the "workspace", a special directory that
contains your project directories but the workbench takes care that
$Path is set so that you can load the package you are developing. You
can configure the workspace to be at any location you want to. The
workbench has an application tool view which lets you export your
application/package with a mouseclick to e.g. the user base directory so
you can test it without the workbench environment.
> Are there tutorials deeling with this problem?
there is documentation for the workbench and it also deals with the
import of existing projects. Some of the material is not really
exhaustive though. If you consider to work with the workbench, I would
recommend to also take a few hours to get familiar with eclipse.
hth,
albert
Adam Berry
> 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 ... ?
>
>
> 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;
for ideas on how to structure the project.
Adam Berry
Wolfram Workbench Development Team
Wolfram Research, Inc
E. Martin-Serrano
Please,
May I ask which version of Workbench do these directions apply to?
E. Martin-Serrano
Sincerely,
dr DanW
I have been trying to figure out how to preserve expository and
sectioning cells in package files for years. I never realized that
Save As > Mathematica Package (*.m) saved in a special format that was
different from the AutoSaved package files of initialization cells. I
was annoyed that I would loose all my text format comments and had to
keep all comments that I wanted to appear in a package file in (* *)
brackets. These, then, would disappear anytime I reformatted the cell
(Convert To > StandardForm), which I do every so often to make them
pretty.
Thanks for the tip. I have flagged your posting with 5 stars to mark
it as an important and useful tip.
Daniel
Adam Griffith
http://www.wolfram.com/products/workbench/ is a great resource for
learning about everything you're mentioning. Also, if you enjoy
developing in a notebook environment, take a look in the front end at
File > New > Package (opens the fantastic front end package editor which
provides the means to easily write a .m file in a notebook environment).
Cheers,
-Adam
Hannes Kessler
under a different name and re-opening it in Mathematica. I'll probably
look now more on .m files in Mathematica during package development
and debugging. But when I re-opened the created .m file in the
Workbench I got an error "Could not open the editor. An unexpected
exception was thrown." followed by
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
332)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:
113)
at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
194)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
110)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:
79)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
368)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
I don't know what to do with it.
Best regards,
Hannes Kessler
Hannes Kessler
I tried to create some test documentation using the workbench but
failed to use the documentation tools palette when Mathematica was
called because some of its elements were hidden and I could not
increase the size of the palette window. In the workbench I had
problems using the help system as the font size is really tiny, but no
possibility to change it. I am afraid such elementary difficulties
will discourage newcomers like me to use the workbench.
Best regards,
Hannes
David Park
Browser and there it is possible to adjust the magnification in the right
hand pane where the descriptive material is contained. The left hand pane
(TOC) does not seem to adjust but is fairly good size (and I'm also one to
complain about non-adjustable small font sizes.)
On my system the DocuTool palette fills the vertical height of the screen
and there is enough room for all the buttons on the palette. But I think
they should really make it adjustable height with scrolling.
David Park
djm...@comcast.net
http://home.comcast.net/~djmpark/
From: Hannes Kessler [mailto:Hannes...@hushmail.com]
Hello Albert,
I tried to create some test documentation using the workbench but
failed to use the documentation tools palette when Mathematica was
called because some of its elements were hidden and I could not
increase the size of the palette window. In the workbench I had
problems using the help system as the font size is really tiny, but no
possibility to change it. I am afraid such elementary difficulties
will discourage newcomers like me to use the workbench.
Best regards,
Hannes
On 25 Feb., 07:54, Albert Retey <a...@gmx-topmail.de> wrote:
David Park
activate scrolling if it is too long for the screen. (But I don't know if
this works because it is never too long for the screen on my PC.)
From: Hannes Kessler [mailto:Hannes...@hushmail.com]
Hello Albert,
I tried to create some test documentation using the workbench but
failed to use the documentation tools palette when Mathematica was
called because some of its elements were hidden and I could not
increase the size of the palette window. In the workbench I had
problems using the help system as the font size is really tiny, but no
possibility to change it. I am afraid such elementary difficulties
will discourage newcomers like me to use the workbench.
Best regards,
Hannes
On 25 Feb., 07:54, Albert Retey <a...@gmx-topmail.de> wrote:
John Fultz
they won't get changed by another program and leave things in an uncertain
state). It's entirely possible that Workbench wants a sole lock on files and
won't play nicely with a file that's locked by another app. Regardless of
whether that's the case or not, though, I wouldn't advise having the file open
in both Workbench and Mathematica simultaneously.
If that's not the issue, it's difficult for me to say. Workbench isn't my area,
and the package is a standard package in every regard (on top of being a simple,
plain text file). I'd suggest submitting it to tech support as a possible bug
in Workbench if you continue to have problems.
Sincerely,
John Fultz
jfu...@wolfram.com
User Interface Group
Wolfram Research, Inc.
On Thu, 25 Feb 2010 17:37:09 -0500 (EST), Hannes Kessler wrote:
> What you said works for saving a Mathematica notebook as a package
> under a different name and re-opening it in Mathematica. I'll probably
> look now more on .m files in Mathematica during package development
> and debugging. But when I re-opened the created .m file in the
> Workbench I got an error "Could not open the editor. An unexpected
> exception was thrown." followed by
>
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
> 3880)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
> 2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
> 332)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
> 493)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
> 149)
> at
>=
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication..
> java:
> 113)
> at
>=
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
> 194)
> at
>=
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
> EclipseAppLauncher.java:
> 110)
> at
>=
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAp
> pLauncher.java:
> 79)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
> 368)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
> 179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>=
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
> at
>=
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
l
>>> 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
Albert Retey
> I tried to create some test documentation using the workbench but
> failed to use the documentation tools palette when Mathematica was
> called because some of its elements were hidden and I could not
> increase the size of the palette window. In the workbench I had
> problems using the help system as the font size is really tiny, but no
> possibility to change it.
it sounds like you are using either a non standard setup, since all
looks very reasonable on the systems I have been using. One thing you
can try is to configure the eclipse help system to use an external web
browser, you have then all the possibilities to change the appearance of
the help content within the web browser of your choice. As for the
documentation tools palette you could try to manipulate the
corresponding notebooks magnification to make everything fit within the
window with something like:
SetOptions[Notebooks[][[1]], Magnification -> 1]
where of course you would have to check at which position the
DocumentationTools-Palette appears in your case...
> I am afraid such elementary difficulties
> will discourage newcomers like me to use the workbench.
I am not trying to convince anyone to use the workbench, as I said, IMHO
it only adds value for certain special tasks and it needs some effort to
get used to it _and_ it might well have its deficiencies. Unfortunatly
at this time there isn't really an alternative to it when you want to
create documentation for the Documentation Center, although there are
some recipes about how you can create documentation for the
documentation center without using the workbench and wolframs
documentation tools. But these also have their deficiencies and also
need some effort to get decent results.
hth,
albert
Hannes Kessler
I tried to change the help system to internet explorer (Window-
>Preferences->General->Webbrowser->Use external Web browsers->Internet
explorer) but nothing changed: All help pages still open in the
internal browser window with a tiny font. I am working under Windows
7.
Best regards,
Hannes Kessler
Albert Retey
> I tried to change the help system to internet explorer (Window-
>> Preferences->General->Webbrowser->Use external Web browsers->Internet
> explorer) but nothing changed: All help pages still open in the
> internal browser window with a tiny font. I am working under Windows
> 7.
Sorry, I have no experience with neither Windows 7 nor Internet
Explorer. On my Windows XP box when I choose "Use External Browser" and
then check "Default System Browser" the help will be opened with
Firefox, which is my "Default System Browser". There I can increase the
zoom factor with the usual menu entry or Ctrl-+. Have you tried to just
check the "Default System Browser" entry?
hth,
albert
Albert Retey
> I tried to change the help system to internet explorer (Window-
>> Preferences->General->Webbrowser->Use external Web browsers->Internet
> explorer) but nothing changed: All help pages still open in the
> internal browser window with a tiny font. I am working under Windows
> 7.
Sorry, I have no experience with neither Windows 7 nor Internet
Hannes Kessler
yes, I tried both and my default browser is also Firefox. Neither one works.
Thanks anyways,
Best regards,
Hannes
Albert Retey
> yes, I tried both and my default browser is also Firefox. Neither one
> works.
I just realized that there is an extra setting for the help system, in Preferences -> Help -> "Open Help Contents" you can choose to open help in an external browser. The other setting seems to affect other uses of the web browser only. Sorry for the confusion... I think when eclipse is running you could even try to just access the help system by pointing an external web browser to your localhost, something like: http://127.0.0.1:1229/help/index.jsp
hth,
albert
AES
Albert Retey <aw...@gmx-topmail.de> wrote:
> I just realized that there is an extra setting for the help system, in
> Preferences -> Help -> "Open Help Contents" you can choose to open help in an
> external browser.
Are you talking about something in Mathematica Preferences here, or in
the Mac OS Help System or some other OS?
I don't find anything that looks like "Preferences -> Help -> "Open Help
Contents"" in the Mathematica Preferences for the Mac version of 7.0.
David Park
From: AES [mailto:sie...@stanford.edu]
In article <hmj219$ead$1...@smc.vnet.net>,
Albert Retey <aw...@gmx-topmail.de> wrote:
> I just realized that there is an extra setting for the help system, in
> Preferences -> Help -> "Open Help Contents" you can choose to open help in
an
> external browser.
Are you talking about something in Mathematica Preferences here, or in
Adam Berry
> What you said works for saving a Mathematica notebook as a package
> under a different name and re-opening it in Mathematica. I'll probably
> look now more on .m files in Mathematica during package development
> and debugging. But when I re-opened the created .m file in the
> Workbench I got an error "Could not open the editor. An unexpected
> exception was thrown." followed by
>
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
> 3880)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:
> 2405)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:
> 332)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:
> 493)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
> 149)
> at
> 113)
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:
> 194)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:
> 110)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
> 368)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
> 179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> 39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>
> I don't know what to do with it.
>
> Hannes Kessler
>
>
could you detail how you attempted to open this .m file in the
Workbench. If you also send me the .m I can step you through
transitioning and starting to work in the workbench.
Thanks,
Albert Retey
>> I just realized that there is an extra setting for the help system, in
>> Preferences -> Help -> "Open Help Contents" you can choose to open help in an
>> external browser.
>
> Are you talking about something in Mathematica Preferences here, or in
> the Mac OS Help System or some other OS?
this thread is named Transistion to Wolfram Workbench, so I thought it
was clear we are talking about Wolfram Workbench and of course it is the
preferences of the workbench that I was talking about...
hth,
albert
David Bailey
> If take your notebook and you do...
>
> * File->Save As...
> * Choose "Mathematica Package" under the file type
> * Save as any .m file...but not using the same name as your .nb file (because
Back at version 6, I started developing code in .m files using the
FrontEnd - just as John describes. The editing experience is so good, I
never made the next step to using the Workbench! The FrontEnd has some
nice features over the Workbench:
1) All the extra Mathematica characters render correctly, rather than
as say /[Breve].
2) You can evaluate the contents of the .m file directly, and any
output appears as if you were working in an ordinary notebook, except
that it is not stored when you save the file - which I find ideal. Of
course, that doesn't stop you pasting such output into a notebook if you
need to save it.
3) The format of the .m file is extremely simple, as John has said,
and the formatting information is hidden in Mathematica comments, so the
..m file is directly readable with Get[], so it is easy to write
utilities, such as a layout utility, that read the .m file as pure text.
If only Wolfram would support colours - (* ::Color[1,0,0]:: *), (* ::
EndColor:: *) I'd say feel this scheme was perfect - indeed, I don't see
why it would not be possible to allow colour in code/input cells.
David Bailey
http://www.dbaileyconsultancy.co.uk
David Bailey
>
>
> If you are only writing pure mathematica package files, the added value
> of the workbench is IMHO limited, it really can help you to save a lot
> of work only if you either plan to provide documentation that you want
I have figured out and documented an easy way to integrate documentation
into the DC without the use of the workbench. See my website for details.
David Bailey
http://www.dbaileyconsultancy.co.uk
AES
Albert Retey <aw...@gmx-topmail.de> wrote:
Yes, it does, thanks.
To pursue the inquiry a bit further, Workbench seems to be called an
"environment" -- a term that may have varied meanings.
Would it also be properly called an "app"?
As an operational question, if you Open Workbench on a Mac, does
"Workbench" appear just the right of the Apple Menu in the menu bar?
Albert Retey
>
> To pursue the inquiry a bit further, Workbench seems to be called an
> "environment" -- a term that may have varied meanings.
>
> Would it also be properly called an "app"?
Eclipse is a regular "application" and the application type is IDE, that
is "Integrated Development Environment", a class of applications that
traditionally integrate stuff like compilers, build tools, debuggers,
version control and some more in one application.
The Wolfram Workbench is a plugin for eclipse which adds support for the
programming language Mathematica to eclipse, that is an editor that
knows Mathematica syntax, a debugger, a profiler and some other tools
that help with standard tasks that a Mathematica programmer will be
faced when writing a Mathematica package or application. If you are
interested, learn more about eclipse at www.eclipse.org
> As an operational question, if you Open Workbench on a Mac, does
> "Workbench" appear just the right of the Apple Menu in the menu bar?
I don't have a Mac handy, and never used neither Wolfram Workbench nor
Eclipse on a Mac, so I simply don't know, I'm also not sure which menu
bar you are referring to...
hth,
albert
Albert Retey
>> If you are only writing pure mathematica package files, the added value
>> of the workbench is IMHO limited, it really can help you to save a lot
>> of work only if you either plan to provide documentation that you want
>> to integrate into the Documentation Center ......
>
> I have figured out and documented an easy way to integrate documentation
> into the DC without the use of the workbench. See my website for details.
I know that and also the documentation of David Reiss, which adds some
other tricks to the ones in your documentation. Both are appreciated and
very helpful and good enough to integrate documentation into the
Documentation Center. But they both assume rather good familiarity with
Mathematica (which the workbench actually does, too) and there are some
additional benefits that only the workbench/documentation tools provide:
e.g. the stylesheets for documentation source notebooks, the toolbars to
edit documentation notebooks and the automatic links that the workbench
inserts when "building" the documentation. So if you are using the
workbench anyway, the tools it provides for creating documentation are a
big help, on the other hand it is not absolutely necessary to use the
workbench to get your documentation done, thanks to your and the other
Davids documentations, which actually one have only the one drawback of
being not "official" and thus might need adaption with a future version...
regards,
albert
hth,
albert
George Woodrow III
On Mar 7, 2010, at 4:01 AM, AES wrote:
> As an operational question, if you Open Workbench on a Mac, does
> "Workbench" appear just the right of the Apple Menu in the menu bar?
>
Yes, on OS X, Workbench is an app, just like any other. In earlier versions (and some betas of version 2), yu would get two icons in the dock, which indicated that there were actually two processes. The activity monitor currently shows just one process, so that issue has been fixed (probably related to the cross platform nature of Eclipse -- I get this behavior with apps using Wine.)
It is shown as a 32 bit Intel (only) application.
george
> In article <hmqiun$sg6$1...@smc.vnet.net>,
> Albert Retey <aw...@gmx-topmail.de> wrote:
>
>> Hi,
>>
>>>> I just realized that there is an extra setting for the help system, in
>>>> Preferences -> Help -> "Open Help Contents" you can choose to open help in
>>>> an
>>>> external browser.
>>>
>>> Are you talking about something in Mathematica Preferences here, or in
>>> the Mac OS Help System or some other OS?
>>
>> this thread is named Transistion to Wolfram Workbench, so I thought it
>> was clear we are talking about Wolfram Workbench and of course it is the
>> preferences of the workbench that I was talking about...
>>
>> hth,
>
> Yes, it does, thanks.
>
> To pursue the inquiry a bit further, Workbench seems to be called an
> "environment" -- a term that may have varied meanings.
>
> Would it also be properly called an "app"?
>
Chuck
illustrated in the video linked in the Welcome section.
I choose open New Project. The wizard pops up. I choose Basic
Project in the Mathematica list.
The wizard freezes. Nothing else happens.
I have also cannot open an existing package and get a long list of
error messages, similar to those submitted earlier by another poster
to this thread.
I am running this on Linux 9.10 and Workbench 2.0.
Chuck
Adam Berry
Eclipse/SWT and the version of GTK used in Ubuntu 9.10, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=299896 for details and a
workaround.
In Workbench 2.0, code files must exist inside a project for them to be
opened with Mathematica code editor, so first create a project, copy the
files into it, and then you can start working with it.
David Park
If you use New/ Project/ it defaults to Mathematica/Application Project.
That would be the normal choice and it works. When I chose Basic Project
instead, the wizard did not freeze, although I canceled before actually
creating the project.
Go to Window/Preferences Mathematica and make certain the Preconfigured box
is checked.
Go to Paclet Development and make certain the two boxes are checked.
Maybe there is a problem with Workbench on Linux?
Patrick Scheibe
if I choose "Basic Project" I have to click "Next".
When exactly freezes the WB? When you click on the "Basic Project" icon
or when you click next?
Have you tried to start the WB from the commandline to see
whether there's an exception when you click?
Cheers
Patrick
Chuck Cannon
by clicking on the icon on the panel and now it seems to work. I
changed nothing.
Maybe I was just doing something stupid.
Okay, I'll play with it more.
Thanks,
Chuck