Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Medical: language refactor #219

Merged
merged 6 commits into from
Oct 15, 2023
Merged

Medical: language refactor #219

merged 6 commits into from
Oct 15, 2023

Conversation

dastrukar
Copy link
Collaborator

Not sure if this is best way to handle the new LANGUAGE changes, but it should at least remove some redundant parts and tidy up some of the code.

note: still questioning on how to handle wound descriptions, and let me know if there's a cleaner way to implement the language stuff

code should be somewhat more bearable to read through
Trying out a new style/format (somewhat based on gzdoom's LANGUAGE file),
seems to make the LANGUAGE file more readable
the helptext stuff is a bit cursed, but it is more cleaner so eh

name format is something like this: [TYPE]_[THING]_[DESC] = ""
example: HELPTEXT_TRK_SCALPEL = "lorem ipsum"
CheckStrip is still used, but that's only for the worn layers thing
@dastrukar
Copy link
Collaborator Author

With 5c53e79, the trauma kit no longer uses LANGUAGE (or just hard-coded strings) to display the blocking item name. (excluding bandages and striptime)
So instead of displaying Take off your armour first!, it would say Take off your garrison armour first! (or whatever armour you have)
@caligari87 let me know if you'd prefer the original behaviour

@dastrukar
Copy link
Collaborator Author

@tedthedragon btw, what's the rationale behind moving all of the colour codes to LANGUAGE?
e.g. UAS_MEDICAL_UI_BLACK / UI_STATUS_BLACK

@caligari87
Copy link
Member

The dynamic tag usage is definitely preferred. I never really iterated on that part of the module past basic functionality anyway.

I like these changes, they make the code more readable for sure.

@dastrukar
Copy link
Collaborator Author

Thanks for the feedback :]

Anyways, assuming that ted's probably not going to respond, I'll just leave the colour stuff alone and mark this PR as ready to merge.

@dastrukar dastrukar changed the title [WIP] Medical: language refactor Medical: language refactor Oct 15, 2023
@dastrukar dastrukar marked this pull request as ready for review October 15, 2023 08:24
@caligari87 caligari87 merged commit 4dfcce5 into master Oct 15, 2023
@tedthedragon
Copy link
Member

@tedthedragon btw, what's the rationale behind moving all of the colour codes to LANGUAGE? e.g. UAS_MEDICAL_UI_BLACK / UI_STATUS_BLACK

My bad, I didn't get the notification that I was mentioned in this

The intention was, as I'm slightly colorblind, that I could modify the colors to have it be more visible for me to read for some of the wound changes and, if someone prefers a different UI color, they could also change it to their preferences.

@dastrukar
Copy link
Collaborator Author

Noted. Will keep that in mind if I end up messing with the LANGUAGE file in the future.

@dastrukar dastrukar deleted the medical-language-refactor branch October 16, 2023 08:09
@caligari87
Copy link
Member

I feel like addressing this through LANGUAGE is the wrong approach. It only solves one very small part of the problem, at the cost of a severe impact to code readability and development convenience.

A screen shader such as this seems like it would be a more comprehensive and reliable solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants