Posts made by dobey

Shouldn't the title of the thread be Kaidan on Ubuntu Touch then?

You want to use already existing accounts in your app? Or you want to provide a new account type in your app's package, which other apps could use?

@marc_aurel said in Revised System User Experience:

The Superbook should work with USB-OTG, but I think it requires an approproate driver

It requires a proprietary driver, DisplayLink, and for the display system to work with said driver. Connecting to UT devices will likely let the keyboard/touchpad work, and perhaps charge the phone, but the display will not be output on the Superbook's screen.

@marc_aurel said in Revised System User Experience:

Other dievices like the Mirabook require a full stack USB-C implementation of the hardware. Is there any device with USB-C support?

USB-C is only a connector. Whether something works over it is a separate matter. The Meizu Pro 5 has USB-C for example, but it only supports USB 2.0. It does not support Displayport, MHL, HDMI, etc… alt modes for video.

@marc_aurel said in Revised System User Experience:

According the mobile use case. For sure UBports is ready for mobile use. In my opinion it is not really optimized like the UX of Sailfish, because UBports inherits the UX of Ubuntu - for good reasons.

But why do you think it is not oriented towards mobile use? This doesn't answer the question I asked, and if you cannot describe what exactly you think is wrong with the Unity8 interface designs, I do not see how you will be capable of improving it.

@marc_aurel said in Revised System User Experience:

Is there anyone who is working on an improved, modern UBports system user interface that is more oriented towards mobile use than the Ubuntu desktop user interface?

I'm curious why you think Unity8 is not more oriented towards mobile use. There are multiple parts which are not at all usable on a PC still.

@marc_aurel said in Revised System User Experience:

I can't wait to get the Superbook of Sentio to test this use case.

Remember though, that it won't work with UT, as it's based on DisplayLink for video, which is proprietary. Even if a correct version of DisplayLink drivers were available for a device that UT supports, I'm not sure if Mir would work on them.

First thing I would suggest is to not store the binary packages within the git repo. They will cause the history to get very large very fast, and keeping them there means anyone who would want to contribute to your repo will have to download them all, every time they clone the repo.

It would be better to configure automatic building of packages using the GitLab CI pipelines, and have the click grabbed as a build artifact. You can then link to the pipeline job, or directly to the artifact, for people to download it.

@BrainRenticus There are no guarantees, though there are some previous threads on the subject which you could search for (search for libertine), where others discuss apps that do and don't work.

Apps which require hardware acceleration for graphics likely won't work. Apps that require special drivers to do things likely won't work, or if they do run, won't be usable on the device (arduino stuff for example). Simpler apps that are more straightforward, without external hardware dependencies, are likely to work better.

@fossMan The standard way of doing things in Ubuntu translations is that translations are for the generic version (nb in this case), unless there is a specific need for regional translations to exist (such as for pt_PT and pt_BR). So you should do everything for the nb locale in this case, I think.

@Krille said in I wanna go home:

The conclusion is that it might be very important weither the "Homescreen" is below or over the open apps from the user point of view and Gnome 3 might have a very good solution for this.

But the GNOME 3 solution is not "minimize all apps" in this case. It is simply that the "all applications" view is not some transparent thing that appears on top of the system, but simply is a separate thing and the open applications are not visible behind it.

There's also an important thing missing from this "comparison" (and which is commonly ignored in many such types of comparisons), which is that it only considers what other systems are currently doing, and not how we can do things different/better.

Why can't the "home" screen just be simple and plain? When you come home to your abode, and you're standing in front of the door, all you can see is the plain exterior. You can't see what's stocked in the pantry/fridge/freezer, or what all accessories, etc… might be stored within it, or even how you can access them. You must first go through the openings to get inside and discover all those things. In the same way, having only the launcher/panel visible along with the background wallpaper is the clean exterior, and it makes it clear where you need to go in order to find the interior.

@BrainRenticus Many apps may not work under libertine unfortunately. It would help if you specified which ones weren't working, but for example Chromium, Firefox, and electron apps are known to be problematic. Other apps which may require hardware acceleration may also fail to start (as it can't currently be supported via xmir on the phones).

@rogier-oudshoorn said in I wanna go home:

In terms of "what is home", i typically use the "scopes" app rather then the dash. For me, on the phone, the dash is just a place of shortcuts for apps that I open a lot.

The "Scopes" app is the dash. The thing where you pin apps on the left edge of the screen, is the "launcher."

@rogier-oudshoorn said in I wanna go home:

(if we liked gnome, we wouldn't be here)

Being able to place icons on the background or not has nothing to do with GNOME. One can also agree with many of the design principles of GNOME, but disagree with their implementation of those principles. Let's not conflate Unity 8 existing with the idea that we must do things traditionally which GNOME has chose to not do in newer versions. If that's really what one wants, MATE/Cinnamon exist for that.

I don't understand the bit about the blue circles though. What's with that? There are no such circles when I open the storage page.

@AlainW94 said in SDK documentation:

@dobey Ok, Thanks for your reply, any idea of where I can find the code itself of it please ?

https://github.com/ubports/history-service/tree/xenial/Ubuntu/History

What are you trying to do exactly? We need to add some things to it for proper handling of VVM?

@AlainW94 said in SDK documentation:

Hi, I know this is a very old topic but I think it is the most appropriate for my question, do you know where can I found documentation on Ubuntu.History (used in the dialer-app) please ?
Thanks!
Alain

I think this one is a case of "the code is the documentation," as this is not meant to be a public API consumed by other apps, but is the internal API for dialer/messages apps to access call/message history. AFAIK, it's a thin wrapper to expose the history-service dbus API to a QML model.

@AppLee You cannot control flight mode from your app because that would allow your app to effect the connectivity of not only other apps, but the system itself.

The app itself cannot disable flight mode, or connect to a network. However, you can show a warning and direct the user to enable network connectivity. Even if the radio is on, it doesn't guarantee you'll be able to connect to any specific domain. The route could be blocked for any number of reasons, and your app should deal with such errors in connection as well.

Something like this as a component for swapping out an error page with real content when connectivity changes, should do.

import QtQuick 2.7
import Ubuntu.Connectivity 1.0

Item {
    Loader {
        id: pageLoader
        asynchronous: true
        anchors.fill: parent
        source: Connectivity.online ? "RealPage.qml" : "OfflinePage.qml"
    }
    Connections {
        target: Connectivity
        onOnlineChanged: {
            pageLoader.setSource(Connectivity.online ? "Realpage.qml" : "OfflinePage.qml");
        }
    }
}

The first place I would look for this, is in the history-service database, to see if the "missing" messages are stored there, along with the encoded pictures and such.

@Aurze said in NexDock 2 and Ubuntu Touch:

If you have a compliant phone, does it mean you could achieve the same with any laptop that has a usb-c?

Nope.

@AppLee Why does your app need control of radio devices on the phone? Flight mode toggle is easily accessible from the top drop-down.

If your app needs to check connectivity status, you should use the Ubuntu.Connectivity API from QML. You can check that network is available and show an error page when it's not, before performing tasks requiring network access.

@AlainW94 Are you not implementing this in the telephony-service and dialer-app code? The former already has plenty of code for popping the notifications for incoming call or sms/mms.

Edit: Oh, and there's already a voice mail thing, so you'd probably need to tweak there anyway to avoid multiple notifications for it, and so the visual voicemail page is opened, rather than calling the voicemail number.