Skip to content
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

Evaluate the architecture of the plugin #10

Closed
claucece opened this issue Jul 2, 2018 · 3 comments
Closed

Evaluate the architecture of the plugin #10

claucece opened this issue Jul 2, 2018 · 3 comments
Assignees
Labels
architecture importance high An issue that is absolutely necessary to have done before final release question

Comments

@claucece
Copy link
Member

claucece commented Jul 2, 2018

See issue otrv4/libotr-ng#114 of libotr-ng.

@claucece claucece added architecture importance high An issue that is absolutely necessary to have done before final release question labels Jul 2, 2018
@juniorz juniorz self-assigned this Jul 4, 2018
@juniorz
Copy link
Member

juniorz commented Jul 4, 2018

  • Extract methods / data structures out of otr-plugin.c
  • Remove the need for a "protocol_name" and "account_name" in libotr-ng. This is required by libotr, but we can provide a compatibility layer and remove this from libotr-ng.
  • Revisit the mapping between PurpleAccount and otrng_client_s.
  • Revisit the globals used in pidgin-otrng.

@olabini
Copy link
Contributor

olabini commented Aug 25, 2018

What is missing here?

@claucece
Copy link
Member Author

I guess nothing. Closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture importance high An issue that is absolutely necessary to have done before final release question
Projects
None yet
Development

No branches or pull requests

4 participants