This is a place to coordinate developers working on dekko2. (It is not the place to discuss individual bugs)

In the good old days we had dekko and it mostly worked ok. At some point a rewrite as dekko2 was deemed necessary. The rewrite was started but not completely finished. In addition the platform has moved on beneath dekko (xenial). Time has gone by and development rate of dekko has dropped.

As of today, there is no working dekko for xenial UT.

Over the last couple weeks I see here and there on various UT telegram channels messages pop up about various people trying to work on dekko. Some wrestling with the build system. Somewhere a test build showed up. Some critical bugs were mentioned (settings, system load). Workarounds and some fixes too. I think it's time to coordinate efforts. So we don't independently solve the same problems multiple times, but instead move forward faster.

So all you dekko2 hackers, speak up below with whatever you do / did on dekko2. What you need help with.

Let's make it happen!

PS: This is not an attempt to hijack the project from the current maintainer @DanChapman . Personally, I think the best future for email on UT would be a Dan maintained dekko2 with a small community of developers cooperating. Dan seems to be on a hiatus right now. Let's see what the future brings.

PPS: If you are not actively developing on dekko, then help us stay focussed by not going off topic here! Maybe you really want to encourage people to work on dekko. Or maybe you are very frustrated because you really need an email client. Well, yes, we know. We all are. Feel free to up (or down) vote posts. Or maybe you want to report an issue or suggest a feature. Then use the bug tracker. Or you just have a question. Then start a new thread or go here https://forums.ubports.com/topic/1750/dekko-0-1-6-beta2-released/1

]]>http://forums.ubports.com/topic/1477/dekko2-developer-community-threadRSS for NodeSun, 15 Sep 2019 09:43:38 GMTSat, 21 Jul 2018 08:26:46 GMT60This is a place to coordinate developers working on dekko2. (It is not the place to discuss individual bugs)

In the good old days we had dekko and it mostly worked ok. At some point a rewrite as dekko2 was deemed necessary. The rewrite was started but not completely finished. In addition the platform has moved on beneath dekko (xenial). Time has gone by and development rate of dekko has dropped.

As of today, there is no working dekko for xenial UT.

Over the last couple weeks I see here and there on various UT telegram channels messages pop up about various people trying to work on dekko. Some wrestling with the build system. Somewhere a test build showed up. Some critical bugs were mentioned (settings, system load). Workarounds and some fixes too. I think it's time to coordinate efforts. So we don't independently solve the same problems multiple times, but instead move forward faster.

So all you dekko2 hackers, speak up below with whatever you do / did on dekko2. What you need help with.

Let's make it happen!

PS: This is not an attempt to hijack the project from the current maintainer @DanChapman . Personally, I think the best future for email on UT would be a Dan maintained dekko2 with a small community of developers cooperating. Dan seems to be on a hiatus right now. Let's see what the future brings.

PPS: If you are not actively developing on dekko, then help us stay focussed by not going off topic here! Maybe you really want to encourage people to work on dekko. Or maybe you are very frustrated because you really need an email client. Well, yes, we know. We all are. Feel free to up (or down) vote posts. Or maybe you want to report an issue or suggest a feature. Then use the bug tracker. Or you just have a question. Then start a new thread or go here https://forums.ubports.com/topic/1750/dekko-0-1-6-beta2-released/1

]]>http://forums.ubports.com/post/10817http://forums.ubports.com/post/10817Sun, 11 Nov 2018 15:14:58 GMTI myself tried to get the setup-dev-env script to work, but learned eventually that this doesn't work right now due to the state of x86 in ubports repository (https://gitlab.com/dekkoproject/dekko/issues/104).

I know others have managed to build dekko, but I am currently stuck with it. Can someone point me to a repo & instructions that work?

]]>http://forums.ubports.com/post/10819http://forums.ubports.com/post/10819Sat, 21 Jul 2018 09:25:13 GMT@doniks thanks for your initiative. I started building dekko 2 since there was the request for it here and i wanted to have it myself on 16.04 and as far as i understood it @DanChapman doesn't have time for it atm. The "script" above is a destillation of setup-dev-env and build-click using docker instead of lxd/lxc. I wanted to use docker since I like it, am familiar with it, the ubuntu-sdk containers are well maintained by @bhdouglass (Thanks!) and the majority of the app developers are using clickable (which uses docker). I would suggest to fork dekko, feed the commands from my "script" back to the setup-dev-env ... s.t. dekko can be built using clickable (custom build script or how it is called). (Then making a pull request...).
Afterwards we would need to fix the plugins/views (compose/calendar/contacts/settings...) not showing up/being opened...
]]>http://forums.ubports.com/post/10823http://forums.ubports.com/post/10823Sat, 21 Jul 2018 12:00:48 GMT@hummlbach said in Dekko2 Community Thread:

The "script" above is a destillation of setup-dev-env and build-click using docker instead of lxd/lxc. I wanted to use docker since I like it, am familiar with it, the ubuntu-sdk containers are well maintained by @bhdouglass (Thanks!) and the majority of the app developers are using clickable (which uses docker).

Great. I still haven't gotten around to test it, but from reading it, it looks to me it could be two scripts: clickable-setup and clickable-build, together with a usage note in README?!

I would not replace setup-dev-env with your new script, since I think the use cases are orthogonal. setup-dev-env attempts to let you build on x86. Also it should enable you to run and test on your dev machine. Furthermore, it's supposedly a way to use the original qtcreator fork aka SDK IDE on your dev machine!

I would suggest to fork dekko, feed the commands from my "script" back to the setup-dev-env ... s.t. dekko can be built using clickable (custom build script or how it is called). (Then making a pull request...).

Do you have an overview who else is hacking on dekko right now? I have a hard time keeping up and keeping an overview with telegram.

Afterwards we would need to fix the plugins/views (compose/calendar/contacts/settings...) not showing up/being opened...

agree

]]>http://forums.ubports.com/post/10824http://forums.ubports.com/post/10824Sat, 21 Jul 2018 12:52:42 GMT@doniks ah sorry I meant setup-click-env not setup-dev-env... So what i wanted to suggest was removing the lxd/lxc stuff from setup-click-env and call the script inside docker container(s) by using clickable instead... It could be used to build dekko for armhf in the first step and place and later perhaps also for x86 (not sure and not a must of course but perhaps to have it consistent...).
I haven't it forked yet... If you give me (and others) access to your repo we can work on it together there. Otherwise I would also fork it...
]]>http://forums.ubports.com/post/10828http://forums.ubports.com/post/10828Sat, 21 Jul 2018 14:16:58 GMT@hummlbach said in Dekko2 Community Thread:

@doniks ah sorry I meant setup-click-env not setup-dev-env... So what i wanted to suggest was removing the lxd/lxc stuff from setup-click-env and call the script inside docker container(s) by using clickable instead... It could be used to build dekko for armhf in the first step and place and later perhaps also for x86 (not sure and not a must of course but perhaps to have it consistent...).

sounds good. setup-click-env should be for clickable imho and thus lxc should go and be adjusted for the new docker setup. setup-dev-env can be revisited later

I haven't it forked yet... If you give me (and others) access to your repo we can work on it together there. Otherwise I would also fork it...

ok. gitlab is down right now for an hour or so. please request access there when it's back (they have a button to request access)

I took it for a spin on my laptop running 18.04 but it failed. (Issue #104 I'm presuming). I tried it on another machine I have with 16.04 still and it was able to build and install. Now onto the next step and try to get things functional.

As for issue tracking ... my thinking is, I want to minimize the disconnect to Dan's upstream. Having a forked git repo is no biggie. We can ensure to remain mergeable. However, setting up a separate infrastructure to track issues would increase the divide. Maybe we can keep low-overhead quick and dirty issue lists in here, similar to your last post. But if we want to track for a longer time and collect reproductions, patches, whatnot, then I prefer to use Dan's tracker. What do you think? Maybe there is some tagging mechanism....

I did load the 0.1.6-alpha0 click you tagged and that worked so I presume something is wrong still with my build environment. Tried blowing away the .build-armhf/ and rebuilding but I don't see anything obvious there. Guess I'll keep digging.

With the 0.1.6-alpha0 click, I was able to confirm that it does render plain text emails but not html ones. Guessing this is related to the existing browser issue where it crashes on certain sites maybe? And I do have one particular email that causes it to segfault outright. Don't know offhand what it in the messages is triggering that though. I was able to send an email though and notifications work so that's something.

]]>http://forums.ubports.com/post/11135http://forums.ubports.com/post/11135Sat, 04 Aug 2018 13:24:10 GMT@thrrgilag my builds also still crashing... As I said, I think they do since I updated the docker container. I've taken a click that I've built with the old container and "patched" it to the current state. I didn't have time yet to investigate whats the problem with the build currently.
Concerning the mails not getting displayed. Me too thought it was an issue with oxide, but I'm not so sure anymore. The oxide error log messages also appear in 15.04, where all mails are displayed fine. Also I have found some html mails that are displayed fine and some that show up at least partly. But theres a message of the second part of the mail needed to be loaded on opening "failing mails". So perhaps it depends on the size of the mails...(?)
]]>http://forums.ubports.com/post/11148http://forums.ubports.com/post/11148Sat, 04 Aug 2018 23:40:59 GMT@thrrgilag said in Dekko2 Developer Community Thread:

@doniks that's the annoying part a log doesn't get created, it fails as soon as it starts it seems.

maybe something in unity8.log then?

another thought: I remember sometime it seemed that UT was cleaning up the log file after the app closed so I had to hack something like this, so I could keep it: while true ; do cat logfile > logfile.keep ; done.