![]() ![]() I remember when I was using Irix (Silicon Graphics) heavily many moons ago. Any UI can benefit from ideas borrowed from others. This thinking is, of course, unfortunate. (Years later, I couldn't help but smirk when Lion had resize handles on all corners and edges.) The point is, if something potentially useful has too many associations with Windows, it was (and still is, to some extent) taboo. I actually got boos from the audience and a look of horror from most of the panel, and a straight up "No. Anecdote: in 2008-ish, at WWDC, there was a feedback forum, and while I can't remember what prompted the question, I asked if there were going to be resize handles on all the corners. If tree view has ever been discussed at Apple in the past 15 years (and I wouldn't be surprised if it hasn't), it was almost certainly rejected as a throwback to the old Windows Explorer ca. So naturally that was left in the OS X Finder along with icon and list views from classic Mac OS. ![]() There was even some outcry in OS 8 when the system got menus where you didn't have to hold down the mouse button to keep them open.Ĭome at it from the other side, NeXTStep Workspace's primary view was column view. Having a tree view would have been mostly unnecessary and very Windows-like, which was something to avoid back then. (fun fact - though on OS X, you can adjust a slider to change icon sizes, back in OS ≤9, there was also "Small Icon View", which used 16x16 icons instead of the traditional 32x32, and put the labels to the side, rather than underneath) Despite a few other miscellaneous additions to the Finder over the years (tab view, At Ease (not really the Finder, but it shipped with certain Mac lines)), for System 7 through OS 9, most folks' file systems weren't that deep or complex. Still no tree view though, and I don't think it was until System 6 that there was a list view, and not til System 7 were there disclosure triangles so you could drill down. With HFS in System 4 (IIRC), that changed. Heck, for a couple System versions, the file system (MFS) didn't support more than one level of folder hierarchy, so it would have been completely pointless. This will include the command in all other Terminal commands and allow you to quickly access it by just entering the script name at the command prompt.The classic Mac OS Finder never had a tree view. If you find you are using this command frequently, you can save it in a simple shell script and then save the script with a unique name to the /usr/bin/ directory. ![]() While navigation in this sense is more robust in the Terminal, sometimes using a GUI to manage files is a better option, and this is where this command comes in. Unlike the Finder, which by default hides a number of files based on Finder-specific settings, this command can be used to quickly access these hidden directories. This command is useful especially when you are navigating through hidden directories using the Terminal. The "pwd" command will output the full path to the "present working directory," and the "open" command will then open this directory in the Finder. In this command, the "grave accent" characters surrounding the "pwd" command (they are not apostrophes) will run the pwd command first so the "open" command can then act on its results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |