Good job and keep up the great work!

Kenneth

Raymon W.

I am adding this also xmlns:flexlib=”flexunit.flexui.*”

but the only component I get is

What am i doing wrong?

-jason

I certainly understand your worry, and I wouldn’t in any way want developers to think that contributing to this project would draw traffic away from their blogs. I see blog posts fitting in as a very important piece of the puzzle. For example, I plan on contributing any new components that I make to the FlexLib library. But I also plan on blogging about each one just like I do now. Blog posts will be a way to announce the component to the world, show some cool examples, and describe in more detail what the component does. The list of current components on the FlexLib page can easily point to a blog post for each component if one exists.

Also, we’re certainly making sure that anyone who contributes gets proper credit on the FexLib project pages. Your name and link to your blog would be published. I don’t think you should think of it as a way to draw traffic away from your blog, but instead as a way to draw traffic to your blog.

As for the marketing potential, I see involvement in this project as a huge boost to promoting yourself in the Flex community. One goal of the FlexLib project is to make sure contributed components are up to certain coding standards that the other project members approve of. The project has just started, so obviously there are only a few people involved, but I would hope that we could attract all the prominent Flex developers to contribute in some way or another. This allows you as a developer to throw your name into the ring with the top Flex contributors out there. I see that as a big opportunity.

Are you referring to Adobe Exchange when you say “one is definitely enough”? Or MXNA as the aggregator? I think MXNA is far too broad to be a legitimate resource for finding a library of custom components. It’s great for announcing and publicizing your work, but I don’t want to have to search through MXNA, filter out the blog posts that have source code, check if they’ve been updated since I last looked, etc etc.

And not to bash the Adobe Exchange too much, but it really doesn’t provide what I want from a component library. If I submit my actual code to the exchange then any updates I do means I have to reupload my code. Or I can simply provide a link to my blog post (which is what I have done with the exchange listings) but then the exchange simply acts like a blog listing aggregator, like a more focused MXNA.

The main point is that we need a central place for the code. This will help all of us work on each other’s code, improve someone else’s code, extend someone else’s code to make new components, etc. And it allows us to set certain standards for code, so you know that if a component is in FlexLib, it’s a solid component, with documented source code. FlexLib is just one piece of the puzzle. We still need blog posts to announce and discuss components. I have no intention of drawing focus away from your blog (or my blog for that matter, we’re in the same boat!).

Feel free to email me separately if you still have concerns about the project. Or post your comments to the flexlib discussion group.