Current Week: [2024 Week 39] Improve Connect animation.

• 2024 Sep 29 13:38: commit: Add bounce to piece drop

  Following this MR: simple-boring-games/hello-world!24 I realized bounce is nice. It's not nicely implemented but it's better than nothing.

• 2024 Sep 29 11:16: commit: Constant paced piece drop animation

  For a start, I struggle with mathematics and if anyone wants to rewrite this please do so.

  This merge request makes the animation linear and non dependent on the piece position, i.e. the piece won't move slower if closer to the top. A drawback of this MR is there is it removes the bounce effect and the exponential acceleration. I have no idea how to add these features, although it could be nice to add one day.

  Without bounce + exponential acceleration it's not terrible, the linear drop looks clean for the user and the code looks nicer and easier to understand.

• 2024 Sep 29 00:50: commit: More beautiful logo for connect game

  Particular made it because it looks good in the bottom right. I.e. it seems more balanced.

  With these new changes:

  Current:

• 2024 Sep 28 23:33: commit: Fix disposing too early bug

• 2024 Sep 28 22:52: commit: Listen to extended logging feature flag

  If something goes wrong without warning or error messages, it's easy to switch a feature flag for further logging.

• 2024 Sep 28 20:46: commit: Add graceful shutdown to backend

  Trying to get back into the flow of things. A small cleanup too.

• 2024 Sep 28 19:31: commit: Copy build folder too

• 2024 Sep 28 19:05: commit: Fix script task name

• 2024 Sep 28 18:45: commit: Update Docker image identification to be commit SHA

• 2024 Sep 28 18:06: commit: Try to fix Hectoball build failure on main

• 2024 Sep 28 17:45: commit: Add Hectoball apps (iOS + Android) [no version]

• 2024 Sep 28 16:55: commit: Add BUILD numbers

  Automated build number increasing the number on main by 1

• 2024 Sep 28 15:09: commit: Automate versioning capacitor android and iOS projects

• 2024 Sep 28 13:46: commit: Check Runner performance after setting up local runner

  Would be good. So it's a bit unfortunate that we cannot prioritize our runner's to Gitlabs runners (in case ours are offline for some reason). See this open issue tracking a Gitlab runner priority feature: https://gitlab.com/gitlab-org/gitlab/-/issues/14976.

  If our runner is offline, enable Gitlab provided runners here under Runners: https://gitlab.com/simple-boring-games/hello-world/-/settings/ci_cd

  Update: So, it cuts the time by about half.

• 2024 Sep 28 05:23: commit: Detect which projects need version bump using pnpm

  With this MR when common is updated, each consuming application should be updated.

• 2024 Sep 28 03:55: commit: Prevent infinite loop if bug in bash script

• 2024 Sep 28 02:27: commit: New folder based versioning approach

  Instead of a global version (i.e. git tag), each folder maintains some kind of version file. This version file gets updated with each (pre) merge request pipeline.

  Scenarios:

  • Version is greater than main: do nothing
  • Version is less than main: throw error
  • Version is same as main: update PATCH by 1

  Idea is:

  • for external applications (i.e. games):
    • MAJOR bump for each massive change
    • MINOR bump for each release
    • PATCH bump with each merge request (automatic)
  • for services (i.e. backend): https://semver.org/
    • MAJOR for incompatible API changes
    • MINOR for added functionality in a backward compatible manner
    • PATCH for backward compatible bug fixes

  Reason I want this is because now we don't have an awkward single version for every single application (meaning the version will also make more sense for end users). Plus it's nice for the backend to use a semver version.