TcxLocalizer - Add the capability to create multiple custom products
I'm using VCL Control Build 52
I'd like to use TcxLocalizer to localize my application but I don't want to place all my localizable strings in "Custom Resource Strings".
I need to organize it a little.
Could you add the ability to create multiple products, just like you've done for your controls ?
The 'Product Name' column is read only in the cxLocalizerEditor. Did I miss something ?
Thanks
Ticket
Q271423
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hello Sylvain.
Thank you for your message.
We agree with you that it is a very useful feature. However, the current version of our cxLocalizer does not support this functionality. Moreover, this task is very complex, and it will require a lot of code changes in the Localizer's core. It is necessary to foresee all available situations. For example, in some cases, these strings should be re-written, but in other cases, it is necessary to append these strings. So, we need to create a special parameter and overwrite Localizer storage's methods to handle these situations. Thank you for understanding.
As a workaround, you can create separate files using our Localizer Editor and then merge these files manually before activating the cxLocalizer.
Best regards,
Ingvar.
Thank you Ingvar for your answer.
Handling multiple ini files will be difficult for us, and I don't like the idea. Sorry.
It's shame that it require too much changes. At the first look, it seems simple.
I did not understand my strings should be "re-written". A string will appear only in one product. It is just a "group by" product option for localisable strings.
Are you sure you can't do something ?
Hello Sylvain.
Thank you for the response. We've discussed this issue with our developers once more, and we decided to convert it to a suggestion. Our developers will consider it, and will possibly implement it in future versions of our controls. Please let me know if you need any additional clarification.
Best regards,
Ingvar.
Thank you for taking into acount my remark.
If you change something, it would be great to also be able to hide some of your products. For example, if my application doesn't use cxScheduler, I would like to be able to "remove" the corresponding product (and all its localizable strings) in the cxLocalizerEditor.
I know that nothing is in the INI file if I do not type in any translation for this product, but the suggestion is just to add a kind of "IsVisible" flag for each product that would be used (and persisted) by the cxLocalizerEditor in order to filter products list.
With these changes, I really think I could use cxLocalizerEditor to localize my app !
Hello Sylvain.
To hide products in the cxLocalizerEditor, you can use filtering capabilities of the inner Grid. Please review the attached video that demonstrates it.
Best regards,
Ingvar.
"To hide products in the cxLocalizerEditor, you can use filtering capabilities of the inner Grid. Please review the attached video that demonstrates it."
=> yes but this filter configuration is not persisted… Could you change the Localizer Editor to be able to persist its grid configuration in an INI file ? With this solution, I could also hide the filter bar on the bottom of the grid (the bar with the "Custmize…" button)
So, my users will only see products were they have to enter translations for.
In fact, what I need is just a way to customize the Localizer Editor grid at startup with an INI file. No need to persist changes made by the user.