Details

      Description

      More and more lower devices have the capability to run AIR so also Apache Flex and this lower devices have screen DPI lower than the minimum 160.

      1. Working.png
        33 kB
        Hugo Ferreira
      2. WithBug.png
        33 kB
        Hugo Ferreira
      3. Screen Shot 2013-09-04 at 12.29.58 AM.png
        25 kB
        Hugo Ferreira
      4. Screen Shot 2013-09-04 at 12.29.26 AM.png
        79 kB
        Hugo Ferreira
      5. Screen Shot 2013-09-04 at 12.29.08 AM.png
        157 kB
        Hugo Ferreira
      6. Screen Shot 2013-09-04 at 12.28.47 AM.png
        91 kB
        Hugo Ferreira
      7. Screen Shot 2013-09-04 at 12.28.22 AM.png
        54 kB
        Hugo Ferreira
      8. RadioButton_240_DPI.png
        66 kB
        Hugo Ferreira
      9. RadioButton_120_DPI.png
        29 kB
        Hugo Ferreira
      10. MultiDPITest.fxp
        14 kB
        OmPrakash Muppirala
      11. MultiDPITest.fxp
        14 kB
        Hugo Ferreira
      12. MultiDPITest_v3.fxp
        24 kB
        Hugo Ferreira
      13. mobile.swc
        185 kB
        Justin Mclean
      14. 240DPI_View_TitleBar.png
        63 kB
        Hugo Ferreira
      15. 240DPI_ToggleSwitch_BorderLine.png
        72 kB
        Hugo Ferreira
      16. 240DPI_TitleBar_Button.png
        70 kB
        Hugo Ferreira
      17. 240DPI_RadioButton_CheckBox_Image.png
        56 kB
        Hugo Ferreira
      18. 240DPI_Callout.png
        70 kB
        Hugo Ferreira
      19. 160DPI_View_TitleBar.png
        47 kB
        Hugo Ferreira
      20. 160DPI_ToggleSwitch_BorderLine.png
        55 kB
        Hugo Ferreira
      21. 160DPI_TitleBar_Button.png
        52 kB
        Hugo Ferreira
      22. 160DPI_RadioButton_CheckBox_Image.png
        42 kB
        Hugo Ferreira
      23. 160DPI_Callout.png
        46 kB
        Hugo Ferreira
      24. 120DPI_View_TitleBar.png
        38 kB
        Hugo Ferreira
      25. 120DPI_ToggleSwitch_BorderLine.png
        42 kB
        Hugo Ferreira
      26. 120DPI_TitleBar_Button.png
        41 kB
        Hugo Ferreira
      27. 120DPI_RadioButton_CheckBox_Image.png
        37 kB
        Hugo Ferreira
      28. 120DPI_Callout.png
        39 kB
        Hugo Ferreira

        Activity

        Hugo Ferreira created issue -
        Hide
        Justin Mclean added a comment -

        The DPI values in Flex, just like in Android, are actually buckets rather than set values, currently 160 dpi mean less than 200 dpi and a 130 odd dpi device does fit into that Flex bucket. However flex is missing the 120 DPI bucket that Android has so are you asking for that to be added?

        Show
        Justin Mclean added a comment - The DPI values in Flex, just like in Android, are actually buckets rather than set values, currently 160 dpi mean less than 200 dpi and a 130 odd dpi device does fit into that Flex bucket. However flex is missing the 120 DPI bucket that Android has so are you asking for that to be added?
        Hide
        Hugo Ferreira added a comment -

        YES.
        Indeed I have the device and simple doesn't fit!

        The thing is if I cant find a workaround, I can lose this oportunity from my client!

        What can I do in meanwhile (workaround), please ?

        Can I samehow override de flex to fit in the screen-resolution until later we have this DPI ?

        Show
        Hugo Ferreira added a comment - YES. Indeed I have the device and simple doesn't fit! The thing is if I cant find a workaround, I can lose this oportunity from my client! What can I do in meanwhile (workaround), please ? Can I samehow override de flex to fit in the screen-resolution until later we have this DPI ?
        Hide
        Hugo Ferreira added a comment -

        Perhaps a new 120 DPI option means less the 160 DPI with smaller fonts and the developer could assign new smaller assets.

        Show
        Hugo Ferreira added a comment - Perhaps a new 120 DPI option means less the 160 DPI with smaller fonts and the developer could assign new smaller assets.
        Hide
        Justin Mclean added a comment -

        Yep that would be possible, you can take and look at the 480 dpi changes that were made and try to do the changes yourself (I guess it's a couple of hours work, it straight forward but a lot of changes) or Ill probably get to it next week sometime when I add the 640 dpi bucket as well. I'm not a designer so the skins I come up with may need a little tweaking.

        Show
        Justin Mclean added a comment - Yep that would be possible, you can take and look at the 480 dpi changes that were made and try to do the changes yourself (I guess it's a couple of hours work, it straight forward but a lot of changes) or Ill probably get to it next week sometime when I add the 640 dpi bucket as well. I'm not a designer so the skins I come up with may need a little tweaking.
        Hide
        Hugo Ferreira added a comment -

        Justin,

        You are the men!!!
        I don't know you but I'm your fan number 1 now!!!

        I'll wait for this. Do you have any idea when this will be available.
        Usually I only download the final Apache Flex version (4.9.1 and now 4.10).

        When this became available, how can I use it. I have to build the Flex framework ? There is any tutorial for that ?
        Sorry if I'm making questions that there are already answered somehere.

        Thank you so much,
        Hugo.

        Show
        Hugo Ferreira added a comment - Justin, You are the men!!! I don't know you but I'm your fan number 1 now!!! I'll wait for this. Do you have any idea when this will be available. Usually I only download the final Apache Flex version (4.9.1 and now 4.10). When this became available, how can I use it. I have to build the Flex framework ? There is any tutorial for that ? Sorry if I'm making questions that there are already answered somehere. Thank you so much, Hugo.
        Hide
        Justin Mclean added a comment -

        Next week sometime but it something more important comes up I'll be working on that.

        No need to compile the framework unless you want to. Just download the nightly build using the installer to get the very latest version.

        Show
        Justin Mclean added a comment - Next week sometime but it something more important comes up I'll be working on that. No need to compile the framework unless you want to. Just download the nightly build using the installer to get the very latest version.
        Justin Mclean made changes -
        Field Original Value New Value
        Summary Low density devices Low density devices (120 dpi bucket)
        Justin Mclean made changes -
        Assignee Justin Mclean [ jmclean ]
        Hide
        Hugo Ferreira added a comment -

        Superb.

        Once again, thank you very much Justin.

        Show
        Hugo Ferreira added a comment - Superb. Once again, thank you very much Justin.
        Justin Mclean made changes -
        Assignee Justin Mclean [ jmclean ] OmPrakash Muppirala [ bigosmallm ]
        Hide
        Justin Mclean added a comment -

        Added action script code and mustella tests, need new fxg skins in order to test.

        Show
        Justin Mclean added a comment - Added action script code and mustella tests, need new fxg skins in order to test.
        Hide
        OmPrakash Muppirala added a comment -

        Skins added. Assigning back to Justin.

        Show
        OmPrakash Muppirala added a comment - Skins added. Assigning back to Justin.
        OmPrakash Muppirala made changes -
        Assignee OmPrakash Muppirala [ bigosmallm ] Justin Mclean [ jmclean ]
        Hugo Ferreira made changes -
        Comment [ Since you already executed the musted tests, what is the next step ? This is already available thru Apache Flex nighlty builds ?
        Thank you very much. ]
        Hide
        Hugo Ferreira added a comment -

        I tried latest nightly build thru Apache Flex installer but still dont have 120 dpi bucket support.
        I saw from dev mailing list that this was finished in a separated branch a week ago. When this will be merged to the nightly build branch ?

        Thank you all,
        Hugo.

        Show
        Hugo Ferreira added a comment - I tried latest nightly build thru Apache Flex installer but still dont have 120 dpi bucket support. I saw from dev mailing list that this was finished in a separated branch a week ago. When this will be merged to the nightly build branch ? Thank you all, Hugo.
        Hide
        OmPrakash Muppirala added a comment -

        Hugo,

        The 120 dpi bucket support is still being worked upon and has not been merged into the develop branch yet.

        Thanks,
        Om

        Show
        OmPrakash Muppirala added a comment - Hugo, The 120 dpi bucket support is still being worked upon and has not been merged into the develop branch yet. Thanks, Om
        Hide
        Hugo Ferreira added a comment -

        OmPrakash,

        Thank you very much for your prompt reply.
        I need to use this urgently in a project. There is any predict date (more or less) for the merge so I can have an idea ?

        Thanks,
        Hugo.

        Show
        Hugo Ferreira added a comment - OmPrakash, Thank you very much for your prompt reply. I need to use this urgently in a project. There is any predict date (more or less) for the merge so I can have an idea ? Thanks, Hugo.
        Hide
        OmPrakash Muppirala added a comment -

        This is the long weekend here in the US, so I will be gone this weekend. I should be able to wrap up the skins in the next two weekends or so. Hope that helps

        Show
        OmPrakash Muppirala added a comment - This is the long weekend here in the US, so I will be gone this weekend. I should be able to wrap up the skins in the next two weekends or so. Hope that helps
        Hide
        Hugo Ferreira added a comment -

        OK OmPrakash,

        Thank you again for your reply. I know that this is now a community framework so ask about timming is not the philosophy of this but now I have an idea of the next step and I can try to gain more time to postpone the 120 dpi support on this project.

        Thanks again.

        Show
        Hugo Ferreira added a comment - OK OmPrakash, Thank you again for your reply. I know that this is now a community framework so ask about timming is not the philosophy of this but now I have an idea of the next step and I can try to gain more time to postpone the 120 dpi support on this project. Thanks again.
        Hide
        Justin Mclean added a comment -

        Currently the 120dpi works but has some issues - do you need just to start testing or to deploy?

        Show
        Justin Mclean added a comment - Currently the 120dpi works but has some issues - do you need just to start testing or to deploy?
        Hide
        Hugo Ferreira added a comment -

        I will first do a full test but its for deploy.

        Show
        Hugo Ferreira added a comment - I will first do a full test but its for deploy.
        Hide
        OmPrakash Muppirala added a comment -

        Good news. I was able to fix the assets for the 120, 480 and 640 dpis. I created a sample app and visually verified that all the components whose skins I touched looked good. I also tested the app on my (Android) Samsung Galaxy S3 phone. I dont see any problems with the skins.

        Justin, I think my part is done here. You can probably do more testing and merge the changes into into develop.

        Thanks,
        Om

        Show
        OmPrakash Muppirala added a comment - Good news. I was able to fix the assets for the 120, 480 and 640 dpis. I created a sample app and visually verified that all the components whose skins I touched looked good. I also tested the app on my (Android) Samsung Galaxy S3 phone. I dont see any problems with the skins. Justin, I think my part is done here. You can probably do more testing and merge the changes into into develop. Thanks, Om
        Hide
        OmPrakash Muppirala added a comment -

        This is the project that I used to test the components for which the skins were modified/generated.

        Show
        OmPrakash Muppirala added a comment - This is the project that I used to test the components for which the skins were modified/generated.
        OmPrakash Muppirala made changes -
        Attachment MultiDPITest.fxp [ 12600941 ]
        Hide
        Hugo Ferreira added a comment -

        This is great news!
        When this feature becomes available on the nightly build, I will use and test in a real 120 dpi bucket device and report the results.

        Show
        Hugo Ferreira added a comment - This is great news! When this feature becomes available on the nightly build, I will use and test in a real 120 dpi bucket device and report the results.
        Hide
        Justin Mclean added a comment -

        Merged into develop branch and will be available in nightly build.

        Show
        Justin Mclean added a comment - Merged into develop branch and will be available in nightly build.
        Justin Mclean made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Justin Mclean made changes -
        Fix Version/s Apache Flex 4.11.0 [ 12324778 ]
        Hide
        Hugo Ferreira added a comment -

        Main screen in 120 DPI

        Show
        Hugo Ferreira added a comment - Main screen in 120 DPI
        Hugo Ferreira made changes -
        Hide
        Hugo Ferreira added a comment -

        Main screen in 160 DPI

        Show
        Hugo Ferreira added a comment - Main screen in 160 DPI
        Hugo Ferreira made changes -
        Hide
        Hugo Ferreira added a comment -

        Main screen in 240 DPI

        Show
        Hugo Ferreira added a comment - Main screen in 240 DPI
        Hugo Ferreira made changes -
        Hide
        Hugo Ferreira added a comment -

        Callout in 120 DPI

        Show
        Hugo Ferreira added a comment - Callout in 120 DPI
        Hugo Ferreira made changes -
        Hide
        Hugo Ferreira added a comment -

        Callout in 240 DPI

        Show
        Hugo Ferreira added a comment - Callout in 240 DPI
        Hugo Ferreira made changes -
        Hide
        Hugo Ferreira added a comment - - edited

        Thank you very much Justin and OmPrakash.

        I did the following:
        1. Download the Nighlty Build after a sucessfull with this new feature;
        2. Update all assets to less 50% size from 240 DPI
        3. Add all 120 DPI reference in code
        4. Test the app

        At first I found 2 issues:
        1. Font size is too small
        2. Callout is too big

        See attachment files.

        Thank you very much.

        Show
        Hugo Ferreira added a comment - - edited Thank you very much Justin and OmPrakash. I did the following: 1. Download the Nighlty Build after a sucessfull with this new feature; 2. Update all assets to less 50% size from 240 DPI 3. Add all 120 DPI reference in code 4. Test the app At first I found 2 issues: 1. Font size is too small 2. Callout is too big See attachment files. Thank you very much.
        Hugo Ferreira made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Hugo Ferreira made changes -
        Comment [ Thank you very much Justin and OmPrakash.

        I did the following:
        1. Download the Nighlty Build after a sucessfull with this new feature;
        2. Update all assets to less 50% size from 240 DPI
        3. Add all 120 DPI reference in code
        4. Test the app

        At first I found 2 issues:
        1. Font size is too small
        2. Callout is too big

        See attachment files.

        Thank you very much. ]
        Hide
        Justin Mclean added a comment -

        Re font size being too small is that in general or only in certain components?

        Show
        Justin Mclean added a comment - Re font size being too small is that in general or only in certain components?
        Hide
        Hugo Ferreira added a comment -

        In general.

        You can see the first screenshoot (main screen of the app) and the last screenshoot (a particular screen in the app) and you can also see the comparision with the same app in different DPIs (160 and 240).

        Show
        Hugo Ferreira added a comment - In general. You can see the first screenshoot (main screen of the app) and the last screenshoot (a particular screen in the app) and you can also see the comparision with the same app in different DPIs (160 and 240).
        Hide
        Hugo Ferreira added a comment -

        Radio Buttons in 120 DPI

        Show
        Hugo Ferreira added a comment - Radio Buttons in 120 DPI
        Hugo Ferreira made changes -
        Attachment RadioButton_120_DPI.png [ 12601480 ]
        Hide
        Hugo Ferreira added a comment -

        Radio Buttons in 240 DPI

        Show
        Hugo Ferreira added a comment - Radio Buttons in 240 DPI
        Hugo Ferreira made changes -
        Attachment RadioButton_240_DPI.png [ 12601481 ]
        Hide
        Hugo Ferreira added a comment -

        I found another bug.
        Radio Buttons still don't support the new 120 DPI configuration (see attachments).

        Show
        Hugo Ferreira added a comment - I found another bug. Radio Buttons still don't support the new 120 DPI configuration (see attachments).
        Hide
        Hugo Ferreira added a comment -

        Those are bugs easy to fix (general fonts size too small, callout and radiobuttons too big) ?
        There is any workaround that I can apply until we have this fixed ?

        Thank you in advance.

        Show
        Hugo Ferreira added a comment - Those are bugs easy to fix (general fonts size too small, callout and radiobuttons too big) ? There is any workaround that I can apply until we have this fixed ? Thank you in advance.
        Hugo Ferreira made changes -
        Attachment Working.png [ 12601692 ]
        Hugo Ferreira made changes -
        Attachment WithBug.png [ 12601693 ]
        Hide
        Hugo Ferreira added a comment -

        I tested the 120 DPI in a new project (test project) and worked like a charm!
        Then I started investigating whats was going wrong and finally I found the bug.

        If you set applicationDPI="160" (autoscale without your own assets) in the ViewNavigatorApplication the RadioButton, fonts and even the titlebar works perfectly but if you ommit this attribute (like I do) for set your own assets in different sizes, then I will find the bug.

        See Working.png and WithBug.png in attachment.

        So, this should be a little bug somehere with a huge impact.

        Show
        Hugo Ferreira added a comment - I tested the 120 DPI in a new project (test project) and worked like a charm! Then I started investigating whats was going wrong and finally I found the bug. If you set applicationDPI="160" (autoscale without your own assets) in the ViewNavigatorApplication the RadioButton, fonts and even the titlebar works perfectly but if you ommit this attribute (like I do) for set your own assets in different sizes, then I will find the bug. See Working.png and WithBug.png in attachment. So, this should be a little bug somehere with a huge impact.
        Hide
        Hugo Ferreira added a comment -

        One last detail. I fully test the app with applicationDPI="320" running in a real device with 133 DPI (120 bucket DPI) and everything worked perfectly (fonts, components, etc ...)

        So, I guess that this should be a single issue.

        Show
        Hugo Ferreira added a comment - One last detail. I fully test the app with applicationDPI="320" running in a real device with 133 DPI (120 bucket DPI) and everything worked perfectly (fonts, components, etc ...) So, I guess that this should be a single issue.
        Hide
        Justin Mclean added a comment -

        Thanks for all the testing I see if I work out what the issue is over the weekend.

        Show
        Justin Mclean added a comment - Thanks for all the testing I see if I work out what the issue is over the weekend.
        Hide
        Hugo Ferreira added a comment -

        No, thank you for providing 120 DPI support in this short time. It's crucial for this project that I have in my hands.

        At the end of the day, everything is perfect (fonts, flex assets, components, etc...). According to the results of my tests, this should be a central little issue that for non-static DPI app (without applicationDPI property), the Flex-SDK is assuming an higher DPI when run in 120 DPI device (my guess). This app have all the assets in the propor size (using MultiDPIBitmapSource for images) and custom components (that extends directly from the Flex-SDK) and deal with different DPI so using non-static DPI it's very important.

        I will look forward for this fix. Please let me know if you need more information or test cases.

        Show
        Hugo Ferreira added a comment - No, thank you for providing 120 DPI support in this short time. It's crucial for this project that I have in my hands. At the end of the day, everything is perfect (fonts, flex assets, components, etc...). According to the results of my tests, this should be a central little issue that for non-static DPI app (without applicationDPI property), the Flex-SDK is assuming an higher DPI when run in 120 DPI device (my guess). This app have all the assets in the propor size (using MultiDPIBitmapSource for images) and custom components (that extends directly from the Flex-SDK) and deal with different DPI so using non-static DPI it's very important. I will look forward for this fix. Please let me know if you need more information or test cases.
        Hide
        Justin Mclean added a comment -

        Fixes font size issue, replace existing file in /frameworks/themes/Mobile with this file.

        Show
        Justin Mclean added a comment - Fixes font size issue, replace existing file in /frameworks/themes/Mobile with this file.
        Justin Mclean made changes -
        Attachment mobile.swc [ 12601733 ]
        Hide
        Justin Mclean added a comment -

        Checked in a fix into develop for the 120 font size issue, was just an issue with the mobile theme CSS.

        Show
        Justin Mclean added a comment - Checked in a fix into develop for the 120 font size issue, was just an issue with the mobile theme CSS.
        Hide
        Hugo Ferreira added a comment -

        Thanks Justin.

        I tested and the fonts are now fixed but the title bar and components are still giant. Probably another small thing somewhere that affects the components and views.

        Show
        Hugo Ferreira added a comment - Thanks Justin. I tested and the fonts are now fixed but the title bar and components are still giant. Probably another small thing somewhere that affects the components and views.
        Hide
        Justin Mclean added a comment -

        Other than radio button and callout mentioned above are you saying there are other issues?

        Show
        Justin Mclean added a comment - Other than radio button and callout mentioned above are you saying there are other issues?
        Hide
        Hugo Ferreira added a comment -

        It seems that the remaining issues are only for radio buttons, callout and view titlebar but it's difficult to have 100% sure without those first 3 items fixed but seems that it's a problem only with those 3 items, yes.

        Show
        Hugo Ferreira added a comment - It seems that the remaining issues are only for radio buttons, callout and view titlebar but it's difficult to have 100% sure without those first 3 items fixed but seems that it's a problem only with those 3 items, yes.
        Hide
        Hugo Ferreira added a comment -

        Hi justin,

        I did more tests (some items are hidden because of the titlebar, etc ...) but I managed to find all the issues and also compare with Flex autosize (applicationDPI="240" and run in 120 DPI device).

        Components that I found that shows bigger:

        • View titlebar
        • TabbedViewNavigator
        • Callout
        • RadioButton
        • CheckBox

        Important issues founded:

        • Space between FormItems

        Not important (dont affect to much) issues founded:

        • ToggleSwitch borderline (this is just a detail but without applicationDPI set the border line seems a little bigger)
        • TextInput round corner should have less radius

        Sorry for only now show the complete report but it's not easy with the current release.

        Thanks.

        Show
        Hugo Ferreira added a comment - Hi justin, I did more tests (some items are hidden because of the titlebar, etc ...) but I managed to find all the issues and also compare with Flex autosize (applicationDPI="240" and run in 120 DPI device). Components that I found that shows bigger: View titlebar TabbedViewNavigator Callout RadioButton CheckBox Important issues founded: Space between FormItems Not important (dont affect to much) issues founded: ToggleSwitch borderline (this is just a detail but without applicationDPI set the border line seems a little bigger) TextInput round corner should have less radius Sorry for only now show the complete report but it's not easy with the current release. Thanks.
        Hide
        OmPrakash Muppirala added a comment -

        Hugo,

        Did you get a chance to test the sample app I attached to this ticket?
        It would be easier to fix if we work on the same test cases.

        Please feel free to modify the project and reattach it to this ticket

        Show
        OmPrakash Muppirala added a comment - Hugo, Did you get a chance to test the sample app I attached to this ticket? It would be easier to fix if we work on the same test cases. Please feel free to modify the project and reattach it to this ticket
        Hide
        Hugo Ferreira added a comment -

        OmPrakash,

        You are right. I just tested and if you remove applicationDPI="120" from the MultiDPITest.mxml you will see everything I mention before in 120 DPI device (you could try for example with HTC Wildfire profile in Flash Builder AIR emulator).

        If I design my application for example for 240 DPI application and let Flex re-layout the application for 120 DPI everything seems to work but I dont want that because I use my own assets (for pixel perfect and best performance).

        Not using applicationDPI set property have 2 big advantages:

        • Pixel perfect in all supported densities
        • Better performance (Flex dont have to re-layout the assets)

        2 disadvantage:

        • I have to supply every asset in different size (using MultiDPIBitmapSource)
        • Dont work for specific with size (TextInput for example) but I already extended this components and deal with that automatically
        Show
        Hugo Ferreira added a comment - OmPrakash, You are right. I just tested and if you remove applicationDPI="120" from the MultiDPITest.mxml you will see everything I mention before in 120 DPI device (you could try for example with HTC Wildfire profile in Flash Builder AIR emulator). If I design my application for example for 240 DPI application and let Flex re-layout the application for 120 DPI everything seems to work but I dont want that because I use my own assets (for pixel perfect and best performance). Not using applicationDPI set property have 2 big advantages: Pixel perfect in all supported densities Better performance (Flex dont have to re-layout the assets) 2 disadvantage: I have to supply every asset in different size (using MultiDPIBitmapSource) Dont work for specific with size (TextInput for example) but I already extended this components and deal with that automatically
        Hide
        OmPrakash Muppirala added a comment -

        Makes sense.

        In that case, maybe you could attach a simple test case where your skins don't show up properly?

        I think you can use the same project and apply your skins and attach it.

        Thanks,
        Om

        Show
        OmPrakash Muppirala added a comment - Makes sense. In that case, maybe you could attach a simple test case where your skins don't show up properly? I think you can use the same project and apply your skins and attach it. Thanks, Om
        Hugo Ferreira made changes -
        Attachment 120DPI_Callout.png [ 12602000 ]
        Attachment 120DPI_RadioButton_CheckBox_Image.png [ 12602001 ]
        Attachment 120DPI_ToggleSwitch_BorderLine.png [ 12602002 ]
        Attachment 120DPI_View_TitleBar.png [ 12602003 ]
        Attachment 160DPI_Callout.png [ 12602004 ]
        Attachment 160DPI_RadioButton_CheckBox_Image.png [ 12602005 ]
        Attachment 160DPI_ToggleSwitch_BorderLine.png [ 12602006 ]
        Attachment 160DPI_View_TitleBar.png [ 12602007 ]
        Attachment 240DPI_Callout.png [ 12602008 ]
        Attachment 240DPI_RadioButton_CheckBox_Image.png [ 12602009 ]
        Attachment 240DPI_ToggleSwitch_BorderLine.png [ 12602010 ]
        Attachment 240DPI_View_TitleBar.png [ 12602011 ]
        Attachment MultiDPITest.fxp [ 12602012 ]
        Hide
        Hugo Ferreira added a comment -

        OK,

        I did another deep test in both projects (my project and the test project - now without specific DPI and also updated here, also several new screenshoots from the test project).

        1. View TitleBar - You can see that the height is smaller in 160 DPI than in 240 DPI but the 120 DPI have the same size as 160 DPI but should be also smaller than 160 DPI
        2. Callout - You can see a slightly lower border in 160 DPI than in 240 DPI but giant in 120 DPI
        3. RadioButtons, CheckBoxs and Images - You can see that they are smaller in 160 DPI than in 240 DPI but the 120 DPI have the same size as 240 DPI
        4. ToggleSwitch border line - You can see that in 160 DPI is slightly lower than 240 DPI but the 120 DPI have the same size as 240 DPI

        About the other issues that I mention before:
        1. TabbedViewNavigator - It was a missing port to 120 DPI in my own project - already fixed
        2. Space between form items - I realize that they are the same independent of the DPI, so I will manage myself this problem
        3. TextInput round corder/radius - They are all also the same independent of the DPI and this is not a problem

        Show
        Hugo Ferreira added a comment - OK, I did another deep test in both projects (my project and the test project - now without specific DPI and also updated here, also several new screenshoots from the test project). 1. View TitleBar - You can see that the height is smaller in 160 DPI than in 240 DPI but the 120 DPI have the same size as 160 DPI but should be also smaller than 160 DPI 2. Callout - You can see a slightly lower border in 160 DPI than in 240 DPI but giant in 120 DPI 3. RadioButtons, CheckBoxs and Images - You can see that they are smaller in 160 DPI than in 240 DPI but the 120 DPI have the same size as 240 DPI 4. ToggleSwitch border line - You can see that in 160 DPI is slightly lower than 240 DPI but the 120 DPI have the same size as 240 DPI About the other issues that I mention before: 1. TabbedViewNavigator - It was a missing port to 120 DPI in my own project - already fixed 2. Space between form items - I realize that they are the same independent of the DPI, so I will manage myself this problem 3. TextInput round corder/radius - They are all also the same independent of the DPI and this is not a problem
        OmPrakash Muppirala made changes -
        Assignee Justin Mclean [ jmclean ] OmPrakash Muppirala [ bigosmallm ]
        Hide
        OmPrakash Muppirala added a comment -

        I have checked in fixes for TitleBar/ActionBar, Callout, RadioButton and ToggleSwitch skins for 120 dpi. Please test it after you get the next nightly build.

        Thanks,
        Om

        Show
        OmPrakash Muppirala added a comment - I have checked in fixes for TitleBar/ActionBar, Callout, RadioButton and ToggleSwitch skins for 120 dpi. Please test it after you get the next nightly build. Thanks, Om
        Hugo Ferreira made changes -
        Attachment 120DPI_TitleBar_Button.png [ 12602053 ]
        Attachment 160DPI_TitleBar_Button.png [ 12602054 ]
        Attachment 240DPI_TitleBar_Button.png [ 12602055 ]
        Attachment MultiDPITest_v3.fxp [ 12602056 ]
        Hide
        Hugo Ferreira added a comment - - edited

        I just retest everything.

        Fixed in this commit:

        • Callout
        • RadioButton
        • ToggleSwitch border line
        • View TitleBar withtout button action

        Still in the same:

        • View TitleBar with button action (probably a missing fix in action content)
        • CheckBox (from your commit list, this is probably a missing component to fix or ommited in the commit)

        You can find in attachment 3 new screenshoots for the titlebar with button action issue and also the demo project updated.

        Thank you very much.

        Show
        Hugo Ferreira added a comment - - edited I just retest everything. Fixed in this commit: Callout RadioButton ToggleSwitch border line View TitleBar withtout button action Still in the same: View TitleBar with button action (probably a missing fix in action content) CheckBox (from your commit list, this is probably a missing component to fix or ommited in the commit) You can find in attachment 3 new screenshoots for the titlebar with button action issue and also the demo project updated. Thank you very much.
        Hide
        Justin Mclean added a comment -

        I've sorted out both issues, just testing and will check in shortly.

        Show
        Justin Mclean added a comment - I've sorted out both issues, just testing and will check in shortly.
        Hide
        Justin Mclean added a comment -

        Checked into develop branch - ActionBar and ActionBar button skins still need a little work.

        Show
        Justin Mclean added a comment - Checked into develop branch - ActionBar and ActionBar button skins still need a little work.
        Hide
        Hugo Ferreira added a comment -

        I just retest everything.

        All the mentioned components are working perfectly now. Thank you very much to all.
        It's possible that one component or feature that I never used may still have issues (but it's not very likely), however if in a near future I detect that, I will create a new jira entry.

        Once again, thank you very much for all your efforts. This is the big difference from Adobe Flex to Apache Flex.

        Show
        Hugo Ferreira added a comment - I just retest everything. All the mentioned components are working perfectly now. Thank you very much to all. It's possible that one component or feature that I never used may still have issues (but it's not very likely), however if in a near future I detect that, I will create a new jira entry. Once again, thank you very much for all your efforts. This is the big difference from Adobe Flex to Apache Flex.
        Hide
        Hugo Ferreira added a comment -

        I just rested everything and the 120 DPI is now fully supported.

        Show
        Hugo Ferreira added a comment - I just rested everything and the 120 DPI is now fully supported.
        Hugo Ferreira made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Hide
        OmPrakash Muppirala added a comment -

        Thanks Hugo, for testing all this and giving so much feedback. You have contributed to the community as much as we did, as well. All the best for your project!

        Om

        Show
        OmPrakash Muppirala added a comment - Thanks Hugo, for testing all this and giving so much feedback. You have contributed to the community as much as we did, as well. All the best for your project! Om
        Hide
        Hugo Ferreira added a comment -

        Thank you OmPrakash. I wish in a near future that this project grows up and could be a successful use case using Apache Flex.

        Regards,
        Hugo.

        Show
        Hugo Ferreira added a comment - Thank you OmPrakash. I wish in a near future that this project grows up and could be a successful use case using Apache Flex. Regards, Hugo.

          People

          • Assignee:
            OmPrakash Muppirala
            Reporter:
            Hugo Ferreira
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development