**** BEGIN LOGGING AT Tue Jul 16 02:59:58 2013
Jul 16 05:26:54 <dimk__> goodmorning everyone
Jul 16 07:58:58 <joopmicroop> hi dimk__ I took a look at your enigma project, on which I have a question, why do you use static almost everywhere?
Jul 16 08:17:39 <dimk__> hahahha joopmicroop I know you mentioned it before. I am looking how would be beneficial
Jul 16 08:18:13 <dimk__> I use static mainly because I am using some helpers like utils / encode/ decode
Jul 16 08:18:21 <dimk__> and I dont want to create new instances
Jul 16 08:19:03 <dimk__> for the moment I am working on another branch where I try to make it dynamic
Jul 16 08:19:18 <joopmicroop> anyway.. it's some nice bit shifting code you've got there :)
Jul 16 08:20:08 <dimk__> my view is that in the instance of enigma , I will pass dependencies to the encryptors through published properties so there want be to called reinstanciation of these helper classes on every encryptor
Jul 16 08:20:10 <joopmicroop> here and there I'd prefer shorter notation and maybe more use of enyo.forEach but all in all, great piece ;)
Jul 16 08:21:14 <dimk__> thank you a lot :) What I would like from enyo people is  to point out possible anti-patterns and possible javascript calls that are not fully supported by the platforms enyo supports
Jul 16 08:21:33 <joopmicroop> maybe I'll look into blowfish to add to your project.. if I have some time left :p
Jul 16 08:22:13 <dimk__> In one case I am a bit concerned because I used the "Object.hasOwnProperty" function while iterating through some objects properties but the enyo.mixin function I found on the source does not use that
Jul 16 08:22:27 <dimk__> thanks , that would be also nice.
Jul 16 08:22:43 <joopmicroop> not supported != not intended.. if it works it works, the fun stuff is to write it as short as possible :)
Jul 16 08:23:25 <joopmicroop> you couldn't just use mixin?
Jul 16 08:24:55 <dimk__> no I wanted a filter function
Jul 16 08:26:18 <dimk__> I may change this , I ll look after work the compatibility of hasOwnProperty. I used it out of habbit working on desktop browsers without checking.
Jul 16 08:27:29 <joopmicroop> enyo.filter followed by enyo.mixin could do it in 2 lines ^^
Jul 16 08:28:02 <dimk__> awesome... I didn't find this function at first place.
Jul 16 08:28:18 <dimk__> I ll refactor it this afternoon!
Jul 16 08:29:45 <joopmicroop> i'd have to look into whats used inside mixin myself but I guess it'll use hasOwnProperty somewhere
Jul 16 08:30:51 <dimk__> from the look I gave it today morning there was nothing connected with hasOwnProperty. No worries I ll take a close look at it.
Jul 16 08:31:36 <joopmicroop> so it's more of a tomato, tomato effect
Jul 16 08:31:48 <joopmicroop> let me know :)
Jul 16 08:34:03 <dimk__> sure! :)
Jul 16 09:04:22 <pjetr> morning
Jul 16 09:10:47 <pjetr> newbee:  if you would read the logfiles of this room. http://enyojs.com/sampler/debug.html is this what you were looking for?
Jul 16 09:12:56 <pjetr> nevermind, I just read the next log and saw that you already found that one :)
Jul 16 09:17:37 <joopmicroop> morning pjetr
Jul 16 09:19:43 <pjetr> morning joopmicroop
Jul 16 09:34:11 <joopmicroop> anyone knows how to make a newline in api-viewer comments
Jul 16 09:47:21 <dimk__> morning pjetr , joopmicroop unfortunatelly I don't
Jul 16 09:48:07 <pjetr> joopmicroop, just to be safe, you have seen this page right: https://github.com/enyojs/enyo/wiki/Documenting-Code
Jul 16 09:49:18 <dimk__> Since you bot are online right now, I have in mind a project for weekend, wont take long. Would you like to alter the comment parsing system that generates the documentation and at the end of each function to add an iframe from a commenting platfor like disqus . There users will be able to give targeted examples to the specific functionality, or helpfull notes and will be easily accessible to anyone reading the API
Jul 16 09:49:43 <pjetr> because I would think /** first line [enter] second line */
Jul 16 09:50:27 <dimk__> I think pjetr  is correct from what I ve seen from comments on source code starts like this and each line with comment starts with star space
Jul 16 09:50:33 <dimk__> *
Jul 16 09:50:38 <dimk__> * Comment here
Jul 16 10:18:29 <joopmicroop> humm doesn't seem to work..
Jul 16 10:19:15 <joopmicroop> maybe I need another text encoding :S
Jul 16 10:21:22 <dimk__> it is possible as well. I am out of ideas
Jul 16 10:21:32 <dimk__> not that I had many
Jul 16 11:30:44 <joopmicroop> can't be hard tough.. just finished eating, I'll fiddle some more
Jul 16 11:33:01 <joopmicroop> humm
Jul 16 11:33:41 <joopmicroop> this works  /** retrun string1 return string2 return */
Jul 16 11:33:55 <joopmicroop> needs return after the opening comments
Jul 16 11:36:54 <dimk__> you need to explicity write "return" ?
Jul 16 12:03:56 <joopmicroop> well no you have to press enter ofc but it's just to show it in chat :p
Jul 16 12:04:31 <dimk__> aha ok I see
Jul 16 12:50:02 <pjetr> dimk__ my weekends are actually quite full as it is. But could you give a bit more info on what you're trying to accomplish?
Jul 16 12:50:48 <pjetr> would you like to host your own enyo API where users can help document the functions?
Jul 16 12:50:58 <pjetr> a bit like on php.net?
Jul 16 12:51:32 <dimk__> a bit like php.net
Jul 16 12:53:17 <dimk__> yes host or enrich the current documentator features. I could make a mock up during this week to get the idea. Each pragraph that describes a "handle" in each component will have its own disqus commenting iframe where ppl can put more details or examples of the use
Jul 16 12:54:23 <dimk__> this could be a feature switched off but through setting able to enable it and be integrated in every project someone would like a bit more "active" involvement of the users of this documentation
Jul 16 12:55:06 <dimk__> I mean I can fork the existsing library that enyo has for generating documentation and  integrate it there
Jul 16 13:24:06 <joopmicroop> dimk__ sounds interesting too, maybe we should skype join or something
Jul 16 13:26:03 <dimk__> https://dl.dropboxusercontent.com/u/16512832/foldedcomment.png
Jul 16 13:26:13 <dimk__> https://dl.dropboxusercontent.com/u/16512832/unfoldedcomment.png
Jul 16 13:26:56 <dimk__> The mock up is REALLY quick. I am at work having paint only and I am not the best in designing. You need to grasp the idea behind. not the visual
Jul 16 13:30:25 <dimk__> joopmicroop:  pjetr  just mentioning you to draw your attention on the channel... see the mock up :P
Jul 16 13:30:36 <pjetr> I was just watching them
Jul 16 13:30:37 <pjetr> :)
Jul 16 13:30:40 <pjetr> btw http://pixlr.com/editor/
Jul 16 13:30:54 <pjetr> it can open and edit .psd's
Jul 16 13:31:18 <dimk__> it shapes my screen in great degree and my coworkers will feel stupid that work while I make drawings :P
Jul 16 13:31:29 <dimk__> mspaint is a window among many other
Jul 16 13:31:34 <pjetr> it does indeed sound interesting
Jul 16 13:31:36 <pjetr> :)
Jul 16 13:33:19 <dimk__> it came out of my need to access infos quick and the pain on looking on forums for that. Forum is usefull but if I can see a tip down below a control why the hell should I look among 1.5 k forum posts
Jul 16 13:33:24 <joopmicroop> super :) what would you suggest as backend?
Jul 16 13:33:34 <dimk__> keeps relative information together
Jul 16 13:33:39 <dimk__> there is absolutely no backend
Jul 16 13:33:44 <dimk__> is ready platform
Jul 16 13:33:46 <dimk__> called discuss
Jul 16 13:33:58 <dimk__> you writte some javascript code.. some iframes and magic is done
Jul 16 13:34:03 <dimk__> rolls by itself
Jul 16 13:34:13 <dimk__> http://disqus.com/
Jul 16 13:34:45 <dimk__> I mean you have the generated files from documentation but the whole commenting platfor is 3rd party... you dont have to reinvent the wheel on that
Jul 16 13:35:58 <joopmicroop> so disqus will be the backend but since enyo api viewer is open source, who will controll the disqus account?
Jul 16 13:36:22 <dimk__> the disquss account is defined by the website url
Jul 16 13:36:33 <joopmicroop> oh..
Jul 16 13:36:46 <joopmicroop> nvm :p
Jul 16 13:37:37 <dimk__> I will explain in greater detail the rest later in the week. Now back to work :P
Jul 16 13:41:20 <joopmicroop> deal!
Jul 16 13:45:13 <pjetr> you got it!
Jul 16 13:48:06 <dimk__> I ll gather requirements and I ll present findings in a gist with example and markdown explanation
Jul 16 13:53:02 <joopmicroop> on a totaly different plane level, if I add controlParentName to a control, then the named components added to it give the duplicated name warning on the owner is there a way to get around this?
Jul 16 14:02:29 <joopmicroop> ok.. nvm on this one too. My own stupid fault
Jul 16 19:28:09 <newbeen> hello
Jul 16 19:37:49 <summatusmentis> hey
Jul 16 19:43:13 <newbeen> hi summa. ploughing along, now that i know enyo is JSON (not js!)...
Jul 16 19:46:08 <summatusmentis> well, more accurately, it's a mixture
Jul 16 19:46:17 <summatusmentis> JSON is the delcarative structure
Jul 16 19:46:19 <newbeen> hurdle: adding "create: function() {}" to my enyo.Panels results in nothing being rendered
Jul 16 19:46:37 <summatusmentis> what's in your create()?
Jul 16 19:46:56 <summatusmentis> if you don't need a constructor, you can leave it out
Jul 16 19:46:58 <newbeen> nothing, i put a blank to test. if i put an alert() it appears, but still rendering nothing
Jul 16 19:47:06 <newbeen> (i really wanted this.addClass())
Jul 16 19:47:28 <summatusmentis> try create: function(inSender, inEvent) {this.inherited(arguments);// whatever else}
Jul 16 19:47:43 <summatusmentis> have you checked the web inspector? make sure you don't have any syntax issues?
Jul 16 19:47:55 <summatusmentis> oh, possibly you need a comma after the }
Jul 16 19:48:01 <summatusmentis> (again, JSON)
Jul 16 19:48:02 <newbeen> yup, no syntax errors. trying your suggestion... (comma, check)
Jul 16 19:48:23 <newbeen> well, that worked fine. needed the two parameters. how's a guy to know?
Jul 16 19:48:45 <newbeen> wrong example: https://developer.palm.com/content/api/dev-guide/enyo/anatomy-of-a-control.html
Jul 16 19:48:56 <summatusmentis> oh, yeah, never use *.palm.com as docs
Jul 16 19:49:02 * newbeen sighs
Jul 16 19:49:03 <summatusmentis> that's enyo1, and doesn't apply
Jul 16 19:49:13 <newbeen> thanks
Jul 16 19:49:24 <summatusmentis> also, you're supposed to intuit convention from the docs :)
Jul 16 19:49:38 <newbeen> is this how kids programme these days?
Jul 16 19:49:54 <summatusmentis> I'm not _certain_ about this, but I think create(), rendered(), and destroy() are event handlers
Jul 16 19:50:05 <summatusmentis> and all event handlers need the (inSender, inEvent) structure
Jul 16 19:50:17 <newbeen> noted, thanks
Jul 16 19:50:48 <newbeen> even this is wrong then, no parameters in create() half way down the page: https://github.com/enyojs/enyo/wiki/Tutorial
Jul 16 19:51:07 <summatusmentis> wait
Jul 16 19:51:13 <newbeen> ah, hang on
Jul 16 19:51:16 <summatusmentis> are you certain you need the parameters?
Jul 16 19:51:21 <summatusmentis> are you sure it's not the this.inherited(arguments) thing?
Jul 16 19:51:22 <newbeen> you're right :)
Jul 16 19:51:26 <newbeen> yup, it's that
Jul 16 19:51:42 <summatusmentis> ok, I was looking at https://github.com/enyojs/enyo/wiki/Object-Lifecycle also
Jul 16 19:52:38 <newbeen> handy page...
Jul 16 19:52:49 <summatusmentis> I think I've also lied to you about event handlers needing that structure
Jul 16 19:52:53 <summatusmentis> but I'm not certain about that
Jul 16 19:53:07 <summatusmentis> I sorta fake my way through things that don't make intuitive sense
Jul 16 19:53:25 <newbeen> seems like a dangerous way of doing things :(
Jul 16 19:53:47 <newbeen> anything but the most trivial of things, anyway. which luckily whatever i'm trying to be is
Jul 16 19:53:52 <newbeen> be=build
Jul 16 19:54:36 <summatusmentis> well, after a while, I learn what's necessary, part if it is just being comfortable with the enyo paradigm
Jul 16 19:54:43 <newbeen> of course, enyo is not alone with this... jquery mobile is shockingly undocumented as well
Jul 16 19:54:56 <summatusmentis> I declare all my functions with (inSender, inEvent), and then ignore them if needed
Jul 16 19:55:06 <newbeen> where a few examples, often out of date and with typos, pass as the authoritative reference...
Jul 16 19:55:16 <summatusmentis> convention is a good habit to form
Jul 16 19:56:31 <summatusmentis> the examples shouldn't be out of date, they're usually pretty good about that
Jul 16 19:56:42 <summatusmentis> the sampler also has code samples
Jul 16 19:56:54 <summatusmentis> I don't know if you know about the sampler/code samples
Jul 16 19:57:06 <newbeen> sure yup, got those
Jul 16 19:57:10 <summatusmentis> kk
Jul 16 19:57:19 <newbeen> not quite there yet to refer to that, but hopefully soon
Jul 16 19:57:42 <summatusmentis> sure, but if the examples don't get you what you need, look there too
Jul 16 19:58:10 <newbeen> odd: the creat() in Panels works ok, but if i move it one level deeper - calling create() on a child Panel - it renders nothing again
Jul 16 19:58:20 <newbeen> no errors... how to debug...
Jul 16 19:59:47 <newbeen> oops, sorry. there was an error:
Jul 16 19:59:48 <newbeen> Uncaught TypeError: Cannot call method 'apply' of undefined
Jul 16 19:59:56 <Joopmicroop> hi
Jul 16 20:00:03 * newbeen waves
Jul 16 20:00:34 * Joopmicroop rides waves
Jul 16 20:00:47 * newbeen politely declines
Jul 16 20:08:07 <newbeen> interesting ruler appears on browser after render and resizing. is that Enyo doing?
Jul 16 20:24:30 <summatusmentis> I don't believe the ruler is enyo's
Jul 16 20:26:29 <newbeen> really, it only appears on debug.html ... nice touch anyhow :)
Jul 16 20:26:56 <newbeen> summa, i'm using bootplate and added a bunch of content to the Panel ... but it doesn't seem to scroll when there's more content than it can display
Jul 16 20:27:11 <newbeen> is it non-scrollable by default? do i need to add a scroller control of some sort?
Jul 16 20:27:23 <summatusmentis> you need to add a scroller, and your scroller needs to have a height
Jul 16 20:27:28 <summatusmentis> enyo.Scroller
Jul 16 20:27:32 <newbeen> thank you
Jul 16 20:27:42 <newbeen> a fixed, pre-specified height? what if i don't know it?
Jul 16 20:27:55 <summatusmentis> yes, a fixed, pre-specified height.
Jul 16 20:27:59 <summatusmentis> you can do a couple things
Jul 16 20:28:09 <summatusmentis> fit: true, if used properly, will calculate it for you
Jul 16 20:28:34 <summatusmentis> or you can build out what you need to build out into it, calculate the height of the children, then reset the height of the scroller
Jul 16 20:28:48 <summatusmentis> (fit: true, and the Fittables associated with it
Jul 16 20:28:50 <summatusmentis> )
Jul 16 20:29:14 <newbeen> does enyo have child height-calculating functions built-in?
Jul 16 20:31:28 <summatusmentis> the DOM does
Jul 16 20:31:44 <summatusmentis> there's something in enyo, I don't remember what it's called
Jul 16 20:32:40 <newbeen> thank you, it seems to have been as easy as changing the default kind of the panel to enyo.Scroller
Jul 16 20:34:17 <summatusmentis> sure thing
Jul 16 21:08:51 <newbeen> looking good so far... impressed with the painless scaling across devices already!
Jul 16 21:09:21 <newbeen> how does one make an enyo.Image clickable, please? (to load/display a different panel?)
Jul 16 21:10:19 <summatusmentis> set an ontap handler on the declaration
Jul 16 21:10:47 <summatusmentis> (ontap is a wrapper event around onclick and other js events, mousedown etc.)
Jul 16 21:50:28 <newbeen> i've set an ontap, but it doesn't seem to do anything
Jul 16 21:51:00 <newbeen> (would you expect the mouse to turn into a clickable-pointer, as with a regular <a> in html?)
Jul 16 21:52:03 <newbeen> components: [ { kind: enyo.Image, src: "assets/homebutton_about.png", ontap: "showAbout" } ], showAbout: function (inSource, inEvent) { alert('test'); }
Jul 16 21:58:27 <newbeen> ah, i needed to move the showAbout method to the outermost kind block...
Jul 16 22:03:41 <newbeen> i can't seem to find a list of events in the API docs :(
Jul 16 22:04:02 <newbeen> specifically, is there an "onshow" event for when a panel is made the active index, please?
**** BEGIN LOGGING AT Tue Jul 16 22:42:58 2013
**** ENDING LOGGING AT Wed Jul 17 02:59:59 2013