Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey there 1000camels. Thanks for the suggestion here; this is a solid point but is admittedly a bit outside my area of expertise. As such I’ve asked the dev leading the charge on this plugin to comment directly. He’ll do so when he hits the forum next.

    We definitely are working forward with responsiveness in mind. While it’s still a couple months out, this is in the works and we’re excited to share what it ultimately becomes ??

    Thanks for the heads up, and for your support. Let me know if we can do anything else down the road.

    Hi, 1000camels!

    Sorry for the delayed response regarding the container ids, I seem to have let this post temporarily slip through the cracks. You have, in fact, found one of the weaknesses with our current architecture. We had a discussion regarding this, and while you’re absolutely correct that we should have a more specific id for those containers (tec-content, for example), we decided that it would most likely be more of a problem for more users at this point if we changed it. Perhaps in a future large-scale update (i.e. 3.0), we’ll be able to remedy this problem, but for now we’re a little bit stuck with the way it is.

    I hope that makes sense, and I hope it doesn’t affect your ability to use the plugin too negatively.

    Happy coding!

    – Paul

    Thread Starter 1000camels

    (@1000camels)

    Hi Paul,

    Thanks for getting back to me. I understand the issue, but I still think this is an important enough issue to address sooner than later.

    If I may ask, how do you handle style changes, because technically any style change you make (including renaming an id) could affect someone’s custom styles.

    ids in general are not good style hooks, because they require aggressive rules to override. also better to use classes. if you do an audit on how people override your styles, you’ll likely see how you id and class names are not optimal. I’ve worked on large projects where we are constantly refactoring classes in order to achieve a robust and flexible environment.

    I look forward to the improvements.

    Your points are well-taken, and you’re right that any style changed might affect someone. The question we’re faced with is will this help more people than it will hinder, and we’re not sure of the answer. In any case, it is on our list, and we hope to come up with a good solution that works for everyone.

    Thanks for your input!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[Plugin: The Events Calendar] request for more specific Id names (ie. content, container)’ is closed to new replies.