Thank you for the words of encouragement and for noticing my little project. By the way, I did abandon Israfil long ago in favor of your much more capable flex-mojos plugin. When I first started working in Flex and Maven, I was new to both technologies and back then the Israfil plugin seemed easier for someone to get up and running without much effort and without in-depth knowledge. But it wasn’t long before I started running into more complex needs that the Israfil plugin just could not support. I started extending it to meet my needs and that was OK, but I did not like the idea of having this one off customization and the demands for change kept growing. Ultimately I delved into the flex-mojos plugin and converted all out projects to use it instead. It did take a more in depth investment of time and learning curve to get up and running with the flex-mojos, but I can say looking back, there are no regrets. Flex-mojos have provided me with a solution for every curve I have thrown at it and we have a fairly complex build. Also its support for pulling down the flex compiler artifacts rather than being dependent on a local install of the flex SDK was very nice since we use both Windows and Linux platforms for Maven builds.

So, let me take this moment to extend a BIG THANK YOU for all your efforts on that project!

I agree that dependency management in the Flex development world is a bit out of sorts and including non-maven-hosted flex dependencies is a pain. Your project and M2 repository hosting the Flex SDK artifacts is a huge benefit for all of us Flex-Mavenites, I certainly wish Adobe and the community would embrace Maven. I will follow up on your zipped artifacts support topic on the Google code site, I like the idea and will do what I can to include it

Thanks Again, Robert

I do like your initiative, specially on the flex universe it is a real pain to find anything on maven central… nor Flex SDK nor 3rd party libraries are deployed there.

FWIW, I started on maven plugin development on a much similar way, but instead of israfil I started hacking servebox… eventually I figured that was too much pain and the project seemed death, so I decide to start a fresh one.

For sure I will advice flexmojos users about your plugin and may use it in the future if it begins to support zipped artifacts (I wrong a ticket on code google).

VELO

Says here http://help.adobe.com/en_US/Flex/4.0/UsingSDK/WS2db454920e96a9e51e63e3d11c0bf69084-7f27.html#WS2db454920e96a9e51e63e3d11c0bf6119c-7fe1

Look at step 5

I agree and wish there were better tooling for the localization effort.
Take a look at this post, I personally don’t like the idea of explicitly defining a resource manager string lookup every single place I need to perform localization, so I take this approach:
http://www.savage7.com/index.php/2009/08/adobe-flex-3-how-to-create-localized-ui-component-control/

Thanks
-Robert

Only 1 other idea: when you are sitting looking at source code
label=”{resourceManager.getString(‘myResources’, ‘myLocalizedButton’)}”

It’d be nice to do an instant lookup from IDE to reassure yourself: “is this string what I think it is?”.

Or, a capability to insert/update a special format trailing comment… with the actual text in the default language ??

I am using FlashDevelop right now, that’s the thing about Flex is the variety of IDEs or source editors people use. But if it was an external executable, it could be used by most IDEs that can invoke a command line utility and capture output.

Thanks for stopping by!
-Robert

Thanks and great work!

If you are wanting to embed a default set of resources in the compiled SWF and then also expose a means for user customizable/overridable resource definitions, one idea that comes to mind is that you could use the localeChain to do this. For example you could define a locale chain of (‘en_US_custom”, ‘en_US’, ‘en_custom’, ‘en’) where both ‘en_US’ & ‘en’ are embedded and ‘en_US_custom” & ‘en_custom’ are loaded at runtime from XML. This would allow the built-in resource manager to deal with all the resource resolution across all sets of resources.

Or maybe a better option after looking at my XMLResourceLoader class is just to embed the default resource bundles and then allow the XMLResourceLoader class to load the chained XML files. It looks like I wrote this to handle adding/updating resource keys in existing resource bundles that may have already been loaded. It first tries to look up an existing bundle by name and then updates the resource entries. If no bundle by that name exists, it then creates a new resource bundle.

– Good Luck!

Hi Manu,

Thanks for the comments. I have run into the very situation that you are talking about where you want to create a set up resources that can easily be edited in the field without requiring recompiling a SWF.
Take a look at this article I just posted, this includes the ground work for loading resource strings from a XML file using the URLLoader and then creating the Flex resource bundles at runtime. This sample may get you a head start if you have not already implemented this logic in your codebase.

http://www.savage7.com/index.php/2009/10/adobe-flex-3-load-localization-resources-at-runtime-using-xml/

Enjoy!
– Robert