Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I have just tried it to replace Pebbled, which was a fantastic job but not maintained too much anymore
and all I can say is waouh. That is really fantastic. I have also upgraded my watch to latest firmware (so I am probably positively biased because Pebble did a great job too...) but while I was expecting some glitches or worst, that went like a charm.
That is the great part of open source: when several people improve things hand in hand, from original source to forks and from authors to contributors and even testers!
I would happily give some free beers (as I did to smoku) if I ever find how to do it?

conclusion: thanks a lot :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

*Sigh* again _worksforme_ https://www.ruff.mobi/gfx/20160409144307.jpg ¯\_(ツ)_/¯

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

This authenticator app was a good usecase to reshuffle appsettings window though.
First it had two dialog box calls - so now alert and confirmation calls are implemented in gecko.
Then it had cancel button right at the top left corner - which forced me to return page heading shifting webview down below.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Hey, thanks a lot for awesome work on the app :)

I'm curious, do you have any plans (possibilities?) for supporting the "developer connection" (https://developer.pebble.com/guides/...er-connection/) thing?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yes, it is on the list, however it has dependency on websockets which in qt5.2 is external.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Really need to test that with a watch app that uses websockets, but not I'm not sure many do.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

for dev connections websocket is used in a bit different pattern, will try to merge your WS branch into my wip and see how it could be utilized. Ultimately phone-side implementation is here and looks fairly simple on a first sight.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That does look quite simple, is that all there is to the developer mode?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Well, yes, most important is I think do_relay which makes direct raw binary channel to the pebble.

There's also cloudpebble part which makes the same but via external wss proxy, but we need some insight from Kath probably to find out how to make it properly from the phone perspective (need to register itself as an endpoint somehow I presume).

Also I've found a repo on merproject hosting qt5-qtwebsocket rpm built for jolla, which allows greatly simplify at least the build. Just built websocket branch with it.
Edit: I forgot openrepos is also an rpm repo :) so that also could be used with coderus build

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

It's quite quiet in the Ubupebblers telegram chat at the moment. You should join!

Yes, my branch was using the coderus rpm on openrepos. Version 5.7 (!) vs 5.3.2 on sfietkonstantin's obs though, so we've got an alternative there if there are problems with a particular version.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I don't have telegram, is there any irc chan alternative?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Hmm no sorry, the Jolla fan club has an irc relay bot, but the ubupebblers doesn't.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I've made some progress on the profile thing - it's in my own WIP branch. I also switched those sliders on the settings page to combos because wtf. Hope you don't mind...

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Well my idea with repeaters and single call with enum states was to make it extensible, not locked to just two conditions (connected/disconnected) but... whatever :) Slider is just my personal preference to make less clicks when choosing options.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yeah I thought that was nice too, but everything else was done as Q_PROPERTYs and it looked like that couldn't take the extra param. I like the idea of a tap and drag setting, but I think the slider just looks plain weird if it's not setting a scalar. I bet there's a good idea for an unlike component there though. Maybe one of those graph based controls where the possible option pop out around your finger and you just drag to the one you want.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I've finished the profile switching. Are all those other commits ok to go? Is there anything else still in progress? I'd like to push out a 0.9-3 because I messed up the version thing on 0.9-2 *again* :)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

those are good i think, i have them in beta and on my phone already. I guess PR is not needed as you've merged and amended commits?
I'm currently working on dev.connection implementation in the wip.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I tried to build rockpool myself. But building from QtCreator yields "Project ERROR: qt5embedwidget development package not found". I've read that sailfish browser can only be build in the Mer SDK VM itself. Is this related? I don't mind the occasional command line, but generally I'd prefer using IDE's for this kind of stuf...

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Yeah I think this conversation does the work of the PR just fine when we're just exchanging commits simply like this.

You have to install some stuff into your build VM - some you can do with the 'SailfishOS' admin interface, but the mozilla stuff you have to add a repo in there so you need to go in with SSH. The README file gives the details.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That's awesome. I'd love to see that working.

One small thing I noticed - On the config for the 'Rain' app, I couldn't cancel. There's no spot in the top left corner, and I can't swipe it or tap it away. Could that be a side effect of the header, or have I just not tested it since the Moz came in?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

D'oh. Reading READMEs, what a brilliant idea! :o

However... after installing those extra packages in the MerSDK, the issue remains :confused:

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Did you definitely switch to the right scratch box? You can add repos and install packages if you don't, but they aren't available to the scratchbox (I think). Also, that zypper repo url was one path too long - I changed it.

0.9-3 building now btw

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Both the spot as swipe to cancel work as expected here in Rain settings on rockpool v0.9-1.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I think I followed instructions correctly. (at least, there were no incidents involving a ceiling fan :D)

Seems to me it went OK, as this is what I'm getting now:

Edit: Updated to v0.9-3. Spot & swipe to cancel still work in Rain settings. Automatic profile switch works great, thanks!

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

And you're definitely building the arm version? Sorry to ask the obvious, but I'm not an expert in this stuff. I also just delved into my scratchbox and noticed there are a lot of package updates pending, including the moz packages. I wonder if there's a new sdk version imminent for 2.0.1 or 2.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Is it on the tablet?
There's only one reason for back spot (right swipe or back navigation) to be blocked - when content rect is not at the left side - eg. zoomed in.
On the phone content is auto-zoomed to fill width, and you cannot zoom out for smaller than width size (eg. child's left cannot be inside viewport, only aligned or outside.
However I could imagine that tabled may not behave same way as the screen is apparently bigger. so zoom-out might be allowed. in that case small content may have child rect inside the view, not aligned. which will block navigation. Ig you can debug contentRect.x change - that will answer this suspicion, and then navigation-block condition could be amended to allow child.x inside view, while still blocking when it's outside (zoomed in)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

No it was on the phone, but I think the window had zoomed/moved a little somehow. I can't replicate it now though, but that means it's no longer a worry.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

You're more an expert than I am :) I did configure the ARM kit for the project, but after the SDK-issues I did a git reset HEAD --hard, after which that kit was gone again, leaving the x86 for emulator as only available kit - even though the Jolla was selected as device. It now builds.

Btw, you can add
to the .yaml file. Manually adding quazip-devel to the sdk is therefor no longer needed.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I'm pretty sure that didn't work before, and I saw quazip in the list of upgrades that zypper wanted to do. Someone must be listening!

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Or is it a nice side effect of adding the mer-core repository?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Could be. Newer version of the same lib anyway.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Weird... it suddenly started to work for me as well :p sorry for the confusion.


On another note, I've found an app that makes the phone barely usable untill you restart the phone. (or maybe restart the deamon, haven't tried that)
I'm talking about this one:
IpCamRemote

I couldn't find anything on the logs...

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Do you know any public cams to test that against? I don't have one...

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

IP: 115.236.50.5
Port: 8800
Username: guest
Password: guest4500

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

Strangely the submit button doesn't seem to do anything for me.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That's the problem that I have as well..
Does your phone suddenly goes slower after submitting?

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I'm afraid not. Nothing in top either. Just nothing happens. Can you see why it's slow on yours?

Btw, there was a problem with the last couple of versions - all previously known notification sources were considered turned off even if they were on. It's fixed in the latest version (0.9-4), but you can manually enable them on the notification page.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

About notifications: Ah! That's why I didn't receive anything! :p

About the IPCam: I find it strange that the link at the top that is showing, contains the provided information, even when I totally remove the watchapp and reinstall it.
Seems like the setup was somehow accepted before, and now it tries to load the IPCamera, which causes into a massive slowdown :(

Edit:

This should be the link:
And submit does:
Edit2:

By the way, have fun watching all kinds of unsecured IP cameras around the world:
http://www.insecam.org/

Edit3:
Feature request: Is it possible to refresh the screenshot by tapping on the Pebble screen at the GUI (without saving the last one, so if you keep tapping on the screen to refresh, it will automatically delete the last screenshot so your phone wouldn't be full of screenshots :p)

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

That's strange actually, to me the fell back to state 1 which is disable-when-active (since true value converts to 1 and false to 0 when doing value("true").toInt()). But yeah, anyway I forgot to mention that outcome.

Re: [Announce] Rockpool - Pebble daemon for Sailfish
 

I noticed this, but within an hour you had published a new version with a fix :) kudos