@Dany I wanted to elaborate further on what Alex mentioned about adding a source path for working on patches.
For example, I just found a problem and wanted to make some quick edits to see if I could fix ArrayList.as. So, I found the file in the sdk, making note of the directory structure. I copied the file and created a duplicate directory and put that in a folder called "monkey-patch" that I have on my desktop. The file and directory that I created was C:\Users\familyRoom\Desktop\monkey-patch\org\apache\flex\collections\ containing a copy of ArrayList.as. The directory and main folder name can be whatever you like, but I used the desktop just for the sake of being easy to find. I named the main folder "monkey-patch" because I think that I may seen it called monkey patching on some forum. In FB, I went to project -> properties -> flex build path -> source path and added the monkey-patch folder via the "add folder" button. Now, the file can be seen in the package explorer, which allows me to make quick edits for debugging and testing, instead of compiling after each edit. There are some limitations, such as if a file you are tweaking has some "include" calls to other files, you will have to include additional directories and files to make FB happy. It took me longer to write this post than it did to setup the monkey-patch and fix the file. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Setup-for-patching-tp45348p45402.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
