incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jude <>
Subject Re: [DISCUSS] taking Apache Flex to the next level
Date Fri, 04 Jan 2013 23:48:28 GMT
Examples would be great.

One thing we can do now is market what Flex *is* (we have that description
in a few places) and that *we are making it better*. That is that we fixing
bugs, adding new components, removing dependencies, setting up Mustella
tests, cutting new releases, working on the new Falcon compiler, updating a
Flex SDK installer for easy installation, pursuing a Git workflow, etc.

We can also mention what we are talking about on the list. That is adding a
JS target, adding AOP in Falcon, adding plugin support to Falcon, more
support to get members setup, etc.

We can also talk about what we have done. That is received legal clearance
of Flex resources from Adobe including the SDK itself, Mustella, the
in-development Flex Next components. We also built an Flex SDK installer,
fixed bugs, added new features, setup whiteboards, imported Jira history,
created a new logo, worked on a official website design and many more I'm
not including, etc

So we can give them a picture of where we are, what we've done and what
we're talking about doing next. From that they can form their own opinion
about where we are going. We can also tell them that since this is an open
source project they can help create Flex's future by contributing.

But yeah, examples, would be great. Especially, a few full blown
applications that they could download and import that targeted multiple
devices and operating systems (or show it running on multiple platforms).
Adobe had some things going in this direction. We can also point them to
the official Adobe Flex site. That information is nearly all relevant. At
one point I was hoping to go through the site and fill in all the gaps but
I didn't see anyway to do that (ran into roadblocks as well as others who
have tried to update it).

We can also mention what we as community members would like to see or hope
to accomplish, what we would be able to help out with and so on.

While we're mentioning it an example explorer, like Tour de Flex, online
and in the browser, would be great. But I would really like to go through
it, update and clean up the examples (add more examples as well including
support for skinning).

BTW Do we have a list of what we've accomplished, what we're working on,
etc somewhere online? Do the monthly minutes include all that?

We really need a blog that we can update as well as a feed for those
working with Flex. Now that I think of it the site needs a lot of work.

On Fri, Jan 4, 2013 at 2:32 PM, <> wrote:

> Actually, just explaining/showing the same code base running in Desktop
> Native Captive Runtime (emphasizing no flash player install necessary),
> Desktop Browser, iPad, iPhone, Android Tablet, Android phone would be a
> GREAT way to show the power. It's shocking how many dev's don't know that
> it's possible and how easy it is to do this. Of the 50 or so that work at
> my company, none of them did until recently...
> On Jan 4, 2013, at 3:25 PM, Michael Schmalle <>
> wrote:
> >
> > Quoting Alex Harui <>:
> >
> >>
> >>
> >>
> >> On 1/4/13 9:37 AM, "Michael Schmalle" <> wrote:
> >>
> >>>> Anything we say about the future right now is likely to be met with
> >>>> suspicion anyway.  I think this is a critical year for Flex.  We have
> to
> >>>> build a track record of releases that show that we are making
> progress.
> >>>
> >>> And here in sits the outside view. Since anything that is in
> >>> whiteboards or not included with releases in the next years will fall
> >>> on deaf ears... Unless the blog is updated regularly, the website has
> >>> layman terms explanations of current projects (maybe more conducive to
> >>> actually clicking links and "discovering what we are about"), right
> >>> now it looks like a developers site, not a users site. Why would a
> >>> user venture past the "download" link if it resembles a "how to build
> >>> the sdk or checkout code.
> >> True, but would be far better to show examples/tutorials instead of just
> >> words.
> >
> > This is really what I was getting at, there is no this is what Apache
> Flex does, try it and you will agree.
> >
> > That is all I meant.
> >
> >
> > I haven't tried to update the site, but it seems like there is no
> >> easy way to put up webservices that Flex examples typically use.  This
> is
> >> another thing either Spoon needs to do or I need to do with my own
> >> "company".
> >>>
> >>> I'm not a web designer nor have the time for it but that is a HUGE
> >>> weak link right there and the blog. Plus it's all free advertising
> >>> that we are not totally taking advantage of.
> >>>
> >> Sure, a better site would help, but IMO, a site is helpful when people
> are
> >> looking for something, and a blog additionally helps those who have
> already
> >> found you.  That's all good, but nothing like going viral.  So far, we
> have
> >> not released anything so new or important that it will create the kind
> of
> >> buzz that is loud enough to make folks start looking for us especially
> in
> >> the face of the headwinds from the past year.  If the JS stuff actually
> >> becomes something, then that has the chance of being that thing that is
> >> buzz-worthy.
> >
> > Yeah well, we both know that kind of tree doesn't grow over night so
> it's really not worth talking about and creating a buzz because as you
> said, when you do that you want it to be something the average dev can try
> and pass onto to others if they like it (IE viral, buzz worthy, whatever
> social explicative works).
> >
> >
> >> I'd love to know what else we could do that would make that kind of
> noise.
> >> The Maven stuff maybe?  I'm not sure a better DataGrid would do it.
> >
> > Talking from the outside, it has to be something that restores faith in
> the whole framework. The reason the buzz died down was because Adobe is
> gaming now, not RIA. So in essence Apache Flex DOES have to reinvent itself
> because a lot of devs I know thinks Flex was all about the Flash Player and
> to them it's dead other than gaming which Adobe still owns stake in. They
> tout their Gaming SDK, not Flex SDK anymore.
> >
> > It's a pitty this conversation even exists, but its up to resourceful
> people to think about the implications of time and how it can errode even
> granite.
> >
> > Mike
> >
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >>
> >>
> >>
> >
> > --
> > Michael Schmalle - Teoti Graphix, LLC
> >
> >
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message