**** BEGIN LOGGING AT Mon Oct 08 02:59:59 2012 Oct 08 08:40:38 Can you do phone notifications with Enyo? Oct 08 08:44:43 BitPuffin: do you mean, notification like behavior? or native notification (e.g. vibrate) ? Oct 08 08:45:15 katratxo: Exactly Oct 08 08:45:21 native Oct 08 08:45:33 Say on Android for example Oct 08 08:45:39 With the notification bar Oct 08 08:45:44 with a message or whatever Oct 08 08:46:33 BitPuffin: the only way to do it is to package your app with phonegap Oct 08 08:47:13 katratxo: Okay, well that shouldn't be a problem I guess Oct 08 08:48:26 BitPuffin: no, it shouldn't be a problem, see (deploying apps) http://enyojs.com/docs/ Oct 08 08:48:57 katratxo: But phonegap appears to only be to access stuff like batterylevel or volume buttons etc? Oct 08 08:50:58 BitPuffin: no, you can make notifications, access camera, etc http://docs.phonegap.com/en/2.1.0/cordova_notification_notification.md.html#Notification Oct 08 08:52:00 katratxo: Oh! Nice! Well I was looking at the Phonegap thing on Enyo's github Oct 08 08:53:55 Well then I know it is doable Oct 08 08:54:00 then I'll use Enyo Oct 08 08:54:11 I have to go now! Thanks a bunch katratxo Oct 08 11:52:12 * fxspec06 stretches Oct 08 14:51:23 hi all, newbie questions when nesting components [] , check this code http://jsfiddle.net/katratxo/KHwgL/ Oct 08 14:53:52 in this example comp1, has 2 subcomp, but to access them i can't do it, this.$.comp1.$.subcomp1, instead i need to use the parent hash ($) Oct 08 15:11:44 hello :) Oct 08 15:12:36 I'm using enyo.Ajax to send some json data to a couchdb server. The couchdb server only accept application/json headers Oct 08 15:13:02 ok Oct 08 15:13:06 so, I've added handleAs: "json" and headers: {"Content-Type": "application/json"} to the constructor parameters. Oct 08 15:13:26 looks like the request header still uses Content-Type:application/x-www-form-urlencoded Oct 08 15:13:36 is that the right way to do? Oct 08 15:13:39 no Oct 08 15:14:35 it should look something like new enyo.Ajax({handleAs: "json", contentType: "application/json", method: "POST", ...}); Oct 08 15:15:04 so, rather than headers: {"Content-Type": "application/json"}, use contentType: "application/json" Oct 08 15:16:23 thanks, didn't see it in the documentation... Oct 08 15:16:40 it's there though :) Oct 08 15:17:06 it is Oct 08 15:17:10 sure Oct 08 15:17:24 under tha enyo.AjaxProperties portion of the API docs Oct 08 15:17:33 but I'm glad I can help Oct 08 15:19:51 works pefectly =) thank you for your help. Oct 08 15:20:02 of course Oct 08 16:16:03 woah, activity in here Oct 08 16:16:08 * fxspec06 dives in head first Oct 08 16:16:37 HEY! No diving in the shallow end! Oct 08 16:16:43 Too true. Oct 08 16:31:08 lol Oct 08 19:36:43 Hi o/ Oct 08 19:40:42 hi Oct 08 22:00:48 Anybody with experience implementing enyo.JsonpRequest/Webservice ? Oct 08 22:42:59 depends on what your question is Oct 08 23:07:54 I've resolved my problem with JsonpRequest ;) Oct 08 23:08:26 But I'm now wondering which is the best way to POST data to a WebService Oct 08 23:08:51 It seems that their is no equivalent to Jsonp to POST, I always hit cross-domain Oct 08 23:19:48 hm.. Oct 08 23:19:55 What is strange is that : Oct 08 23:20:03 new enyo.Ajax({ Oct 08 23:20:03 url: "http://localhost:9000/newsitems", Oct 08 23:20:03 method: "POST", Oct 08 23:20:03 postBody: JSON.stringify(data) Oct 08 23:20:03 }); Oct 08 23:20:10 hit the server Oct 08 23:20:23 i'm not experienced. i id say enyo.Ajax would be your best bet Oct 08 23:20:44 but body is not seen as json, and as soon as I add Oct 08 23:20:44 contentType: "application/json" Oct 08 23:20:54 the request become a OPTIONS Oct 08 23:21:01 and don't hit the server Oct 08 23:21:54 have you looked at enyo.WebService? Oct 08 23:22:17 you would do that, but it would initialize an object Oct 08 23:22:34 yep but same behavior Oct 08 23:22:35 then you'd do object.send({params: etc}); Oct 08 23:23:01 hm. Oct 08 23:23:18 you mean the json payload inside the send parameters ? Oct 08 23:23:21 http://enyojs.com/api/#enyo.AjaxProperties Oct 08 23:23:23 or url params ? Oct 08 23:23:36 yes, you can try that Oct 08 23:24:10 this is def beyond my 'expertise' so you know. Oct 08 23:24:26 try Oct 08 23:24:30 handleAs: "json" Oct 08 23:24:36 instead of contentType Oct 08 23:24:53 .. but that's as a response... =\ Oct 08 23:25:45 yep that doesn't work either ^^ Oct 08 23:25:57 Ayesh: I think fxspec06 is onto something. contentType isn't what you want to set on the request. Oct 08 23:26:58 out of curiosity, have you tried sending without stringifying the data? Oct 08 23:27:52 and i wonder if mimeType would have a difference, too. but i believe that is something entirely different. Oct 08 23:30:08 On a cross-domain free environment, the syntax working is this one : Oct 08 23:30:21 var moute = new enyo.WebService({ Oct 08 23:30:21 url: "http://localhost:9000/newsitems", Oct 08 23:30:21 method: "POST", Oct 08 23:30:21 postBody: JSON.stringify(data), Oct 08 23:30:21 contentType: "application/json" Oct 08 23:30:21 }); Oct 08 23:30:38 I'll try with mimeType, for science ;) Oct 08 23:31:11 negatif on mimeType Oct 08 23:31:19 contentType is the one used it seems Oct 08 23:32:42 I'll have to use a different lib to do the POST then Oct 08 23:32:55 or serve the HTML from my webservices Oct 08 23:34:19 what lead me to try so far was the fact that on a cross-domain protected environment Oct 08 23:34:21 new enyo.Ajax({ Oct 08 23:34:22     url: "http://localhost:9000/newsitems", Oct 08 23:34:22     method: "POST", Oct 08 23:34:22     postBody: JSON.stringify(data) Oct 08 23:34:22 }); Oct 08 23:34:37 Was handled by my web service Oct 08 23:34:55 but dismissed because the body not being json Oct 08 23:38:24 Ayesh: for webservice, you are calling .send() afterwards? Oct 08 23:38:39 yep Oct 08 23:38:42 otherwise, it won't send. k Oct 08 23:38:59 As i said it works like a charm when I authorize cross-domain Oct 08 23:39:14 yeah, so i haven't an answer. are you testing in chrome or on the device? Oct 08 23:39:21 Chrome Oct 08 23:39:26 because, chrome has cross domain issues, the device does not Oct 08 23:39:40 Firefox as the same behavior Oct 08 23:39:44 (I mean not working ;) ) Oct 08 23:39:50 well, enyo is now cross platform. i'm so used to touchpad development Oct 08 23:40:02 are you deploying as a web app or a mobile app? Oct 08 23:40:19 In this project there will be both Oct 08 23:40:34 only get for device / desktop Oct 08 23:40:38 and Post on desktop Oct 08 23:40:46 ah so yes, you may be better off using a different service to manage the cross domain. or asking someone other than myself. Oct 08 23:41:06 hmm. i wonder if we can get a sugardave in here Oct 08 23:41:40 ^^ Oct 08 23:41:55 What i read make me think there is only 2 solutions Oct 08 23:42:00 the 1st is the easiest Oct 08 23:42:12 make a form with the target pointting to the webservice Oct 08 23:42:17 as form are allowed cross domain Oct 08 23:42:34 the second imply lot of shenannigan with iframe and their parameters Oct 08 23:43:01 there are some jquery plugins doint that but it's like a black box for me Oct 08 23:53:40 Anyway, thank you for your help fxspec Oct 08 23:54:09 I'll continue to investigate it tomorrow Oct 08 23:54:15 bye bye o/ Oct 08 23:54:40 good luck, sorry i couldn't help you Oct 08 23:55:52 Playing ping pong was of great help ;) **** ENDING LOGGING AT Tue Oct 09 02:59:59 2012