The IDL Data Point has a post showing an example of using the new object-oriented interface for user functions in ENVI 5. Mark discussed batch programs in ENVI 5 last week.
I don’t look forward to rewriting old ENVI user functions, but the new interface does look much better than the clunky old ENVI programming interface. My biggest question is how well is it documented?[1]
My next question would be is there a way to write an extension that works for both old and new versions of ENVI? I think so. ??
May 21st, 2012 at 3:36 am
I have mixed feelings, too. Another pile of functions/procedures to learn. As a minimum, we’ll have to arrange that the extensions appear both in the ENVI 5 and ENVI Classic menus. I took part in the beta, and I got the impression that a lot of users would, like me, shun the new single window GUI and stick to the classic. I use two monitors and want to spread the displays over both. Personal opinion: the new GUI sucks.
July 18th, 2012 at 9:29 am
I think the new GUi has its advantages but needs some improvements:
– dockable views that can be dragged out of the GUI on demand (which should work nicely on multiple monitors)
– concurrent zooming/panning in multiple views on demand
– dockable overview window(s)
– an improved and integrated ‘Save/Restore layer state’ tool that saves open layers similar to an mxd in ArcGIS
– a decent simple color and ramp selector that SHOWS colors (I can’t believe they still stick to those old stupid color names that don’t show colors and ramps)
– And lastly, all the useful tools that got scratched and only reside in Classic now should get moved over (e.g. spatial pixel editor, ROI tool, etc.)
I made feature requests on all of these items, and hope they’ll be integrated in a future version. The ENVI 5 interface is a good start but needs lots of improvements still, imho.
July 18th, 2012 at 1:13 pm
On a second thought, sticking with the Classic and adding decent zoom tools and an overview window instead of the classic zoom and scroll windows would be probably the best solution :)