Palm Developer Day Enyo Liveblog 25
This liveblog may only be of interest to developers, but it's potentially the biggest news of the day. Palm is introducing an all-new app framework for webOS that is going to replace their current Mojo framework next year. The talk begins around 5:10 Eastern, so stay tuned.
Here's the description from the agenda:
Track 1: A First Look at Enyo, Next Generation webOS App Framework Speaker: Matthew McNulty, Director, webOS Tools and Frameworks, HP Description: This session offers a sneak peek of what's next for JavaScript development on webOS. Learn about the benefits of the next-generation framework and its impact on webOS developers. In addition to giving an overview of the framework and supporting tools, Matt will demonstrate applications built using this new technology.
Liveblog is after the break!
Alright, event over - wrap up coming soon!
25 Comments
Live stream here: http://www.ustream.tv/channel/palm-enyo
I can't wait to dig into this. Very promising stuff!
Thank you HP/Palm for my Pre2 :))
Wow... I'm actually glad I didn't go to dev day. The only thing good there would have been the Pre2.
I'm not liking what I'm seeing, because Enyo looks too dumbed-down for me. I prefer to actually build it from scratch and if I cannot do that, then I will not continue working on webOS stuff.
I've never liked Ares, and I certainly don't like Enyo, save for the scalability.
There will still be the PDK. There's nothing like really building it from scratch than building it using C/C++.
I am using the PDK for a game right now, but I am a web developer at heart. I have never used anything like Dreamweaver or Frontpage (now called Expression Web) and I never will.
Ares and Dreamweaver are the same thing essentially, and Enyo looks like it is Ares.
I like a few things, but if I cannot build everything completely by hand (as in, not modular but still using WEB THINGS such as div tags) then I will not do any further development for webOS. And this is coming from a person who has already undertaken the extensive development efforts for a massive app (desktop/mobile combo) that will partially redefine the devices and platform. Can't say much since it will be the only thing of its capacity and capability on any mobile platform and I can't let someone take my idea before I can get the product out the door, though whether or not that happens is questionable at this point in time.
Web development already abstracts things very much. Mojo abstracted things even more than standard web development, even more so than web development using jQuery. It's not so much "building from scratch" as it is taking widgets and connecting them using lines of code. I guess it's unfortunate that Enyo abstracts things beyond the point that you feel comfortable with it.
My understanding is that Enyo will have all the capabilities of Mojo, but with greater speeds, faster development time, and both more accessible development and the ability to develop in the traditional web development style.
With Mojo, it adds things, not so much abstracts them. It adds more tools, as well as UI components.
With Enyo, it doesn't sound like I can actually write the code using the currently-standard model-controller-view system in Mojo.
If they maintain that model-controller-view system with Enyo and allow me to keep building the way I'm used to as well as with the added benefits of scalability and fewer memory leaks then that would be great.
Oh, and most of the memory leaks come from developers who aren't careful. A lot of those Ares apps have leaks because the developers aren't aware of how to prevent a leak.
Don't you also have the option of building from scratch?
I don't know, but I would certainly hope so.
According to the live blog you can.
Easiest way to find out is to register for the early access program when they open it up.
I've never used Frontpage either. When I used to make websites, I used to use notepad and Photoshop.
Wait, so if I'm understanding this correctly, it's basically write once, run on any webkit-based browser/system?
That is how I read it. But that may just be wishful thinking. That could make WebOS a lot more appealing to new developers!
I'm on the other side of the spectrum. I love it. Programming for the masses, that will work on all platforms. And more my speed like PowerPoint programming. Can't believe real developers like A.T. wouldn't be able to dig deeper and work even crazier magic with it....?
@arthurthornton what are you developing/have developed that we would know? Just wondering.
Gamer Friends for PSN
YT2V for webOS (first app I made for webOS, but it was a bit ahead of its time, and will be rewritten and made to fully work with webOS 2.0 and JS services)
A couple other apps I cannot speak of
And over a dozen apps in planning, none of which are on webOS and a couple that aren't on any other platform.
I hate, hate, hate GUI development environments. I'm strictly a text editor + CLI type of guy. I prefer my QEdit (DOS,OS/2) and TSEPro (Windows). So, I can definitely understand some of the developers saying.. "Whaa?" at first glance.
However, you have to let this sink in. I don't believe for a second that an Ares like browser environment will be required for developing applications. After all, they simply allow you to visually code. If you write using the frameworks, it doesn't matter what it is written with.
The Enyo frameworks is going to replace the Mojo frameworks. On the plus side, you're applications will run on anything with a WebKit browser, and the scaling is taken care of with the frameworks.
IMHO, I'm going to continue to stick with with my text editors and my CLI... and I'll be able to take advantage of the Enyo frameworks.
For us developers who use vim and like complete control, I see Enyo+Ares playing the role that the emulator currently plays. IIRC, they mentioned they don't even use the emulator anymore, they just test their apps out on Enyo+Ares. If that's the case, that's great. I hate having to start up the emulator, waiting for it to boot, and having it hog my system resources.
@arthurthorton - I was there and I have to tell you that you dont have do use any framework at all if you dont want to(unless you need to access system resources, devices etc). Everything Enyo is everything Mojo wasn't being slow and non- accelerated.
Most the HP guys demoing coding dont use Ares unless they want to quickly prototype and they all prefer other frameworks like Jo or Phonegap for cross platform. If you want to stick with pure javascript and html5 then go for it but ignoring what Enyo brings to the table is just being obstinate.
I use Mojo and will continue to until it is deprecated.
I'm not ignoring Enyo. I'm saying I will not continue doing webOS stuff if I can't hand code everything I want to. If I have to set up all of the stuff in their "modular" system, I probably won't bother with webOS. I love webOS and its amazing capabilities, but I don't like using stuff that is "modular" in the sense they're showing. That being said, I will be one of the first in line to see Enyo, because the code they showed wasn't great. If it is decent (in my opinion) then I will use it, otherwise, I won't.
Ok, you'll abandon it and then what? Program in Java for Android or Objective-C in iOS? Might as well stick with C/C++ in the PDK, or PhoneGap for cross-platform javascript development.
I would just stick with web development. Still a multi-billion dollar industry. Larger than mobile development.
Ah, I see. Well, until we know more about Enyo, I guess you still have at least six months of mobile web development to enjoy, or you could go the PhoneGap route.