Skip to content

First Release Requirements (0.1.0) #54

Closed

Description

@RobDavenport

This is a tracking issue for any tasks which need to be completed prior to announcing our first real release. If theres any other tasks you think might be important or critical to it, please reply to this issue and make suggestions.

The "Nice To Haves" List I can see as being priority issues in the near future/future releases.

Hard Requirements:

Nice To Haves:

Activity

  1. pinned this issue on Sep 8, 2022
  2. Andre-LA commented on Sep 8, 2022

    @Andre-LA

    If possible add #9 to the list, otherwise making menus will be a bit harder to implement.

  3. RobDavenport commented on Sep 8, 2022

    @RobDavenport
    MemberAuthor

    Thanks for the suggestion @Andre-LA , unfortunately, there's still a lot of questions about how we want to handle this feature. For example, different font sizes for different resolutions, what exactly a "font" should be (bit depth, etc). The issue itself has more details about this though.

    Currently it would be possible to do a workaround by using sprite images as your "font" and just calling draw_sprite for each letter. Not ideal, but I expect that once the text feature is implemented it will just be sugar for that.

    Anyway I've added it as a "Nice to have" but realistically I think that, along with Gamepad support would be great for the 2nd major update.

  4. changed the title [-]First Release Requirements[/-] [+]First Release Requirements (0.1.0)[/+] on Sep 13, 2022
  5. unpinned this issue on Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions