We are considering moving from a NetBeans project to MyEclipse and M4M.

I have noticed that M4M does not support setting text properties using a resource string as NetBeans does. This is a deal-breaker for us unfortunately so I really hope you have plans to include this in an upcoming release.

Looking at the .form file, settings like this are simply removed by M4M resulting in empty strings being shown in the UI:

Code:

<Component class="javax.swing.JLabel" name="lblSelectMibView">   <Properties>     <Property name="text" type="java.lang.String" editor="org.netbeans.modules.i18n.form.FormI18nStringEditor">       <ResourceString bundle="com/example/Messages.properties" key="TEXT_KEY" replaceFormat="java.util.ResourceBundle.getBundle(&quot;{bundleNameSlashes}&quot;).getString(&quot;{key}&quot;)"/>     </Property>   </Properties> </Component>

[/code]

*** Date:
Tuesday, March 31, 2009 11:53:38 AM PDT

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_11


*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310


*** Eclipse details:
Eclipse Platform

Version: 3.4.1
Build id: M20080911-1700




Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700


Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400


Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800


Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800




Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
C:\eclipse\plugins\org.eclipse.platform_3.3.101.v200809111700\splash.bmp
-launcher
C:\eclipse\eclipse.exe
-name
Eclipse
--launcher.library
C:\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-framework
plugins\org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
-vm
C:\Program Files\Java\jre6\bin\client\jvm.dll

We know about this and we already have it on our TODO. We will try to get this out asap. Sorry for the inconvenience caused.

Good to know you're working on it. Thank you for the response. Is there any way I track when this fix will be available?

Im afraid there is not way for you to track this but I'll keep you updated on this thread.

Subscribing to thread.

This support will be in the 8.x release family and it's very important for our planned Matisse rework that will take place on the Eclipse 3.5 platform later this year.

support-nipun wrote:

This support will be in the 8.x release family and it's very important for our planned Matisse rework that will take place on the Eclipse 3.5 platform later this year.

Has this been addressed in 8.0M1? I don't see it in the list of "Recent Enhancements and Fixes" for 8.0M1

Thanks.

Since I haven't gotten a response, I had to test this out myself. This hasn't been resolved. It's the same issue.

I need an update on the status of this problem.

We didn't have time to get this into the 8.0 release unfortunately, but we are considering a larger scale Matisse refresh all together for the 8.5 release early next year

So any word on whether this is fixed for 8.5?