Merge lp:~olivier-faurax/gwibber/link-in-likes into lp:gwibber
Proposed by
Olivier FAURAX
Status: | Rejected |
---|---|
Rejected by: | Robert Bruce Park |
Proposed branch: | lp:~olivier-faurax/gwibber/link-in-likes |
Merge into: | lp:gwibber |
Diff against target: |
154 lines (+42/-20) 2 files modified
po/gwibber.pot (+17/-18) ui/templates/base.mako (+25/-2) |
To merge this branch: | bzr merge lp:~olivier-faurax/gwibber/link-in-likes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Bruce Park | Disapprove | ||
Review via email: mp+55021@code.launchpad.net |
Description of the change
This change adds links and names of people who "Likes" something on facebook.
Ex: "3 users liked this" -> "3 users liked this (Jon Smith, Robert Doe)" (with the names being clickable).
This implementation is based on "trial and error" on my facebook account.
I don't know mako, so better code can perhaps be written.
Also, if another service than facebook uses "Likes", perhaps my implementation will break.
So, don't hesitate to test and report.
To post a comment you must log in.
Unmerged revisions
- 970. By Olivier FAURAX
-
merged trunk
- 969. By Olivier FAURAX
-
New content of data["likes"]
- 968. By Olivier FAURAX
-
Add links in likes (tested with facebook)
Thanks for taking the time to submit this patch, unfortunately Gwibber has gone through extensive changes recently and your patch no longer applies to the latest codebase.
Unfortunately, the feature you were attempting to add is still missing. It may be possible to port your patch to the new Gwibber, although this will be difficult due to a number of underlying technologies having changed.
To get you started, you should have a look here:
http:// bazaar. launchpad. net/~super- friends/ friends/ trunk-next/ view/head: /friends/ protocols/ facebook. py#L86
That is where we extract the relevant data from the JSON that Facebook delivers to us. You'd have to get the names from there, and then append them to the message if you wanted to see this. Although we should probably discuss the design of this with Ken because I'm not sure what is the best way to accomplish this currently.