Personally I read the full source to see what's going on, and then figure
out how to work around bits of it, so for example I might see when the
header title is set and the selectors used, and then use its own routines to
modify them (eg hdr = widget.byClass("twtr-hd", "div") and then manipulate
the DOM myself) rather than use a modified version of the widget js file
itself.
This way it's easier for me to keep up with changes to the widgets (eg the
recent addition of intents) and to ensure I'm staying within the rules about
presenting twitter content (logos, names, etc), but YMMV
--
T
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
