another advantage is you can use the components in the DesignView of FB.
DK On 3/1/07, Doug McCune <[EMAIL PROTECTED]> wrote:
In my mind, the main reason to shoot for pure AS3 is for consistency. You can accomplish everything in AS3 that you can do in MXML. I know sometimes it's easier to hack together something quickly by using a combination of MXML with AS3 script blocks, but the exact same component can be built with pure AS3 only. One goal of FlexLib is to have some level of consistent coding standards. The easiest standard that I can think of is to shoot for the level of quality of the Flex SDK framework classes themselves. That means solid AS3 classes with well-documented code. One reason the Flex SDK is so useful for learning from and figuring out is that all the code follows the same coding guidelines. Now, that said, we're not going to exclude good components if they use MXML. The AS3 versus MXML distinction is supposed to be more of a guideline. If you've got something you want to contribute and it's MXML classes, we can roll that into FlexLib. We may try to convert MXML stuff to pure AS3, hopefully project members will step up and help each other out when it comes to this. But if it makes the most sense for the component to remain in MXML then it will stay in MXML. So that's just my personal opinion, I'm sure Darron has his own reasons for preferring AS3-only classes. But hey, get involved in the project and everything's up for discussion :) Doug On 3/1/07, Engkee Kwang <[EMAIL PROTECTED]> wrote: > Doug and Darron, > > This is awesome and many thanks for initiating the project. > > I have one question... why the emphasis on pure AS3 vs. MXML? > > -Engkee > > > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, "Doug > McCune" <[EMAIL PROTECTED]> wrote: > > > > I'm pleased to announce FlexLib: a new open-source project for Flex > 2 > > components. This project is a Google Code hosted project, released > > under the MIT license. I've been working with Darron Schall, Mike > > Chambers and Ted Patrick to get the project up and running. We're > > hoping to build a concentrated community effort for custom Flex > > component development. > > > > Have you been looking for a community project to contribute to? Do > you > > have custom components you've been releasing on your blog? Want to > > brainstorm about new and improved components? > > > > The project currently contains a handful of components that have > been > > developed by me or Darron (including some new ones I haven't blogged > > about yet). We want to get the Flex developer community involved and > > have a central resource that will help us all build off each other's > > work. To get involved take a look at the project page on google code > > (link below) and read the HowToContribute wiki page. > > > > For more information read through the project website, join the > > discussion group, and email me if you have more questions. If you > want > > to contribute your code, drop us a line and we'll get you involved. > > > > FlexLib project page: http://code.google.com/p/flexlib > > > > Announcement on my blog: > > http://dougmccune.com/blog/2007/02/28/announcing-flexlib-open- > source-flex-component-library/ > > > > Darron Schall's announcement: http://darronschall.com/weblog/ > > > >
-- Douglas Knudsen http://www.cubicleman.com this is my signature, like it?
