Active Topics
-
Porting apps to Leste (40)
to Maemo 7 / Leste by Maemish - 1 day, 21 hrs ago -
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 6 days, 1 hr ago - more...
| The Following 3 Users Say Thank You to abranson For This Useful Post: | ||
|
2016-02-09
, 09:34
|
|
Posts: 203 |
Thanked: 375 times |
Joined on Nov 2009
|
#542
|
Originally Posted by smoku
Dude, we don't even have a release yet, and by the time you wrote this, I didn't even have my own name and no about dialog or something. I don't think that's the most important part. What went wrong in FOSS that everyone starts off with hating every other project? If you don't want other people to look at your code, don't publish it, it's as simple at that.
Yup. It is a rewrite of pebbled. You can see that if you follow the codebase from revision 1. ;-)
As with a long tradition of Ubuntu apps it does not credit the authors of code being rewritten. ;-)
Originally Posted by smoku
Actually in some areas Rockwork supports more stuff than libpebble2 by now.. I'd say the best documentation available is a combination of the two.
Nope.
The best source for Pebble documentation are official libpebble and libpebble2.
EDIT: fixed typo
Last edited by mzanetti; 2016-02-09 at 09:53.
| The Following 5 Users Say Thank You to mzanetti For This Useful Post: | ||
|
|
2016-02-09
, 09:43
|
|
Posts: 203 |
Thanked: 375 times |
Joined on Nov 2009
|
#543
|
Originally Posted by javispedro
If you look at the commit times of RockWork you'll notice that all of them are late night, mostly weekends. RockWork is really a spare time project. That said, how did this become about competition? I've intentionally made the platform integration very sparated from the rest of the code.
That said, we cannot really compete with a full-time employee working on it. "Rewriting" it back from their version should be considered an option. For me at least it looks easier than writing a store UI.
Actually in the beginning I started off trying to port the sailfish pebble directly, but then, all the SFOS specific parts were deeply integrated all over the place. After the 100th #ifdef I gave up and started from scratch, trying to avoid this mistake.
EDIT: Also, writing the store UI is super simple, that's a matter of an afternoon or so. Maintaining a WebView with all the hacks that integrates with the pebble store website is IMO *much* more hard work.
Originally Posted by javispedro
Yes, pebbled has been a pleasure to "rip off". At this point there is nothing useful for me in it any more, especially since support for watch firmware >= 3.0 is quite poor. Anyhow, the offer still stands, I'd be happy to accept a SFOS backend in RockWork.
They also removed support for the pre-3.0 firmware on the original models, btw.
Sadly no, their "documentation"/implementation is far from complete. Like every other smartwatch, I had to sniff their protocol out, otherwise I still wouldn't know how to upload a binary. Almost nothing of BlobDB is documented there.
The best source for documentation at this point is pebbled, and the fact that Ubuntu guys decided to rip it off entirely and even Pebble employees themselves are using parts of it now should be kind of proof...
| The Following 8 Users Say Thank You to mzanetti For This Useful Post: | ||
 |
|
2016-02-09
, 09:54
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#544
|
Originally Posted by mzanetti
A more appropriate question would be: what went wrong in FOSS that everyone starts with forking, renaming the project, wrapping behind their doors, refactoring, rewriting, and only then offering to maybe, you know, actually share code and avoid a fork?
What went wrong in FOSS that everyone starts off with hating every other project?
Specially when upstream is still quite alive with plenty of contributors, if only slow?
The sad part is that we had the same discussion like, less than a few months ago..
But oh well, that opportunity is lost already, so let's center on the future. I personally agree on the store UI changes and dropping pre3.0 support. Slots are too annoying either way.
EDIT:
Originally Posted by mzanetti
In the sense of evaluating what will be the best option ahead for users (and developers) of Pebble and Sailfish, and at this point, I believe it's 'embracing your fork'.
That said, how did this become about competition?
But no need to "act surprised" when meeting resistance after taking over the reins of still-alive project.
Last edited by javispedro; 2016-02-09 at 10:12.
 |
|
2016-02-09
, 10:18
|
|
Posts: 1,716 |
Thanked: 3,007 times |
Joined on Dec 2009
@ Warsaw, Poland
|
#545
|
Originally Posted by abranson
I didn't completely give up on SailfishOS though.
[...] since Smokku gave up on his Jolla,
I'm still hoping that SFOS port for OnePlus One reaches the state that it could replace Android as my daily driver.
I bought OnePlus One exactly because it looked like it would be any day now... and after a year - still big NOPE...
__________________
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
| The Following 2 Users Say Thank You to smoku For This Useful Post: | ||
|
|
2016-02-09
, 10:46
|
|
Posts: 203 |
Thanked: 375 times |
Joined on Nov 2009
|
#546
|
Originally Posted by javispedro
I really wanted to reuse pebbled as it was, I think I even still have a directory on my disk where all the SFOS stuff is #ifdef'ed out and replaced with ubuntu specific things. It just wasn't feasible any more at some point. Reusing software is a hard thing if it hasn't been created with platform abstraction in mind. I really hope I did a decent job with that in RockWork (as I've only ran it on Ubuntu so far, this part yet has to be proven).
A more appropriate question would be: what went wrong in FOSS that everyone starts with forking, renaming the project, wrapping behind their doors, refactoring, rewriting, and only then offering to maybe, you know, actually share code and avoid a fork?
Specially when upstream is still quite alive with plenty of contributors, if only slow?
The sad part is that we had the same discussion like, less than a few months ago..
But oh well, that opportunity is lost already, so let's center on the future. I personally agree on the store UI changes and dropping pre3.0 support. Slots are too annoying either way.
| The Following 4 Users Say Thank You to mzanetti For This Useful Post: | ||
|
|
2016-02-14
, 00:02
|
|
Posts: 287 |
Thanked: 862 times |
Joined on Dec 2015
|
#547
|
I've been having a lot of fun trying to port Rockwork back over to Sailfish. The daemon's running, and connecting to the pebble (v3 firmware). Music/volume control works, and notifications, which have lots more flavours than the old v2: telegram, whatsapp, hangouts, which i've mapped over to the android and native apps where present. I also managed to find a bit of code to decode the notification actions, so you can now open the email on the phone from the watch.
| The Following 13 Users Say Thank You to abranson For This Useful Post: | ||
 |
|
2016-02-14
, 13:00
|
|
Posts: 654 |
Thanked: 2,368 times |
Joined on Jul 2014
@ UK
|
#548
|
Originally Posted by abranson
This is awesome
I've been having a lot of fun trying to port Rockwork back over to Sailfish. The daemon's running, and connecting to the pebble (v3 firmware). Music/volume control works, and notifications, which have lots more flavours than the old v2: telegram, whatsapp, hangouts, which i've mapped over to the android and native apps where present. I also managed to find a bit of code to decode the notification actions, so you can now open the email on the phone from the watch.
despite some initial misunderstandings, it looks like things are progressing to the point where the fork will contribute some useful enhancements back to the original project.There's so much overlap between people interested in Sailfish and Ubuntu Touch, that it makes a lot of sense to collaborate on this!
|
|
2016-02-17
, 13:15
|
|
Posts: 1 |
Thanked: 1 time |
Joined on Feb 2016
|
#549
|
Originally Posted by abranson
Awesome news! With the authorization of mzanetti or smoku (if necessary, I don't know), is that something you can publish at some point ?
I've been having a lot of fun trying to port Rockwork back over to Sailfish. The daemon's running, and connecting to the pebble (v3 firmware). Music/volume control works, and notifications, which have lots more flavours than the old v2: telegram, whatsapp, hangouts, which i've mapped over to the android and native apps where present. I also managed to find a bit of code to decode the notification actions, so you can now open the email on the phone from the watch.
Thanks!
| The Following User Says Thank You to ClumsyRooster For This Useful Post: | ||
|
|
2016-02-17
, 14:47
|
|
Posts: 287 |
Thanked: 862 times |
Joined on Dec 2015
|
#550
|
Originally Posted by ClumsyRooster
Oh certainly. I've got it installing as an rpm now, but diving into the QML has been tricky so far, especially seeing as I don't really know much about that. The Rockwork QML looks much more complex than anything I've seen in Sailfish so far, and my usual technique of cobbling it together using other projects as example isn't really working - there are just too many elements and attributes
Awesome news! With the authorization of mzanetti or smoku (if necessary, I don't know), is that something you can publish at some point ?
.What I might do is get the platform integration for the daemon mostly together, then pop it up on Github and see if anyone else fancies looking after the UI. If not, then I'll just have to get a book or something and learn it properly.
Mzanetti has been giving me tips, and I'm pretty sure smoku is aware and ok with it.
 |
| Tags |
| pebble, pebble time, pebbled |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 19:16.
Yes it started off with the pebbled code, but he's done a really nice job expanding and refactoring it. He's added a large amount of new support, and kept all of the Ubuntu specific stuff separate leaving a core libpebble that's really comprehensive. I believe we could add Sailfish support around it and even share a common codebase in the future, and Michael was keen on collaborating on that. Pebbled has stalled a bit lately since Smokku gave up on his Jolla, so Sailfish rockwork (Rockpool?) would be able to keep the flow of code coming and keep up to date.