Separation of logic and display layers in next rebuild

[Chris]

In the next rebuild could you please separate the display layer and hooks/logic (aka separate concerns in programming terms) and move to an MVC or MVVM or alike app structure.

I think this would make maintenance of your app a lot easier for your team, and allow for custom hooks to be applied much easier by developers (it would be a dream events set of plugins).

so you could just disable features with something like:

globally:
tribe_events_disable_feature('feature-one,feature-two');

by section
tribe_events_disable_feature('feature-one,feature-two','/events/category/');

per page:
tribe_events_disable_feature('feature-one,feature-two','/events/page-one/');

and have functionality like:

tribe_include_feature('tec-tickets')

to make sure the wiring is there for the interface to grab it (aka it could already be active so it will nonse the code)… that way we can just drop features in and out of pages like magicians and write of your greatness all over the internet!

Also would be great have complete ‘easy’ access to replace functionality or extend functionality:

• Completely replace your code with ours (backend/frontend/both)
• Add our own plugins to yours (easily) to add functionality (eg: ticket types there are rsvp and ticket atm but extending that requires a degree in how your developer thinks – it’s very complex)

We can do all of these things now, but it takes many hours or days of code review, instead of simply dropping in a customisation from a skeleton template, or simply cloning an existing object and adding a few ‘different’ settings. I can see where this is developing over time (and the efforts you have already made are great), but I think the code needs to be simplified so it can be customised easily so that more people will purchase and buy these plugins.

Would also be great to have ignitiondeck eccommerce support… will add that to user voice. as they are getting 100-300 downloads a day and gathering steam now that automatic has bought woocommerce (and it’s plugins are rediculous expensive on their site, unless go to a GPL club to get it). Ignitedeck would also be a good play for you if you want to be seen as a ‘premium’ expensive plugin as their pricing is also up in the hundreds of dollars for the paid versions. It would be an awesome integration, as we are now moving from woo to ignitiondeck for our ecommerce platform. (would be happy to test it also)

[George]

Thanks for your feedback here, @Chris. I will forward this to our development team for consideration for future releases.

Please let me know if there are any other issues or questions I can try to help with.

Sincerely,
George

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts