Results 1 to 4 of 4
Like Tree1Likes
  • 1 Post By areacode212
  1.    #1  
    So, I'm trying to dip my foot into WebOS development, partly for fun, and partly with the long-term goal of making an x265-compatible media player, since Kalemsoft won't work with HEVC files.

    I'm trying the Enyo tutorial on the HP site, as well as a tutorial which I found on a different site, and neither of them are working right in the 3.0.5 emulator.

    I'm stuck on this part:

    https://developer.palm.com/content/a...tutorial2.html

    The PageHeader and RowGroup objects are not appearing in the app in the emulator--I'm just getting a blank page. Any ideas?
    Preemptive likes this.
  2. #2  
    The easiest mistake to make and fix(!) would be a path problem for the framework. The tutorial assumes that the enyo framework is at:
    Code:
    src="../../enyo/1.0/framework/enyo.jsjsjs&$quot$;
    relative to your index.html file.
    So first be sure to make that path correct relative to your index.html file.
    If you are not familiar with relative paths, the code from the tutorial is saying that from the index.html you need to go up 2 directory levels ("../../") and then you should find the enyo folder there.
    I just did a test where I copied the "framework" folder from the SDK (HP webOS/SDK/share/framework) and put that copy inside the FeedReader folder that the tutorial tells you to make, so to get this to work I needed to change the path to:
    Code:
    src="framework/enyo/1.0/framework/enyo.jsjsjs&$quot$;
    since I put the SDK's outer framework folder INSIDE the FeedReader folder, so it is at the same level as index.html. You don't need to do that, but you do need to make sure that path is correct.

    EDIT: Realized the project was being tested in the emulator.!

    Perhaps someone with more experience with Enyo 1 and emulator can correct or confirm, but I think that for building, packaging, installing and testing in the emulator you will need to have that path from root as:
    Code:
    src="/usr/palm/frameworks/enyo/0.10/framework/enyo.jsjsjs&$quot$;
    I was thinking of browser-based testing and Enyo 2 building where you aren't relying on the built-in framework.
    Last edited by bbito; 01/20/2015 at 03:35 PM.
  3. #3  
    Quote Originally Posted by bbito View Post
    ... I think that for building, packaging, installing and testing in the emulator you will need to have that path from root as:
    Code:
    src="/usr/palm/frameworks/enyo/0.10/framework/enyo.jsjsjs&$quot$;
    Yep, that works in the emulator!

    I made the tutorial structure, ran palm-package and palm-install to the emulator and the app shows enyo UI bits when launched in the emulator.

    I'd suggest making a corresponding "debug.html" that has a relative path to your framework folder as I described earlier for browser-based testing as described here:
    https://developer.palm.com/content/r..._tutorial.html
  4.    #4  
    Thanks bbito, I will try it out and report back.

Similar Threads

  1. Enyo introduces Moonstone,Spotlight,Enyo 2.4
    By akitayo in forum webOS Development
    Replies: 3
    Last Post: 04/14/2014, 05:28 PM
  2. Enyo apps on all your Enyo-enabled devices
    By rsanchez1 in forum webOS Discussion Lounge
    Replies: 14
    Last Post: 12/16/2011, 01:34 AM
  3. beginner
    By jon0604 in forum webOS Development
    Replies: 0
    Last Post: 08/18/2009, 09:32 AM
  4. beginner
    By jpsu2001 in forum Palm OS Devices & Apps
    Replies: 21
    Last Post: 05/04/2005, 03:20 AM
  5. Help for a Beginner
    By jackeyres in forum Palm OS Devices & Apps
    Replies: 8
    Last Post: 02/15/2004, 12:15 AM

Posting Permissions