Yeah, they have housed the bookmarks manager in a tab, and the display field in a tab. _That is one of the reasons that the bokmarks are so responsive, they are preloaded into memory when the app starts and are just there, this coupled with the more efficient structure, using a .plist file, gives Safari the edge in that area.
Chimera pulls the contents of the bookamrks from file dynamically as they are called for, that is why there is a small pause before the sidebar opens. _It has to call for and parse the info before it can display the bookmarks.
For Safari to utilize tabbed browsing, the entire browser .nib and the objective C underpinnings would have to be re-written. _Apple is nothing if not calculated, if they had wanted to add the tabbed feature, they would have either
A. implemented it already;
or
B. created the interface to minimize changes when it was added.
As it stands now niether one of those conditions have been met. _If they do decide to implement this feature ( and they just might... keep gripping) then they will have to wait for the official release, with an entirely new metaphor for the browser window.
my three dollars and eighty-two cents.
Jesuit 2.0 RC 0.21345
For Safari to handle tabbed viewing there must be code in place to manage and create each tab, and the specific history for each tab. _
That code is not currently in Safari it would have to be added. _The way the .nib is set up now only allows for two tabs, when you start adding tabs to the field you must handle the placement of the bookmarks viewer. _It is pretty obvious that they want it to be in the window and not in a sidebar or floating palette so it would stay in the tabset.
That being the case Safari would now have to worry about the placement of the bookmark manager in relation to every new tab opened or closed. _You wouldn't want say two tabs of content, then the manager and three more pages of content. _You could argue that the tab would always be the first tab in the set, but once you start adding tabs you get the tabbed UI, would the bookmarks have a tab that says bookmarks? _Would it be the only tab that didn't have a heading? _
If that is the case then you would get into a custom class, and away from the standard tabfield, hence a new .nib. _Apple has already demonstrated that it doesn't want the tab to show on the bookmarks manager.
Then you would have to tag the tab that handles the bookmarks so that it can be called to from the UI, but it's placement in the set keeps changing everytime you add or delete a tab. _Do you have any idea how cumbersome that would be, and how much it would slow down the UI? _And of course the aforementioned problems would require a crapload of code to track the order of the tabs and the number. _End result code bloat.
If you take the bookmakrs out of the tab set, the you would have to put it somewhere else, a hidden canvas or a palette/drawer. _That would require a new .nib.
And I actually agree with you that it would go against the "macness" of Safari, I never said that the only reason it wasn't included was programmatic. _I just was approaching it from a code standpoint.
Jesuit