gehel wrote:


The problem is that when we generate other use cases, or change the existing 
ones, we need to manually merge the added / changed properties back in our own 
version.



What would be great, would be to be able to have a small file with just the 
modified keys (images in our case) and have it overriding the generated 
ApplicationResources.properties just for those properties. (Is it clear enough 
?!?).


(end of quote)




a default path to the image is generated each time, why not simply use it ? 
alternatively you could choose to not use the default resource bundle and only 
rely on translations (_fr.properties etc..), the only drawback here is that you 
won't see the images unless you're using these translation bundles



I think it's better to simply use the image path proposed in the default 
resource bundle, won't that work ?
--
Wouter Zoons - [EMAIL PROTECTED]

http://www.andromda.org/
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=631#631
Posting to http://forum.andromda.org/ is preferred over posting to the mailing 
list!


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to