**** BEGIN LOGGING AT Wed Jan 09 03:00:00 2013 Jan 09 18:58:11 hey guys, is there a source that explains deploying Enyo 2 apps to webOS? I haven't been able to find it. Jan 09 18:58:59 Also, all the deployment tuts explain using the bootplate. Is there a way to do it w/o the bootplate? Jan 09 19:00:25 sure, you've just gotta link the library the right way Jan 09 19:00:38 <_minego> GodGinrai: To package for webOS just create an appinfo.json document, and run palm-package. You will also need to make this call to let webOS know that it is ready to show the main page: if (window.PalmSystem) PalmSystem.stageReady(); Jan 09 19:05:13 ok Jan 09 19:05:34 summatusmentis: What is "the right way"? Jan 09 19:06:26 I don't kmow the specifics, but I think it's just making sure the link to the lib points to the path of where the lib is Jan 09 19:06:43 <_minego> GodGinrai: For webOS specific stuff there are a few open source enyo kinds that can help. Check out https://github.com/JayCanuck/enyo-2-components/tree/master/webos-ext and https://github.com/ArthurThornton/enyo1-to-enyo2-kinds Jan 09 19:08:54 I don't need to do anything phone-specific. It's just a simple Mahjong scoring app that I want to deploy to webOS for my phone, and Android for my friends Jan 09 19:09:25 <_minego> GodGinrai: Then just an appinfo.json and the call to stageReady() should be enough Jan 09 19:11:08 <_minego> bootplate just pulls in https://github.com/enyojs/enyo, https://github.com/enyojs/layout and https://github.com/enyojs/onyx. You can do the same in your own app. Jan 09 19:35:12 Does the minify script require that you have the bootplate dir structure? Jan 09 19:35:17 GodGinrai: there's a recent blog post about using PhoneGap to deploy apps for webOS Jan 09 19:36:00 GodGinrai: if you're doing multi-platform deployment, you should definitely move to bootplate Jan 09 19:36:28 GodGinrai: trying to find the blog post....hang on Jan 09 19:37:46 GodGinrai: http://blog.openwebosproject.org/post/39278618299/javascript-apps-for-open-webos-with-enyo-and-cordova Jan 09 19:37:58 sugardave: I hate the bootplate's dir structure Jan 09 19:38:06 it says open webOS, but following those guidelines should also work for webOS Jan 09 19:38:24 <_minego> What's wrong with the bootplate dir structure? Jan 09 19:38:44 heh, don't look at bootplate-mvc, then :) Jan 09 19:38:53 It has one folder for source Jan 09 19:39:09 I want to use css/, js/, assets/ Jan 09 19:39:30 you can do that Jan 09 19:40:00 <_minego> That's just the default. I don't see any reason you couldn't tweak it however you'd like. Jan 09 19:40:22 at a minimum: source/css, source/js, source/assets Jan 09 19:40:39 but there's already an assets dir where you're supposed to put images, etc. Jan 09 19:41:12 and I know there is some way to drop a script in a dir to tell the deploy script what to copy and where (have only looked at it once, long ago) Jan 09 19:41:23 <_minego> I like the "source" dir myself. I try to have one css file per enyo kind, and that makes it easy to keep them next to each other. Jan 09 19:41:32 sugardave: That's kind of pointless, since you're putting more folder hierarchy between the index and the code Jan 09 19:42:07 <_minego> GodGinrai: If you're not using the deploy script then you can use whatever folder structure you want. Jan 09 19:42:54 meh, not pointless if it helps you organize your source in a way you like better Jan 09 19:43:05 yea, I can, but why do I need the bootplate, then, if I'm not using the deployment scripts? Jan 09 19:43:31 Isn't that the point of it? For quick deployment? Jan 09 19:44:03 <_minego> sugardave: What is bootplate-mvc? Jan 09 19:44:13 it's the backbone.js stuff Jan 09 19:44:22 I'm looking at bootplate-mvc, there is: source/apps, source/controllers, source/css, source/ext (extra js/kinds), source/models, source/views Jan 09 19:44:29 so that pattern is well-known Jan 09 19:44:33 It's the new model view controller stuff they are adding, IIRC Jan 09 19:44:39 <_minego> Ah Jan 09 19:44:43 _minego: yeah, the MVC/Backbone stuff Jan 09 19:45:03 CollectionRepeater and CollectionList ftmfw Jan 09 19:45:03 <_minego> Is there any more info on that yet? I haven't heard much about it. Jan 09 19:45:14 sugardave: I don't plan to use bootplate-mvc anyway. I hate MVC Jan 09 19:45:35 why can't open webos have enyo 2 on the operating system when shipped? i see that as totally pointless and redundant . but i don't know much Jan 09 19:46:01 Is there a reason to, fxspec06 ? Jan 09 19:46:04 i just don't see how that'd hurt anything, to have it exist. heh. Jan 09 19:46:08 <_minego> fxspec06: I prefer that it doesn't. It changes too quickly. I don't want my apps tied to the version the OS has. Jan 09 19:46:35 If the app devs instead deploy it themselves, it lets apps not conflict w/ each other due to Enyo versions Jan 09 19:46:39 <_minego> fxspec06: Although, I suppose having a copy in a fixed location wouldn't hurt anything as long as apps could still include their own copy if they want to. Jan 09 19:46:41 well yeah, if HP is behind enyo and webos then it only makes sense to include the tool associated with that operating system, one less step for developers Jan 09 19:46:57 it shows committment to me i guess Jan 09 19:47:57 _minego: there's the intro: https://github.com/enyojs/enyo/wiki/Enyo-MVC-Intro Jan 09 19:48:07 <_minego> sugardave: Thanks Jan 09 19:48:07 fxspec06: If Enyo removed support for a kind or function at one point Jan 09 19:48:21 and the repo is https://github.com/enyojs/bootplate-mvc Jan 09 19:48:22 and you have an app that uses it Jan 09 19:48:29 i mean it's one opinion, i'm sure there are a few, and there's probably a special reason it's not. Jan 09 19:48:38 then you have to keep your OS Enyo at that level Jan 09 19:48:38 <_minego> sugardave: Oh, did you have a chance to look at that tgz I sent you a link to? It seems to load fine everywhere except on the veer where it gets that weird exception in enyo.depends Jan 09 19:48:47 yeah, i'd personally like for the device to update daily or nightly in the background if i so desire Jan 09 19:48:52 then apps that need a newer Enyo won't work Jan 09 19:49:00 _minego: no, I'm head-down on converting this app to MVC :) Jan 09 19:49:23 <_minego> sugardave: np, it isn't urgent. It would be nice to figure it out at some point though. Jan 09 19:49:24 i'd rather have the latest for me or anyone else who thinks the same than have outdated and half working half ugly Jan 09 19:50:05 fxspec06: having the latest will make your old app break Jan 09 19:50:06 <_minego> fxspec06: Changing the build of enyo would break many apps. It changes way too quickly these days. Jan 09 19:50:24 maybe they have something cooler in the works and they can't say. that's what i hope Jan 09 19:51:10 I doubt they are going to chuck Enyo for some OTHER system Jan 09 19:51:15 then put it in folders like the old days Jan 09 19:51:20 * fxspec06 how hard is that Jan 09 19:51:28 it takes like 6-9MB Jan 09 19:51:28 I can see just having developers continue to include Enyo with their apps. If you are big-time, you could always host it on CDN or something Jan 09 19:52:09 <_minego> fxspec06: As a developer I'd prefer to include a copy in my app. I then know it is the version that I tested with. Jan 09 19:52:19 i think that would decrease performance though. files in OS i would think can run faster Jan 09 19:52:31 testing? that's what users are for! **** ENDING LOGGING AT Wed Jan 09 19:52:32 2013 **** BEGIN LOGGING AT Wed Jan 09 19:54:19 2013 Jan 09 20:21:03 <_minego> sugardave: I know that webOS isn't the top priority for enyo right now, but if I can show you guys an example that causes series scrolling issues on webOS phones would you look at it? It is something that should scroll well. Jan 09 20:23:00 _minego: you should post about it on the forums and somebody will likely take a look at it. If it's just happening on the Veer, though, I'm not sure when it will get looked at :) Jan 09 20:25:18 <_minego> sugardave: This is a different issue. It is happening on the pre3 (and I think on other pres as well, but I haven't tested yet) Jan 09 20:25:57 <_minego> sugardave: k, I'll try to create a small example that shows the problem and post it on the forums. Jan 09 20:25:57 post it up and let us know about it, then :) Jan 09 20:26:02 +1 Jan 09 20:26:53 <_minego> sugardave: I'll create an example tonight. Thanks. Jan 09 20:27:02 <_minego> sugardave: I'll try to do the same for the veer issue. That isn't as urgent for me though. Jan 09 22:32:43 <_minego> sugardave: I posted an example for the veer loading issue: http://forums.enyojs.com/discussion/1101/enyo-depends-on-the-veer-causing-uncaught-rangeerror-recursion-too-deep-exception Jan 09 22:32:58 <_minego> sugardave: I am still working on the example app for the pre3 scrolling issue Jan 09 23:46:34 * phil_bw wanders by Jan 09 23:47:10 hey does anyone here have any experience with the newly added mvc components? Jan 10 00:00:09 clearly I'm a bit on the cutting edge side... Jan 10 00:21:37 <_minego> It would seem that way Jan 10 00:27:15 can i set the contents of a component from an external file? Jan 10 00:27:42 something like: {contentFrom: "hello.html"} Jan 10 00:32:12 <_minego> I don't know of any automatic way to do that, but you could load the file and set the content. Jan 10 00:35:47 is there any enyo helper to do that? Jan 10 00:40:08 <_minego> These will help: https://github.com/enyojs/enyo/wiki/Consuming-Web-Services Jan 10 00:46:16 i guess i will write my own.. Jan 10 00:46:38 i haven't tried any Jan 10 00:47:07 var x = document.createElement('script'); Jan 10 00:47:51 x.onLoad = enyo.bind(this, myFunctionName); Jan 10 00:48:08 x.src = 'myfile'; Jan 10 00:48:23 then it will call onload and have that do what you want and voiala Jan 10 00:49:12 :) Jan 10 02:49:47 * fxspec06_ was able to use minify and deploy Jan 10 02:49:52 after some tweaking **** ENDING LOGGING AT Thu Jan 10 02:59:59 2013