Last Comment Bug 569180 - Use GTMUILocalizer in MainMenu.nib, BrowserWindow.nib, and other non-layout-sensitive nibs
: Use GTMUILocalizer in MainMenu.nib, BrowserWindow.nib, and other non-layout-s...
Status: NEW
:
Product: Camino Graveyard
Classification: Graveyard
Component: General (show other bugs)
: unspecified
: All Mac OS X
: P2 normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on: 716552
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-30 21:46 PDT by Smokey Ardisson (offline for a while; not following bugs - do not email)
Modified: 2012-01-09 12:37 PST (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments

Description Smokey Ardisson (offline for a while; not following bugs - do not email) 2010-05-30 21:46:27 PDT
One of the things we've mentioned a few times since somewhere in the 2.0 cycle is switching nibs over to GTMUILocalizer, starting with a few key nibs that aren't layout-sensitive.

This would allow us to do things like fix bug 525758 without resorting to a nasty hack since we were well past string freeze, and also keep improperly-updated-by-l10n-tools BrowserWindow and MainMenu nibs from horking the browser, rendering bookmarking non-functional, and similar things we've seen.  It would also let us do things like turn them into compiled xibs (presumably for speed, but also to prevent casual hacking).

This bug is a P? on the 2.1 list, meaning "Priority to be determined."  It's a definite want, so P2 for MainMenu and BrowserWindow (up to beta 1/l10n freeze), P3 for other nibs.
Comment 1 Smokey Ardisson (offline for a while; not following bugs - do not email) 2010-05-30 22:05:04 PDT
(This is also part of our long-term single-binary l10n strategy: http://wiki.caminobrowser.org/User:Sardisson/Towards_a_single_Camino_binary#Make_nib_changes_not_require_localizer_changes_to_prevent_breakage )
Comment 2 Stuart Morgan 2010-05-31 14:30:42 PDT
Apparently we can't use Apache-licensed code, which is what GTM is (this is based on news stories about how Mozilla hopes to update the MPL by the end of 2010, and one of the things they are looking at is making it Apache-compatible). So I don't think we'll be doing this for 2.1 :(
Comment 3 Samuel Sidler (:ss) 2010-05-31 15:22:39 PDT
We could if we shipped under the GPL or LGPL instead of the MPL/tri-license, I bet...
Comment 4 Smokey Ardisson (offline for a while; not following bugs - do not email) 2010-05-31 15:41:33 PDT
All code in the tree has to be compatible will all three of the tri-license's licenses (see bug 495620, where we had a GPL-incompatible license), so, no, I don't think we can get around that.

Note You need to log in before you can comment on or make changes to this bug.