GUI designer & I18N

Hi

Are there any thoughts on the support for localized GUIs in the Aurora's GUI designer?

My personal preference would be to use old good property files for storing localized data and to have an ability to bind a component property to resource bundle and a key in that bundle.

7 comments
Comment actions Permalink

+1
The properties files is not old :))

I also put your suggesstion to TWiki
http://www.intellij.org/twiki/bin/view/Main/IntelliJUIDesigner

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Sergei S. Ivanov" <no_reply@jetbrains.com> wrote in message
news:26141422.1058261155493.JavaMail.itn@is.intellij.net...

Hi

>

Are there any thoughts on the support for localized GUIs in the Aurora's

GUI designer?
>

My personal preference would be to use old good property files for storing

localized data and to have an ability to bind a component property to
resource bundle and a key in that bundle.


0
Comment actions Permalink

Sergei S. Ivanov wrote:

Hi

Are there any thoughts on the support for localized GUIs in the Aurora's GUI designer?

My personal preference would be to use old good property files for storing localized data and to have an ability to bind a component property to resource bundle and a key in that bundle.


Of course, we are going to support internationalization. Actually we
don't know how to make it right. We didn't discuss this issue yet :) At
the firt glance properties files are good enough. Perhaps automatic
extraction of resources is also useful. But there are many approaches
how people work with properties. For example some developers create one
property file per "form". Another ones create single properties file per
"project". What are the keys in the resource bundle? So we want that
IDEA will be convenient for both groups.

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

As i can see, the unique key must be key like:
binded.package.name.className.formName.fieldName ?

E.q. the key that getted by MySwing.class.getName() + "." + formName + "." +
fieldName


--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Vladimir Kondratyev" <vova@intellij.net> wrote in message
news:bf0kso$h54$1@is.intellij.net...

Sergei S. Ivanov wrote:

Hi

>

Are there any thoughts on the support for localized GUIs in the Aurora's

GUI designer?

>

My personal preference would be to use old good property files for

storing localized data and to have an ability to bind a component property
to resource bundle and a key in that bundle.
>

Of course, we are going to support internationalization. Actually we
don't know how to make it right. We didn't discuss this issue yet :) At
the firt glance properties files are good enough. Perhaps automatic
extraction of resources is also useful. But there are many approaches
how people work with properties. For example some developers create one
property file per "form". Another ones create single properties file per
"project". What are the keys in the resource bundle? So we want that
IDEA will be convenient for both groups.

>

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

>


0
Comment actions Permalink

But if UIDesigner in future will support binding one form to more classes,
then thi key must be simple:
formName.fieldName

I wrong?

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Alexey Efimov" <aefimov@spklabs.com> wrote in message
news:bf0m1e$m4u$1@is.intellij.net...

As i can see, the unique key must be key like:
binded.package.name.className.formName.fieldName ?

>

E.q. the key that getted by MySwing.class.getName() + "." + formName + "."

+

fieldName

>
>

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Vladimir Kondratyev" <vova@intellij.net> wrote in message
news:bf0kso$h54$1@is.intellij.net...

Sergei S. Ivanov wrote:

Hi

>

Are there any thoughts on the support for localized GUIs in the

Aurora's

GUI designer?

>

My personal preference would be to use old good property files for

storing localized data and to have an ability to bind a component property
to resource bundle and a key in that bundle.
>

Of course, we are going to support internationalization. Actually we
don't know how to make it right. We didn't discuss this issue yet :) At
the firt glance properties files are good enough. Perhaps automatic
extraction of resources is also useful. But there are many approaches
how people work with properties. For example some developers create one
property file per "form". Another ones create single properties file per
"project". What are the keys in the resource bundle? So we want that
IDEA will be convenient for both groups.

>

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

>

>
>


0
Comment actions Permalink

Alexey Efimov wrote:

But if UIDesigner in future will support binding one form to more classes,
then thi key must be simple:
formName.fieldName

I wrong?

+1. For me that's seems a better approach, than naming with class name.

0
Comment actions Permalink

Hi

I noticed that a new empty forum has been created, that's why I decided to post here a topic, which has not yet been widely discussed. Just a little flamebait :)

Back to the question.

In my opinion, GUI designer should not limit the user to, say, one resource bundle per form file. There should be an ability to specify a "default" resource bundle for a form file, but there should be an ability to override it on a lower level (panels or components). For every (potentially) localizable property, e.g. "title", "tooltip" or "mnemonic", there will be a plain text entry field and also an additional popup, which will (a) allow to select a localization string from a resource bundle, (b) allow to select an alternative resource bundle and (c) allow to create a new entry in the resource bundle suggesting default key name generated according to a scheme, like ".

.((.)+)]]> ".

The actual resource key naming conventions are not really important, because they tend to be different from project to project. IDEA may try to support several prodefined naming schemes. What is really important is that IDEA should make it really simple to overview all available localization strings and allow to select the one to be used or create a new one.

All this certainly needs to be backed by an integrated resource bundle editor (a la NetBeans).
http://www.intellij.net/tracker/idea/viewSCR?publicId=3534

Opinions welcome.

0
Comment actions Permalink

I think PopUps will bother. Its be very pleasure if you can localize forms
by onoter one tool.
For example, you have a form with some text, which can be localized, then
you run localization util and open form, then localization util scan entire
form.
Then not translated string found (seems to be not like
${i18n..}) then it put in "non translated" strings table. Then table is connstructed, user can translate some strings. Then string is translated, localization util replace string occupancy in form with something like this: ${i18n..} e.t.c The resourcebundle - is name of resource without location information. For example - resourcebundle - "resource". It must be perform search via ResourceBundle.getBundle("resource"); For default location it find file "resource.propeties", but if exists file "resource_EN.properties", then it will be loaded for English location. BTW, if we look at ResourceBundle documentation, we can see that resources can be and in Java classes, it may give IntelliJ abiliti for best refactoring, i guess: http://java.sun.com/j2se/1.4.2/docs/api/java/util/ResourceBundle.html Thanks! -- Alexey Efimov, Software Engineer Sputnik Labs, http://www.spklabs.com "Sergei S. Ivanov" ]]> wrote in message
news:20412339.1058282253323.JavaMail.itn@is.intellij.net...

Hi

>

I noticed that a new empty forum has been created, that's why I decided to

post here a topic, which has not yet been widely discussed. Just a little
flamebait :)
>

Back to the question.

>

In my opinion, GUI designer should not limit the user to, say, one

resource bundle per form file. There should be an ability to specify a
"default" resource bundle for a form file, but there should be an ability to
override it on a lower level (panels or components). For every (potentially)
localizable property, e.g. "title", "tooltip" or "mnemonic", there will be a
plain text entry field and also an additional popup, which will (a) allow to
select a localization string from a resource bundle, (b) allow to select an
alternative resource bundle and (c) allow to create a new entry in the
resource bundle suggesting default key name generated according to a scheme,
like ".

.((.)+)". >]]>

The actual resource key naming conventions are not really important,

because they tend to be different from project to project. IDEA may try to
support several prodefined naming schemes. What is really important is that
IDEA should make it really simple to overview all available localization
strings and allow to select the one to be used or create a new one.
>

All this certainly needs to be backed by an integrated resource bundle

editor (a la NetBeans).

http://www.intellij.net/tracker/idea/viewSCR?publicId=3534

>

Opinions welcome.



0

Please sign in to leave a comment.