Hi Edward, In case of 1 - it depends if license is compatible with Apache.
In case of 2 there is no problem cause it the same license. Whatever works for your progress actually. It would be awesome have StackLayout. Thanks, Piotr czw., 3 gru 2020 o 21:50 Edward Stangler <[email protected]> napisał(a): > > Right, but: > > 1. Add a Spark component to Royale that is not in Apache Flex? (at > least not in non-experimental) > > 2. Use the experimental Apache Flex Spark StackLayout (very > complicated, many flash imports) or use a simpler (pure Spark) custom > made one? > > Don't want to spend time and find out it's not appropriate. > > > > On 12/3/2020 1:20 PM, Yishay Weiss wrote: > >> Would Royale want a Spark StackLayout? > >> It's been very useful to have a version of mx:ViewStack for Spark that > > has a dataProvider. > > > > Sounds like you answered your own question. The culture here, as I > understand it, is for people to work on the things they find useful. > > > > > > > > > > From: Edward Stangler > > Sent: Thursday, December 3, 2020 6:16 AM > > To: [email protected]<mailto:[email protected]> > > Subject: Spark StackLayout > > > > It's been very useful to have a version of mx:ViewStack for Spark that > > has a dataProvider. It's just a SkinnableDataContainer (or such) + > > StackLayout. > > > > Would Royale want a Spark StackLayout? > > > > Apache Flex has an experimental StackLayout, but it's unbelievably > > complicated with lots of flash imports. > > > > A straightforward (and short) implementation of StackLayout was fairly > > easy for Flex, and I guess would be for Royale, too. > > > > > > > > -- Piotr Zarzycki
