I would like to see the Mac version of MATLAB not requiring X11, but
still being able to work as a headless Unix tool as an option
(especially for very long computations, distributed computing, etc.).
I would like to see the Mac version of MATLAB defaulting to the user's
~/Documents folder, with some way for me to customize this path when
opening MATLAB from the Finder. But more to the point, I would like to
not care about specifying the current directory any more.
I would like to be able to specify a MATLAB command to run from the Finder.
I would like to see the Mac version of MATLAB being able to open on its
own, and open all of its MATLAB file types, more than just what it does
today (where it can now open files if MATLAB is already running, yay).
I would like to see a single icon for MATLAB that I can click on to run,
not a pile of directories and a "launcher" application.
I would like a true 64-bit version of MATLAB that makes the most
advantage of multi-core Intel processors on all of the latest Macs.
I would like to have high-resolution graphics in MATLAB on the Mac that
compare well with Quartz. I would like to have QuickTime support
(Animation, if nothing else) for image processing and rendering. I
would like for AppleScript OSA to be supported as part of the language,
just like COM is for Windows.
I would like Mac keyboard shortcuts that work, and are consistent.
I would like Simulink Toolbars on the Mac.
I would like a cleaner, tighter, more consistent interface across the
MathWorks product line.
I want these things not only on the Mac, but on all of the platforms
MATLAB can run on. I want equality for the interfaces MATLAB presents
on each platform, and I also want MATLAB to do the right
platform-specific things, such as keyboard shortcuts, file dialogs or
printing, where it makes sense.
There's more, and it doesn't sound like a rant to me.
I don't think I'm the only one who feels like this.
I'm a Mac Developer at the MathWorks (one small voice). Some of this is
very optimistic thinking on my part. And we need much more than
(internal) Mac developers to do these things well.
We were unable to make much progress in the next release due to the time
we needed to port our 80+ products to Intel Mac, which are now in their
first public beta, and so you won't see forward motion on these and
other important matters until after the next release, after our Intel
support is nailed down. Sorry about the rate of progress, but...
Please speak your mind,
Nick Forge wrote: