On Thu, Jul 12, 2012 at 12:43 PM, Carol Frampton (JIRA) <j...@apache.org>wrote:
> > [ > https://issues.apache.org/jira/browse/FLEX-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413114#comment-13413114] > > Carol Frampton commented on FLEX-33106: > --------------------------------------- > > Hi Om, > > re: Integrated Carol's patch for env.AIR_HOME variable in build.properties > > Only half of the patch was integrated in. Line 23 and line 24 from the > attached build.xml dated July 10th are missing. > The missing lines are > <!--load environment variables prefixed with env --> > <property environment="env"/> > > Fixed. > When installing, I said I did not want to download either osmf.swc or > textLayout.swc yet it let me proceed with the install. These components > are not optional so it should not have let me proceed. The NEXT button > should stay grey until I agree is selected for both of these. > What if the user does not agree to these licenses? Can they not use the entire Flex SDK because of that? Can we let the user make the conscious decision of not choosing these two components and let them finish the rest of the installation? For example, I dont think I have ever used the OSMF functionality ever. In any case, I have fixed this issue now. Please take a look. > > I think a better design might be to separate these into two screen. One > screen has osmf and textLayout with the mpl license and an "I Agree" > button. When/if that is selected the NEXT button becomes active and you > proceed to the optional component screen. The NEXT button is active since > the optional components are optional and you should be able to click thru. > > Please test the current build and let me know if the UI makes works. If not, I will rework the UI tonight as you have suggested. Thanks, Om
