Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi Prism/Compiler    [ Add a report in this area ]  
Report #:  82321   Status: Reported
Resourcestrings badly wanted
Project:  Embarcadero Prism Build #:  3.0.22.713
Version:    1.1 Submitted By:   Magne Rekdal
Report Type:  New Feature Request Date Reported:  2/19/2010 4:21:36 PM
Severity:    Serious / Highly visible problem Last Updated: 3/4/2010 4:10:44 PM
Platform:    All platforms Internal Tracking #:  
Resolution: None  Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: 10
Description
I have around 100.000 lines of code for medical decision support and medical records software that I planned to port to Delphi Prism.  The software relies heavily on resourcestrings, and needs to be available in Norwegian, English, Swedish and Danish.

I haven't found a good way to handle these resourcestrings in Prism. The oxidizer command line utility will convert resourcestrings into some ugly-looking function names, that's about all I have round.
Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments

Robert Ogren at 10/13/2010 6:05:47 AM -
You can get the same functionality by using .NET resource files (.resx). The IDE maintains a wrapper class for the resources so you can access them easily in code.

It would be nice with a resourcestring keyword that created a .NET resource in the background like the old Delphi.NET did. It would surely help porting and sharing code between win32 and Prism.

I'm currently experimenting with putting the resource strings in a separate unit and then having an automated conversion script that creates a resx file as part of the build process.

Server Response from: ETNACODE01