Improve backend module output #60
Conversation
…out, using Bootstrap classes
…e more independent regarding the widget ViewHelper template and be more integrative using default backend components
…but it's not the last step BackendTemplateView should be used
There was a problem hiding this comment.
Thank you for this PR. The backend module needs truly some refactoring. It is more or less the same since the beginning with TYPO3 4.7 (?).
Currently, it looks like this in my test setup with a screen resolution of 1920x1080:
With your changes it looks like this:
To be honest: It looks a bit broken. The search/filter fields above and the result listing shouldn't have a different width in my opinion.
Good idea but not ready to merge, I would say.
|
Please make shure the current stylesheet file was loaded, maybe it's needed to clear the cache to rebuild compressed ressources. The result should look like this, old house, new paint. 😄 |
There was a problem hiding this comment.
You're right. The backend slub-event-backend.css file is browser cached. The standard TYPO3 cache clear doesn't help here. That's always the trouble when changing styles of backend modules. I should remember that.
That's what it looks like now on my test setup with TYPO3 10.4.
So'll merge this.
Thank you again.
This pull request is about taking the backend modules closer to the TYPO3 defaults and contains one bugfix related to the FunctionBarViewHelper. No changes in the business logic were made.
The layout should be more responsive and some no longer used style definitions were deleted.
Just take a look at it. If everything is fine, merge it please, otherwise let's talk about it.