-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[In Progress] Port to TelepathyGlib #17
base: master
Are you sure you want to change the base?
Conversation
Thanks. Reviewed. |
Thanks. Reviewed. Looks fine. I'll be able to test on Monday (Australia). |
Tested on Fedora 18. No new errors in logs. Game playing board state is mostly shared, but not fully; differences are;
Hope that helps! |
I am not working on this currently. Anyone who wishes to take this up, please feel free to do so. |
Tried to test it using rdesktop. Successfully made two instances,but not able to connect the two activities. Using Ubuntu 18.04. In the neighbourhood view, after hovering on other user I am not getting an option of "Invite to Cookie-search", but I am getting it for Chat. And if any error results,are they seen through the log activity? |
@@ -206,28 +209,28 @@ def _joined_cb(self, activity): | |||
|
|||
def _new_tube_common(self, sharer): | |||
""" Joining and sharing are mostly the same... """ | |||
if self._shared_activity is None: | |||
if self.get_shared_activity() is None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self._shared_activity
is in the GTK 2 toolkit sugar-toolkit, and is not in the GTK 3 toolkit sugar-toolkit-gtk3.
self.get_shared_activity
is in both toolkits.
My guess is that the code hadn't been changed during the port to GTK 3, before the port to TelepathyGLib. If we're not sure if collaboration worked for the GTK 2 release of the activity, the way to be sure is to test that release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I also think that collaboration should be tested for GTK 2 first, It seems that there are not much changes from telepathy to TelepathyGlib for this activity, and the differences @quozl pointed out might be seen before telepathy port.
Game playing board state is mostly shared, but not fully; differences are;
Now seen a couple of instances where collaboration code is not properly ported to GTK 3 .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it is endemic. Root cause is missing-in-action activity maintainers, and well-meaning volunteers during GCI or students in GSoC who have concentrated on a GTK 3 port without fully understanding the collaboration feature, and reviewers with the same limited focus. Another cause is activities copied from other activities that do collaboration, without implementing collaboration in the new activity. Is why we re-worded the project idea this time, and @nswarup14 is doing "Maintain 25 activities" rather than "Port to GTK 3".
I don't think it is worth testing collaboration with this activity, given that there is so little shared state. I suggest testing Write and Chat first. |
Reviewed it again. Comments -
|
Yes, the port is not yet needed because the activity does not yet work with collaboration. See also #18. If that issue can't be fixed, then the fragmentary collaboration should be stripped out. |
Explanation
Fixes #13. This PR ports to TelepathyGLib.
Reason
The telepathy library does not have its bindings for Python 3, and porting Telepathy to its PyGObject binding is a pre requisite for the Port to Python 3 Project.
Test result
No error related to the port to TelepathyGLib.