[ALOY-1040] Android: Bouncy logo does not appear while running sample alloy widget app
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Resolved |
| Resolution | Won't Fix |
| Resolution Date | 2014-06-06T16:17:41.000+0000 |
| Affected Version/s | Alloy 1.4.0 |
| Fix Version/s | n/a |
| Components | Widgets |
| Labels | parity, qe-3.3.0 |
| Reporter | Paras Mishra |
| Assignee | Tim Poulsen |
| Created | 2014-06-04T05:32:54.000+0000 |
| Updated | 2014-06-09T03:43:55.000+0000 |
Description
Android: Bouncy logo does not appear while running sample alloy widget app. It works fine on iOS simulator 7.1
Steps to reproduce:
1. Copy the app from https://github.com/appcelerator/alloy/tree/master/test/apps/widgets/widget_bouncylogo into an alloy project
2. Run the project
Expected:
Bouncy logo should appear
Actual:
Bouncy logo does not appear
Copying the app content from https://github.com/appcelerator/alloy/tree/master/test/apps/widgets/widget_bouncylogo into an new alloy project is presenting an issue displaying the bouncylogo. In this case, the bouncylogo is much bigger and when floating down, it might eventually end up hidden below the lower edge of the screen. The reason seems to be related to tiapp.xml property
If running the widget/widget_bouncylogo sample app using jake (as documented in the Alloy Git Repo)the ti.ui.defaultunit property in tiapp.xml is set as 'system' instead of dp:Using this configuration it works fine as expected. This is reproducible also using CLI 3.2.3,TiSDK 3.2.3GA and Alloy 1.3.1, so is not a regression.[~skypanther] How hard is that to fix?
That's fine. We should deprecate at least this widget in 1.4.0 and have this as a known issue. Can we point to some suggested ones to replace it?
This widget, along with the others in the Alloy repo, are deprecated as of the 1.4.0 release. They will be removed in a future version. The release notes will state that there are known issues, which will not be addressed. I will contact the original author of the modules and give them the opportunity to retake ownership & maintenance of their widgets. (For the bouncy logo widget specifically, see my comment describing the fix that a customer could apply -- account for the density factor -- if use of the widget were crucial.)
Please move tickets into your sprint before resolving them.