Enyo-ify Facebook

[snorri788]

How hard would it be to create a brand new Facebook app in Enyo? I hardly use the current webOS Mojo Facebook app, and instead resort to the web version. However I would love to have a new app and have it coded in enyo instead so that it is faster and more versatile.

Has anyone started doing this already? If not, how would you go about doing so?

[geekpeter]

touchpad version is enyo isnt it? or did you mean the phone variant?

[Herrie]

Phono = mojo, TP is Enyo. Would be good to port to Enyo 2 and use updated API so all functionality works properly....

-- Sent from my TouchPad using Communities

[Vistaus]

Enyo 2 works great on the Pre 3 at least. Tested out the new Dutch Railways app created by Palmclub.nl yesterday which is written in Enyo 2 and it works superb on both the Pre 3 and TP so Enyo 2 would be a good way to go plus fhe Facebook API is publicly available so anyone could do it

As a placeholder, one could App Tuckerbox the TP FB app on the Pre 3 which works fine, just a little awkard because of the sliding pane, but for basic tasks just fine.

[Grabber5.0]

Enyo is not faster. That was one of the selling points, but it was bs. It may have been faster when they were still prototyping, but in the end, it's kind of a wash. I think they are both fast until you start dealing with long lists. Of course, on phones, Enyo is even a bit slower than Mojo most of the time.

[Derek Kessler]

Enyo 1 is not necessarily faster (on smartphones).

Enyo 2, however, really is. I've played with a handful of Enyo 2 apps on TouchPad and on my Pre3 and they fly in a manner Enyo 1 and Mojo never could.

[broncot]

Originally Posted by Vistaus

As a placeholder, one could App Tuckerbox the TP FB app on the Pre 3 which works fine, just a little awkard because of the sliding pane, but for basic tasks just fine.

Nice tip, never thought of trying the TouchPad FB app on the Pre 3, thanks!

[hrminer92]

Originally Posted by Derek Kessler

Enyo 1 is not necessarily faster (on smartphones).

Enyo 2, however, really is. I've played with a handful of Enyo 2 apps on TouchPad and on my Pre3 and they fly in a manner Enyo 1 and Mojo never could.

What is the list of Enyo 2 apps that you're referring to? I would like to try them out.

I may try out the facebook tablet app on my Pre3 and see how it goes.

[Herrie]

Enyo 2 works great on the Pre 3 at least. Tested out the new Dutch Railways app created by Palmclub.nl yesterday which is written in Enyo 2 and it works superb on both the Pre 3 and TP so Enyo 2 would be a good way to go plus fhe Facebook API is publicly available so anyone could do it

As a placeholder, one could App Tuckerbox the TP FB app on the Pre 3 which works fine, just a little awkard because of the sliding pane, but for basic tasks just fine.

I was in contact with the developer and he actually made it with Enyo, not with Enyo 2. I'm currently working on an Enyo 2 9292 app, but it's been a quite steep learning curve so far. My time is limited but hope to have an initial version in the next couple of weeks and from there to expand. It's my first app so not easy at all...

What's done so far:

Get disturbances
Get planned maintenance

Get saved locations from account
Get saved trips from account (partly done)

Todo before initial release:

Complete saved trips implememtation (70% done)
Nearby stops & departures (based on GPS)
Trip planning
Account login and create cookie on device
Make it working properly on phones (back gesture, sizes for Veer, Pre2/3 etc)

Future version after initial release:

Add settings (might do on initial release version)
Multi language
Ability to update saved trip & locations from app
Include Google Maps in trip advices


-- Sent from my TouchPad using Communities

[Vistaus]

A 9292 app would be nice, but I don't see that as a priority when it comes to useful Dutch apps... but then again, it's probably one of the easiest ones because they have code to work with.

And you're right, I misread: Spoorino is Enyo 1.

@broncot: You're welcome!

[Vistaus]

Originally Posted by hrminer92

What is the list of Enyo 2 apps that you're referring to? I would like to try them out.

To mind comes:

-Top Watch, a new free app in the App Catalogue.
-Phx Maps, you can grab it from the thread in Open Source Development.
-OWO Memos, also grabbable from OSD.
-Sprw beta, you can grab it from Its blog (sprw)
-Macaw Enyo, but you need to package it from Git for now and the scrolling is jerky at the moment but being worked on.
-Preware Enyo2, but it's fare from usable though the concept is there already.

And there are probably more that I can't think of right now :P

[Herrie]

Originally Posted by Vistaus

A 9292 app would be nice, but I don't see that as a priority when it comes to useful Dutch apps... but then again, it's probably one of the easiest ones because they have code to work with.

And you're right, I misread: Spoorino is Enyo 1.

@broncot: You're welcome!

Can you make your list, so I can have a look to see what can be done?

9292 is closed source API but I did some snooping around in the Android APK and found interesting bits that I can use for the Enyo 2 app

[Misj']

Originally Posted by Herrie

Can you make your list, so I can have a look to see what can be done?

9292 is closed source API but I did some snooping around in the Android APK and found interesting bits that I can use for the Enyo 2 app

I think both the (excellent) SpoorInfo app and a potential 9292 app are off topic...still I would guess that 9292 open data should be usable. And it is freely available.

As for an Enyo2 version of the facebook app. For webOS 3.0 there really is no good reason to go Enyo2. For open webOS 1.0 there is likely no good reason to go Enyo2 (since the core-apps are all written in Enyo1, and we therefore can assume that the framework is a first-class (senior) citizen of the open OS (albeit not actively developed anymore)). If you want to (potentially) go beyond webOS (3.0) then things are different of course.

That being said. Any further development is good development.

[Herrie]

Originally Posted by Misj'

I think both the (excellent) SpoorInfo app and a potential 9292 app are off topic...still I would guess that 9292 open data should be usable. And it is freely available.

As for an Enyo2 version of the facebook app. For webOS 3.0 there really is no good reason to go Enyo2. For open webOS 1.0 there is likely no good reason to go Enyo2 (since the core-apps are all written in Enyo1, and we therefore can assume that the framework is a first-class (senior) citizen of the open OS (albeit not actively developed anymore)). If you want to (potentially) go beyond webOS (3.0) then things are different of course.

That being said. Any further development is good development.

9292 Open Data is pretty much the same as Open OV. However 9292 Open Data would require you to develop your own databases etc, while the Android, iOS and Windows Phone app use the closed source 9292 API which has everything in there already. It's as easy as sending a request and getting a JSON with all the right data back! So that's what I'm using

Enyo 2 certainly has advantages over Enyo (1), especially performance wise and cross device portability. The OWO Memo app written in Enyo 2 works a lot faster on my Veer compared to the stock app on the Veer. Since the Veer only has 800 Mhz CPU it might be that the performance difference is more noticeable there compared to a Pre3 or TP which runs faster by default?


How about other (NL) apps you'd like to see on webOS?

[Vistaus]

I'll see if I can make a list Herrie

@Misj: Well, the Pre 3 FB app is in need of a replacement so Enyo 2 would be the best to start with and Enyo 2 apps run fine on the Pre 3.

[kevets]

This prompted me to check out the OWO Memos app... and jeez.... if all of our apps were Enyo 2 and as snappy as this I would never leave webOS.

Can we get an Enyo 2 browser with new webkit? One day?

[Vistaus]

Yes, dkirker is taking care Isis Enyo 2 web browser!

[eblade]

Originally Posted by Misj'

I think both the (excellent) SpoorInfo app and a potential 9292 app are off topic...still I would guess that 9292 open data should be usable. And it is freely available.

As for an Enyo2 version of the facebook app. For webOS 3.0 there really is no good reason to go Enyo2. For open webOS 1.0 there is likely no good reason to go Enyo2 (since the core-apps are all written in Enyo1, and we therefore can assume that the framework is a first-class (senior) citizen of the open OS (albeit not actively developed anymore)). If you want to (potentially) go beyond webOS (3.0) then things are different of course.

That being said. Any further development is good development.

There are plenty of good reasons to use Enyo 2 across the board, the only good reasons I can think of to use Enyo 1 is if you need access to one of the libraries that it came with, which no one ever used, such as the Accounts interface. I don't know that it was even possible for non-Palm apps to use those libs, I tried for quite a while before I gave up and wrote my own based on it.

[dkirker]

These forums need a nick mention feature, like in IRC.

WRT to Enyo2 vs Enyo1 vs Mojo... It all depends... Enyo2 BLAZES on devices like the iPhone 5 and Android phones, and the computer... But, the list implementation BLOWS CHUNKS so far on webOS 2.0 devices. I suspect that this has to do with lack of compositing (hardware acceleration), or a poor implementation. Some of it could be cleaned up, IMO. Enyo1 lists on the other hand, perform rather well...

[Herrie]

Originally Posted by dignitary

Never, ever make an app around a closed-source API without written permission amounting to a license from the provider unless:

• You enjoy having to explain to users why the app they're depending on broke and there's no documentation to tell you why, leaving them in a lurch for long periods of time (see: WhatsApp for webOS)
• You have really good legal representation if/when the data provider decides to send a few threatening letters your way from its legal team

Thanks for the advice. It's more for improving my own development skills and it would never be a commercial project. We don't have many webOS users in our small country. I would be surprised if there would be 20+ people using the app to be honest.

API doesn't change much, it's just the most convenient app when you get around by public transport a lot here in NL.