Re: [SailfishDevel] How to show toast notification?

2020-03-02 Thread richard grooff via Devel 
 Hi, 

Are you aware of the example at Nemo QML Plugins Notifications - Sailfish OS

| 
| 
|  | 
Nemo QML Plugins Notifications - Sailfish OS


 |

 |

 |

 Best regards, Richard 



On Monday, March 2, 2020, 1:29:02 PM GMT+1, Tamas Miklos  
wrote:  
 
 Hi,

I'd like to show a quick notification to the user of my SFOS app after 
selecting a certain PullDownMenu item.  The notification doesn't need to be 
modal or have any buttons or require any user interaction.  Much like how the 
Toast notification works in Android apps.  The closest I got to something like 
that is showing a DockedPanel and then hiding it after 2 seconds.  But, it 
would be great to achieve that without DockedPanel.


Thanks,
Tamas

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org  ___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Correct way to implement an import/export dialog

2019-10-23 Thread Richard Grooff via Devel 
Maybe use the new phone app with its tabs as an example: tab import and export 
with the same component underneath...

Regards, Richard 

On Wednesday, 23 October 2019, E.S. Rosenberg wrote:
> Both pulldown and push up menus as is already have 3 options, the pull up
> menu has an import option so I want to change that to import/export and the
> page it goes to switches between import and export based on user desire.
> 
> Op wo 23 okt. 2019 om 01:43 schreef Андрей Кожевников <
> coderusin...@gmail.com>:
> 
> > like a caller ui? push up to export, pull down to import?
> >
> > вт, 22 окт. 2019 г. в 23:29, E.S. Rosenberg <
> > es.rosenberg+sailfishos@gmail.com>:
> >
> >> Hi all,
> >> I would like to build a dialog that allows both import and export on the
> >> same page or at least accessible from the same pulley menu item.
> >>
> >> At first I thought I would just have two different forms with buttons on
> >> the same page however according to:
> >>
> >> https://sailfishos.org/develop/docs/silica/sailfish-application-pitfalls.html/#using-buttons-instead-of-platform-style-gestures
> >>
> >> that seems to be the "wrong" way.
> >>
> >> So I wondered is there a "right" way to implement this while trying to
> >> stay within the SFOS UX paradigms?
> >>
> >> Thanks!
> >> Eli
> >> ___
> >> SailfishOS.org Devel mailing list
> >> To unsubscribe, please send a mail to
> >> devel-unsubscr...@lists.sailfishos.org
> >
> > ___
> > SailfishOS.org Devel mailing list
> > To unsubscribe, please send a mail to
> > devel-unsubscr...@lists.sailfishos.org
>

-- 
Sent from my Sony Xperia X with Sailfish X
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Nemo DBus typedCall

2017-06-15 Thread richard grooff via Devel 
Hi, 

With the risk of being totally wrong (I'm not really into DBus): according to 
the DbusInterface example in this page: Nemo Mobile D-Bus QML Plugin — Nemo 
Mobile D-Bus QML Plugin 2.0.0 documentation, you should set signalsEnabled = 
true. 
  
|  
|   |  
Nemo Mobile D-Bus QML Plugin — Nemo Mobile D-Bus QML Plugin 2.0.0 documentation
   |  |

  |

 
Regards, rgr


  From: Dylan Van Assche via Devel 
 To: Sailfish OS Developers mailing list  
 Sent: Thursday, June 15, 2017 2:38 PM
 Subject: Re: [SailfishDevel] Nemo DBus typedCall
   
Hi,
I'm trying to listen to the MCE DBUS API for changes from the display and the 
radios.
For some reason, I won't receive the signals while writing on the /request 
endpoint works perfectly.
Someone an idea?

Seems that Slava can make this work: 
https://github.com/monich/harbour-lib/blob/master/src/HarbourSystemState.cpp

DBusInterface {
id: dbusFlight
bus: DBus.SystemBus
service: "com.nokia.mce"
path: "/com/nokia/mce/signal"
iface: "com.nokia.mce.signal"

// Signals

function radio_states_ind(state) {
console.log(JSON.stringify("MCE radio state= " + state))
}

function display_status_ind(state) {
console.log(JSON.stringify("MCE display state= " + state))
}
}

Cheers,
Dylan



 Original Message 
Subject: Re: [SailfishDevel] Nemo DBus typedCall
Local Time: June 12, 2017 12:00 AM
UTC Time: June 11, 2017 10:00 PM
From: slava.mon...@jolla.com
To: Sailfish OS Developers 
Dylan Van Assche 

 Yes, in that respect the changes are backward compatible. Whatever you are 
getting from GetProperties can be monitored by handling the PropertyChanged 
signals. You just need to be prepared that SetProperty and other calls 
(Connect, Disconnect etc.) may respond with net.connman.Error.PermissionDenied 
if your process doesn't have enough privileges for that.
 
 The idea is that the user has to be reasonably sure that a random app pulled 
from Jolla Store doesn't mess with the system configuration (e.g. doesn't 
enable mobile data behind your back). Most likely, a similar fate is awaiting 
ofono and a few other D-Bus interfaces. Right now Jolla Store apps can do way 
too much over D-Bus. We (well, at least I) will try not to not break backward 
compatibility of D-Bus APIs except when the breakage is absolutely inevitable, 
even though those are not officially supported APIs.
 
 And as always, all these changes are open for close examination at 
git.merproject.org.
 
 Cheers,
 -Slava
 
 
 

Can I still monitor for changes and read properties? Can you give a more 
complete view what will change exactly? I am building an universal bridge 
between Python and QML with integrated Platform APIs based on DBUS and other 
stuff.

Dylan
 




 Original Message 
Subject: Re: [SailfishDevel] Nemo DBus typedCall
Local Time: June 11, 2017 7:16 PM
UTC Time: June 11, 2017 5:16 PM
From: slava.mon...@jolla.com
To: devel@lists.sailfishos.org
Dylan Van Assche 

And keep in mind that starting with Sailfish OS 2.1.1 non-privileged processes 
won't be able to set this property (as well as do a few other connman things, 
e.g. manipulate the services). In order to be able to use the restricted D-Bus 
APIs you would have to ask the launcher to run your app under nemo:privileged 
but that would automatically disqualify the app from getting accepted to Jolla 
Store. Sailfish OS is getting security conscious!

Cheers,
-Slava




You’re missing the property name. You need:
 
string:Powered variant:boolean:true
 
ref:
https://together.jolla.com/question/56437/i-would-like-to-toggle-internet-connectivity-via-terminal-with-dbus/
 
typedCall('SetProperty', [ {'type':'s', 'value': 'Powered'}, {'type':'v', 
'value': valuet}], …);
 
ref: https://talk.maemo.org/archive/index.php/t-92303.html 
 
 
-kimmo
 
From: Devel [mailto:devel-boun...@lists.sailfishos.org] On Behalf Of Dylan Van 
Assche via Devel
 Sent: 10. kesäkuuta 2017 12:45
 To: Sailfish OS Developers mailing list
 Subject: [SailfishDevel] Nemo DBus typedCall 
Hi devs,
 
I'm playing around with the Nemo DBus QML plugin but I'm a little bit stuck 
when using the function typedCall().
 
 
 
    DBusInterface {

    id: wifi

    bus: DBus.SystemBus

    service: 'net.connman'

    path: '/net/connman/technology/wifi'

    iface: 'net.connman.Technology'

 

    signalsEnabled: true

 

    function setState(powered) {

    var value = powered? 'true': 'false'

    typedCall('SetProperty',

  {'type':'s', 'value':value},

  function() { console.log('[INFO] wifi power state set') },

  function() { console.log('[ERROR] wifi power state 
failed') })

    }

 

    function propertyChanged(name, value) {