Jiro Doke

Very nice entry Nick!

This may be about preference, but it would be nice if I call the function without any output argument, then it would open the published HTML in the MATLAB browser. This is the same behavior as "publish".

Otherwise, I really like it. I plan on highlighting this entry for this week's Pick of the Week.

Thanks for the submission!

Hi Mirko,
Very nice entry! I have a need to put copyrights to all of my MATLAB files, so this will be very handy. I noticed one problem. If I have a function with some help comments and then have MATLAB code immediately after the comments (without a blank line), it doesn't append the copyright information:

function out = testfunction(in)
%TESTFUNCTION Summary of this function goes here
% Detailed explanation goes here
out = rand(in);
end

I expected this to become

function out = testfunction(in)
%TESTFUNCTION Summary of this function goes here
% Detailed explanation goes here

% Copyright 2011 The MathWorks, Inc.
out = rand(in);
end

Also, I have a couple of suggestions. I would like the tool to keep the number of blank lines between the comments and code. For example, if I have code like this:

% This is a comment

a = rand;

then the output should be

% This is a comment

% Copyright 2011 The MathWorks, Inc.

a = rand;

Notice that there's a blank line between the copyright line and the code. This preserves the spacing that originally existed in the code.

Second, I think it the function should look for:
1. "cell divisions"
2. blank line
3. Revision line
4. code line

"cell divisions" are used in cell mode like this:

%% Title
% This is a title cell.
%% Section 1
% This is section one.

In the above case, I think the copyright info should go right after the first cell (Title cell):

%% Title
% This is a title cell.

% Copyright 2011 The MathWorks, Inc.
%% Section 1
% This is section one.

This is a great entry. Thanks for creating this (and improving on Raymond's entry)! I am planning on highlighting this for Pick of the Week.

This is great Joseph! It's a very ingenious idea. I noticed a small bug. When you pass in a colormap (CLRS), it swaps the order. You can see the issue from this example:

  imagesc(peaks(500))
  colormap(jet(16)); colorbar
  colormap(vivid(jet(16))); colorbar

Notice the "jet" colormap is swapped when I call with vivid - it goes from red to blue instead of blue to red.

Oh....one more thing. I put NaNs in my signal so it wouldn't plot, but turns out it confuses dsplot's outlier search routine. Any good ways to get around that?