**** BEGIN LOGGING AT Fri Feb 03 03:00:01 2017
Feb 03 14:30:08 <trex0051> Hello guys.  I'm trying to convert an app to 2.7 and when I run it, I just get this error : https://www.screencast.com/t/xqTdX1nE the line in index.js is : var app = new IFO(); and IFO is defined: var IFO = kind({...
Feb 03 15:16:33 <m0cs1> Hello!
Feb 03 15:16:41 <m0cs1> Where you define v?
Feb 03 15:16:46 <m0cs1> On ViewController?
Feb 03 15:27:58 <trex0051> I never define it.  But yes, it is in ViewController
Feb 03 15:29:15 <trex0051> I'm not sure if I've gotten past that, or now have an earlier error, but it seems my requires are not correct.  When I use : var FullScreen = require('src/views/FullScreen'); I get the error: ERROR enyo-dev/process-source-stream: could not be resolved, will be reported at the end (module=enyo/FittableColumns)
Feb 03 15:29:39 <trex0051> that line is in my index.js in my top level folder
Feb 03 15:29:56 <trex0051> there is a file at top/views/FullScreen.js
Feb 03 15:30:16 <trex0051> grr, I mean top/source/views/FullScreen.js
Feb 03 15:30:28 <trex0051> grr, I mean top/src/views/FullScreen.js
Feb 03 15:36:55 <m0cs1> Because absolute path is needed
Feb 03 15:37:11 <m0cs1> like "../../views/FullScreen"
Feb 03 15:38:25 <m0cs1> Sorry, relative path
Feb 03 15:41:29 <m0cs1> https://enyojs.com/docs/latest/developer-guide/getting-started/conversion-to-2.7.html
Feb 03 16:03:22 <trex0051> Thanks.  I did go through that guide, and here are some of the other things I've tried: require('../../src/views/FullScreen'); require('../src/views/FullScreen'); require('./src/views/FullScreen'); require('../../views/FullScreen'); require('../views/FullScreen');
Feb 03 16:16:42 <Cage1___> Hello all
Feb 03 16:20:37 <trex0051> Cage1___: Hello
Feb 03 16:21:42 <Semanticfire> wow activity on the Enyo channel ;)
Feb 03 16:27:32 <Cage1___> Why, is that a surprise? :)
Feb 03 16:28:16 <Cage1___> What's the latest and greatest? Any rumors or leaks on next gen Enyo? :)
Feb 03 16:28:56 <Cage1___> "Make Enyo Great Again!"
Feb 03 16:29:19 <Cage1___> 😀
Feb 03 16:30:50 <Semanticfire> lets leave politics out of it ;)
Feb 03 16:31:01 <Semanticfire> looking forward to nexgen though
Feb 03 16:31:11 <Cage1___> what politics? :) i just want to make enyo great again!
Feb 03 16:31:40 <Cage1___> sadly, it won't be backward compatible...
Feb 03 16:31:56 <Cage1___> and i dont know how much "enyo-ness" will be preserved
Feb 03 16:32:08 <Cage1___> it might just be reactjs with some moonstone components
Feb 03 16:33:33 <Cage1___> have you heard any details?
Feb 03 17:03:05 <Semanticfire> nope
Feb 03 17:05:13 <Semanticfire> but I understood that migration to 2.7 is not helpfull
Feb 03 17:07:45 <Cage1___> yeah, i gave up on that.
Feb 03 17:08:34 <Cage1___> did you sign up for the private beta
Feb 03 17:10:40 <Semanticfire> I did, but not sure I can share anything about it, got no feedback yet
Feb 03 17:11:44 <Cage1___> me too. they said they have some legal stuff to work out.
Feb 03 17:11:54 <Cage1___> lawyers = bad news
Feb 03 17:13:15 <Semanticfire> better now then later
Feb 03 17:26:29 <trex0051> Okay, how are my views involved in package.json if at all?
Feb 03 17:28:04 <Cage1___> whatcha mean?
Feb 03 17:28:19 <Cage1___> the files containing your views need to be listed in package.json
Feb 03 17:28:32 <trex0051> Thank you, and how?
Feb 03 17:29:01 <Cage1___> standard format for file name, with subpath, if needed
Feb 03 17:29:14 <Cage1___> do you have the sample app?
Feb 03 17:29:18 <trex0051> under what key?
Feb 03 17:29:51 <Cage1___> no key, just a list in quotes
Feb 03 17:29:53 <trex0051> No, I basically started converting after enyo init
Feb 03 17:30:16 <Cage1___> enyo.depends("file1.js", "file2.js", "file3.js");
Feb 03 17:30:40 <Cage1___> and it is package.js, not package.json
Feb 03 17:31:18 <Cage1___> hmm , you may want to look at the bootpate
Feb 03 17:31:20 <Cage1___> bootplate
Feb 03 17:31:43 <trex0051> okay, so just the package.js in each folder, but not in the top folder at all?
Feb 03 17:32:19 <Cage1___> top level folder will will need it as well, and will need to point to each folder that contains a package.js
Feb 03 17:32:37 <Cage1___> as in enyo.depends("dir1/", "dir2/");
Feb 03 17:32:55 <Cage1___> then enyo will look in dir1 and dir2 for their package.js and parse those
Feb 03 17:33:01 <Cage1___> best to look at bootplate
Feb 03 17:33:22 <trex0051> According to the docs : The package.js file has been removed, as it is no longer needed.
Feb 03 17:34:07 <trex0051> can you direct me to the 2.7 bootplate?
Feb 03 17:34:11 <Cage1___> oh, is this 2.7?
Feb 03 17:34:30 <trex0051> yes
Feb 03 17:36:05 <Semanticfire> one of the reasons I stayed away from it
Feb 03 17:36:26 <Semanticfire> in the nextgen discussion its clear migrating will not help you with the nextgen
Feb 03 17:36:56 <Cage1___> for that, i think you when you do enyo.pack, it generates based on your module.export's. so no need for package.json / package.js
Feb 03 17:37:16 <Cage1___> yes, i'd hold off on migrating to 2.7 for now
Feb 03 17:37:22 <Semanticfire> http://forums.enyojs.com/discussion/comment/10508/#Comment_10508
Feb 03 17:38:18 <trex0051> I have no idea what version I was on, but it was quite buggy and I was looking for some stability
Feb 03 17:38:27 <trex0051> Is there any way to find out what version that was?
Feb 03 17:38:40 <trex0051> (By looking at the files?)
Feb 03 17:38:42 <Semanticfire> okay I'm off guys, enyo the weekend
Feb 03 17:39:42 <trex0051> Have a good weekend Semanticfire
Feb 03 17:40:53 <Cage1___> look in enyo directory for package.json
Feb 03 17:41:03 <Cage1___> hopefully it has a version listed in it
Feb 03 17:42:01 <Cage1___> whatcha working on?
Feb 03 17:42:09 <Cage1___> (if you don't mind sharing)
Feb 03 17:42:38 <trex0051> A game
Feb 03 19:16:44 <m0cs> I migrate from 2.5 to 2.7
Feb 03 19:18:21 <m0cs> Enyo doc its not friendly you r right @trex0051
Feb 03 19:18:56 <m0cs> So... you resolve your problem?
**** ENDING LOGGING AT Sat Feb 04 03:00:02 2017