The twitter.lib.php was broken out and used the Libraries module to include it for a while in (4.x) (http://drupal.org/node/1853794)

I agree that this probably wasn't the best approach but I still think there are some good reasons to break this module into it's smaller parts so other modules can leverage the api.

It would be great to break the twitter.inc out to an api module that handles caching and access to the library.

We can then make that the primary module and move user related functions to twitter_users and views related functions to twitter_views.

This way a module could require the twitter module and leverage it's caching and twitter api calls without any of the other features provided by the twitter module.

Comments

Jaesin’s picture

Jaesin commented
Title: Break the API out into a seperate module. » Separate the API, User features and views features into their own respective modules.

Let me know if this sounds like a good plan and if it is already included in the roadmap for the twitter module.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Issue summary: View changes
Status: Active » Closed (works as designed)

Contributions welcome, the proposal makes sense but not sure if it's on the roadmap currently. Re-open if you're keen to make this happen.