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

Finish initial Conversations/SMS/IM user interface #565

Open
1 of 14 tasks
MerlijnWajer opened this issue Aug 6, 2021 · 2 comments
Open
1 of 14 tasks

Finish initial Conversations/SMS/IM user interface #565

MerlijnWajer opened this issue Aug 6, 2021 · 2 comments
Assignees

Comments

@MerlijnWajer
Copy link
Member

MerlijnWajer commented Aug 6, 2021

We now have a Conversations application written in Qt5+QML and Hildon that can read the rtcom database and has some Telepathy support, but it needs more work.

This list is an unordered list of things that still need doing

  • Remove 'w00t' menu
  • Merge group chat / telepathy backend rework
  • Support for group chats (Wizzup has this working locally, on a protocol level)
  • Interface for group chat
  • Running on start, in the background, ideally before modem is online'd, so that Telepathy doesn't miss anything. Don't let people 'quit' it with a button
  • Mark messages as read when viewed
  • Detect changes using rtcom dbus signal, not internal message received
  • Detecting if an account is online or offline, and disallow sending messages if it is offline.
  • libnotify support with notifications in the lock screen
  • Being able to copy text
  • Being able to click on links
  • osso-abook integration for searching and messaging contacts
  • osso-abook integration to match incoming messages to a contact in rtcom (I think)
  • Be able to initiate a message to a new context or random number

Old message:

We lack a user interface for communications.

Our aim is to use Telepathy as a backend for all communications, and re-use the rtcom-eventlogger event structure for logging communication messages.

Any protocol, signal, whatsapp, jabber, etc, we'll initially try to use it from Telepathy. There is no fallback-plan as of now.

We could use either gtk2/gtk3 or qt5.

It would be nice if we can re-use some of the html/css from Fremantle, which allows for nice modifications:

https://wiki.maemo.org/Conversation_Mods

yappari could provide a good base for some of the UI and other interaction:

* https://talk.maemo.org/showthread.php?t=84605
* http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_i386/yappari/2.0.26/ (todo: check what the actual latest version was)

Freemangordon said he would be OK with Qt5, I (MerlijnWajer/Wizzup) feel the same.
@MerlijnWajer
Copy link
Member Author

I think the current thinking is the following:

  1. Take yappari (https://github.com/agamez/yappari); strip out all the Whatsapp code and a lot of features
  2. Port yappari to Qt 5 so that we can use it
  3. Add rtcom-eventlogger reading and writing code
  4. Add telepathy code, test with telepathy-ring's 'tel' protocol (use telepathy-qt or telepathy-glib)
  5. Make osso-abook integration work once osso-abook code is done, Yappari already supports it
  6. Make other telepathy protocols work too (xmpp, etc)

@MerlijnWajer MerlijnWajer self-assigned this Oct 3, 2021
@MerlijnWajer
Copy link
Member Author

@MerlijnWajer MerlijnWajer added this to the July goals milestone Jun 20, 2022
@MerlijnWajer MerlijnWajer modified the milestones: July goals, Maemo Leste Beta Nov 22, 2022
@MerlijnWajer MerlijnWajer changed the title Conversations/SMS/IM user interface Finish initial Conversations/SMS/IM user interface Nov 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant