Closed Bug 505601 Opened 15 years ago Closed 15 years ago

Remove SharedMenuCocoa

Categories

(Camino Graveyard :: Toolbars & Menus, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino2.0

People

(Reporter: stuart.morgan+bugzilla, Assigned: stuart.morgan+bugzilla)

Details

Attachments

(2 files)

I was poking at the SMC warnings today, and was inspired to go see if this wildly-out-of-date code is really still the state of the art for the program it's meant for, and/or if that program was dead.

I found this fascinating tidbit in the URL Manager Pro docs:

"We prefer you use the Bookmark Menu Extra, but you may still want to use the Shared Menus feature instead. [...] Shared Menus are mainly still supported for users of URL Manager who come from Mac OS 9.

Note: Shared Menus are not supported on Intel Macs."

So... the author doesn't recommend that anyone use it any more, there's a replacement interface using modern OS X technology that doesn't require us to keep shipping that code, and it already doesn't work for something like 2/3 of our users. Oh, and there's a haxie for people who really really want it Shared Menus in arbitrary apps that don't build it in.


Is there a good reason not to rip it out of the app and the tree?
I'm going to land this in two parts, one to stop building SMC, and then another to actually remove all the source. Here's part one (part two I won't make a patch for, since it'll just be file removal).
Part one landed on CVS trunk and CAMINO_2_0_BRANCH. Leaving open for part two once tinderbox cycles.
Source removed on CVS trunk and CAMINO_2_0_BRANCH.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Camino2.0
There are still some traces of SMC on various wiki pages, that might need to be reviewed: http://wiki.caminobrowser.org/Special:Search?search=shared+menus&go=Go
Those all describe branches on which the framework still exists.
I happened to be watching minus just as the warning about this scrolled by…what, why is ld looking for a path that doesn't exist for a framework we no longer build?  mxr knew why ;)
Attachment #398582 - Flags: superreview?(stuart.morgan+bugzilla)
Comment on attachment 398582 [details] [diff] [review]
Don't tell ld where to look for the framework

Oops!
sr=me
Attachment #398582 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
(In reply to comment #8)
> (From update of attachment 398582 [details] [diff] [review])

Landed that on cvs trunk and CAMINO_2_0_BRANCH.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: