Resolve "Migrate to materialize.css" #427
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Alsijil!427
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "58-migrate-to-materialize-css"
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?
Closes #58
changed milestone to %"2.0a1"
added 1 commit
368915db- Migrate to materialize-css. Advances #58.Compare with previous version
assigned to @hansegucker
Maybe @hansegucker can have a quick look at the materialize stuff to verify that everything that looks correct was done correctly ;)…
unmarked as a Work In Progress
added 3 commits
masterc94f960d- Merge branch 'master' into 58-migrate-to-materialize-cssCompare with previous version
Why did you remove the title?
AlekSIS/AlekSIS#146
resolved all threads
After a first look, everything seems to be fine. I will test it later.
That's not materialize.
Please add class
greenfor optical feedback and add an text likeAdd filter.I think instead of having one card
Lessonswe should have a card for every weekday and remove the headingLessons.It may look better with
green-text.changed this line in version 3 of the diff
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
We should use theme-based colours for the buttons because every school can choose their own colours.
It's the question: Is optical feedback on actions (green: add, red: delete, etc.) more important than theme colours? The way materialize buttons are used in AlekSIS until now is the first one.
In bootstrap it looks much cleaner with only one card per week. Maybe you could post a screenshot from the week view later (I don't have working lessons, yet…).
Maybe you're right, yes. I will change that.
changed this line in version 5 of the diff
added 1 commit
9d21f053- Merge branch 'master' into 58-migrate-to-materialize-cssCompare with previous version
It is much clearer to use the background colour for the whole row.
What do you think, @nik?
added 1 commit
fe70659b- Fix title in templates.Compare with previous version
I have no clue. In case of doubt, @hansegucker makes better frontend decisions. But please post two screenshots.
Please post screenshots.
Hmm… maybe we should use one card for every weekday ;)…
I have to confess that I like the variant showed on 1 and 3, but the blue link is a little bit irritating. Maybe we should use a customized link colour.
So you think that we shouldn't use the lighten-2 class?
changed this line in version 7 of the diff
added 3 commits
c94f960d- Merge branch 'master' into 58-migrate-to-materialize-css782bc9ad- Use one card per weekday.48e71279- Merge branch '58-migrate-to-materialize-css' of...Compare with previous version
1 and 3 are too intense. If we use a background, then 2 and 4.
added 1 commit
fad76d47- Remove superflous text class.Compare with previous version
I agree with @nik.
@hansegucker: Feel free to mark this discussion as resolved if you agree too.
I have no problem with 2 and 4, but the link colour have to be changed definitely.
btn-dark?
btn-dark? Maybe add waves? Icon?
Red is correct here?
Looks like bootstrap.
Yup. With this button you can delete a filter.
Then the button shouldn't have the label "Add filter", should it? And the icon should be "delete".
added 2 commits
dc9b0668- fix tag.d1d5f989- Merge branch '58-migrate-to-materialize-css' of...Compare with previous version
added 1 commit
82d7539e- Fix link and text.Compare with previous version
btn-darkis the secondary colour so this button can be customized. I think we don't need an icon for the select button.btn-darkis the secondary colour so this button can be customized.changed this line in version 11 of the diff
changed this line in version 11 of the diff
added 2 commits
17f7a5f7- Fix templates.8fbd0847- Merge branch '58-migrate-to-materialize-css' of...Compare with previous version
Where is this class defined? In Materialize?
And the secondary colour is the default colour for buttons. It's unnecessary to add an extra CSS class for that.
Yes, you are right, the icon isn't necessary here.
For
btn-darksee above.Maybe you want to look at the code again ;)...
Aaaah okay i will remove it.
changed this line in version 12 of the diff
added 1 commit
36911718- Remove unnecessary class btn-dark.Compare with previous version
Which colour should we use for links?
In data tables, I think the links should not have a colour. The whole table row should be clickable (but the texts inside still need to be
<a>s to make it work without JavaScript, but they should not look like links.Opinion, @hansegucker
changed this line in version 13 of the diff
added 1 commit
978ecbb6- Use colour classes from core.Compare with previous version
In timetable.css in Chronos is a similar case.
changed this line in version 14 of the diff
added 1 commit
8d1f276b- Apply suggestion to aleksis/apps/alsijil/templates/alsijil/week_view.htmlCompare with previous version
resolved all threads
changed this line in version 15 of the diff
added 1 commit
e20f0de8- Apply suggestion to aleksis/apps/alsijil/templates/alsijil/week_view.htmlCompare with previous version
added 2 commits
127fdef9- Add stylesheet for links in datatables.94145366- Merge branch '58-migrate-to-materialize-css' of...Compare with previous version
bootstrap_form?I am not sure but if it's a form it should use material_form.
I am certain that a form with only hidden input fields does not need a Material theme.
That's correct.
resolved all threads
changed this line in version 17 of the diff
added 1 commit
d44ce23a- Use material_form.Compare with previous version
mentioned in commit
02cd44ea72merged