• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [Proposal] On-the-fly NIB localization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Proposal] On-the-fly NIB localization


  • Subject: Re: [Proposal] On-the-fly NIB localization
  • From: "M. Uli Kusterer" <email@hidden>
  • Date: Tue, 16 Nov 2004 15:28:06 +0100

At 0:07 Uhr +1100 17.11.2004, Wade Tregaskis wrote:
Ha, try using an iBook.

I *did* use an iBook G3 600 until its backlight broke this summer. But I had a little more RAM in it, and that made it work better than putting more load on the CPU (and cluttering the RAM with twice the strings!). Maybe I wasn't clear: I should've said memory in general. Upping the RAM or getting a faster hard disk got me much better results than a 200MHz increase in CPU speed. So I'd personally much rather rely on RAM and disk than on a fast CPU.


Anyone, back to the topic itself - I like where the original poster was going to some degree... having dozens of different versions of the same file seems like unnecessary redundancy to me, whether it's by design or otherwise.

Depends on how they're generated, IMHO. With a nice tool (nibtool, PowerGlot, etc.) the actual translation is the only part you need a human for, and the rest can be done mostly automatically (or at least re-applied automatically once it's been done by a human once).


If you pre-generate files this way at build time, it's more like cacheing the automatic translations so you don't have to run them each time at startup.

GTK doesn't work with co-ordinates so much as divisions; you partition your window into multiple areas, which by default auto-scale as appropriate for their contents... true, the interface that results is generally pretty gross if you're not careful, but there are nonetheless many virtues to this method.

If you like GTK's auto-layout containers, check out Renaissance. With a little fiddling to give it nice Aqua metrics, this should get you pretty nice UIs.


I think they even have plans to (eventually) create a visual GUI builder for Renaissance. With that instead of the raw XML files, I'd definitely be interested in using that for my apps.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >[Proposal] On-the-fly NIB localization (From: Moses Hall <email@hidden>)
 >Re: [Proposal] On-the-fly NIB localization (From: "M. Uli Kusterer" <email@hidden>)
 >Re: [Proposal] On-the-fly NIB localization (From: Wade Tregaskis <email@hidden>)

  • Prev by Date: Re: Printscreen on Mac OSX --
  • Next by Date: Re: Best way to catch signals in a Cocoa app
  • Previous by thread: Re: [Proposal] On-the-fly NIB localization
  • Next by thread: Re: [Proposal] On-the-fly NIB localization
  • Index(es):
    • Date
    • Thread