as people might have noticed LuneOS is finally… uhm.. released? It is a first Beta version and shows a lot of progress. It still is a bit from a daily driver, though. If you happen to have one of the supported devices, I can only recommend to try it. Especially on the TouchPad it is quite easy to set up.
So what did I supply to this build in the end? There are a number of things, actually. As you might now I created the C+Dav connector (which also runs on legacy webOS). So you have contact and calendar sync with every server out there that supports the carddav and/or caldav protocols. Which includes Google and Yahoo but also home based solutions like Owncloud (there are even owncloud hosting services out there) and eGroupware. Together with that contact sync goes a (still very rough) contacts app that I worked on. Probably this PIM will be my main field of involvement for the next updates, too (if not somebody else steps up and wants to work on a nice contacts app or calendar app).
Then the update service was my work as was the permission handling for media db. So I’m still more the guy that works behind the curtain and my work is not so visible. Ah.. with one more exception from that: I drove Preware 2 a bit forward. It can now install IPKs from disk and from URLs.
If you find any bugs in those, feel free to contact me. Or even better open a ticket in our bug tracker and assign me.
webOS always had tons of twitter clients, most of them great. But then came the most recent death of webOS some time later the API change of twitter. This lead to tons of formerly great twitter clients for webOS now being obsolete and not working anymore.
Ever since I discovered for my TouchPad I loved Spaz HD. It has this nice configurable column interface where you can easily have timelines of multiple accounts next to each other. Yes, I have two twitter accounts, one for my webOS-ramblins (mostly written in English for the international people) and one for my more political discussions (written in German). With Spaz HD I could manage them easily from one single card.
The other advantage of Spaz HD over the only remaining twitter client out there, Project Macaw, is that it feels more responsive. Macaw is a great client, too. I like it on my phone, very much. But to be hones, I can’t stand to use it on my TouchPad. Especially interacting with the App-Menu feels so damn laggy almost all the time. Probably someone has to go through the code and add “enyo.nextTick” into UI callbacks, so that the come back faster and the UI stays responsive.
Anyway, a few months ago Metaview fixed the API issues in Spaz HD (and Spaz) (and also enabled unified columns, so you can have mentions and messages from all your accounts in one column. Great!). I used that for some months, but noticed that sometimes tweeting would fail. Today I investigated that issue a bit more and found out that some characters, namely !, (, ) were not encoded correctly on their way to twitter. Apparently the 1.1 API got more selective there. So I fixed that and Metaview build some new packages (so most of the credits belong to him anyway!):
Ok, I’m not the guy behind the UI… credit for that still goes to @shiftyaxel. But I did some work at the settings stuff and fixed a few bugs with Preware 2 not displaying packages on Open webOS. Yes, this is taken from Open webOS (but only the emulator).
There is still a bug, the Grabber Toolbar is missing. I’m not sure why that is. But that means you can’t install / uninstall / update packages right now.
I always wondered, why there was no CalDav/CardDav synergy connector for webOS. CalDav is one of these web (or at least web-like) open standards that webOS usually uses.
Since some time webos-ports put some effort in creating a synergy connector for CardCav. The repository can be found here. The day I recognized that activity I got in touch with them and moved the connector forward quite a bit. Especially the CalDav part and that it is using the webOS Mojoservice-Sync-framework which takes away a lot of the pain doing a synergy connector was my idea and my work. Currently I am using the connector fine on my Veer and my wife’s Pre 3 for calendar and contact sync (contact only one way from server, calendar two way). I still have a private fork with more experimental version here.
The software sadly did not make its way yet into Preware or the App catalogue… you can apply as beta tester by contacting me ;-). I am still testing with my eGroupware server. Owncloud also seems to work fine, now. I did some rudimentary tests with Yahoo (calendar seems to be fine). Google Calendar is not yet working, though.
I think if webos ports gets this synergy connector into a stable release, open webos will solve one of it’s more pressing issues: That there are no synergy connectors delivered with it.
I must admit that I like the caldav connector that much, that I stopped using SyncML. Therefore that is bad news for all my SyncML using friends: further development of the SyncML connector is rather unlikely. SyncML support seems to be fading out in most server implementations, because CalDav is much easier to implement (actually it’s very similar to webdav and most is done by the webserver already…). A lot of the knowledge I gathered in writing the SyncML connector and quite some bits of the code did go into the CalDav connector. So I’m quite happy with the current situation.
Actually the most pressing issue in SyncML was the slow sync that did happen from time to time and liked to mess up my data a lot.
Maybe, if there are people that are really in need of the SyncML connector and can’t use anything else and are willing in testing (and risk loosing/messing up their data), I’ll reimplement the SyncML connector in the Mojoservice-Sync-framework also, which takes away some of the issues the SyncML connector always had. Till then it might benefit from some improvements in iCal/vCard parsing and generation. But nothing happened on this front, yet.
In a previous post I was looking for a Google Reader alternative for webOS. Shortly after that post I found a TheOldReader app in the app cataloge. Actually this is a modified feeder version. I tried it and it is a decent app (I had some issues with TheOldReader itself, though with missing articles and not updated feeds).
Another possible alternative is to run your own server with Tiny Tiny RSS. This works quite nice and has a web interface which is simple. For webOS there is only an inofficial client though: tt-rssenyo. It is a bit rough, but works nice, too. Currently you’d have to build it from the source yourself, sadly.
What about feedly? I abandoned feedly for some reasons. One of them is that I never got any feedback on any of my requests. Neither for API access (which is now public) nor for APP keys (which are now required) or anything else. So I’m not willing or even able to build a webOS client for feedly. Would be quite fast to implement based on the open source client feeder. Maybe someone else will stand up, someday?
I’ll maybe invest some time in improving the tt-rss client from above, which I am using regularly now. The original author switched to Blackberry, but it’s enyo and quite platform independent. Maybe we’ll get that into the App cat someday, or at least into Preware.
Of course there is a new patch needed. This is also submitted to the Preware Patch portal and will show up in the Memos feed sometime in the future. Alternatively the patch can be downloaded from here: https://raw.github.com/Garfonso/ExportNotes/master/permission.patch
I hope some of you find this useful, not only for leaving webOS behind.
If I get access to the feedly.com api and the api really is similar to the google reader one, that I might be able to update one of the above mentioned feed readers to use the feedly.com cloud service quite fast and publish it in the HP app cat. That would be great.
It is getting quite in webOs land. I fear people already noted that. Many developers left us and also a lot of users. I’m not sure if anybody is still using anything I ever published to webOsnation. Maybe?
If you got here, be asured: I am still actively using my webOs devices (a Veer, a TouchPad) and so does my wife (a Pre3 and also a TouchPad). So I am still in need to sync them with my eGroupware Server (i.e. I am still working on my SyncML Plugin).
Additionally I bought a Galaxy Nexus nearly a year ago and did play with that and Open webOs. Issue with Open webOs is: It has no Mojo. Therefore a lot of apps for the Pre won’t work on Open webOs and this also includes Preware. So I got in contact with webOsports and was working a bit to get Preware rewritten in Enyo2 and running on Open webOs (yeah, future.. here we come. :)). That took a bit time away from my SyncML efforts… but then again I did not have thaaaat much time to spent on them, anyway.
I hope that will change again, a bit, in the future… I got some ideas on how to best sync tasks. Maybe I’ll look into that in the near future. I looked a lot into contact sync in the last week.
There still is an issue one of my french friends had. The app is not really nice to the memory consumption and gets killed if it tries to sync too many items at the same time. I need to restructure that to only load the items into memory that get send during with the next message. That will limit memory consumption to some managable level. I did not achieve that, yet… this really needs a lot of restructuring and will break a lot of things. I hope I’ll manage to look into that someday soon.
Anyway, feel free to look into Preware 2 (the Enyo2 version) and give me some feedback.
There now is a patch in Preware called “Enhanced Contact VCard Export“. The patch repairs some defiencies in the contact export of webOS. One of those, the URL issue, is handled by my SyncML App also. Nonetheless, it makes sense for people trying the SyncML App to install the patch if available to you, because the SyncML App uses that very export function in webOS to export contacts and send them to the server.