That's very useful Peter, many thanks! It looks like I can use the framework.swc for the common part of these classes. Will get round to it later this week, I hope.
On 10 June 2015 at 14:26, Peter Ginneberge <p.ginnebe...@gmail.com> wrote: > > I had a quick look yesterday and when I toggled "mx only" vs "spark only" > I saw the mx.swc swapped for the spark.swc. A sparkskins.swc is added for > "spark only" while there is no equivalent for "mx only". > > For AIR projects a sparkair.swc is also added, there is again no mx > equivalent. > > Both component sets have a framework.swc, which I guess contains common > functionality used in both sets. > > regards, > Peter > > > > On 10/06/2015 12:59, Mihai Chira wrote: > >> Great points, thanks all. >> >> Does anyone know how I can check which swcs are included in mx-only >> projects and which in spark-only projects, so I can see where I can put >> the >> common functionality if that's the route I / we'll choose? Thanks. >> >> On 10 June 2015 at 12:40, Kessler CTR Mark J <mark.kessler....@usmc.mil> >> wrote: >> >> Issues I see or agree with. >>> >>> -MX only or Spark only projects. >>> -Inheritance of these classes / child classes. >>> -Possible different behavior. >>> >>> >>> >>> -Mark >>> >>> >>
