I’ll give this a go again on Sunday. Even if I do get this setup, the fact that I’m having so much trouble is probably an indicator that others who want to contribute will also.
Bottom line: The simpler we make it to contribute, the more likely we will get more contributors. The more contributors we have, the quicker FlexJS will mature and the more releases we can get out the door. (which should then be a self-feeding process) I think that making things simple should be higher priority than adding features because if things are simpler, features should be added quicker by default with more contributors. When I do get my IDE setup for working on the source, I will try to document the process on the wiki. Harbs On Nov 6, 2015, at 12:13 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote: > On Fri, Nov 6, 2015 at 2:02 AM, Harbs <harbs.li...@gmail.com> wrote: > >> I agree with Justin here. I’ve been playing with FlexJS for a good few >> weeks already and I still do not have a good setup for working on the SDK. >> I would have been productive a long time ago already if we would have the >> following: >> >> 1. Simple building of the SDK. Environment variables are tough to get >> right. Either Maven or some GUI which would help users set environment >> variables would be very helpful. >> 2. A way to make the SDK built from source IDE compatible. >> 3. Source linking between the source and built SDK. >> >> I think these three items will go a long way in adding contributors to the >> SDK and hopefully get out quicker releases. >> >> > I have been able to get 2 and 3 working for me. It's a bit tricky to setup > and I am not sure how to share that setup with others. > > For 2: I have checked in the Flash Builder project files for all the FlexJS > framework swc projects. Have you tried simply importing those Flex Library > projects into FlashBuilder all at once? What kind of errors are you seeing? > > For 3: After selecting FlexJS as your SDK in Flash Builder, you can simply > add the above mentioned Flex Library projects as 'project dependencies' to > the FlexJS app project. This way you can tweak the SDK code as you are > building up your FlexJS app example. Again, if you can try this setup and > let me know what errors you are getting, I can try to help you with that. > > Thanks, > Om > > >> On Nov 6, 2015, at 11:08 AM, Justin Mclean <justinmcl...@me.com> wrote: >> >>> HI, >>> >>>> Nobody is saying simpler builds wouldn’t help. But how much? >>> >>> A lot I think. Developer are unable to contribute if they can’t compile >> and test their changes. >>> >>>> More than a more functional DataGrid? Or a more Spark and/or MX-like >> component set >>>> that reduces migration time for your app? Or being able to write your >> JS >>>> using AS? >>> >>> IMO you would more likely get people contribution things like that if it >> was simpler to build. >>> >>>> To folks reading this who are interested in >>>> FlexJS: what is the most important two or three things we should be >>>> working on? >>> >>> IMO: >>> 1. Simpler builds >>> 2. More frequent releases (say every 3 or 4 months). >>> 3. Compiling MXML >>> 4. Working documented examples / how to port existing applications >>> >>>> The build script was improved in this release such that if you have a >>>> couple of known sets of circumstances, like not having any of the repos, >>>> that running “ant all” will get all the repos and build them in the >> right >>>> order. >>> >>> I meant to ask before does that use well known versions or does it just >> grab the latest out of the develop (or another) branch? >>> >>> Thanks, >>> Justin >> >>
