I think this is a great list but that it should be more courteous and professional in tone. I am really thankful that Adobe's committed to finish out the spark set and I'm sure it's a lot of work. Lets cheer these folk on instead of making any timeline that isn't tomorrow a failure. That would be very deflating rather than inspiring if it were me.
Igor, it's not an either or. I agree that folk who can should focus on new components as well but say there are 2000 companies out there with an mx based program that would like to upgrade to spark, but can't redo everything from scratch. If one out of 10 of those companies would take one item off of that list and hit it, then we can truely move on to the spark architecture rather than have to write new code with the mx one, when a better architecture is available. What good will be a fancy new component and new architecture if you cant change the height of a toolbar without subclassing it? Having said that I do want to move on as well so I'll suggest some new components in the Ideas thread as soon as I have the time to describe them properly. On Thu, Mar 1, 2012 at 12:26 PM, Igor Costa <igorco...@gmail.com> wrote: > The missing point to Flex SDK is, Move on! > > If those components are not sparked by spark itself, move on. Don't > replicate legacy code into a new formula. > > Let's be more creative people, implementing new components based on Spark > Architecture. Because later on, we will have a new architecture that we > should do X implementation of our current Spark ones. > > As Jonathan mentioned, hole Halo components that didn't included in Spark > cycle, can be achieved by Skins. Like some of them used in Tink new > components. > > Suggest new components that isn't ready for Desktop/Web/Mobile > > If we try to re-create legacy we will not be able to evolve the SDK in a > community matter. > > > > Regards > Igor > > > On Thu, Mar 1, 2012 at 2:19 PM, Omar Gonzalez <omarg.develo...@gmail.com > >wrote: > > > On Thu, Mar 1, 2012 at 7:18 AM, Carol Frampton <cfram...@adobe.com> > wrote: > > > > > Omar, > > > > > > I am sorry that this is going to sound a little snippy but would you > > > prefer we stop working on getting the compiler and mustella ready and > > work > > > on moving the new spark components over to apache? I'm guessing not. > > > > > > Definitely not. The purpose of the list I made was not to put pressure on > > you guys to donate more code, I simply made the list so that we can have > a > > clear list of what components exist and which are not actually ported to > > Spark. Also, Jonathan mentioned some components should not exist, I'll > > address his email next but the purpose of this list was not to say we > > absolutely have to port each MX component 1:1 to Spark, the list was > meant > > to start a conversation around all of the "missing" components. I really > do > > appreciate the work you're doing to get Mustella and the compiler ready, > so > > please don't take this as a stab at your efforts. This list needed to be > > done regardless of the current status of code to be donated. > > > > > > > I think calling it vaporware is a bit strong. I think on your chart > you > > > should note "potential contribution" from Adobe or some such wording, > not > > > because we wouldn't donate them but there might be others versions that > > > have been done in the community that people prefer to ours. > > > > > > Carol > > > > > > > Agreed, again I wasn't calling it vaporware to be a jerk, I was just > saying > > it a.) does not exist in our repository, and b.) does not exist anywhere > > that we can actually look at any of the Spark work that Adobe has done. > > Because of these two reasons then I was/am unable to provide any kind of > > status that wouldn't be just pure speculation on my part. Since putting > the > > list up Tink has pointed out he has done work regarding some of the > > "missing" Spark components and I've indicated so by adding notes in the > > list to where people can see examples and his source code. > > > > If you could provide more insight into which components have had more > work > > done I'll gladly update the list and add some notes to the list, I just > > couldn't come up w/ that list of work Adobe has done on my own. Right now > > its Accordion and one other? > > > > -- > > Omar Gonzalez > > s9tpep...@apache.org > > Apache Flex PPMC Member > > >
