I think martin has nailed it. Now how easy/difficult to do is a different matter :)
Regards Hank On 1/18/06, Martin Wood <[EMAIL PROTECTED]> wrote: > I think a conjunction of the two ideas would be good. > > When using jar's you can also provide the source code, this is useful > when you are using the jar within a project and can then examine the > code of the library you are using. I use this all the time when > developing RCP (Eclipse Rich Client Platform) applications as its > quicker to just highlight a type or a call and hit 'Open Declaration' to > read the source comments without having to do a mental context switch > into the API docs. > > So it maybe worth considering enhancing the SWC concept to include the > FAR idea, something like a 'src' folder inside the SWC would be enough. > > Of course this would rely on tools to support the option and be able to > make use of it. > > An option for MTASC / HamTASC like : > > mtasc -swc myLib.swc -includeSource ...other args... > > then we just need the various editors to support the use of the swc > option when invoking MTASC and using them as 'project references' :) > > If a complete scheme like this could be worked out I think it would be > fantastic, one of the most difficult things for me when developing flash > is keeping my libraries and classpaths organised. For java its easy, i > just stick my jar's in a lib folder and forget about them. > > martin. > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
