> > > Completely agree. This was my issue with the 1-1 list, just because it was > done once doesn't mean it should be done the same way forever. > > -- > Jonathan Campos >
I should reiterate the fact that this list is not a proposition that each MX component be match 1:1 with what should be available in Spark. This is why in some cases in the list, like for mx:ApplicationControlBar, I point to spark.component.Application.controlBarContent, because it no longer makes sense to have that component. The list was meant to have an actual inventory of what is actually existing on the MX side and start a conversation about what we need to make on the Spark side. Very much like this good debate on a simple Spacer, it was meant to spark a conversation. :P I hope that through these conversations we can come to some general consensus on which components are actually needed on the Spark side, or not needed like mx:ApplicationControlBar. -- Omar Gonzalez s9tpep...@apache.org Apache Flex PPMC Member
