The File Exchange Toolbox
Authored by the MATLAB and Simulink user community on the MATLAB Wiki.
The File Exchange Toolbox is provided by the MATLAB Central team to remove the hassle from the process of downloading and uploading submissions to the File Exchange.
| Table of contents |
Usage
- fxsearch - This function passes through the search term to the File Exchange search engine. fxsearch(search_term) initiates a search on the File Exchange.
- fxdownload - If you know the File ID of a File Exchange entry, fxdownload is the simplest way to get it.
- fxcite - This is useful for generating an approved citation for a given download. The result returned is suitable for immediate inclusion in an M-file. See also Citing Files from the File Exchange.
- codemetrics - Generate the code metrics for a given directory.
Coming soon: File Exchange upload assist.
Tasks
>> fxsearch('hirsch')
[download something]
>> fxsearch fractal >> fxdownload(11742)
[click around]
Comments
Please use this page to report bugs and suggest improvements for The File Exchange Toolbox.
John D'Errico
I took a look at fxsearch. It needs some serious work before its a credible replacement for my web browser interface to the FEX.
>> fxsearch getreuer - works nicely, though a bit slow. Really slow compared to Safari. >> fxsearch hansel - finds nothing. What if I can't remember his whole name? >> fxsearch D'Errico - this causes an error of course. >> fxsearch derrico - nothing. >> fxsearch d''errico - not. I really thought this one would work. >> fxsearch d"errico - still not.
Ok, so I'm sure its not personal. I decided to find a function that I'd put up there.
>> fxsearch gridfit - This did find my code.
Then I was able to click on my name. So I'm up there after all. It was still slow.
Suppose I want to look for something, but I'm not sure of the keywords? I tried this.
>> fxsearch grid
It found 50 results. Really slowly though. Then it crashed.
java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError
Yup. Its gonna take a lot of work before I give up the web browser interface. A lot.
When I look at a tool, one of the things I'd ask myself is if it adds anything. Since we have already a very nice interface to the file exchange, this adds another route to the FEX. A slow route, via the command line. Do most users use the command line help anymore? I'd argue that most use doc instead of help. If fxsearch is to be of value, it needs to do more than just emulate an existing interface. Even the download ability seems of little value. If I download something now from the web, it downloads and automatically extracts itself if zipped.
John 10:12, 4 Aug 2006 (EDT)
Scott Hirsch
1. Have a "Back" link. I found that after I downloaded a file, the only link was to my downloads. I'd like a link to go back to my previous page (likely the search results).
2. Provide a link to view code that's been downloaded (i.e. open it in the editor). This was the biggest missing link for me - I'd spend time working in the useful web pages, then need to switch over to the CD browser to poke around to open the right file.
Java Exception: java.lang.NullPointerException at javax.swing.JComponent._paintImmediately(Unknown Source) at javax.swing.JComponent.paintImmediately(Unknown Source) at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source) at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) In paintImmediately null graphics