Well there are two main ways for Monkey Patching. Option 1. Create a package class path starting from your project and add the modified files there. However you'll need to disable RSLs for this to work.
Option 2. Keep RSLs enabled. Create a custom preloader for your application and have it make a reference to your modified classes [1]. This is due to the fact RSLs are loaded in frame 1 and classes are a first-in-wins type of a setup. [1] http://www.jamesward.com/2009/03/10/flex-monkey-patching-and-framework-rsls/ -Mark -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, August 05, 2013 10:45 AM To: dev@flex.apache.org Cc: OmPrakash Muppirala Subject: Re: Working on SDK with source-path option Hmm. Well, like I think I said, I've never tried this using FlashBuilder or the IDEs. I work from the command line. But fundamentally, the process should be: Make a monkey-patch, submit the monkey-patch. I just noticed that there is no link to how to monkey-patch Flex. I thought there was a definitive guide somewhere. In looking through some forum posts, it appears that in FB, folks are using library projects to monkey patch. So maybe that's better than the source-path option and doesn't require that you can build individual projects from ANT. So, I think first goal is to get on the wiki a monkey-patch guide for FB users. Anybody have one ready to go? -Alex On 8/5/13 7:19 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >So far, I'm not convinced (understatement following) that this way is >the way we want to teach to noob contributors... > >We need to document it, for sure, especially because I'm curious to >see it in action, but I now think that although it is more laborious, >the method Justin - and myself on occasion - use has better >reproducibility and usability. > >EdB > > > >On Mon, Aug 5, 2013 at 2:40 AM, Alex Harui <aha...@adobe.com> wrote: >> Yeah. And maybe add more source path so fewer swc get used. But >>sometimes I have to simply replace the class constant with the actual >>value. >> >> >> >> >> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. >> >> OmPrakash Muppirala <bigosma...@gmail.com> wrote: >> >> >> >> On Sun, Aug 4, 2013 at 10:07 AM, Alex Harui >><aha...@adobe.com<mailto:aha...@adobe.com>> wrote: >> Try copying that file into source path. >> >> The file is already in the source path. Do you mean copy to local src >>directory? >> >> Sometimes I just temporary alter the method signature. >> >> >> >> >> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. >> >> OmPrakash Muppirala <bigosma...@gmail.com<mailto:bigosma...@gmail.com>> >>wrote: >> >> >> On Thu, Jul 25, 2013 at 11:07 AM, Alex Harui >><aha...@adobe.com<mailto:aha...@adobe.com>> wrote: >> >>> >>> I've hit other occasional compiler issues where it can't resolve some >>> class constants that are used as optional parameters in method >>>signatures. >>> I think I've generally gotten around them, but I honestly don't >>>remember >>> how. >>> >> >> Can you try to remember how you fixed this issue? I am trying to >>create a >> simple example as per Erik's request using >> flex-sdk\frameworks\projects\spark\src as a source path and I am running >> into this issue with the EaseInOutBase and some other class. >> >> Thanks, >> Om >> > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
