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

Implement empty numbering style #4811

Merged
merged 7 commits into from
Apr 3, 2024

Conversation

carlobeltrame
Copy link
Member

Fixes #4597

I found a more or less rational reason for this feature while setting up a camp myself. By using different numbering schemes for different categories, the activity numbers change less often when moving around some stuff on the picasso. And having roman numerals etc. for meals etc. may be perceived as too noisy.

@carlobeltrame carlobeltrame added the deploy! Creates a feature branch deployment for this PR label Mar 22, 2024
Copy link

github-actions bot commented Mar 22, 2024

Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

Copy link
Member

@manuelmeister manuelmeister left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very interesting.
I dislike the empty space, but I don't think that we should move the chip to the top in isolated cases (maybe if all categories have empty numbering styles?)

image

Besides that, it could be useful to have a schedule entry number deattached from the flow and instead only respect the current activity or category. e.g. 1. Nachtessen

@@ -8,7 +8,7 @@
<CategoryChip dense :category="activity.category()" />&thinsp;{{
$vuetify.breakpoint.smAndUp
? `${activity.title}: ${items[0].number}`
: items[0].number
: shortDescription(items[0])
Copy link
Member

@manuelmeister manuelmeister Mar 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be shorter. Maybe just the day and start time?
Also between "day" and the number there should be a non-breaking space.

image

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 9febee4

@carlobeltrame
Copy link
Member Author

I dislike the empty space, but I don't think that we should move the chip to the top in isolated cases (maybe if all categories have empty numbering styles?)

Maybe we could swap the category chip and number, so the category chip is always on top?

Besides that, it could be useful to have a schedule entry number deattached from the flow and instead only respect the current activity or category. e.g. 1. Nachtessen

I don't really understand what you mean. Can you elaborate or make a mockup?

@carlobeltrame
Copy link
Member Author

I dislike the empty space, but I don't think that we should move the chip to the top in isolated cases (maybe if all categories have empty numbering styles?)

Maybe we could swap the category chip and number, so the category chip is always on top?

Done in dda3ff2, check out whether you like that better.

@pmattmann
Copy link
Member

Counter-proposal:

The font of the number could also be smaller or in gray

image

@BacLuc
Copy link
Contributor

BacLuc commented Mar 31, 2024

It would be good if we had this numbering style in our development data

@carlobeltrame
Copy link
Member Author

It would be good if we had this numbering style in our development data

In bcf4a76, I set all meal categories (in all camps except for the snow camp) to the new empty numbering scheme, and in the Harry Potter camp I also added some material items and story context to one such activity.

@carlobeltrame
Copy link
Member Author

Counter-proposal:

The font of the number could also be smaller or in gray

image

For direct comparison, the current implementation looks like this:
Screenshot 2024-04-01 at 20-17-05 eCamp v3

Copy link
Contributor

@BacLuc BacLuc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the api tests come through, this is good for me

@carlobeltrame carlobeltrame dismissed manuelmeister’s stale review April 2, 2024 20:50

Implemented requested changes as far as they were understandable

@carlobeltrame carlobeltrame added deploy! Creates a feature branch deployment for this PR and removed deploy! Creates a feature branch deployment for this PR labels Apr 2, 2024
@carlobeltrame carlobeltrame added this pull request to the merge queue Apr 3, 2024
Merged via the queue into ecamp:devel with commit 47407d1 Apr 3, 2024
41 of 42 checks passed
@carlobeltrame carlobeltrame mentioned this pull request Apr 12, 2024
carlobeltrame added a commit to carlobeltrame/ecamp3 that referenced this pull request Apr 13, 2024
Follow-up from ecamp#4811
This does not change anything in the production database. It's just a
desperate attempt to not let the prod seeds and prod camp templates drift apart.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy! Creates a feature branch deployment for this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add numbering scheme for schedule entries without any number
4 participants