Nedialko

I find this a very limited tool;
it is by far not robust and the 'documentation'
is not around the right priorities.

Admittedly, it's a tough job to translate between
Matlab = an array programming language with zillions of readily available 'library' functions

to

Fortran = a strong typed language, whose even later flavours may still be a bit 'deficient' as to handling
and declaring arrays; not to mention that one needs the Diogenes lantern to look around for
zillions of libraries, scattered around the Net (i.e NOT readily available !), that barely implement
a subset of Matlab's 'core' vector-matrix math

As said, I find the approach taken by matlab2fmex as utmostly unappealing in its:

* all-or-nothing approach: you won't get a single .F90 line out unless you:
a) think small, and
b) are ready to go back
to the drawing board of your ORIGINAL Matlab code to make it compatible with the tons of matlab2fmex's
(sometimes very unintuitive) rigid constraints

* that a long list of Matlab-inspired operator-primitives will accompany every teeny bit of user function;
instead of having directed the user to a matlab2fmex 'standard' .F90 module, from which to pick primitives that are ACTUALLY NEEDED.

* that it ambitions to go all the way to actual mex compilation:
a) this is a non-sequitur (see above)
b) it loads the translations with yet another layer (the mex one) of human-unintelligible .F90 code

* All this is made 'turn key' for a beginner in both Matlab and Fortran?!
No kidding guys!

===============

Overall: yet another poor semi-automatic translator

Hello Cristian,
It is a nice surprise to see your note at fileexchange.
I hadn't been around here for a while, so I didn't see it until now.

My idea was to provide a couple of develop/debug tools packaged in a separate toolbox.
Some fairly unsophisticated things are surprisingly still missing even in the latest Matlab releases.

One such thing is matching 'begin' & 'end' blocks of code.
Emacs does it, but ...
a. not everebody uses it
b. it's hard to configure right for the novice

So I developed a Matlab function to do the same - it could be part of, say - I style-checker which goes beyond my ambition, but is no doubrt useful: the world is full of half-literate 'research' code, documented in 'chinese-like' Ingilish ;-)

Another very useful and yet again 'not-a-priority-for-mathworks' tool would be a good call-tree generator. fileexchange has seen a couple of really 'pedestrian' ones, whose output is hardly intelligent and overwhelming in its flow of less useful details.

Would be nice to hear from you, if ever.
Ned.

P.S. I had submitted a toolbox proposal to Mathworks. Then after a long time I got contacted by some female pencil pusher, who said that I had to register a business to be entitled support and further interest from them. So the idea fell right down the stack of my numerous priorities.

Hello Nedialko

The other day R2010b appeared. "Variable and Subfunction Highlighting" looks as a nice updated/new feature, however, I had hoped for more new features in the IDE.

Your initiative hasn't raised a lot of respons. The tools in the FEX, which support the IDE, are typically not downloaded many times per month. How come?

I myself doesn't use any IDE-tools from the FEX on a regular basis. I can't tell why really.

One size certainly doesn't fit all! About me:
-- solo developer and Matlab only
-- tries to apply OOD/P
-- support work with explorative analysis of measured data from buildings
-- use the Matlab editor and like mlint a lot (I once tried xemacs, but at that time I stuck with ED from down-under)
-- use a test driven workflow with a home made interactive testing framework

What does it take to make IDE-tools successful on the FEX?

Wishlist:
-- project manager - switch between sets of open files, search paths, ...
-- picklists containing names from my own classes - long descriptive names
-- refactoring tool - rename, move code into a package, ...
-- tool to make class diagrams (UML)

/ per

I kinda wish there were a more straight-forward way of accessing structs that live inside an array. For example, in a JSON string that has a series of unkeyed objects living in an array (i.e., "arrayName": [ {"color": "red"}, {"color": "green"}, {"color": "blue"} ]), accessing those objects is odd. Instead of using arrayName(i).color you must use arrayName{1,i}.color. Not a huge deal, just different than what I was expecting.

Other than that, it is very particular about properly-formatted JSON string inputs, and that's a good thing. Nice job.