Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-20230] Auto-create storyboard from splash images

GitHub Issuen/a
TypeImprovement
PriorityMedium
StatusClosed
ResolutionWon't Fix
Resolution Date2016-10-03T23:11:39.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsiOS
Labelsn/a
ReporterRick Blalock
AssigneeEric Merriman
Created2016-01-13T18:30:33.000+0000
Updated2017-03-22T18:03:50.000+0000

Description

The current plan in 5.2 for storyboard support for launch images is great (especially since the iPad Pro requires it). However, we should not expect a Ti user to have to use XCode to do this. We should make it easier to support storyboard launch images without the Ti user having to use XCode. Whether that is packaging the provided image in to a storyboard we maintain, or some other way, we can discuss that here in this jira. Specifically: Users want to keep existing functionality where they provide an appropriately sized splash screen image (e.g. Default.png) and it will show on the appropriate device.

Comments

  1. Chee Kiat Ng 2016-01-14

    This was briefly discussed during the implementation of launchScreen.storyboard support. It is difficult not to break behavior and continue using splash images.

    A short explanation would be:

    1. it is not possible to distinguish between shorter screens and longer screens on the iPhone devices during ti build (Xcode project creation phase) 2. it is not possible to distinguish between landscape and portrait for iPad devices during ti build (Xcode project creation phase). 3. Apple doesn't advise the use of a static image if using launchScreen.storyboard. (and may eventually remove support for static splash screens) Because of 1 and 2, forcefully using the splash images will end up them being stretched out of proportion.

    Conclusion:

    Use the property to decide between using splash screens or launch screen for now. There is no way to reuse current splash screens into launch screen. We have to devise some method such as app designer to create launchScreen.storyboard without ti devs having to access Xcode.
  2. Chee Kiat Ng 2016-10-03

    After much discussion, closing this ticket as won't fix because no matter how we try to automate any creation of a static image to a storyboard, it's never optimal or pretty. If there's a strong need to use storyboard, it's advised to dive straight in and create a storyboard up to satisfaction instead of relying on a automated tool that might not do a good job.
  3. Lee Morris 2017-03-22

    Closing ticket as the issue will not fix and with reference to the above comments.

JSON Source