Dekko2 Developer Community Thread

hummlbach

@dekkerj1 No thats no nexus 4 specific issue. (Its working fine on my nexus 4.) The versions posted here have an issue with starting the daemon fetching the mails in the background called dekkod. The file needed to start (.config/upstart/dekkod.conf) contains a version specific path (it shouldn't, will be corrected in the next days) thats why you need to execute the command:

@lakotaubp said in Dekko2 Developer Community Thread:

Then ran rm -f ~/.config/upstart/dekkod*

If you have installed on of the alphas you need to delete at least dekkos cache, since the alphas messed up the cache for some mails causing dekko to crash. You can clear the cache either by using the ut tweak tool or by executing rm -rf .cache/dekko* in the terminal. (To be sure, close dekko before doing all this. At best also stop dekkod by running stop dekkod in the terminal.)
Afterwards restart your device if you haven't stopped dekkod from terminal.
There are still some corner cases causing problems. Me for example has problems with deleting mails. @lionelb has reported hes still unable to read mail and dekkos is crashing if repeatedly tries to. But in there very most cases it seems to work fine. If you're still having problems, please report whats the problem exact. At best check whether its a known issue on
https://gitlab.com/dekkoproject/dekko/issues and report it there if its not yet.

dekkerj1

@hummlbach Thanks, that fixed it.

doniks

@flohack said in Dekko2 Developer Community Thread:

Just asking to know if we should try to get more help rushing in

@Flohack I'm thinking: one thing ubports core team could maybe do to facilitate work on dekko would be to fix packages/dependencies for amd64.

Right now the development workflow is more or less tied to testing on an armhf device. If we could sort out these errors: https://gitlab.com/dekkoproject/dekko/issues/104#note_88572323 then I think we might be able to test dekko on development machines directly which would simplify things.

Update: or maybe not. whatever the problem was in that issue 104, it doesn't hit when we do it like this https://gitlab.com/dekkan/dekko/commit/8b3aa09c7ec7b9d10b957c2d1013afe3bf737ea8 . Now ultimately that doesn't succeed either (yet?), but at least it doesn't stop at apt dependencies

A Former User

I'd like to add my thanks and congratulations to everyone who has worked on this.

dR0W

Thanks to all the developers involved in this project for the great work.
Tested on my BQ Aquaris E4.5

delijati

Hi,
tried to debug an error i had with using Dekko2. So i compiled it (after some code changes) for amd and run into the Oxide not installed error.

So to sum it up as Oxide is going to be replaced by QtWebEngine this also needs to be done for Dekko2. Or is there a plan to add a transparent layer that redirects to qtwebengine?

Here the issues i created regarding that topic:

One other question is there a repo with the source of dekko1?

doniks

Hi @delijati

Can you describe what you had to do to test on amd64? This is my attempt:
https://gitlab.com/dekkan/dekko/commit/8b3aa09c7ec7b9d10b957c2d1013afe3bf737ea8
If I remember it right, I could build it but wasn't able to run it.

Regarding oxide , yes at some point the rendering engine probably has to be replaced, but unless that becomes blocking, it has no priority at the moment.

What error with oxide do you get?

Wrt dekko1, dunno

advocatux

@delijati have you checked older branches here https://gitlab.com/dekkoproject/dekko/tree/master?

delijati

@doniks Hi i just found your branch. My changes seam to be almost the same. The error is that Oxide is missing for amd64.

[20180921 13:35:15.789 CEST [dekko.plugman.incubator] >> Comp failed:  "file:///opt/develop/privat/mobile/ubports/__dekko_build/debug/install-root/bin/plugins/ui/MainUI.qml:5 module \"com.canonical.Oxide\" is not installed\n"

I'm not sure how the plan for Oxide and amd64 looks like, is it hard to add it to the build chain for amd64, is there any plan to do it at all for xenial, bionic?

doniks

@delijati said in Dekko2 Developer Community Thread:

@doniks Hi i just found your branch. My changes seam to be almost the same. The error is that Oxide is missing for amd64.
[20180921 13:35:15.789 CEST [dekko.plugman.incubator] >> Comp failed:  "file:///opt/develop/privat/mobile/ubports/__dekko_build/debug/install-root/bin/plugins/ui/MainUI.qml:5 module \"com.canonical.Oxide\" is not installed\n"

I've checked my branch again. It's not the exact same error that I got. Maybe there is still something we can learn from each other's changes. Can you push yours somewhere?

hummlbach

Since there are popping up questions regarding email client from time to time, a short update on the state:
Actually we already had dekko 2 beta ready for upload to the openstore. But now we thinking of getting rid of oxcide first... @delijati already started working on this and has dekko 2 running prototypically without oxcide.
So expect dekko 2 to be in the openstore before/not after ota5 will be released.

Lakotaubp

@hummlbach Great news great project and great work by one and all. Thank you for the time and effort.

doniks

Tadaa

https://forums.ubports.com/topic/1750/dekko-0-1-6-beta2-released

Wanna test, praise, curse, suggest, wish? Absolutely, jump over to the other thread and fire away!

Lakotaubp

@doniks on my way !!

matteo

@lakotaubp Hey guys! Great job done on this email Client! I just installed it on my pro5 and it is working as I remember. But I still get an app crash every time I try to reply to an email (by hitting the arrow or the reply to all option, whilst the forward option seems to work).
I'm wondering whether you also noticed such an issue, since I didn't read any bug complain in this thread up to now.

Thank you!

Matteo

doniks

@matteo said in Dekko2 Developer Community Thread:

@lakotaubp Hey guys! Great job done on this email Client! I just installed it on my pro5 and it is working as I remember. But I still get an app crash every time I try to reply to an email (by hitting the arrow or the reply to all option, whilst the forward option seems to work).
I'm wondering whether you also noticed such an issue, since I didn't read any bug complain in this thread up to now.

Standing on the shoulders of giants man Shoulders of giants!

Issues are tracked in the bugtracker not in this forum thread. This thread is to coordinate developers. You know, like, you have a patch, or you're stuck with compiling it, etc.

Let's hop over to the other thread: https://forums.ubports.com/topic/1750/dekko-0-1-6-beta2-released for general comments, feedback, testing. Over there you'll also find the link to the bugtracker. Please do raise an issue. Especially, if you have a stable reproduction!

doniks

Any gitlab CI experts around? It seems that Dan has put something in place that still does ... something ... https://gitlab.com/dekkan/dekko/-/jobs but

a) I don't understand what makes it pass/fail ... why would the last job fail because "qbs not found" but the second last job succeeded? qbs is used in the build process and that hasn't changed
b) Can we make it create .click files that can be downloaded?

I guess the magic is triggered from here https://gitlab.com/dekkan/dekko/blob/master/.gitlab-ci.yml

Any advice?

guru

I raised this in the Support Category and was asked to bring it up here:

When one deletes a mail in Dekko2 (0.1.6-beta2) from the list of the current mail folder, the list gets moved down to show a green Undo button for a few seconds, and then the list is moved up again, when this button goes away. The disadvantage of this down/up movement is, that sometimes you hit the wrong mail when selecting the next mail to read or to delete.

Is this configurable? If not a will file a bug issue.

hummlbach

As far as i can see, its not configurable, so feel free to file a feature request.

guru

https://gitlab.com/dekkan/dekko/issues/21