-
Notifications
You must be signed in to change notification settings - Fork 898
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
Toolbar Redesign #6554
Labels
Comments
Closed
This was referenced Aug 2, 2016
This was referenced Aug 5, 2016
This was referenced Aug 5, 2016
This was referenced Aug 18, 2016
This was referenced Aug 25, 2016
This was referenced Oct 4, 2016
This was referenced Feb 24, 2017
This was referenced Mar 4, 2017
Merged
Merged
This issue has been automatically marked as stale because it has not been updated for at least 6 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So far we have
ApplicationHelper::ToolbarChooser
ToolbarHelper
ApplicationHelper::ToolbarBuilder
app/helpers/application_helper/button/*
(only a couple of buttons are converted, rest are normal hashes) --ApplicationHelper::Button::Basic
andApplicationHelper::ToolbarButtons
ApplicationHelper::Toolbar::Basic
).ToolbarButtons
case statement by moving button classes to the toolbar definition.ApplicationHelper::Toolbar::Basic
subclasses. Implement the more complex ones as subclasses ofApplicationHelper::Button::Basic
.Next
toolbar_builder
to separate button classes.ApplicationHelper::ToolbarBuilder
toApplicationHelper::Toolbar::Basic
ApplicationHelper::Toolbar::Basic
instead of logic around pre-defined buttons history_1...10 that are being removed when the toolbar is build.ApplicationHelper::Toolbar::Empty
or handle the case of empty toolbar in some simpler way.Once this is done, try to simplify it ;-)
The text was updated successfully, but these errors were encountered: