| .. is too complicated to be evaluated [message #71329] |
Thu, 11 November 2004 07:03  |
Eclipse User |
|
|
|
Originally posted by: mik.c-l-a-s-s-x.it
Hello,
I have updated to Eclipse 3.0.1 and VEP to:
org.eclipse.ve (1.0.1) "Visual Editor"
org.eclipse.ve.cde (1.0.1) "Visual Editor Common Data Editor"
org.eclipse.ve.doc (1.0.1) "Visual Editor User Guide"
org.eclipse.ve.java.core (1.0.1) "Visual Editor Java Core"
org.eclipse.ve.java.core (1.0.1.1) "Visual Editor Java Core"
org.eclipse.ve.jfc (1.0.1) "Visual Editor for Java Foundation Classes"
org.eclipse.ve.jfc (1.0.1.1) "Visual Editor for Java Foundation Classes"
org.eclipse.ve.propertysheet (1.0.1) "Visual Editor PropertySheet"
org.eclipse.ve.swt (1.0.1) "Visual Editor for Standard Widget Toolkit"
I always get "java.lang.xxx IWA0125E ResourceLanguages.getString("xxx" is
too complicated to be evaluated)" when working on localized (externalized)
code.
I was not getting this error on the previous version. What happened ?
Cheers,
Mik
--
============================================================ ================
> ClassX Development Italy Via Francesca, 368/I I-56030 S.M. a Monte (PI) <
> Tel.(+39)-0587-705153 Fax.(+39)-0587-705153 WEB: http://www.classx.it <
============================================================ ================
|
|
|
|
|
| Re: .. is too complicated to be evaluated [message #71426 is a reply to message #71407] |
Thu, 11 November 2004 11:04  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Michele Puccini wrote:
> Thanks Rich,
>
> I'll try to switch to the maintenance driver.
>
> Localization is a bit of pain with VE (and more generally with Eclipse). Are
> there any plans to improve it in the next versions ?
>
> Some suggestions:
> - Ability to specify a common resource properties file and resources
> handling class for a set of classes (i.e. package-specific or
> project-specific).
The VE doesn't prevent you from doing this. As long as it is a static
the VE will be able to process it and show you the value (like it does
now). It could be a package or project static.
What it doesn't do is allow you to change or edit the resource file
through the property sheet. We have some thoughts on that and a defect,
but we haven't been able to work on it yet.
Anything else would be an Eclipse thing. They handle the externalization
process itself.
> - I would like to handle localized text in VE (the best would be VAJ style).
>
> Thanks,
>
> Mik
>
--
Thanks,
Rich Kulp
|
|
|
| Re: .. is too complicated to be evaluated [message #602981 is a reply to message #71329] |
Thu, 11 November 2004 09:40 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
We switched to a new way of parsing which gave us a more powerful
parser, BUT a few types of settings were left out. We have since fixed
this in the maintenance driver M20041109. You can either try that, or if
you don't want to step up to a development build yet, you will need to
fully-qualify with package name the ResourceLangauges in the getString stmt.
--
Thanks,
Rich Kulp
|
|
|
| Re: .. is too complicated to be evaluated [message #602985 is a reply to message #71388] |
Thu, 11 November 2004 10:14 |
| Eclipse User |
|
|
|
Thanks Rich,
I'll try to switch to the maintenance driver.
Localization is a bit of pain with VE (and more generally with Eclipse). Are
there any plans to improve it in the next versions ?
Some suggestions:
- Ability to specify a common resource properties file and resources
handling class for a set of classes (i.e. package-specific or
project-specific).
- I would like to handle localized text in VE (the best would be VAJ style).
Thanks,
Mik
--
============================================================ ================
> ClassX Development Italy Via Francesca, 368/I I-56030 S.M. a Monte (PI) <
> Tel.(+39)-0587-705153 Fax.(+39)-0587-705153 WEB: http://www.classx.it <
============================================================ ================
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> ha scritto nel messaggio
news:cmvtk5$a3p$1@eclipse.org...
> We switched to a new way of parsing which gave us a more powerful
> parser, BUT a few types of settings were left out. We have since fixed
> this in the maintenance driver M20041109. You can either try that, or if
> you don't want to step up to a development build yet, you will need to
> fully-qualify with package name the ResourceLangauges in the getString
stmt.
>
>
> --
> Thanks,
> Rich Kulp
|
|
|
| Re: .. is too complicated to be evaluated [message #602991 is a reply to message #71407] |
Thu, 11 November 2004 11:04 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
Michele Puccini wrote:
> Thanks Rich,
>
> I'll try to switch to the maintenance driver.
>
> Localization is a bit of pain with VE (and more generally with Eclipse). Are
> there any plans to improve it in the next versions ?
>
> Some suggestions:
> - Ability to specify a common resource properties file and resources
> handling class for a set of classes (i.e. package-specific or
> project-specific).
The VE doesn't prevent you from doing this. As long as it is a static
the VE will be able to process it and show you the value (like it does
now). It could be a package or project static.
What it doesn't do is allow you to change or edit the resource file
through the property sheet. We have some thoughts on that and a defect,
but we haven't been able to work on it yet.
Anything else would be an Eclipse thing. They handle the externalization
process itself.
> - I would like to handle localized text in VE (the best would be VAJ style).
>
> Thanks,
>
> Mik
>
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.05849 seconds
Home