**** BEGIN LOGGING AT Tue Jul 10 02:59:58 2012 Jul 10 04:22:42 latest synergv screen .. :) http://ericbla.de/gvoice-webos/?p=543 Jul 10 06:44:34 EricBlade1, looking good Jul 10 06:50:21 wrea: thank you :) Jul 10 10:39:52 EricBlade1: i'm an emacs user and a lisp coder and i seriously disagree Jul 10 10:40:01 EricBlade1: (inheritance) Jul 10 10:40:36 that large levels of inheritance are good, or that having an editor to search them is good? Jul 10 10:40:44 EricBlade1: the interface which you offer indicates what functionality an object claims to have. the type itself rarely really matters, the question is: does it behave the way you want it to. Jul 10 10:41:08 ==inheritance is good== Jul 10 10:41:26 the editory to search them obviously helps, but i find the api-tool to do the trick quite well (so far) Jul 10 10:41:39 it may not be perfect, but it's 'good enough' Jul 10 10:41:52 of course it is, but if you need to know the inner workings of something, it becomes quite difficult to trace it through a dozen source files Jul 10 10:42:22 i often find myself read the build.js instead of the source just because it's easier to search Jul 10 10:42:34 why would you need to know the inner workings? you need to know what it /does/ and that must be documented. rigorously Jul 10 10:42:52 EricBlade1: oh, you have stepping etc in chromium! and it jumps correctly Jul 10 10:42:55 that may help a lot Jul 10 10:43:23 and you can add (conditional) breakpoints etc... Jul 10 10:44:04 if somewhat related kinds were in the same files, that'd help the searching too, but might get pretty messy to define "somewhat related" Jul 10 10:44:40 dull trick: extend your kind with the name of the function you want to trace. call this.inherited(arguments) in it and step into that. this.inherited has one 'odd' function through which you step and it then pops further down into what you want to find. Jul 10 10:44:52 why would they need to be in the same file? Jul 10 10:45:02 chromium just jumps to the right one Jul 10 10:45:43 running the app in debug just to find a code location? uh.. Jul 10 10:46:10 if i could ctrl-click on something to see where it's defined in the parent, i'd be all good Jul 10 10:46:45 unfortunately, javascript editors haven't seem to have come up to 1994 yet Jul 10 10:47:23 and if language parsing were something i were even remotely skilled at, i'd have built something by now for enyo Jul 10 10:49:43 EricBlade1: for kinds, i might be up for the task. could potentially be fun to write something of the likes... distant future, if ever. Jul 10 10:51:26 unfortunately, my editor of choice makes extending it's functionality in that sort of thing rather difficult unless you already know what you're doing, as the editor is written in XUL. god only knows why someone wrote an editor in XUL, but I like Komodo Jul 10 10:51:28 gm gentlemen Jul 10 10:52:56 gm Jul 10 10:53:11 good morning fxspec06 Jul 10 10:53:23 i get to go to school today Jul 10 10:53:32 woooooooooooooo Jul 10 10:53:58 go back to bed, no school Jul 10 10:54:02 * madnificent is glad he got up and running with a useable editor, saves him loads of work Jul 10 10:54:07 lol, no definitely school today Jul 10 10:54:28 hmm. i need to stop thinking of new functions to add, my menu is now taking up the entire width in portrait mode Jul 10 10:54:35 are you guys in the U.S. Jul 10 10:54:47 * EricBlade1 is Jul 10 10:54:59 http://developer.palm.com/appredirect/?promocode=moeoi70002bhgis that's for game on, i know there's a few left Jul 10 10:55:24 * madnificent is not Jul 10 10:55:38 are you in canada? because, i only had one canada friend Jul 10 10:55:56 belgium Jul 10 10:55:59 * fxspec06 wishes for global promos Jul 10 10:58:29 i really really wish webos could deal with multiple just type actions Jul 10 11:00:09 does anybody use facebook apps? Jul 10 11:01:20 fxspec06: we have an app which uses facebook as authentication somewhere Jul 10 11:01:57 heh, not quite what i was going for, but i'll take it! Jul 10 11:02:25 fxspec06: they have a javascript api which handles just about everything for you Jul 10 11:03:06 interesting Jul 10 11:10:11 gotta fly Jul 10 11:10:23 buenos dias amigos Jul 10 11:21:05 i'm a little frightened by the fact that the webOS maps app is allowing me to pull up a satellite view that is less than 2 weeks old Jul 10 12:59:08 EricBlade1: you've just found yourself dumping a body Dexter-style, haven't you? ^_^ but yes, it is Jul 10 13:07:27 hi all Jul 10 13:08:36 what's the syntax for referencing something by the string of it's name? Jul 10 13:08:51 suppose I have a kind Thing Jul 10 13:09:20 and within Thing, I want to reference the Other kind, but Other is named "other_#", and I need to find # dynamically Jul 10 13:10:19 is it just this.$.thing.$[other_#] ? Jul 10 13:17:58 summatusmentis: that should work, though not sure what other_# is Jul 10 13:18:11 summatusmentis: you're breaking abstraction with the double $ though Jul 10 13:19:47 I know I'm breaking abstraction Jul 10 13:20:03 alright, so it's a lot deeper than that Jul 10 13:20:27 but what it comes down to is I have this.$.formDiv.$.acc.$.qs.$.qbody.$.input_7 Jul 10 13:20:59 and when I try to log this.$.formDiv.$.acc.$.qs.$.qbody.$["input_7"] it doesn't work Jul 10 13:21:07 oh, wait Jul 10 13:21:58 do I have to use the id of the dom element? or the name assigned with enyo? Jul 10 13:23:03 no, that doesn't work either Jul 10 13:23:13 it just prints undefined Jul 10 13:23:49 and, for the record, this.$.formDiv.$.acc.$.qs.$["qbody"] logs just fine Jul 10 13:31:20 should addComponent allow me to add a previously created component? createComponent seems to work, but addComponent seems to fail. Jul 10 13:31:51 madnificent: do you have any ideas? Jul 10 13:32:07 is it encapsulation that's breaking this? Jul 10 13:34:45 summatusmentis: { components : [ { name : "foo" } ] , getComponentByName : function( name ){ return this.$[name]; } } builds a component of which you can call getComponentByName( "foo" ); on it. Jul 10 13:35:22 you 'break' encapsulation, meaning that you can't change the inner component without thinking where it may be used outside anymore. Jul 10 13:35:40 the code will work, but it may become horribly complex. Jul 10 13:36:53 I'm _only_ using this to pull data form input elements Jul 10 13:37:04 it's all within a parent kind Jul 10 13:37:29 wait, so you're suggesting creating getComponentByName() ? Jul 10 13:41:08 no, i'm using that as a canonical example to show you how you can use the alternative naming. Jul 10 13:42:00 summatusmentis: the name which you provide to $ is the "name" argument that was given when the kind was created. Jul 10 13:44:43 I can't even log it using this.$.formDiv.$.acc.$.qs.$.qbody.$.input_7 Jul 10 13:45:01 but logging this.$.formDiv.$.acc.$.qs.$.qbody.$ shows an input_7 Jul 10 13:46:35 * madnificent is lost without the code, doesn't have time to look at it. still wonders about addComponent Jul 10 16:57:48 anyone run into rendering only on touching in android? Jul 10 20:12:16 uh, stupid question Jul 10 20:12:26 is there a way to destroy components and re-create them w/ the same name? Jul 10 20:12:38 or rather, what is the proper way to do this? Jul 10 23:33:37 summatusmentis: can't you destroy them and then create the new ones. i think it should work Jul 10 23:33:43 destroyComponent, i believe it is Jul 10 23:33:48 but i'm not sure Jul 10 23:33:52 and i'm heading to bed right now :) Jul 10 23:39:49 looks like the source for documentation is changing again... sheesh Jul 11 02:08:12 oops, almost forgot Jul 11 02:08:14 * phil_bw wanders by Jul 11 02:26:57 how's it going fxspec06? **** ENDING LOGGING AT Wed Jul 11 02:59:58 2012