Enyo 2.0 beta 5 brings panels, bootplates, and more | webOS Nation
 
 

Enyo 2.0 beta 5 brings panels, bootplates, and more 5

by Derek Kessler Wed, 13 Jun 2012 8:08 pm EDT

Enyo 2.0 beta 5 brings panels, bootplates, and more

While we're still waiting for Enyo 2.0 to come with the rest of the Open webOS kit, we'll take an update to the beta framework when we can get one. In fact, this week we're getting one with a bump to Beta 5. Included in this release are sliding and stacking panels, a 'Bootplate' starter template, an improved API viewer, and an expanded and reorganized developer documentation set.

From the user-facing perspective, the news you'll care about is the new 'Panels' UI widget set, a "highly configurable and extensible way to manage and transition between views" in Enyo apps. We're all well and familiar with Enyo's sliding panels metaphor, which is continuing into Enyo 2.0. The new Panels UI widgets, however, don't fit entirely into that domain. Think of them as sub-panels (like in Sparrow), in that you can have a multi-pane set inside a larger panel, as the sample page (source links below) demonstrates.

There are four 'arrangers' available for Panels: CardArranger (full width, fade to next), CardSlideInArranger (full width, swipe to switch with snapping), CarouselArranger (partial width, swipe to switch with snapping), and CollapsingArranger (CarouselArranger, except the panels stack up on the left instead sliding off screen). Panels is also designed to be extensible, so developers can easily develop their own transitions.

On the developer side of things is Bootplate, a complete starter project that can be used as a template for building your own app. Bootplate is designed to be completely self-contained, even packaging the Enyo library and any other necessary dependencies, making it easier to deploy complete apps across multiple platforms. We read through the Developer Guide page a few times, and most of it's over our head, but we can see how Bootplate could prove to be useful for developers.

Also included in Enyo 2.0 beta 5 is an updated Enyo API viewer that both improves performance and better handles multiple libraries. It also now supports the addition of third-party Enyo libraries, and is included with Bootplate. Lastly, the Developer Guide has been expanded (adding new parts - see above - will make that a necessity) and reorganized into more logical chapters. It's all still on the Enyo Github wiki, though it may eventually move to a new format that'll be easier to handle.

5 Comments

Wow!! They're really cool to play with! They could be a game for kids on their own!!

I await impatiently to see what magic the devs can use them for!!

I've just played with the demo, and wow is it cool! Also, all of the arrangers did work in this Internet Explorer 8, a browser with no HTML5 support, but yet one with a big audience, as it is the latest IE available on WindowsXP, an operating system still widely used.

Wow !!! Finally, some good news !!
Can't wait till September !!! (Open) WebOs forever !!!

Too bad it will never see the light of day on a phone - HP or otherwise.

Enyo isn't webOS, really. It's just the interface layer, so it'll make it to other platforms easily enough. The real question is, based on the lackluster performance of Enyo apps on other platforms, how long will it be until they're performing equally as well using Phonegap as a native app would?
 
That's the elephant in the room that no former webOS developer that has since branched out into iOS and Android wants to answer. Put bluntly, a Phonegap-built application will almost invariably run much slower than a native application, and the problem with webOS developers jumping on the PhoneGap ship is that they don't want to take the time to learn the native languages of each platform to create a truly native and optimized experience like the truly professional mobile developers in the industry do. You know, the ones that get paid the big bucks, and this is unfortunately what will keep those ex-webOS developers in "industry-amateur" status until HTML5 becomes the defacto native mobile development platform.