You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by "david@achievelabs.com" <da...@achievelabs.com> on 2015/04/23 17:59:34 UTC

Legacy Flex ( 3.0 ) upgrade to Open Source

Our mobile platform is built on older Adobe Flex. Our system allows us to
build complete learning programs using device detections, but not currently
using Phone Gap or Cordova, or any responsive design. 
(non responsive design) 

I'd like to know how best to integrate the brilliance of this new code base
and people behind it. I feel we are losing this battle unless we use updated
, fully responsive code base.

What if LearnCast became an open sourced solution, all build with the new
Open FLEX stack.

I'd like to know who / how / and timing for something like this. 

Is this possible ? 

David



--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

RE: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by "david@achievelabs.com" <da...@achievelabs.com>.
Thank you ALEX David Clemons CEO&nbsp; LearnCast (208) 867 4666 


-------- Original Message -------- 
Subject: Re: Legacy Flex ( 3.0 ) upgrade to Open Source 
From: "Alex Harui [via Apache Flex Users]" 
&lt; ml-node+s2333346n10180h60@n4.nabble.com &gt; 
Date: Fri, April 24, 2015 9:30 pm 
To: " david@achievelabs.com " &lt; david@achievelabs.com &gt; 

 On 4/24/15, 5:01 PM, " [hidden email] " &lt; [hidden email] &gt; wrote: &gt;Alex - Thank you for your interests! Flex JS output to Cordova, sounds &gt;very &gt;compelling. I gues the biggest question is what will it take to acquire a &gt;few mentors / experts who know the inside of the Flex JS well enough to &gt;make &gt;progress with us to convert older code base into to current best practice &gt;code base. FlexJS is still in alpha/beta so there aren’t too many experts out there. Apache projects are largely volunteer-driven, and we are looking for folks to get involved by helping grow the framework, or being a guinea pig for code base conversion. &nbsp;If you are interested, I will do what I can to make it work for you. You mentioned responsive UI. &nbsp;I’m not sure what the best practices are today, especially in Flex, so I can’t say whether FlexJS currently supports it, but your project can influence the way FlexJS handles UI. &gt; &gt;Are you interested in having a chat with myself and my team? If you are interested in working with alpha or beta level code, then yes let’s have a chat next week or whenever you are ready. -Alex      If you reply to this email, your message will be added to the discussion below:  http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156p10180.html    To unsubscribe from Legacy Flex ( 3.0 ) upgrade to Open Source, click here .  NAML  






--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156p10182.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by Alex Harui <ah...@adobe.com>.

On 4/24/15, 5:01 PM, "david@achievelabs.com" <da...@achievelabs.com> wrote:

>Alex - Thank you for your interests! Flex JS output to Cordova, sounds
>very
>compelling. I gues the biggest question is what will it take to acquire a
>few mentors / experts who know the inside of the Flex JS well enough to
>make
>progress with us to convert older code base into to current best practice
>code base.

FlexJS is still in alpha/beta so there aren’t too many experts out there.
Apache projects are largely volunteer-driven, and we are looking for folks
to get involved by helping grow the framework, or being a guinea pig for
code base conversion.  If you are interested, I will do what I can to make
it work for you.

You mentioned responsive UI.  I’m not sure what the best practices are
today, especially in Flex, so I can’t say whether FlexJS currently
supports it, but your project can influence the way FlexJS handles UI.

> 
>Are you interested in having a chat with myself and my team?

If you are interested in working with alpha or beta level code, then yes
let’s have a chat next week or whenever you are ready.

-Alex


Re: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by "david@achievelabs.com" <da...@achievelabs.com>.
Alex - Thank you for your interests! Flex JS output to Cordova, sounds very
compelling. I gues the biggest question is what will it take to acquire a
few mentors / experts who know the inside of the Flex JS well enough to make
progress with us to convert older code base into to current best practice
code base. 
Are you interested in having a chat with myself and my team? 



--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156p10178.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by Alex Harui <ah...@adobe.com>.

On 4/23/15, 8:59 AM, "david@achievelabs.com" <da...@achievelabs.com> wrote:

>
>Our mobile platform is built on older Adobe Flex. Our system allows us to
>build complete learning programs using device detections, but not
>currently
>using Phone Gap or Cordova, or any responsive design.
>(non responsive design)
>
>I'd like to know how best to integrate the brilliance of this new code
>base
>and people behind it. I feel we are losing this battle unless we use
>updated
>, fully responsive code base.
>
>What if LearnCast became an open sourced solution, all build with the new
>Open FLEX stack.
>
>I'd like to know who / how / and timing for something like this.
>
>Is this possible ?

I don’t know much about LearnCast.  Have you been following discussions
about the progress on FlexJS?  It can output Cordova apps.

-Alex


Re: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by "david@achievelabs.com" <da...@achievelabs.com>.
OM,  Thank you for your notes and clear communication. 

The Update to 4.14.1 would be an effort for someone who already knows FLEX
and the most recent updates and new features of FLEX. Our goal is to make
our Platform very "responsive" because we are currently detecting 10,000 +
devices and setting up attributes for each device (Old School). But I want
to better understand what it will take to make this upgrade a reality. 

Flex has offered our Authoring side a really cool drag and drop UI / UX that
allows our users to quickly - simple actions to build out content pages with
instant previews. 

I now need to re-think Responsive design for the desktop , mobile tablets
etc. We want to keep current. 

If we can use our DB structures and add on and optimize - that would be a
very good idea ! 

David 





--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156p10179.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: Legacy Flex ( 3.0 ) upgrade to Open Source

Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Apr 23, 2015 10:02 AM, "david@achievelabs.com" <da...@achievelabs.com>
wrote:
>
>
> Our mobile platform is built on older Adobe Flex. Our system allows us to
> build complete learning programs using device detections, but not
currently
> using Phone Gap or Cordova, or any responsive design.
> (non responsive design)

The best bet would be to upgrade your app to Flex 4.14.1 (latest version)
and ensure that you follow the Flex mobile best practices.  This way you
can target the web, desktop, iOS and Android platforms all in one code
base. More details in this conference presentation:
https://www.youtube.com/watch?v=V8vT_IKLugw

>
> I'd like to know how best to integrate the brilliance of this new code
base
> and people behind it. I feel we are losing this battle unless we use
updated
> , fully responsive code base.

Depending on how your current codebase is architected, it would be a medium
to large effort to rewrite in Flex 4.14.  But it would be several times
costlier to move to Javascript/Phonegap route.  You will need to make the
choice based on your budget,  team skillset, etc.

>
> What if LearnCast became an open sourced solution, all build with the new
> Open FLEX stack.

If I understand you correct,  you want to open source your project under
the ASF banner?  I believe Apache Flex would not be an appropriate place
for LearnCast.  It might be better as a project on its own.  Look at
http://incubator.apache.org/ more details on how to bring a project into
ASF.

>
> I'd like to know who / how / and timing for something like this.
>

> Is this possible ?
>
> David

Thanks,

Om


>
>
>
> --
> View this message in context:
http://apache-flex-users.2333346.n4.nabble.com/Legacy-Flex-3-0-upgrade-to-Open-Source-tp10156.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.