@MrHoliday Well for UT only one device can register for push notifications I think, the other one will get overwritten in the push server probably...

@RudiH
try terminal app
than goto downloadfolder i think its in phablet/ Download
$ cd Downloads
than tip
unzip filename

(hope that works :0)

Yeah, this needs definitely some improvement. App development (not only for webapps) is held back by not recieving enough attention for too long making it way to difficult to deliver great applications at the moment. My respect to everyone who is developing anyways, there are some great apps on Ubuntu Touch!

If you have wishes or ideas how to improve the problems, be sure to speak up.

@Flohack Well, I'm not worried by Qt itself: it's generally well-documented (property and method deprecations too), so anything can easily (in general) be set up to prevent issues.

The problem comes when we take in account UT-specific code, which makes usage of Qt private imports. I see, running 'grep' on my local folder where I keep all the UT code, that more than 10 components depend on them - including Unity8, the web browser, the Ubuntu UI Toolkit, the Ubuntu keyboard, and some Mir helper.

It means this software should be heavily tested in order to check if there's any regression. This is what Canonical used to do anytime they were moving to a newer version - IIRC they had to fix a few things when they moved to Xenial which uses Qt5.6.

A (partially) good news is that everything should have been already tested on Qt 5.6 and it should just work "out-of-the-box". Anyway I don't think there's any value in moving from the current patched version of Qt 5.4.x to another - as long as we stay on vivid, Qt 5.4 is not the problem.

I think this should be one of the main discussions after we've started to work on Xenial. Qt version, UITK, Unity8, Mir, and the package format are things extremely related each other. The only thing that I can say for sure is that it wouldn't be a problem if we were on Snaps, Flatpaks or Appimages, since they bundle a specific version of the required libraries... 😕

@CiberSheep said in Scope, the forgotten ones.:

I know they're not really popular but they are a really good idea.
For me, they would be great if they would be more like a "sink" or rss feed. Add and remove services (very much like the Today's but more flexible).
Also, can't forget that Falcon is a scope and it does a really good job for me ^__^.
Let's not forget the scopes.

For me there are definitely some to be moved to openstore:

euronews today Cinema Soundcloud Flickr The Weather Channel Twitter Scope

Thanks @fulvio, it's working for me now.

I never heard about this service to be honest, but it looks like the API is pretty well-documented, so i guess it would be possible. There used to be a working Nextcloud-app in the OpenStore (My stupid FP2 is still broken, so i can't check the current status of that) and i think we should try to integrate more popular open services (like Nextcloud) and open standards (like CalDav and CardDav) first and then work our way down to the more niche stuff like this.

However, with our limited time and resources, there's still a lot that needs to be done, before we can get the core-team to work on stuff like this. But, of course, someone in the community (maybe even you) can look into it and write an app or a patch for that.

👍👍👍👍👍👍👌👌👌👌super

Hi,

we need to be very clear on the terms when talking about UX matters.

Pencil is a wireframing/flowcharting tool (which I know very well and often use instead of Balsamiq). Fluid UI is more of a "low-fi prototype demo" service.

The two are not interchangeable nor synonimous.

@Nic264 I used to work on the core apps project and still have the Balsamiq credentials stored somewhere. The tool is pretty slick (though a little slow at times) and allows for both wireframing and live-testing.

It's probably not a problem, and if it is we'll cross that bridge when we come to it. See the following:

0_1491764555932_upload-7edd56ae-e5b6-4462-a5be-025c90400b6c

Glad to hear. I'd like to compile a shortlist of current languages supported by Snaps in a followup post. Something small, nothing fancy, but something that can be used as a base reference.