Forums | MacLife

As long as they bring hierarchical folder menus back, I will be happy.

Pariah wrote:

FutureDreamz wrote:

Pariah wrote:

Apple needs to just adopt a browser that spawns Finder Windows. Separating the browser from individual folder windows would solve the whole problem.
You could have multiple Browsers open but when you doubled clicked on a folder in the browser it would open a folder window that could not turn into a Browser window, because it's a Finder Window not a Browser window.

like in Classic? there's a checkbox for that.

I dunno, never used classic.

...And I did...
PWND111

Pariah wrote:

Apple needs to just adopt a browser that spawns Finder Windows. Separating the browser from individual folder windows would solve the whole problem.
You could have multiple Browsers open but when you doubled clicked on a folder in the browser it would open a folder window that could not turn into a Browser window, because it's a Finder Window not a Browser window.

What Apple really needs to do is add tabs to the Finder just as Cocoatech has.  That would solve a lot of problems.

maleko wrote:

Pariah wrote:

Apple needs to just adopt a browser that spawns Finder Windows. Separating the browser from individual folder windows would solve the whole problem.
You could have multiple Browsers open but when you doubled clicked on a folder in the browser it would open a folder window that could not turn into a Browser window, because it's a Finder Window not a Browser window.

What Apple really needs to do is add tabs to the Finder just as Cocoatech has.  That would solve a lot of problems.

Lord knows tabs are the only redeeming feature I can personally find in that piece of kludge.

The latest seed reportedly fixes a known driver problem that affects World of Warcraft on PowerPC machines.

Despite early hope that the 10.5.2 update would fix Time Machine's Airport Extreme + USB (AirDisk) drive backup incompatibility, the latest Mac OS X developer seed does not appear to fully address this issue. While AirDisk drives can sometimes now show up in the newest Time Machine, backup attempts to them have been unsuccessful. While these reports are based on beta/developer versions of the software and admittedly limited testing, Apple lists "no known issues" in their seed notes for this latest version. It's also conceivable that an Airport Extreme firmware update may also be necessary as well to fully implement this feature.

Update on the release: http://www.macrumors.com/2008/01/23/mac … e-backups/

Last edited by WalrusCP (2008-01-23 2:40 pm)

WalrusCP wrote:

The latest seed reportedly fixes a known driver problem that affects World of Warcraft on PowerPC machines.

Despite early hope that the 10.5.2 update would fix Time Machine's Airport Extreme + USB (AirDisk) drive backup incompatibility, the latest Mac OS X developer seed does not appear to fully address this issue. While AirDisk drives can sometimes now show up in the newest Time Machine, backup attempts to them have been unsuccessful. While these reports are based on beta/developer versions of the software and admittedly limited testing, Apple lists "no known issues" in their seed notes for this latest version. It's also conceivable that an Airport Extreme firmware update may also be necessary as well to fully implement this feature.

Update on the release: http://www.macrumors.com/2008/01/23/mac … e-backups/

I pretty much said as much  yesterday on post 24 of this very topic.

ScifiterX wrote:

jeremiah256 wrote:

WalrusCP wrote:

Looks like the haters of the menu bar will be pleased with the new release coming soon. Also looks like network disks will (possibly) finally be supported for Time Machine.

Go here for the scoop on these and other leaked features/changes:

http://www.macrumors.com/2008/01/21/mac … d-sharing/

Hopefully they do fix Time Machine's wireless issues with AEBS (and other routers).  I recommended the AEBS to a friend based on this feature prior to Leopard's release.

I don't think this update will completely solve the AEBS issues as I understand them but will probably mitigate the issues. I think the actual solution will take a combination of this and a AEBS firmware update.

Specifically part of the problem as I've read it is that the AEBS's firmware misrepresents the status of AirDisk backups by reporting them as complete to Time Machine when they have only finished loading in the buffer and not actually written to a drive as of yet.

ScifiterX wrote:

Of course the "Back" arrow wouldn't do that. It is set to go back a window, much like a browser's back arrow. The "Path" button is for going up levels and they complemented it by restoring OS 9's control/right click activated title bar hierarchal path functionality under Leopard and even extending it to the Safari browser.

If you go to customize the Finder's tool bar you can add a path widget.

That sort of what I was alluding to, Pariah. That has been part of the functionality since OS X 10.0. However since OS X 10.5 that has been redundant as right/control clicking the windows title in the Finder has the same effect, not unlike how it worked under OS 9 (except for OS 9's complete lack of a toolbar).

Funny, I had double checked that functionality with a 10.4 user before posting. He reports control/right click did nothing for him.

Both myself and Pariah mentioned doing it with the path button here, however.

PS: Reading the other Leopard feature topic, it appears it was changed from command click to control/right click in the OS X 10.4 to 10.5 transition. Since that the case, it's not that the function was missing but that it was mapped at odds with the rest of Apple's UI (control/right click for contextual menus).

Pariah wrote:

reece_james wrote:

Pariah wrote:

Apple needs to just adopt a browser that spawns Finder Windows. Separating the browser from individual folder windows would solve the whole problem.
You could have multiple Browsers open but when you doubled clicked on a folder in the browser it would open a folder window that could not turn into a Browser window, because it's a Finder Window not a Browser window.

That's a level of complexity that most users don't need. I vote for the checkbox in the finder, but it should default to how it is now and it should be an option on a folder's window or a shortcut. That way it makes it easy to swap between custom and system wide views.

I think the mixing of the metaphors causes complexity and confusion while separating the Finder and the Browser would simplify and and make things more consistent.
Back before OSX I used Greg's Browser which was a very prescient implementation of what the OSX browser view turned out to be. Using Greg's browser with the old Finder worked great. It's the mixing of two very different approaches to folder viewing that causes the current problems.
Having a separate "Browser.app" would allow browser fans to have exactly what they wanted while also allowing the Finder to have actual, reliable and persistent view settings. This makes the strength of the browser not stomp all over the views concept.

I agree that there should be a clear distinction between spacial mode (the term for the OS 9 behavior coined by ars) and browser mode, but let me see if I follow..  Are you proposing that a Finder Browser should exist as a separate single-window application?  If a user double-clicks on a folder in column view the contents are displayed  in a new "spatial" window, while a single-click retains the current behavior (displaying the contents in a new column).  And list view and icon view will retain the current behavior in browser mode.  Do I have all that right?  That sounds somewhat like what the Ars article proposed, and it seems like it ought to work. 

My idea (before reading the article) was to simply change the behavior of the "single window" button to apply globally to all folders (which is basically the Windows approach, except that alternating between metaphors is one click away).  This method differs in that it allows multiple browser windows to exist at one time, while disallowing any spatial windows.  Conversely, spatial mode disallows any browser windows, while preventing a folder's contents from being displayed in two different spatial windows.