{"id":282,"date":"2009-08-18T17:27:59","date_gmt":"2009-08-18T21:27:59","guid":{"rendered":"https:\/\/blogs.mathworks.com\/steve\/2009\/08\/18\/moving-toolbox-functions-into-matlab\/"},"modified":"2019-10-28T16:56:05","modified_gmt":"2019-10-28T20:56:05","slug":"moving-toolbox-functions-into-matlab","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/steve\/2009\/08\/18\/moving-toolbox-functions-into-matlab\/","title":{"rendered":"Moving toolbox functions into MATLAB"},"content":{"rendered":"
\r\n

I'm sorry to have disappeared off the blogging map the last couple of weeks. I got involved in some projects that needed many\r\n hours of uninterrupted, focused time, which somehow doesn't mesh well with keeping up with the blog. ;-)\r\n <\/p>\r\n

Last week StephenLL commented<\/a> on my \"Five years of Image Processing Toolbox changes\" post<\/a>. Stephen said he'd like to see the function padarray<\/tt><\/a> moved into MATLAB.\r\n <\/p>\r\n

I think that's a reasonable request.<\/p>\r\n

There have been several cases in the past when we have moved Image Processing Toolbox functionality into MATLAB.<\/p>\r\n

The first case was the image file reading and writing functions. When Image Processing Toolbox version 1.0 shipped in 1993,\r\n it included several pairs of functions for reading and writing image formats: tiffread<\/tt>, tiffwrite<\/tt>, bmpread<\/tt>, bmpwrite<\/tt>, etc. Pretty soon, users started complaining that we were charging them for a toolbox when all they wanted to do was read\r\n or write a TIFF file. So we decided to move the functionality into MATLAB. Based on our experience with the original functions,\r\n we also decided to present the functionality with redesigned interfaces. For example, we learned that it was frequently useful\r\n to be able to read the metadata from an image file without actually reading the image pixels. The new image I\/O functions\r\n were imread<\/tt><\/a>, imwrite<\/tt><\/a>, and imfinfo<\/tt><\/a>, and they shipped with MATLAB 5.0 in 1997.\r\n <\/p>\r\n

A simpler MATLAB move, similar to what Stephen is suggesting for padarray<\/tt>, happened a little bit later with circshift<\/tt><\/a>. This is one of the earliest cases I can remember where an Image Processing Toolbox function moved without modification\r\n into MATLAB. In this case, the first opportunity to ship the function was in a toolbox release, but it was written with the\r\n idea that it might go into MATLAB at some point.\r\n <\/p>\r\n

The Image Processing Toolbox function ind2rgb<\/tt><\/a> moved into MATLAB a year or two after MATLAB 5.0. The driving factor here was the newly added ability to put image data\r\n onto user interface buttons in Handle Graphics. Users would read an indexed image from an indexed image file, for example,\r\n but then get stuck because the button wouldn't take the image data in indexed form.\r\n <\/p>\r\n

The function rgb2ind<\/tt><\/a> eventually found its way from the toolbox into MATLAB also, but not until the R2009a release earlier this year. This change\r\n was motivated in part by the reintroduction of GIF format support a couple of years ago. Users wanted to write GIF files,\r\n but the GIF format supports only indexed images, and MATLAB users without the Image Processing Toolbox found it difficult\r\n to convert their truecolor images to indexed form.\r\n <\/p>\r\n

Moving rgb2ind<\/tt> was actually a fairly complicated move. Conversion to indexed format is a complex calculation, and rgb2ind<\/tt> called several other Image Processing Toolbox functions to do portions of the work. So all of these functions moved over\r\n to MATLAB together with rgb2ind<\/tt>.\r\n <\/p>\r\n

I wrote the original version of padarray<\/tt> and figured it might be a candidate for moving into MATLAB at some point. I can't really say for sure, though, whether and\r\n when that might happen. Such a function move affects product tests, reference pages, release notes, and so it requires coordination\r\n from several people and maybe a day or two of person-time. I suspect also that the current implementation may have some dependencies\r\n on other Image Processing Toolbox utility functions, so these dependencies would need to be resolved. It's not a huge amount\r\n of time, but then we never seem to have enough time to do everything we want to do with the product.\r\n <\/p>\r\n

Anyway, thanks again, Stephen, for the suggestion.<\/p>