OpenNeo/impress
OpenNeo/impress
1
0
Fork 1
Code Pull requests Activity
impress/app/views/pet_states/edit.html.haml

46 lines
1.3 KiB
Text
Raw Normal View History

Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
- title "#{@pet_type.human_name}: #{pose_name @pet_state.pose}"
- use_responsive_design
%ol.breadcrumbs
%li
= link_to "Rainbow Pool", pet_types_path
%li
Handle new colors/species in the Rainbow Pool Oh right, yeah, we like to do things gracefully around here when there's no corresponding color/species record yet! Paying more attention to this, I'm thinking like… it could be a cool idea to, in modeling, *create* the new color/species record, and just not have all the attributes filled in yet? Especially now that we're less dependent on attributes like `standard` to be set for correct functioning. But for now, we follow the same strategy we do elsewhere in the app: a pet type can have `color_id` and `species_id` that don't correspond to a real record, and we cover over that smoothly.
2024-11-15 19:56:07 -08:00
= link_to @pet_type.possibly_new_color.human_name,
pet_types_path(color: @pet_type.possibly_new_color.human_name)
Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
%li{"data-relation-to-prev": "sibling"}
Handle new colors/species in the Rainbow Pool Oh right, yeah, we like to do things gracefully around here when there's no corresponding color/species record yet! Paying more attention to this, I'm thinking like… it could be a cool idea to, in modeling, *create* the new color/species record, and just not have all the attributes filled in yet? Especially now that we're less dependent on attributes like `standard` to be set for correct functioning. But for now, we follow the same strategy we do elsewhere in the app: a pet type can have `color_id` and `species_id` that don't correspond to a real record, and we cover over that smoothly.
2024-11-15 19:56:07 -08:00
= link_to @pet_type.possibly_new_species.human_name,
pet_types_path(species: @pet_type.possibly_new_species.human_name)
Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
%li
= link_to "Appearances", @pet_type
%li
Remove now-unused pet state show page
2024-10-11 17:48:23 -07:00
\##{@pet_state.id}
Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
= outfit_viewer pet_state: @pet_state
Add SupportFormBuilder to make the support form templates nicer Instead of hand-rolling HTML, this offers helpers like `f.field`, to help ensure the HTML is consistent, and to keep the templates more focused on the unique form elements.
2024-11-30 11:26:23 -08:00
= support_form_with model: [@pet_type, @pet_state] do |f|
Add `errors` helper to support form builder It still has no good CSS to it, but that's okay, this is just to DRY it up.
2024-11-30 11:46:19 -08:00
= f.errors
Add SupportFormBuilder to make the support form templates nicer Instead of hand-rolling HTML, this offers helpers like `f.field`, to help ensure the HTML is consistent, and to keep the templates more focused on the unique form elements.
2024-11-30 11:26:23 -08:00
= f.fields do
= f.radio_grid_fieldset "Pose" do
- pose_options.each do |pose|
= f.radio_field do
= f.radio_button :pose, pose
= pose_name(pose)
= f.field do
Migrate pet state edit form to .support-form class Most notable change here is extracting the pose option bubbles into a `data-type="radio-grid"`, and pulling that into the `.support-form` CSS. My rationale is that, unlike most fields, this field benefits from being 100%-width, and I don't want to specify that as an override if I can avoid it, because that's fragile-y. Instead, I extract this into a generic type of field that `.support-form` can use (it feels pretty reusable anyway!), and require the caller to specify how many columns they want as `--num-columns`.
2024-11-30 10:49:47 -08:00
= f.label :glitched, "Gliched?"
Use radio buttons for poses in Rainbow Pool form, instead of dropdown Just a bit easier to find what you want! especially with the grid layout
2024-09-27 22:34:52 -07:00
= f.select :glitched, [["✅ Not marked as Glitched", false],
Migrate pet state edit form to .support-form class Most notable change here is extracting the pose option bubbles into a `data-type="radio-grid"`, and pulling that into the `.support-form` CSS. My rationale is that, unlike most fields, this field benefits from being 100%-width, and I don't want to specify that as an override if I can avoid it, because that's fragile-y. Instead, I extract this into a generic type of field that `.support-form` can use (it feels pretty reusable anyway!), and require the caller to specify how many columns they want as `--num-columns`.
2024-11-30 10:49:47 -08:00
["👾 Yes, it's bad news bonko'd", true]]
Add `actions` helper to support form builder
2024-12-01 09:30:17 -08:00
= f.actions do
Migrate pet state edit form to .support-form class Most notable change here is extracting the pose option bubbles into a `data-type="radio-grid"`, and pulling that into the `.support-form` CSS. My rationale is that, unlike most fields, this field benefits from being 100%-width, and I don't want to specify that as an override if I can avoid it, because that's fragile-y. Instead, I extract this into a generic type of field that `.support-form` can use (it feels pretty reusable anyway!), and require the caller to specify how many columns they want as `--num-columns`.
2024-11-30 10:49:47 -08:00
= f.submit "Save changes"
Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
- content_for :stylesheets do
= stylesheet_link_tag "application/breadcrumbs"
= stylesheet_link_tag "application/outfit-viewer"
Migrate pet state edit form to .support-form class Most notable change here is extracting the pose option bubbles into a `data-type="radio-grid"`, and pulling that into the `.support-form` CSS. My rationale is that, unlike most fields, this field benefits from being 100%-width, and I don't want to specify that as an override if I can avoid it, because that's fragile-y. Instead, I extract this into a generic type of field that `.support-form` can use (it feels pretty reusable anyway!), and require the caller to specify how many columns they want as `--num-columns`.
2024-11-30 10:49:47 -08:00
= stylesheet_link_tag "application/support-form"
Use radio buttons for poses in Rainbow Pool form, instead of dropdown Just a bit easier to find what you want! especially with the grid layout
2024-09-27 22:34:52 -07:00
= page_stylesheet_link_tag "pet_states/edit"
Add edit form to Rainbow Pool for pet states, for support staff only
2024-09-27 22:14:00 -07:00
- content_for :javascripts do
= javascript_include_tag "outfit-viewer"
Copy permalink