You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by steven.c.hankin on 28 Apr 2011 23:31 UTC
Yesterday, while preparing the Ferret-UAF video, the following thought occurred to me: namely that the "natural" way to invoke the THREDDS browser from the Ferret command line (the way that you don't have to look up to remember), is simply to omit the filename argument from the command. Such a command is incomplete and seems to be begging for a UI to help complete it. Thus the THREDDS browser would come up in response to these commands:
yes? use ! user looking for a netCDF file
yes? file ! user looking for an ASCII dataset
What you think of this? Can you think of conflicts that would occur if we took this approach?
It seems possible to add this approach without invalidating the "open" alias or the /BROWSE qualifier. All of these approaches can work together.
Reported by steven.c.hankin on 28 Apr 2011 23:31 UTC
Yesterday, while preparing the Ferret-UAF video, the following thought occurred to me: namely that the "natural" way to invoke the THREDDS browser from the Ferret command line (the way that you don't have to look up to remember), is simply to omit the filename argument from the command. Such a command is incomplete and seems to be begging for a UI to help complete it. Thus the THREDDS browser would come up in response to these commands:
yes? use ! user looking for a netCDF file
yes? file ! user looking for an ASCII dataset
What you think of this? Can you think of conflicts that would occur if we took this approach?
It seems possible to add this approach without invalidating the "open" alias or the /BROWSE qualifier. All of these approaches can work together.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1849
The text was updated successfully, but these errors were encountered: