**** BEGIN LOGGING AT Sat Jul 13 02:59:58 2013 Jul 13 08:22:51 goodmorning all Jul 13 10:39:30 hello... Jul 13 10:40:08 is there a downloadable "kitchen sink" app for enyo, please? Jul 13 10:40:57 (coming from a jquery mobile background, primarily to see how "pages" are achieved/simulated in enyo) Jul 13 10:46:31 well I guess you can see all the source code on the browsers developers tools Jul 13 10:46:38 I can't say for sure Jul 13 10:47:49 hi; i've downloaded the bootplate and sampler files, read the tutorial... but still can't seem to grasp how multiple "pages" would be structured in enyo code Jul 13 10:48:21 or maybe there it can't? it's just the index.html with a chain of JS objects rendering themselves into it... ? Jul 13 11:56:00 newbee: are you listening ? Jul 13 12:01:26 I also start using enyo recently. My findings is as follows: Is a modular approach. By creating a new file you always start by calling the enyo.kind({}) , then you define a name among other properties. Now this kind is a class declaration in the inner workings. In order to use it you need to create an instance out of it. Now back in another kind li Jul 13 12:01:26 ke the App kind on app.js file you can call it in the "components:[]" section of "App" by name. When it is called in the components section what does internally is that instantiates a new instance of the Class (Kind) you declared before. But in order to be aware of the existance of the class you need to include your new file in the package.js Jul 14 01:29:01 dimk: thanks, i think i got that much from the tutorial etc. so i see how the 'kinds' are declared and launched; i guess i'm looking for the best way to structure "pages" - i.e. different sections of an app, and moving between them Jul 14 01:29:34 the sample apps are kind of simple 'one page' apps where content gets refreshed within the same place Jul 14 01:31:56 it would be great if there were a full-featured app demoing things like transitioning between 'pages' (pages = different functional 'sections' of an app) Jul 14 01:33:48 well there are the enyo.Panels Jul 14 01:34:08 they provide a way to transition between different sections of the application Jul 14 01:34:24 newbee: http://enyojs.com/sampler/ have you seen this? Jul 14 01:35:55 yes... but that's not quite what i mean. i think Jul 14 01:36:35 unless that's the answer: the one index.html page is enough? Jul 14 01:37:16 I believe it is, since we are talking for an application see it as the window that opens when you run a desktop application Jul 14 01:37:17 in this sampler app, it's still one 'functional' section if you see what i mean. if you had an app with two separate features, would you still use one index.html page? Jul 14 01:37:26 even your browser is one window if you think of it Jul 14 01:38:01 i agree, that's the user experience - just thinking about how the code (in enyo) would need to be laid out Jul 14 01:38:08 (best) Jul 14 01:38:21 there is way to have more than one applications if they provide totally irellevant functionality but there is the need to communicate before the second will launch Jul 14 01:39:32 alright, great - i guess this will have to do for a starting point anyway Jul 14 01:39:41 see here... on the very end there is a section "sharing enyo" Jul 14 01:39:41 https://github.com/enyojs/enyo/wiki/Managing-Your-Project Jul 14 01:40:27 oh, nice info. not see that Jul 14 01:40:39 but I would mostly go with one application :) Jul 14 01:40:43 happy learning :D Jul 14 01:40:50 is your app public? Jul 14 01:41:32 I am in this stage also, so don't take everything I say for granted, I may reconsider on the way :) Jul 14 01:41:52 my app? no I just made the login functionality .. hahahhaha Jul 14 01:42:22 have you used other frameworks? or only enyo? Jul 14 01:42:37 I created another social networking app but on enyo 1 as part of my research for my master thesis. Right now I have nothing available Jul 14 01:42:44 yes I used jquery mobile Jul 14 01:43:11 working alone was unbearable, I compined it with requireJS and BackboneJs Jul 14 01:43:13 ah ok. so you know what i mean by "pages" for logically organising the code... Jul 14 01:43:50 you need to see it from the aspect of "modules" right now Jul 14 01:44:11 right Jul 14 01:44:48 is a bit strange at first but gets better. E.g. you won't organize the code in an MVC approach, but small plugins with a specific functionality that can be a bit complex but not too much Jul 14 01:45:12 excellent, thanks. that's what i was trying to understand/confirm :) Jul 14 01:45:12 ofcourse some more complex plugins will be composed from many smaller ones. Jul 14 01:46:01 I hope I helped! Good luck! I am eager to see what you created when you make progress! Jul 14 01:46:21 haha, long way off yet, let's see Jul 14 01:46:30 I almost finished an encyrption/decryption library I was missing. I ll publish soon on github Jul 14 01:46:43 i'm looking at enyo primarily because jQM's support for different resolutions and devices is just terrible Jul 14 01:47:11 i read in a review that enyo handles this quite well. so i'm hoping... Jul 14 01:47:56 I didn't get excited with jQM either Jul 14 01:48:23 it would have been really nice to have a 'kitchen sink' enyo sample app, pity there isn't one Jul 14 01:49:04 or maybe i need to look at the samples again and see them in terms of plugins, as you say Jul 14 01:49:12 in more advanced level, you ll be able not only to handle the resolution, but with the same components and same code but some breakpoints to totally change the layout of the app between mobile and tables/desktops Jul 14 01:49:31 yes look at these samples Jul 14 01:50:11 thanks a lot dimk, it's been great to have your advice Jul 14 01:50:33 a bit past my bedtime. i'll report here on how it's going :) Jul 14 01:51:00 np! :)) I am waiting eagerly :) **** ENDING LOGGING AT Sun Jul 14 03:00:00 2013