Cavemanon
/
SnootGame
24
0
Fork 15
Code Issues 2 Pull Requests 2 Projects Releases 4 Wiki Activity

UI Overhaul #47

New Issue
Closed
opened 2021-07-01 05:14:36 +00:00 by MichaelYick · 11 comments
MichaelYick commented 2021-07-01 05:14:36 +00:00
Owner
Copy Link

(from https://git.snootgame.xyz/Cavemanon/SnootGame/issues/45#issuecomment-622)

I guess while I've been doing some UI changes, there's things I have noticed and/or needs to be done:

  • Lots of wasted real estate, text box isn't completely used and the font size is small, not ideal on larger monitors
  • Change All Bitmap Text on Buttons, to be instead just render actual ttf text onto the buttons similar to #11
  • Variant Save files difference, (3x2 vs 2x2)
  • Better color co-ordination & Font outline, both the background and font work against each other at times, like the deep FF blue text being hard to read against dark backgrounds
  • Alignment of Name Text, Currently not centered, left-aligned
  • Windowed resolutions, Has a weird default size
  • On Screen Keyboard Input consideration during Ending 4 for mobile phones
(from https://git.snootgame.xyz/Cavemanon/SnootGame/issues/45#issuecomment-622) I guess while I've been doing some UI changes, there's things I have noticed and/or needs to be done: - [X] Lots of wasted real estate, text box isn't completely used and the font size is small, not ideal on larger monitors - [X] Change All Bitmap Text on Buttons, to be instead just render actual ttf text onto the buttons similar to #11 - [X] Variant Save files difference, (3x2 vs 2x2) - [X] Better color co-ordination & Font outline, both the background and font work against each other at times, like the deep FF blue text being hard to read against dark backgrounds - [X] Alignment of Name Text, Currently not centered, left-aligned - [X] Windowed resolutions, Has a weird default size - [X] On Screen Keyboard Input consideration during Ending 4 for mobile phones
MichaelYick added the
Medium Priority
 label 2021-07-01 05:14:36 +00:00
MichaelYick added this to the Monster-Update-6 milestone 2021-07-01 05:14:52 +00:00
MichaelYick added the
enhancement
 label 2021-07-01 05:14:59 +00:00
Nio commented 2021-07-01 10:57:42 +00:00
Member
Copy Link

I am in the middle of trying to have a fork to help working on this (since I suppose this is the issue that we are using now for all UI related prettification). For some reason I can't create a fork, according to Git I own this repo and thus can't fork it. Not sure why.

Also, I wanna help out but I'm unsure if I can do that when someone else is already at this. ( e.g. Nutbuster , whom I can't refer to here because the editor doesn't recognize that nick) Happy to divide tasks within or focus on another one.

I am in the middle of trying to have a fork to help working on this (since I suppose this is the issue that we are using now for all UI related prettification). For some reason I can't create a fork, according to Git I own this repo and thus can't fork it. Not sure why. Also, I wanna help out but I'm unsure if I can do that when someone else is already at this. ( e.g. Nutbuster , whom I can't refer to here because the editor doesn't recognize that nick) Happy to divide tasks within or focus on another one.
Nio commented 2021-07-01 13:51:42 +00:00
Member
Copy Link

Did a quick look, for a keyboard we could do this:
https://lemmasoft.renai.us/forums/viewtopic.php?t=25972

I couldn't find anything on calling the system default/current keyboard on android, they have something in their github but it doesn't look like it has been put into the live version.

Did a quick look, for a keyboard we could do this: https://lemmasoft.renai.us/forums/viewtopic.php?t=25972 I couldn't find anything on calling the system default/current keyboard on android, they have something in their github but it doesn't look like it has been put into the live version.
MichaelYick commented 2021-07-01 15:13:09 +00:00
Author
Owner
Copy Link

For some reason I can't create a fork, according to Git I own this repo and thus can't fork it

you sure you're on the right repo? Not even I own this repo, its owned by the Cavemanon organization.

Also, I wanna help out but I'm unsure if I can do that when someone else is already at this

I think its possible, but it might cause some issues that would require fixing some merges, but other than that I don't see a reason not to. Maybe Nutbuster can weigh in on this.

>For some reason I can't create a fork, according to Git I own this repo and thus can't fork it you sure you're on the right repo? Not even I own this repo, its owned by the Cavemanon organization. >Also, I wanna help out but I'm unsure if I can do that when someone else is already at this I think its possible, but it might cause some issues that would require fixing some merges, but other than that I don't see a reason not to. Maybe Nutbuster can weigh in on this.
Nio commented 2021-07-01 16:34:30 +00:00
Member
Copy Link

you sure you're on the right repo? Not even I own this repo, its owned by the Cavemanon organization.

I think I am at least. See the attachment, the snippet was taken from https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Monster-Update-6 .

I think its possible, but it might cause some issues that would require fixing some merges, but other than that I don't see a reason not to. Maybe Nutbuster can weigh in on this.

Yep, I don't want to step on any toes.

> you sure you're on the right repo? Not even I own this repo, its owned by the Cavemanon organization. I think I am at least. See the attachment, the snippet was taken from https://git.snootgame.xyz/Cavemanon/SnootGame/src/branch/Monster-Update-6 . > I think its possible, but it might cause some issues that would require fixing some merges, but other than that I don't see a reason not to. Maybe Nutbuster can weigh in on this. Yep, I don't want to step on any toes.
repoowned.png
16 KiB
repoowned.png
nutbuster commented 2021-07-02 01:03:59 +00:00
Member
Copy Link

Currently working on most of the UI stuff, I guess I should make a WIP pull request but it mostly fixes both #47 and #9 (see android.jpg).
On the topic of the On-Screen Keyboard (OSK), it's only for one section of the ending and you just have to display the textbox higher up and just use the built-in OSK without having to create one from scratch, at worst it looks jank (but the android port is kind of 'doomed' to looking as pretty as possible since phones have a bajilion aspect ratios and weird screen shapes)

I will probably actually test the actual game on real hardware, since I do have a phone with 'standard' specs.

@Nio, You already have a fork: https://git.snootgame.xyz/Nio/SnootGame_w_ExtrasMenu

Currently working on most of the UI stuff, I guess I should make a WIP pull request but it mostly fixes both #47 and #9 (see android.jpg). On the topic of the On-Screen Keyboard (OSK), it's only for one section of the ending and you just have to display the textbox higher up and just use the built-in OSK without having to create one from scratch, at worst it looks jank (but the android port is kind of 'doomed' to looking as pretty as possible since phones have a bajilion aspect ratios and weird screen shapes) I will probably actually test the actual game on real hardware, since I do have a phone with 'standard' specs. @Nio, You already have a fork: https://git.snootgame.xyz/Nio/SnootGame_w_ExtrasMenu
osk.jpg
136 KiB
android.jpg
397 KiB
osk.jpg android.jpg
Nio commented 2021-07-02 04:55:05 +00:00
Member
Copy Link

Currently working on most of the UI stuff, I guess I should make a WIP pull request but it mostly fixes both #47 and #9 (see android.jpg).

I am not entire sure, but I can see a weird mono-colored box in each of the options just behind the texts in the screenshot. Not sure if you noticed it. I am not sure what that is, too regular for artifacting.

@Nio, You already have a fork: https://git.snootgame.xyz/Nio/SnootGame_w_ExtrasMenu

Oh, I don't usually use forks, so I don't really know them - you can only have one then, I presume?
Anyhow, I could use that to put the stuff you need me to work on - if any. Happy to help if I can.

@PrincipalSpears , will the revamped Extras menu go into Monster update 6?

I will probably actually test the actual game on real hardware, since I do have a phone with 'standard' specs.

Good idea, way back when I made a very simple android game I was running it on a virtual device and boy did it differ on the real thing :D Anyhow, I volunteer testing it on a physical device as well once we have a build ready to test.

> Currently working on most of the UI stuff, I guess I should make a WIP pull request but it mostly fixes both #47 and #9 (see android.jpg). I am not entire sure, but I can see a weird mono-colored box in each of the options just behind the texts in the screenshot. Not sure if you noticed it. I am not sure what that is, too regular for artifacting. > @Nio, You already have a fork: https://git.snootgame.xyz/Nio/SnootGame_w_ExtrasMenu Oh, I don't usually use forks, so I don't really know them - you can only have one then, I presume? Anyhow, I could use that to put the stuff you need me to work on - if any. Happy to help if I can. @PrincipalSpears , will the revamped Extras menu go into Monster update 6? > I will probably actually test the actual game on real hardware, since I do have a phone with 'standard' specs. Good idea, way back when I made a very simple android game I was running it on a virtual device and boy did it differ on the real thing :D Anyhow, I volunteer testing it on a physical device as well once we have a build ready to test.
nutbuster commented 2021-07-02 05:08:46 +00:00
Member
Copy Link

I am not entire sure, but I can see a weird mono-colored box in each of the options just behind the texts in the screenshot. Not sure if you noticed it. I am not sure what that is, too regular for artifacting.

I can't be bothered recreating the transparent gradient properly, was going to chalk it to the artists to give a clean image, it's way less noticable on the Quick Buttons however.

Oh, I don't usually use forks, so I don't really know them - you can only have one then, I presume?

Yeah, only one fork but you can have mulitple branches.

Anyhow, I could use that to put the stuff you need me to work on - if any. Happy to help if I can.

Probably be better to focus on other tasks, I'm just doing the UI stuff for now.

> I am not entire sure, but I can see a weird mono-colored box in each of the options just behind the texts in the screenshot. Not sure if you noticed it. I am not sure what that is, too regular for artifacting. I can't be bothered recreating the transparent gradient properly, was going to chalk it to the artists to give a clean image, it's way less noticable on the Quick Buttons however. > Oh, I don't usually use forks, so I don't really know them - you can only have one then, I presume? Yeah, only one fork but you can have mulitple branches. > Anyhow, I could use that to put the stuff you need me to work on - if any. Happy to help if I can. Probably be better to focus on other tasks, I'm just doing the UI stuff for now.
👍 1
Nio commented 2021-07-02 09:01:40 +00:00
Member
Copy Link

I can't be bothered recreating the transparent gradient properly, was going to chalk it to the artists to give a clean image, it's way less noticable on the Quick Buttons however.

We have the blank gradient buttons and the other ones as well, see attachments.
Also, if we use the new Extras menu (the one in my branch), we'll need more buttons (if you're resizing them for the mobile version that is). The round button is "reverse engineered" to the likeness of the original one, in lieu of that, but I think it turned out relatively nicely.

Probably be better to focus on other tasks, I'm just doing the UI stuff for now.

OK, will do.

>I can't be bothered recreating the transparent gradient properly, was going to chalk it to the artists to give a clean image, it's way less noticable on the Quick Buttons however. We have the blank gradient buttons and the other ones as well, see attachments. Also, if we use the new Extras menu (the one in my branch), we'll need more buttons (if you're resizing them for the mobile version that is). The round button is "reverse engineered" to the likeness of the original one, in lieu of that, but I think it turned out relatively nicely. > Probably be better to focus on other tasks, I'm just doing the UI stuff for now. > OK, will do.
blank_idle.png
4.3 KiB
buttonblank.png
7.5 KiB
blank_idle.png buttonblank.png
👍 1
MichaelYick commented 2021-07-04 01:26:24 +00:00
Author
Owner
Copy Link

@nutbuster did I get everything that c131ce6328 accomplished checked?

@nutbuster did I get everything that https://git.snootgame.xyz/Cavemanon/SnootGame/commit/c131ce6328edce89f170d6cea556714c1d45e915 accomplished checked?
nutbuster commented 2021-07-04 01:38:57 +00:00
Member
Copy Link

Yeah, and the save files are 3x2 - so everything in general is checked off.

Yeah, and the save files are 3x2 - so everything in general is checked off.
MichaelYick commented 2021-07-04 01:39:26 +00:00
Author
Owner
Copy Link

kewl

kewl
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
unbumoversion
fixcrash
russia
Patch9
NewPatch
Patch7
Patch9.1-RoastedLaika
Patch9-RoastedLaika
Monster-Updates-Release
MonsterUpdate
Labels
Clear labels   
bug

Something is not working

  
Critical Priority

Absolutely urgent issues that must be delt with before others can even be considered.

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
High Priority

Bugs that cause crashes, major story errors, or other massively negative issues. Features that are a must-have inclusion or else the game won't be as good.

  
Low Priority

Minor or easy to miss errors. Features that'd be nice, but can be done with out.

  
Medium Priority

Errors that stick out, but aren't fatal to gameplay. Features that are in decent demand or would improve gameplay by a signifigant amount

  
Meta

for all the other fun stuff about the project thats not code

  
needs more info

Something is wrong

  
question

   
refactor

Cleaning up the cruft

  
wontfix

This won't be fixed

  
bug

Something is not working

  
Critical Priority

Absolutely urgent issues that must be delt with before others can even be considered.

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
High Priority

Bugs that cause crashes, major story errors, or other massively negative issues. Features that are a must-have inclusion or else the game won't be as good.

  
invalid

Something is wrong

  
Low Priority

Minor or easy to miss errors. Features that'd be nice, but can be done with out.

  
Medium Priority

Errors that stick out, but aren't fatal to gameplay. Features that are in decent demand or would improve gameplay by a signifigant amount

  
Meta

for all the other fun stuff about the project thats not code

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
Low Priority
Medium Priority
Meta
needs more info
question
refactor
wontfix
bug
Critical Priority
duplicate
enhancement
help wanted
High Priority
invalid
Low Priority
Medium Priority
Meta
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Monster-Update-6
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Cavemanon/SnootGame#47
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?