You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by OmPrakash Muppirala <bi...@gmail.com> on 2014/08/23 06:06:34 UTC
Re: Draft TourDeFlex announcement
I'm on it.
Thanks,
Om
On Fri, Aug 22, 2014 at 8:55 PM, Alex Harui <ah...@adobe.com> wrote:
> Yes, I would like to wait for Om to put the binaries on flex.a.o so we can
> include a link like he suggested.
>
> On 8/22/14 7:52 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> >Hi,
> >
> >Anyone have anything to add/suggested changes?
> >
> >Thanks,
> >Justin
> >
> >--------------------------------------------------------------------------
> >-------------------------------------------
> >The Apache Flex community is pleased to announce the release of Apache
> >Flex TourDeFlex 1.0
> >
> >The Apache Flex Tour De Flex component explorer provides a sample set of
> >working
> > Apache Flex examples.
> >
> >This application is based on work donated by Adobe and their component
> >explorer and
> >is expected to be updated over time. We welcome contributions to it from
> >the wider
> >Apache Flex community.
> >
> >The Apache Flex TourDeFlex is available in source form from the following
> >download page:
> >http://www.apache.org/dyn/closer.cgi/flex/tourdeflex/1.0
> >
> >When downloading from a mirror site, please remember to verify the
> >downloads using signatures or MD5 hashes.
> >
> >For more information on Apache Flex, visit the project home page:
> >http://flex.apache.org <http://flex.apache.org/> <http://flex.apache.org/
> >
> >
> >Thank you for using Apache Flex,
> >The Apache Flex Community
> >--------------------------------------------------------------------------
> >-------------------------------------------
>
>
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> https://blogs.apache.org/roller-ui/authoring/preview/flex/?previewEntry=apache_flex_tourdeflex_1_0
> I assume you have the credentials to login?
Don't believe I do.
> If not, I can do it first thing in the morning (around 6 hours from now)
That should be fine.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Like modifying the .xml to add the 4.12 examples. That isn't a
> code change or recompilation either.
The XML is now compiled into application so yes that would require a recompilation, and you would need to put new compiled swfs from a source package that hasn't yet been voted on. Please let's try and set a good example here and follow the normal voting and release process rather than trying to work around it.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
On 8/25/14 7:53 AM, "Justin Mclean" <ju...@me.com> wrote:
>Hi,
>
>> So before I go and ask on general@incubator
>Ask away.
>
>> But it is ok to add a copy of explorer.html as index.html
>No code was changed or recompiled, it's a HTML file. If you really think
>it should be reverted go ahead and remove it.
I don't think it needs to be reverted. I think it is fine to do this and
more. Like modifying the .xml to add the 4.12 examples. That isn't a
code change or recompilation either.
-Alex
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@me.com>.
Hi,
> So before I go and ask on general@incubator
Ask away.
> But it is ok to add a copy of explorer.html as index.html
No code was changed or recompiled, it's a HTML file. If you really think it should be reverted go ahead and remove it.
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
On 8/25/14 12:29 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Mon, Aug 25, 2014 at 12:11 AM, Justin Mclean <ju...@classsoftware.com>
>wrote:
>
>> Hi,
>>
>> > Never mind. I misread your email as you wanting to fix the minor
>>issues
>> > before releasing.
>> No problem.
So before I go and ask on general@incubator, are some of you still under
the impression that we can't push fixes to TDF to the web-site without a
release vote? But it is ok to add a copy of explorer.html as index.html
and move stuff around to fix a few other issues? Again, I saw a mentor
thread saying it is ok to modify an .xml config file on the site, but
couldn't find the thread that explicitly said we don't need a release vote
for the badge installer, which is my current understanding of the
situation. The badge installer is not in the source package for the
installer AFAICT.
IMO, I think we are fine pushing TDF modifications to the site without a
release vote.
-Alex
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Mon, Aug 25, 2014 at 12:11 AM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Never mind. I misread your email as you wanting to fix the minor issues
> > before releasing.
> No problem.
>
> > I am going to push it to prod now, before I go to sleep. Please do plan
> to
> > include the url in the announcement. Iff someone raises an objection,
> you
> > can simply remove the url from the announcement.
> I'll send t out last thing tonight, unless anyone has any objections. I
> think anything major would of been discovered by now. (BTW that's in 6
> hours or so.)
>
> > BTW, I will also get a blog post ready and loaded to go.
> Much appreciated.
>
>
The blog post is here:
https://blogs.apache.org/roller-ui/authoring/preview/flex/?previewEntry=apache_flex_tourdeflex_1_0
I assume you have the credentials to login? If not, I can do it first
thing in the morning (around 6 hours from now)
Thanks,
Om
> Thanks,
> Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Never mind. I misread your email as you wanting to fix the minor issues
> before releasing.
No problem.
> I am going to push it to prod now, before I go to sleep. Please do plan to
> include the url in the announcement. Iff someone raises an objection, you
> can simply remove the url from the announcement.
I'll send t out last thing tonight, unless anyone has any objections. I think anything major would of been discovered by now. (BTW that's in 6 hours or so.)
> BTW, I will also get a blog post ready and loaded to go.
Much appreciated.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Done.
http://flex.apache.org/tourdeflex/explorer.html
Thanks,
Om
On Mon, Aug 25, 2014 at 12:04 AM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> On Sun, Aug 24, 2014 at 11:56 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
>> Hi,
>>
>> > But won't that require a new RC and a new vote? Are you okay with
>> skipping
>> > that part?
>> Why? It what was voted on and released right?
>>
>>
> Never mind. I misread your email as you wanting to fix the minor issues
> before releasing.
>
> I am going to push it to prod now, before I go to sleep. Please do plan
> to include the url in the announcement. Iff someone raises an objection,
> you can simply remove the url from the announcement.
>
> BTW, I will also get a blog post ready and loaded to go.
>
> Thanks,
> Om
>
>
>> Thanks,
>> Justin
>>
>
>
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Sun, Aug 24, 2014 at 11:56 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > But won't that require a new RC and a new vote? Are you okay with
> skipping
> > that part?
> Why? It what was voted on and released right?
>
>
Never mind. I misread your email as you wanting to fix the minor issues
before releasing.
I am going to push it to prod now, before I go to sleep. Please do plan to
include the url in the announcement. Iff someone raises an objection, you
can simply remove the url from the announcement.
BTW, I will also get a blog post ready and loaded to go.
Thanks,
Om
> Thanks,
> Justin
>
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> But won't that require a new RC and a new vote? Are you okay with skipping
> that part?
Why? It what was voted on and released right?
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Sun, Aug 24, 2014 at 11:49 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Are we good to push it to production?
>
> Unless anyone thinks the minor issues found so far should stop it being
> produced I'm fine for it to be pushed live.
>
>
But won't that require a new RC and a new vote? Are you okay with skipping
that part?
> With a slight tweak we can change the announcement and remove the link and
> then announce that next time we release.
>
I would rather release the app on the site with bugs then not do it at
all.
Thanks,
Om
>
> Thanks,
> Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Are we good to push it to production?
Unless anyone thinks the minor issues found so far should stop it being produced I'm fine for it to be pushed live.
With a slight tweak we can change the announcement and remove the link and then announce that next time we release.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Are we good to push it to production?
Thanks,
Om
On Aug 24, 2014 6:16 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> Hi,
>
> > One minor issue we probably need to change where the loading bar is
> located which is not noticeable when running locally.
> >
> > Someone mind raising a JIRA?
>
> Done - https://issues.apache.org/jira/browse/FLEX-34493
>
> Thanks,
> Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> One minor issue we probably need to change where the loading bar is located which is not noticeable when running locally.
>
> Someone mind raising a JIRA?
Done - https://issues.apache.org/jira/browse/FLEX-34493
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Can the page have a favicon?
Thanks for checking it out I've raised a JIRA for the misisng favicon here [1]
Justin
1. https://issues.apache.org/jira/browse/FLEX-34488
Re: Draft TourDeFlex announcement
Posted by Andrew Wetmore <co...@gmail.com>.
Can the page have a favicon? The tab is showing up with a blank rectangle
beside its name rather than an image in Chrome.
On Sat, Aug 23, 2014 at 8:11 AM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Or directly go to the page:
> > http://flex.staging.apache.org/tourdeflex/explorer.html
> >
> > I will check tomorrow morning for any feedback. If none, I will go ahead
> > and push it to production.
>
> Looks good to me.
>
> One minor issue we probably need to change where the loading bar is
> located which is not noticeable when running locally.
>
> Someone mind raising a JIRA?
>
> Justin
--
Andrew Wetmore
http://cottage14.blogspot.com/
http://portfolio.cottage14.com
http://annapolisndp.ca
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Or directly go to the page:
> http://flex.staging.apache.org/tourdeflex/explorer.html
>
> I will check tomorrow morning for any feedback. If none, I will go ahead
> and push it to production.
Looks good to me.
One minor issue we probably need to change where the loading bar is located which is not noticeable when running locally.
Someone mind raising a JIRA?
Justin
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Okay, it has been pushed into the staging area. You can test it by going
to
http://flex.staging.apache.org and selecting About Flex > Tour de Flex
Or directly go to the page:
http://flex.staging.apache.org/tourdeflex/explorer.html
I will check tomorrow morning for any feedback. If none, I will go ahead
and push it to production.
Thanks,
Om
On Sat, Aug 23, 2014 at 12:59 AM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > In the meantime, I have couple of spare hours tonight and I want to make
> it
> > productive. I am going to go with the RC3 bits
> The RC3 bits and the tag are both identical so either is fine. If you run
> into any issue post here I'm up or 5 or 6 hours yet.
>
> Thanks,
> Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> In the meantime, I have couple of spare hours tonight and I want to make it
> productive. I am going to go with the RC3 bits
The RC3 bits and the tag are both identical so either is fine. If you run into any issue post here I'm up or 5 or 6 hours yet.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
On 8/23/14 12:10 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>We had a big discussion about this when we released the first version of
>the Installer badge, installer config xml, etc. which goes on the website
>as well. You both might want to refresh on that thread before taking it
>to
>general@i.a.o.
I tried to go find the threads. I saw one where we can change the .xml
file without a vote. Was the conclusion also that we can change the badge
installer without a vote?
-Alex
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
We had a big discussion about this when we released the first version of
the Installer badge, installer config xml, etc. which goes on the website
as well. You both might want to refresh on that thread before taking it to
general@i.a.o.
In the meantime, I have couple of spare hours tonight and I want to make it
productive. I am going to go with the RC3 bits to avoid any further
arguments.
Thanks,
Om
On Fri, Aug 22, 2014 at 11:47 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > Might be a good question for general@incubator. Mind if I ask there?
> Ask away. But I think we should set a good example here and not try and
> get around the rules.
>
> > I'm all for faster release cycles. I think it is 30 minutes minimum to
> > validate the TDF RC.
> It not really that complex to validate it IMO. And if we release often
> there well be less changes between versions and as it really multiple small
> applications you have a good idea of which ones you need to look at and
> which you can ignore.
>
> > Given the potentially high traffic and profile TDF
> > might get, we might be tempted to immediately fix any problem reported.
> There is no need to fix every issue immediately, we just need to
> acknowledge the issue (like in JIRA for instance), hopefully someone will
> fix it, and it can be released when we make the next release. Exactly the
> same situation as the SDK, it's not like that is 100% bug free (or we would
> have no open JIRAs)
>
> > Doing daily releases would be a little too fast for me.
> I don't think we need daily releases and voting periods will overlap
> probably making it very confusing. But if enough people show interest and
> contribute examples I could see a release a month.
>
> > Only successful builds would get pushed.
> Which can still be non functioning, should we ship everything just because
> it compiles?
>
> Thanks,
> Justin
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Might be a good question for general@incubator. Mind if I ask there?
Ask away. But I think we should set a good example here and not try and get around the rules.
> I'm all for faster release cycles. I think it is 30 minutes minimum to
> validate the TDF RC.
It not really that complex to validate it IMO. And if we release often there well be less changes between versions and as it really multiple small applications you have a good idea of which ones you need to look at and which you can ignore.
> Given the potentially high traffic and profile TDF
> might get, we might be tempted to immediately fix any problem reported.
There is no need to fix every issue immediately, we just need to acknowledge the issue (like in JIRA for instance), hopefully someone will fix it, and it can be released when we make the next release. Exactly the same situation as the SDK, it's not like that is 100% bug free (or we would have no open JIRAs)
> Doing daily releases would be a little too fast for me.
I don't think we need daily releases and voting periods will overlap probably making it very confusing. But if enough people show interest and contribute examples I could see a release a month.
> Only successful builds would get pushed.
Which can still be non functioning, should we ship everything just because it compiles?
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
On 8/22/14 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> We definitely want it to look good, but I would expect folks will find
>> lots of stuff when they start poking around, so I wouldn't spend too
>>much
>> time on it. IMO, if a problem is found, it would be fine to modify the
>> repo, make a local build, and drop new files on the website.
>
>Really? That would be releasing unreleased software in my books and a bit
>no-no under Apache rules. While we don't vote on and release the web site
>content but this content come from releasable software and is code so I
>really don't think we can do that.
Might be a good question for general@incubator. Mind if I ask there?
It's an interesting case. If we were to put any other app on flex.a.o, we
wouldn't be making source code available for the general public, but I
suppose one could argue that with TDF, at least the example source is
being made available, although not as a package.
>
>It's really not too hard to call a vote on this, and it's relatively easy
>to compile and test, lets actually try and follow the Apache Way here.
>Small gradual improvement and release as often as we can.
I'm all for faster release cycles. I think it is 30 minutes minimum to
validate the TDF RC. Given the potentially high traffic and profile TDF
might get, we might be tempted to immediately fix any problem reported.
Doing daily releases would be a little too fast for me.
>
>> And/Or, if you want to be really bold, we could set up Jenkins to
>>deploy a
>> nightly build to the site.
>--1 to that, procedure aside, we don't want to be publishing potentially
>very broken stuff to the web site. And given the number of times Jenkins
>seems to stuff up, it seem very risky to me.
Only successful builds would get pushed.
Anyway, we'll see what others think.
-Alex
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> We definitely want it to look good, but I would expect folks will find
> lots of stuff when they start poking around, so I wouldn't spend too much
> time on it. IMO, if a problem is found, it would be fine to modify the
> repo, make a local build, and drop new files on the website.
Really? That would be releasing unreleased software in my books and a bit no-no under Apache rules. While we don't vote on and release the web site content but this content come from releasable software and is code so I really don't think we can do that.
It's really not too hard to call a vote on this, and it's relatively easy to compile and test, lets actually try and follow the Apache Way here. Small gradual improvement and release as often as we can.
> And/Or, if you want to be really bold, we could set up Jenkins to deploy a
> nightly build to the site.
--1 to that, procedure aside, we don't want to be publishing potentially very broken stuff to the web site. And given the number of times Jenkins seems to stuff up, it seem very risky to me.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
IMO, it can wait until you're ready.
We definitely want it to look good, but I would expect folks will find
lots of stuff when they start poking around, so I wouldn't spend too much
time on it. IMO, if a problem is found, it would be fine to modify the
repo, make a local build, and drop new files on the website. CTR, no need
for voting. Then at some point, we can cut another release.
And/Or, if you want to be really bold, we could set up Jenkins to deploy a
nightly build to the site. But that's for later. I'm fine with whatever
you put up there.
-Alex
On 8/22/14 10:05 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>I have the RC3 bits from when I built it, but my main goal here is to make
>sure that whatever goes on the website looks really good.
>
>I will get the tag and build from there and see how things go.
>
>Also, do we want to announce on the weekend? Let's wait until Monday
>morning. That will also give me more time to work on the site.
>
>Thanks,
>Om
>On Aug 22, 2014 9:45 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>> IIRC, I think you have to manually build that one example. That was a
>> build script change, but still, a change to the released sources. And
>>we
>> might want to figure out why the OSMF video is black and that might
>> require a code change.
>>
>> On 8/22/14 9:40 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>> >Hi,
>> >
>> >> IMO, it doesn't matter since we're going to muck with the results to
>>fix
>> >> two or three known issues.
>> >Much about == change where a few files live, I don't believe there
>>needs
>> >to be any changes to code or anything else.
>> >
>> >Thanks,
>> >Justin
>> >
>> >
>>
>>
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I have the RC3 bits from when I built it, but my main goal here is to make
sure that whatever goes on the website looks really good.
I will get the tag and build from there and see how things go.
Also, do we want to announce on the weekend? Let's wait until Monday
morning. That will also give me more time to work on the site.
Thanks,
Om
On Aug 22, 2014 9:45 PM, "Alex Harui" <ah...@adobe.com> wrote:
> IIRC, I think you have to manually build that one example. That was a
> build script change, but still, a change to the released sources. And we
> might want to figure out why the OSMF video is black and that might
> require a code change.
>
> On 8/22/14 9:40 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> >Hi,
> >
> >> IMO, it doesn't matter since we're going to muck with the results to fix
> >> two or three known issues.
> >Much about == change where a few files live, I don't believe there needs
> >to be any changes to code or anything else.
> >
> >Thanks,
> >Justin
> >
> >
>
>
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
IIRC, I think you have to manually build that one example. That was a
build script change, but still, a change to the released sources. And we
might want to figure out why the OSMF video is black and that might
require a code change.
On 8/22/14 9:40 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>Hi,
>
>> IMO, it doesn't matter since we're going to muck with the results to fix
>> two or three known issues.
>Much about == change where a few files live, I don't believe there needs
>to be any changes to code or anything else.
>
>Thanks,
>Justin
>
>
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> IMO, it doesn't matter since we're going to muck with the results to fix
> two or three known issues.
Much about == change where a few files live, I don't believe there needs to be any changes to code or anything else.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by Alex Harui <ah...@adobe.com>.
On 8/22/14 9:18 PM, "Justin Mclean" <ju...@me.com> wrote:
>Hi,
>
>> Should I build from the git repo or from the released src kit?
>Really has to be from the code in the release.
IMO, it doesn't matter since we're going to muck with the results to fix
two or three known issues.
Get it up there whatever way is easier. Theoretically, you built it in
order to vote. Do you still have those bits around?
-Alex
Re: Draft TourDeFlex announcement
Posted by Justin Mclean <ju...@me.com>.
Hi,
> Should I build from the git repo or from the released src kit?
Really has to be from the code in the release.
> I thought I might get to fix some bugs on the way if I build from the repo.
Check out ApacheFlexTourDeFlex1.0 tag and you'll match what was in the release. Just be careful as I've made a few other changes today.
Thanks,
Justin
Re: Draft TourDeFlex announcement
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Should I build from the git repo or from the released src kit? I thought I
might get to fix some bugs on the way if I build from the repo.
Thanks,
Om
On Fri, Aug 22, 2014 at 9:06 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
> I'm on it.
>
> Thanks,
> Om
>
>
> On Fri, Aug 22, 2014 at 8:55 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Yes, I would like to wait for Om to put the binaries on flex.a.o so we can
>> include a link like he suggested.
>>
>> On 8/22/14 7:52 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>> >Hi,
>> >
>> >Anyone have anything to add/suggested changes?
>> >
>> >Thanks,
>> >Justin
>> >
>>
>> >--------------------------------------------------------------------------
>> >-------------------------------------------
>> >The Apache Flex community is pleased to announce the release of Apache
>> >Flex TourDeFlex 1.0
>> >
>> >The Apache Flex Tour De Flex component explorer provides a sample set of
>> >working
>> > Apache Flex examples.
>> >
>> >This application is based on work donated by Adobe and their component
>> >explorer and
>> >is expected to be updated over time. We welcome contributions to it from
>> >the wider
>> >Apache Flex community.
>> >
>> >The Apache Flex TourDeFlex is available in source form from the following
>> >download page:
>> >http://www.apache.org/dyn/closer.cgi/flex/tourdeflex/1.0
>> >
>> >When downloading from a mirror site, please remember to verify the
>> >downloads using signatures or MD5 hashes.
>> >
>> >For more information on Apache Flex, visit the project home page:
>> >http://flex.apache.org <http://flex.apache.org/> <
>> http://flex.apache.org/>
>> >
>> >Thank you for using Apache Flex,
>> >The Apache Flex Community
>>
>> >--------------------------------------------------------------------------
>> >-------------------------------------------
>>
>>
>