Breaking changes in JTwitter?
Daniel Winterstein
I'm considering a couple of breaking changes for the next version of
JTwitter. I'd like to get your feedback before going ahead.
The Twitter API has grown considerably since JTwitter started. As a
result, the Twitter.java file has got rather unwieldy. So I'm
considering:
1. Moving the Status, User, and Message classes into their own files.
2. Organising some of the methods in Twitter into other classes. We'd
have separate classes for geo-location, account-management and users.
So a method such as `twitter.show(screenname)` might move to
`twitter.users().show(screenname)`
What do people think?
Is the extra clarity of the code worth breaking backwards
compatibility a bit -- or should we leave things as they are?
Also, it's been suggested we move to a Maven repository. What's the
level of interest in this?
Please reply to me personally to avoid spamming the list (unless your
reply is meant for the whole list).
Thank you, &
Best regards,
- Daniel
--------------------------------------------------
Daniel Winterstein
Edinburgh
http://winterwell.com http://soda.sh