New Release:

Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases
Github mirror: https://github.com/brennoflavio/greenline/releases

You now can translate Greenline for your language, go to UBports translation project and feel free to contribute

https://hosted.weblate.org/projects/ubports/greenline/

Many thanks for UBports admins to make this happen.

Changelog:

• Animated stickers now renders correctly
• Fixed a bug where the name and photo in the notification was not shown correctly
• Now you can start new chats. Either by inputting a phone number or importing a contact into the app
• Translation support

Progress towards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

@777x you mean that there's some delay between pressing the button and the message to appear in the list? What is your device?

@perrete not anytime soon, there's limitations on both Whatsapp and the projects this app depends on to make calls possible

New Release:

Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases
Github mirror: https://github.com/brennoflavio/greenline/releases

Changelog:

• Group detail page now show members, and group description
• Messages now has their dates before the hour
• On opening a chat page with unread messages, it will show a divider so you know what are the new messages

Progress towards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

If I'm not mistaken eventually Ubuntu Touch will show the keyboard for those apps, but some core components needs upgrading / reworking, and its a working in progress

A new Alpha is out:

Download here: https://git.brennoflavio.com.br/brennoflavio/greenline/releases
Github mirror: https://github.com/brennoflavio/greenline/releases

Changelog:

• Render and allow saving contact array messages (the ones when you send 2 or more contacts in the same message)
• Allow sending reactions. Open the reaction page and you'll see reaction emojis in the bottom
• Allow archiving chats locally, so they don't appear in the main page
• Render unsupported messages, so you know they arrived. In terms of message support, there's no plans to support further message types, most of the remaining ones are business oriented and very specific like pools and broadcast messages.
• Add infrastructure to support translations

Progress torwards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

Nice work @projectmoon looks like a solid project. Never thought that Greenline could be used as a base for anything, the way the app is structured is too "whatsapp-specifc" and with a lot of code shortcuts, a bit hacky to be honest.

I'm seeing that you're building some non python modules into the project, numpy as an example. How are you building that for arm64? Are you cross compiling, building in a arm64 worker, or something else? Thanks!

@projectmoon @amaurydbz we just got the patches released in original Futify. Would you mind checking if the updated store version works for you? Thanks

@mihael Thanks for the screenshot, that's expected for now, it will only allow selecting for messages that has reactions to be seen. Once we fully support reactions, you'll be able to use it to send reactions aswell.

@pparent Thanks for reporting, I think I was able to catch your bug, should be fixed in the last release.

@mihael can you give me more details on that? That menu should show who sent the reaction and which reaction (emoji) was sent. Support for sending reactions is not implemented yet, but planned.

@linus67 Yeah this is known, a better chat is planned with a divider between unread / read messages, and timestamp in messages.

Progress towards beta: https://git.brennoflavio.com.br/brennoflavio/greenline/milestone/1

There's a new release for this app.

https://github.com/brennoflavio/greenline/releases

Changes:

• Support for sending and receiving location messages. Live location are rendered as regular location (only the first update is received) as Whatsapp Web / Whatsmeow does not have full support for live location.
• Finished support for ContentHub, now you can send files and media from other Apps directly to Greenline, no need to open the app first
• Some dead code removal and cleanups, with the new migration support.
• Fixed a bug where clearing data did not delete everything related to the app.

With the new migration system, the app will be slow to open the first time after the upgrade. This happens to adjust the database to the newest code. Should happen only one time, other opens should go normally. This only happens when there's migrations to run, which should be rare after Beta.

Hey, getting back to this project after a few weeks of vacation with a small release that fixes some bugs shown from the new crash report tool:

https://github.com/brennoflavio/greenline/releases

I'm also going to start preparing this software for a release in OpenStore. There's a few features missing and bugs to fix, after that, I'll release a beta version and only focus on bugs.

So if you find any new issues please report, so this can be released in a good shape. Thanks for your help and support!

@pparent did you use the restart button in system settings? If so its a bug that needs to be fixed. That button should remove everything from your system. If you remember, give me more details, I'll try to reproduce it.

Anyway the only file outside the app data/cache/config directory is a unit file in your user systemd directory, you can see it by running sysremctl --user status greenline.service

@AdFundum did you find a command that works from the terminal/adb shell? If so, does that command work if you make your app unconfined?

Its possible that UT does not have an app armor policy that fits your use case, and that's the cause of your problem. From the list of policy groups I cannot see anything that would allow a confined app to change the background image.

https://docs.ubports.com/no/latest/appdev/platform/apparmor.html

@mihael noted!

Btw there's a new release: https://github.com/brennoflavio/greenline/releases

If you didn't disconnected your Whatsapp account in the last update, please take time to do it. Takes a few minutes and will improve your experience with the app.

Changes:

• Now links inside text are clickable and will open the browser
• Mentions are also treated as links, clicking on them open the messages
• Text between stars are rendered as bold message, like in Whatsapp
• Now sending a message while offline does not crash the app anymore
• Daemon should be way faster to reconnect when going back from offline to online or switching networks
• Fix bug when clearing data app not deleting all files

@gpatel-fr I'm talking about the title, that an app has no API to set an action when clicking on the notification bubble.

I think your example shows that, as it is not using the official lomiri api for this. So it doesn't work with an http post to the push server for example.

There's a new release for this app. This release contains a big standardization / internal refactor. I highly recommend that you:

• Logout from the app in your main Whatsapp device
• In Greenline settings, reset the app
• Install the update
• Then login again

If you don't disconnect, there's a high chance that the app will crash in some places. As we approach to a beta release, I added more safeguards to catch bugs and make the app more robust, fixing some bugs on the way. Hopefully this will be the last time this will be needed, as from now on I'll adopt a data migration system for changes.

https://github.com/brennoflavio/greenline/releases

Changes:

• Allow sending documents
• Add option to catch and report crashes
• Add option to pause daemon when closing the app
• Render Whatsapp text messages with buttons
• Fix images rotating in chat page
• Restore old behavior for unread count bubble in app drawer
• Handle Group Information and other whatsmeow events
• Remove daemon configuration database, centralize all configuration in python
• Harden media download, prevent crashes when downloading unavailable media
• Reorganize code into modules, better separation of concerns
• Add tests for daemon <> python communication and python <> qml communication
• Document and test all python interfaces, with real, sanitized Whatsmeow data
• App now validates at build and at runtime all data structures, logs errors, and ensures consistency between app parts

Its definitely a Lomiri UI inconsistency, not an app issue. From apps perspective, there's no way to tweak this behavior. And there's no difference between an app using dbus or the http apis to send notifications, they end up flowing over the same path in your device.

@ChromiumOS-Guy please keep the discussion on feedback and suggestions, avoiding giving orders or similar statements.

The way you put it is a bit rude for my taste. It does not sound intentional, but with a bit of out of context to me. Its not that the app is being developed without a data model in mind, more like new requirements (replies, edits, new message types, etc.) requires rethink on how things are done, which is pretty common on any medium o higher complexity project.

@Vlad-Nirky Its not an impression, the app is inefficient in its current state, optimizations are needed. The perception will vary depending on the amount of whatsapp data you receive. Its a combination of having the backend written in python (which means that on receiving new events, a python process is created to process it on the fly) and the qml frontend re-rendering on each event that emits a qml update. So for example receiving a new chat means re-rendering the whole chat list.

Not too worried about it yet, but something for me to look in the future. I'm not 100% decided on how this app will manage its data so not gonna waste time optimizing something that might change. Probably will get back to this once the app support all possible Whatsapp events / message types, which will give clarity on how to model everything.