@dtarrant Okay but a source code example would be helpful where someone implements a webview based on Morph.
Posts made by Krille
RE: Why some xenial webapps don't work
Hey, I also have big problems with uMastonauts. The webview crashes every time I start it. Switching to import Morph.Web 0.1 does'nt work. The app is useless until I know how to fix this but I have no idea. :-(
Is there a working example webapp with the morph browser engine where we can look how to do this?
RE: System-wide Dark Theme request
A global switch would make problems I think. Not all apps are working correctly with dark themes. The developer needs to check everything in the GUI to ensure, that everything is visible. For example in the Qml Component ListItem, the title will be unvisible by default in dark theme. Other issues are possible too, because Qml is very flexibel and allows the developer to change all colors like he want. A forced dark theme on a very customized app design could make an app unusable.
Something like redshift would be much better in my opinion.
RE: UI / UX discussion
A full width appdrawer would look very nice and minimalistic. Also the launcher would be visible so it gets more focus from the user. I would really like that =)
Edit: But if you go to the task overview and kill all active apps, which app would be then visible? Only the background or launch the appdrawer automatically then?
RE: UI / UX discussion
@gb the app launcher is not easy to reach for right handed users. So I most use the apps overview und search the scopes app.
For left handed users its the opposite I think. For them its hard to reach the apps overview. So I would say its important that Ubuntu Touch gets a left-handed-mode which switches the actions on the edges.
Comparing scopes with the fire tablet
Hey guys. I was thinking about scopes the last days. I know the most of you are thinking that they are deprecated but Im not 100% sure that this is right.
Maybe you know it, maybe not, the amazon fire tablet with the opensource fire os has also something like scopes. It looks and feels very similiar to the ubuntu phone scopes but on the fire tablets they are working very well as you can see here: https://the-digital-reader.com/wp-content/uploads/2015/09/fire-new-tablet.jpg
The question is: Why?
I think the reason is: The scopes are a place where you can DISCOVER something, not where you want to reach a specific content. On the fire tablet you just go through books, videos, games, like in a store where you can see interesting things but you dont want to buy something specific. And every time you go to this scopes, you can discover something new. Thats why they work. On the Ubuntu Phone, you have the gallery scopes where only the images are, you already own. They dont change without your action so you dont can discover there something. So the gallery scope is just useless like the most other scopes. You need scopes where you can discover NEW things. Thats why the nearby scope was a good idea I think.
The advantage of this system is: You dont have to check 10 apps for something new. You could say, that you have push notifications for this but if you are following 1000 People on a social media, you dont want to have a notification for each new post. :-D But maybe you want to take a look on the posts from the last five minutes without opening the app. And you dont want to have a notification for each article of the new york times but you want to read through all the titles sometimes.
But you dont need a summary of all pictures you have on the phone. They are nothing new.
What I want to say: We do not necessarily have to do away with scopes. We just need BETTER scopes which offer something new to discover and which makes fun and dont just show a list of content that's on the phone.
So in an ideal world you are on your scopes and see all your apps. You swipe to the next scope where you can see whats new in the new york times, on the next scope you see microblog posts from something like twitter, facebook or mastodon. On the next you see pictures posted from friends on something like instagram or pixelfed. And on the next scope you see new articles from your RSS feeds.
Or another idea: We could write a tool which creates a scope from a rss url. :-D
So in conclusion: The scopes can be very awesome if they focus on "discovering new things which are INTERESTING for the user". They have potential, which we should keep and not kick away. The problem is that facebook would never create an Ubuntu Touch facebook scope and we can not use an API for this but we should see this as potential for the future when in 2-3 years everyone is using Ubuntu Touch (yes, I am VERY optimistic :-P)
RE: UI / UX discussion
Hey, first of all: Awesome work! The mockups are looking great and I like your ideas. Thank you for your effort. :-)
About 1.: The design is awesome. To make the scopes in background blurred is a very good idea. It is logical for the user that all apps are "on top of" the scopes.
About 2. and 3.: To show the launcher only with a long press would mean that it needs more time to access the launcher. There I would see a problem. The launcher and especially the home button needs to be reachable as fast as possible. But I would agree with: Instead moving only to the last app opened, move to the previous (left) or next (right) app. This would be more logical for the user.