Which additional quick actions would you like to have?

+100 :) But i can put only one vote.

My god, the ONE really useful shortcut to have on the status page is NOT possible to put there, neither as shortcuts or quick actions. What ARE they thinking???

Exactly even I wonder why Jolla did not ask community itself. Given that we are such an active and vibrant community. One simple poll would have been helpful.

@Larswad, because it is not a toggle to be added to switches nor an action to be added to actions. I hope they've already known what they'll wanna do with it. The only way, I think, is to be able to add it to shortcuts to open the Settings page.

In general they need to add a quick access to set your status. Also the brightness and loudness options are rendered differently as sliders. So why not also a similar extra option for your online status?

I had the same idea, and I did already some research, but I have not found anything by now. I thought of something like the desktop links in /usr/share/applications, just passing some additional parameters.

I second you on this, a simple option to define my own command would be very ideal.

Wouldnt that clutter the pulley? How about having these available in a separate place?

The idea was not to put them all into events view pulley. That would be senseless, I agree. I edited the post to be clear that the emphasis is on choice, since everybody has his/her own priorities.

Okay, so having the choice to put them (which is currently missing) rather than putting them in a precise spot, am I understanding it right?

I really miss that.

yes to scedule meeting

Did it! I added this to /usr/share/jolla-calendar/DbusInvoker.qml

signal createNewEvent

onCreateNewEvent: {
    pageStack.push("pages/EventEditPage.qml", {}, PageStackAction.Immediate)
    requestActive.start()
}

and here's my new file, /usr/share/lipstick/quickactions/com.jolla.calendar.conf:

priority=4
requires-package=jolla-calendar
icon=icon-m-time-date
title=Create an Event
remote-service="com.jolla.calendar.ui"
remote-path="/com/jolla/calendar/ui"
remote-interface="com.jolla.calendar.ui"
remote-method="createNewEvent"

Disclaimer: I have no idea what I'm doing in QML

Wonderful! Would you like to make an RPM? Something like "Additional quick actions". If not, then with your permission, I can start tomorrow. Too tired now. At least now we know where to look, so the others should not be too difficult.

That's a brilliant idea. I'm sure we could add additional DBus calls to add extra actions - there isn't a lot available in the standard Jolla apps yet. Would this be a patch manager thing?

Whilst I agree that "take a selfie" is about the most useless action of them all, to take a photo you do not need a quick action. Launching a camera is actually fewer steps away (1: swipe up, 2: tap Camera icon, as opposed to 1: swipe right, 2: swipe down, 3: tap shortcut).

I do not see the point in "quick actions" that are just replacement of a regular app launch. The point of a quick action is to provide a direct shortcut to actions that require additional steps. For the same reason I do not see the point in adding the entire Settings app there, as I have seen suggested somewhere: it is easier and faster to open it normally, from the launcher.

Actually I think you could create a .desktop definition containing all those extra parameters including the call of the app, have it in the app drawer and be much quicker.

You can edit the file /usr/share/lipstick/quickactions/com.jolla.camera.conf to do this. Change:

remote-method="showFrontViewfinder"

to

remote-method="showViewfinder"

and the shortcut will open the camera app with the last viewed camera instead of the front one. Not sure how to change the text though. It's in /usr/share/translations/lipstick-jolla-home_eng_en.qm but it's a binary file.

Good work, Andy!

About the string. If the mountain doesn't come to Mohammed... ;-)

Just edit the title line to title="Take a photo". The disadvantage is that the string is hard-coded and does not change when you change the language but if you can live with that...

Made an RPM package to support all languages. Hope you will enjoy!

yes, should sync all mail accounts and including twitter feeds if set to manual.

I think this is supposed to be set in ambience one day.

I still don't understand why this can't be done with the volume controls, as in other operating systems. Maybe not unlike enough...

@tokaru, +1!

this should be a MUST. I' m waiting for this already a long time....

I think it should be possible to set the default app for anything: browser, email, media player, maps...

Yes if you know how to set up URL handlers as requested here.

That one is already implemented.

In my opinion, it should be implemented as a switch, like WiFi/Flight mode

Did you follow my link? That's exactly how it is implemented ;)

I dont understand why it is still possible to "share" a photo via twitter but sending a simple tweet is impossible without a client?

That's a good idea. I'll see if I can tinker one.

Here comes my solution.
Add these lines to /usr/share/voicecall-ui-jolla/main.qml after line 324 (inside DBusAdaptor of Component):

signal openDialerNumber(string mynumber)
onOpenDialerNumber: {
    dial(mynumber)
}

Then create one file for each number you want have represented among quick actions, like /usr/share/lipstick/quickactions/com.jolla.voicecall.Pers1.conf:

priority=4
requires-package=jolla-voicecall
icon=icon-m-person
title="Call Person 1"
remote-service="com.jolla.voicecall.ui"
remote-path="/"
remote-interface="com.jolla.voicecall.ui"
remote-method="openDialerNumber"
remote-arguments/size=1
remote-arguments/1/argument="+1234567890"

Just tested it works. Maybe somebody could find a more elegant solution regarding main.qml, e.g. passing the number from inside the quick action's config file to the dialer. This way the qml file could stay unchanged for further quick dialers.
EDIT: found out how to pass parameters along with the signal and changed the code accordingly.

Well done, @lakutalo! So now we just need a way to pass parameters from text input to conf file to keep it unchanged too. And where does that mynumber string go?

In my tiny little world I would be OK with one conf file per contact containing the number itself in it. This way I created two conf files, and everything was fine for two direct quick call action buttons. I guess you wanted to open dialer with a number prompt, didn't you? I'll see if I can find out.

No, I want to enable the user to enter the phone number(s) once (somewhere in Settings, for example) and they can change the number easily.