@dobey It does not seems to be working. I tried following 2 options One: Exec=webapp-container --allow-file-access-from-files --app-id="testionic.jitto" $@ www/index.html Two: Exec=webapp-container --local-content-can-access-remote-urls --app-id="testionic.jitto" $@ www/index.html Both are not working. Same error ... :anxious_face_with_sweat:

Voice assistant is I think an essential part of a mobile OS these days, although given the time and resources required I can understand why it might take a back seat .. imo it shouldn't anymore really, its the only thing I keep wishing UT had

@rival Have you checked if your user can run docker? That is, docker ps works? I think I hit a similar issue that was resolved when I added my user to the docker group

@arubislander said in Download a file using webapp-container: But why, though? Wouldn't it have been perfectly OK for Morph to also download in it's own private folder? The files could have been exported from there to another location on the filesystem via Content Hub (as they already can be currently) I don't know the specifics of why things work this way in regards to webapp-container/morph. IMO, the current behavior is wrong. But if one wants to change it, they should open an issue about the behavior on github. This isn't the place to resolve that.

@lduboeuf you are correct...there is some basic C++ docs on how to do this so if it's not possible in QML i might have to do that as a workaround.

@boky Congrats. You've found an issue. The documentation really shouldn't be telling you to just run --help to get documentation. The valid arguments should be documented there instead. Also, webapp-container should probably do argument parsing before trying to connect to the display. Though, this may be an issue with how Qt works in this case, and more difficult to fix. You can report issues at https://github.com/ubports/morph-browser for these.

Me, too. I have hoped that the scopes could develop into something similar, but those are gone too.

@Lakotaubp Unfortunately, I don't know anything about app development specifically and how to recreate a UI. I can build Halium and troubleshoot it, but apps are higher level than I am comfortable with. I could probably code a sub-par gui with Rexx if ubports ever supported it

And finally it work! I have added information on the track with help of taglib. I have search in media-hub but not found any reference to QMultimediaPlayer or something to give information of the current track (like dbus or other system). But I have find lot of metadata files parsing. After using taglib to add some informations on my track i'm able to display them in the HUD! Thank you for your help @wdehoog

Well, if you can't get a working binary the template probably won't help you. But you could use clickable's debugging features to help with the app not starting. Another thing to look at is the unity8 logs as well.

@boky Clickable uses a docker container, the image size is around 3GB for each target. Older images can remain but you can clean them with docker rmi (read the manual before)

Yes, I tried to do that: https://forums.ubports.com/topic/3943/refresh-icon-view-in-app-drawer-in-real-time/12 What do you want the script to do?

@ernest Update: the download works fine in Morph it's the Onion browser that had the issue.

@magdesign It's probably possible to reactivate the FirefoxOS touch UI in desktop Firefox, but someone would need to get a version of Firefox working without Libertine (To have GPU support etc.). See: https://developer.mozilla.org/en-US/docs/Mozilla/Gecko/Chrome/API/Browser_API/Using https://github.com/mdn/browser-api-demo https://hacks.mozilla.org/2014/08/building-the-firefox-browser-for-firefox-os/ Edit: Hmm seems like some useful functions were removed in FF65

@Craig Maybe you could help out here: https://gitlab.com/clickable/clickable/issues/122

Ah ok, thx. guess i'll try to find another way to port it!

@PhoenixLandPirat as you said most part of the code can be reused, i did once a quick test, sailfish own components as to be replaced, but for someone used with qml it is not so difficult. Congrats for your idea @manland