Re: IB localization question
Re: IB localization question
- Subject: Re: IB localization question
- From: Christiaan Hofman <email@hidden>
- Date: Mon, 04 Jul 2011 11:11:57 +0200
On Jul 4, 2011, at 9:27, Ulf Dunkel wrote:
> Hi Christiaan.
>
>> I partly disagree. For some layout problems it is very well doable to
>> adjust some layout in code, and it's really no pain and not much
>> maintenance. In fact, it is even better for consistency, as IME often
>> the explicitly localized layouts are very hard to keep consistent,
>> especially if the localizers do the layout. Again, it depends on how
>> complex your UI is.
>
> I have difficulties following your approach, because it sets an axiome which claims that complex NIB layout cannot be handled with the "One For All" method. That's not true.
>
No, I'm saying that the one-for-all approach can lead to unacceptably ugly UI. And this should be fixed in code. And fixing in code can be more difficult and less stable for more complex UI.
I am NOT saying that any complex UI CANNOT be handled in a way. I am saying that more complex UI TENDS TO BE more difficult to handle. That should be obvious.
>
>> For instance, I have defined a function that takes an array of buttons
>> and smartly auto-sizes it in a perfect right-to-left row (trying to make
>> them the same size, unless they become too big, but with a minimum size,
>> etc), a common configuration. Just adding the IBOutlets and using this
>> function in windowDidLoad is far less pain and leads to a more
>> consistent layout for the buttons in all localizations than having to
>> adjust the localized NIBs every time some changes are made. And it looks
>> better than needing buttons that are large enough for all localizations
>> (something that is also very hard to determine).
>
> Although your solutions seems to be nice for any type of buttons in the "usual" button row of dialog layouts, it does only cover half the problem. Our "One For All" method covers all NIB layout issues and doesn't add more code to the app.
You forget the "for instance". It solves one common problem. I have a few other solution for other common solutions. And I have been able to cover everything I need.
The one-for-all method does NOT cover everything. Unless you accept just ugly UI. I think that can be unacceptable in certain situations, and saying otherwise IMHO makes you a bad developer. You should not accept bad UI. Again, it depends on your UI how far you need to go.
>
> We basically stop to think about how the base language (English) NIB layout can be simplified and designed to even fit much longer strings. That can be done in almost no time, and we do it in IB. Then iLocalize transfers the layout (with all programmatic bindings, of course) to all localized NIBs with a single click.
>
> It really works fine.
>
> ---Ulf Dunkel
I like to have the best layout if that is possible. Your approach is necessarily always a compromise, and trust me, sometimes an unacceptable one (you may not run into that, but then you're just lucky). I don't need to compromise.
Christiaan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden