OTOH, things that might be worth doing include: More FlexJS Components: "Easy" ones like DateChooser, ColorPicker. Hard ones like Tree and PieChart.
FlexJS Mobile Components: Mimic the ones in Flex mobile. FlexJS Mobile Publishing: Do what is needed to generate Cordova/PhoneGap projects or applications from FalconJX FlexJS Effects: Try to get some sort of Effects components to work. FlexJS ASDoc: Integrate it into the build, make sure everything has a comment. FlexJS Checkintest: Port the Flex SDK BasicTest. Comment out what we don't have in the component set. Try to get it to run. FlexJS and Falcon Release: Rat found a couple of dozen files in both FlexJS and Falcon that need headers. Installer Resource Management: I still don't understand why we hard code resources into the Installer in RuntimeLocale.as. Since I hope to make this the "last" installer release, it makes sense to me to un-hard-code the resources so that new resources can be added post release. We could use ResourceModules or simply read in properties files since all resources are currently text. I'm sure I'll think of moreŠ Thanks, -Alex On 1/12/14 12:24 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >That sounds like a good plan. > >Alex, I don't have any inspiration for my next 'project'. Is there >anything on your list I might be able to help with? > >EdB > > > >On Sun, Jan 12, 2014 at 7:55 AM, Alex Harui <aha...@adobe.com> wrote: >> Update: I've adjusted this plan a bit. There were issues like the >> installer.xml wants a basedir. I could copy it into the destination >> directory and run it from there, but then I have to not overwrite it >>when >> expanding the package. Also, the installer.xml wants to load some >> properties from files. >> >> However, what I want to know before the package is expanded is the >> licensing information which shouldn't rely on basedir. So my new plan >>is >> to create installer-config.xml files with the licensing info and we'll >>put >> those next to the release packages. Then the installer can pick that up >> early, offer up the licenses, then expand the package and run the >> installer script inside. >> >> Let me know if you see any problems with this approach, >> >> -Alex >> >> On 1/10/14 2:25 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >> >>>Hi, >>> >>>> Interesting. So we'd put the installer.xml files up separately on a >>>> server somewhere as part of release distribution? >>> >>>Could be either - but outside the zip with the release distribution >>>seems fine to me. >>> >>>Thanks, >>>Justin >> > > > >-- >Ix Multimedia Software > >Jan Luykenstraat 27 >3521 VB Utrecht > >T. 06-51952295 >I. www.ixsoftware.nl
