[Alpha] Greenline - A qml Whatsapp client for Ubuntu Touch
-
-
@brenno.almeida great work!only use your app now since it is fast smooth and reliable.
only hickup, anyone else keeps missclicking the send button? its really hard to press for some reason (xiaomi redmi note 9 pro)
I have this issue on the Quintus. Maybe the mouse area is too small?
-
Thank you again for this app!
If I can draw attention to one detail (I don't want you to be overwhelmed with requests):
-
The app somehow refreshes itself at a few seconds interval.
-
That makes that, while I scroll down the list of messages in order to look for an older conversation, suddenly the app takes me back to the top.
-
I think the same thing happens inside a conversation when there is a long message and I click on "read more" - after a few seconds the message collapses again.
I opened an issue for it: https://github.com/brennoflavio/greenline/issues/4
Again, a big thank you!
-
-
@brenno.almeida the version after fixes the counter that kept growing till reboot. amazing
-
Thanks you all, keep feedback coming, it helps a lot. No problem to report usability / polish issues aswell.
@nbdynl yeah broke that a while ago, still not 100% correct as muted chats still counts but at least consistent now.
-
@brenno.almeida
Thanks a lot for this great app!
I get the impression—purely subjective, mind you—that the app uses quite a bit of power.
Do you think it would be possible to add an option in the settings to set the refresh rate for new messages (or even to stop it unless I check manually)?
Or am I mistaken?
What do you think? -
@Vlad-Nirky I use the latest version from yesterday and test it over last night.
I haven't noticed any increased battery drain. The Pixel 3a switches to deep sleep mode without any issues. < 2% battery drain per hour. Tested last night with notifications enabled. -
@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.
-
@brenno.almeida so a premenantly temporary solution.
yeah just make sure to refactor at some point. great client as is but i recommend you structure the client around the data not the other way, that way lies pain suffering and keyboard bashing. -
@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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login