**** BEGIN LOGGING AT Fri Jun 29 02:59:59 2012 Jun 29 15:47:07 * madnificent sees if he can hack enyojs itself Jun 29 16:42:41 EricBlade: the issues I was having yesterday seem to be related to the fact that I'm sending a base64 encoded image in the URL Jun 29 16:48:25 summatusmentis: i doubt that the url can take such a long string (unless it's really tiny) Jun 29 16:48:34 summatusmentis: post doesn't have those limitations on size Jun 29 16:49:02 madnificent: this is a post request Jun 29 16:50:12 but I keep getting a SocketException error on android built phonegap Jun 29 17:31:43 summatusmentis: and your content is being sent as a post variable, right? Jun 29 17:31:46 summatusmentis: as in: form data Jun 29 17:32:40 * madnificent is getting closer to a "features" extension for enyo :) (w00t! springs to mind) Jun 29 17:38:39 indeed, the url is http://stuf.more.stuff.com/image?imageData=as;lkjljasdfasdfasdfsdf Jun 29 17:38:43 or equivalent Jun 29 17:39:52 summatusmentis: how big is the file? what android version? i find it really odd that enyo would choke on it. Jun 29 17:41:36 android 2.3, and it shouldn't be that big, it's being taken at 50% quality, although I guess it's being taken at 2048x1536 Jun 29 17:43:21 summatusmentis: i'd try with a smaller image first then. i don't think there is a limit to the size you can upload (android might clearly add some restrictions, but i'd be somewhat surprised about that) Jun 29 17:44:03 the thing is, we never had this issue w/ the native android app Jun 29 17:44:14 sending to the same server, the same way Jun 29 17:47:42 even at 800x600, it does the same thing Jun 29 17:48:06 and I can successfully send the post request through a chrome plugin Jun 29 17:48:18 so, it's either enyo, phonegap, or android Jun 29 17:48:37 and I don't think it's enyo, because I can make other post requests just fine Jun 29 17:50:12 what does phonegap have to do with the post request? Jun 29 17:50:32 can you try uploading a relatively big file to a website through the android browser? Jun 29 17:50:47 (upload the same image to an image host, for instance) Jun 29 17:51:10 i don't understand how enyo could be messing it up... Jun 29 17:51:13 (but i may be wrong) Jun 29 17:57:20 the only thing I can think of is that there's something in the way enyo.Ajax forms the request Jun 29 17:57:29 or perhaps the translation into java from phonegap Jun 29 18:13:59 phonegap doesn't translate to java, it's a web application Jun 29 18:15:29 * madnificent is ready to hack his changes out of the enyo core and into a library which extends the enyo core. still in doubt as to whether or not that'd be the best approach Jun 29 18:17:49 phonegap provides access to device specific mechanisms. I'm getting a SocketException Jun 29 18:21:24 why would you use phonegap for the upload? why not just upload as html formdata? Jun 29 18:22:53 summatusmentis: should i paste the dynamic-formbuilding-or-whatever file upload code for you? Jun 29 18:47:09 I'm not using phonegap for the upload, but it goes through a Java shim Jun 29 18:47:11 that's my point Jun 29 18:53:23 * madnificent doesn't see why one would do that, but fair enough :) Jun 29 19:00:10 * madnificent decides not to hack the features system out of enyo, too much clutter Jun 29 20:22:57 very silly question: i have the specification for a kind (which doesn't have a name) in a variable (like inProps). how do i create a single instance from it? :3 Jun 29 20:23:33 something like new enyo.kind({ kind : enyo.Control, content : "foobar"}).renderInto(document.body); Jun 29 20:23:46 i seem to recall there was something like this, but can't seem to find it. Jun 29 20:40:25 I think it's new KindName({stuff: here}).renderInto(document.body); Jun 29 20:52:49 summatusmentis: yes, however, i don't have the kindname Jun 29 20:52:55 at least, not in that form Jun 29 20:55:38 summatusmentis: i only have {stuff:here , kind : "PerhapsKindIsNotEvenHere"} Jun 29 21:02:57 oh Jun 29 21:02:58 hrm Jun 29 21:04:24 i thought i could fake it by doing new enyo.getObject( inProps.kind )( inProps ); but that doesn't seem to be instantiating the arguments i give it through inProps (either, that, or the initialization works differently than I'd expert Jun 29 21:04:33 which i'm now doublechecking (just a sec) Jun 29 21:06:31 summatusmentis: if i make a kind, NamedComponent, then shouldn't the creation like: new NamedComponent( { nestedInstance : "something" } ); have the variable nestedInstance available? Jun 29 21:07:59 because it seems like it isn't propagating that value Jun 29 21:08:11 (and that is really surprising me at the moment) Jun 29 21:09:11 * madnificent is lost here Jun 29 21:49:05 yes, nestedInstance has to be published, I believe Jun 29 21:56:17 please elaborate :) Jun 29 21:56:32 oh Jun 29 21:56:44 well, i kind-of doubt it... but i could try Jun 29 21:58:16 so, when you define a kind, and you want to be able to set the nestedInstance variable upon instantiation, it has to be listed within the published block of the kind defintion Jun 29 22:02:27 are you certain? (i'm willing to believe you, but i think we tried and discovered otherwise (but i'm not thinking that they might've been published earlier on) Jun 29 22:10:11 I'm like 90% certain Jun 29 22:10:43 internally then, you have to do something w/ it Jun 29 22:10:55 hmmm, if i set it published, and i do: Jun 29 22:11:30 new NamedComponent( { nestedName : "something" } ); then it isn't set in the created instance. perhaps i'm doing something really silly, but it seems i can't find a normal way to set it... Jun 29 22:11:47 summatusmentis: thanks for helping out btw, my mind is clouded b/c of the metaprogramming that i'm trying to figure out. Jun 29 22:13:36 when you say set it published, you mean that it's declared in the published block, right? Jun 29 22:13:55 then w/in that kind, you can refer to this.netstedName Jun 29 22:14:04 yeah, the getters/setters are built for me. so it must have worked Jun 29 22:14:30 but it doesn't seem to get /set/ to "something" when i use new NamedComponent( { nestedName : "something" } ); Jun 29 22:14:58 https://github.com/enyojs/enyo/wiki/Creating-Components Jun 29 22:15:13 where are you referring to it? Jun 29 22:15:32 my understanding is that you cannot refer to it in any sub-kind declarations Jun 29 22:16:02 so, if NamedComponent has a Button internally, you can't refer to netstedName in the declaration of the Button Jun 29 22:17:03 I've gotta run, sorry Jun 29 22:17:05 good luck Jun 29 22:17:10 summatusmentis: will you be here in an hour or so? i'm a tad tired, but i should first build some basic canonical example before going further. Jun 29 22:17:27 thanks for the advice, wonder if i'll find the solution still Jun 30 01:28:34 hmmm, inEvent.preventDefault() and return true doesn't seem to be working Jun 30 01:28:46 I'm trying to prevent a link from being called Jun 30 01:31:54 https://gist.github.com/02ec3ffabf5504740f3d Jun 30 01:32:35 anyone have any ideas? Jun 30 01:46:31 my guess, is that the link is somewhere inside the content ? Jun 30 01:52:44 yeah Jun 30 01:52:52 Jun 30 01:58:19 even tried adding inEvent.srcEvent.preventDefault(); inEvent.srcEvent.stopPropagation() Jun 30 02:28:01 Tibfib_: aren't events propagated from the deepest level, upward? Jun 30 02:35:25 * phil_bw wanders by **** ENDING LOGGING AT Sat Jun 30 02:59:58 2012