Hi Doug, I'll talk specifically about the Scheduling Framework here, which is something that the Adobe Consulting group have contributed to the community. There are currently no plans to bring that framework into the actual Flex SDK, so I wouldn't have any concerns in that area - I'll update the Scheduling Framework page on Adobe Labs to make that clearer.
There isn't a team allocated to enhancing the Scheduling Framework within the consulting group - it is now very much something we hope the community will step up to the mark and lead. We are doing some bug fixes to the framework at present, those that have been provided back to us by the community, and we'd greatly welcome any enhancements too. The feedback and contribution mechanism is very basic at present (mainly, the Discussions tab on Labs), but if and when enhancements start coming in, we'll look into moving it to somewhere like RIAForge. Thanks, Alistair -- Alistair McLeod Technical Practice Leader (Rich Internet Applications and LiveCycle) Adobe Consulting Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK p: +44 (0) 131 338 6108 [EMAIL PROTECTED], http://weblogs.macromedia.com/amcleod Registered office: 151 St. Vincent Street, Glasgow G2 5NJ Company No. SC101089 -----Original Message----- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Doug McCune Sent: 01 February 2007 21:12 To: flexcoders@yahoogroups.com Subject: [flexcoders] More knowledge of future component development? I know this is a very tricky line that Adobe has to walk between what they can say about future components released in the framework. But here's my issue: I'd love to build more components for Flex, my only worry is that I'll be duplicating energy spent by the Flex team (or Adobe consulting). For example, say I wanted to take the Scheduling Framework and enhance it. I know the labs page says it's in 0.01 alpha or whatever, and they mention that a 1.0 release will happen eventually. So if I knew that in one month a more robust and amazing scheduling framework was going to be released I wouldn't even bother. But if that 1.0 release isn't going to happen for 12 months, then it's worth my time doing it on my own. This is the same with other components in the framework. I'm not going to concentrate on enhancements to the DataGrid, for example, because I know Adobe plans on focusing on that with the Flex 3 framework, and any enhancements that I make will probably pale in comparison. But I have been working on the TabNavigator because I haven't seen any mention of that from an official Adobe source. I've been amazingly impressed with Adobe's openness with developers overall, the release of the framework source, the info regarding the release schedule, etc. If it was possible to give us a little bit more on which components in the framework have planned upgrades, then it might be easier for us to focus our efforts. I know Adobe has said they want us to build more components, I just don't want to build the same ones that the Flex team's building. Doug -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links
