So with regards to this commit: b113caa
I've had overnight to think about this, and I'm wondering if it wouldn't be BETTER to refine this in a few ways:
- Restore the previous code using the arrows image, and wrap that code it in a conditional statement. Tie that to a NEW admin config option so that folks who CHOOSE to continue to use the arrow images CAN do so. The new Font Awesome implementation would be the default image display.
- Refine the Font Awesome implementation so that shopowners can enter the icon code from the shop admin. This way if they don't like the default icon, they can enter the icon code for the icon that they like OR if they say wanted to use a DIFFERENT font library (like Foundation Fonts), they could..
- Include support for stores that do not already have Font Awesome in place. Must not load if Font Awesome is already loaded.. For that last part, I'm thinking we can "borrow" the code lat9 used to do this very same thing in the CSS Buttons module.. 😺
Now that all said, I'm wondering if there shouldn't be supplemental files included to support those who insist on using that CSS JS Loader so that this module will work with it (and potentially avoid those questions)??? This would be similar to how there are COWOA merged files included in the Super Orders install package..
So with regards to this commit: b113caa
I've had overnight to think about this, and I'm wondering if it wouldn't be BETTER to refine this in a few ways:
Now that all said, I'm wondering if there shouldn't be supplemental files included to support those who insist on using that CSS JS Loader so that this module will work with it (and potentially avoid those questions)??? This would be similar to how there are COWOA merged files included in the Super Orders install package..