<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks for the feedback! See responses inline.<div><br><div><div>On Aug 16, 2012, at 4:33 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>looking at [1] and also reading the client JS code from the TODO app<br>(->app.js), I am wondering if there is a newer version of the draft?<br></blockquote><div><br></div>This is more up to date but also needs some updating.</div><div><a href="https://github.com/aerogear/aerogear-js/blob/master/src/pipeline/README.md">https://github.com/aerogear/aerogear-js/blob/master/src/pipeline/README.md</a></div><div><br><blockquote type="cite"><br>Also, inside of the rest adapter of aerogear.js the 'delete' function<br>is called 'del' ([2]), not sure if that's a good idea..<br></blockquote><div><br></div>I was using delete but that is a reserved word in JavaScript so linters hate it. I decided to change to del but we can change it to remove or something else. I am open to suggestions.<br><blockquote type="cite"><br>While reading the app.js file, I also noticed that some of the 'setup'<br>syntax needs to be documented (e.g. the draft is missing details on<br>settings,url etc of the cfg object):<br>var todo = aerogear.pipeline([<br> {<br> name: "tasks",<br> settings: {<br> url: "/todo-server/task"<br> }<br> },<br>...<br><br>Also - perhaps for now it is OK, but I think it (still) reads a bit<br>too much jQuery/ajax like?!<br>projectGet = Projects.read({<br> ajax: {<br> success: function( data, textStatus, jqXHR ) {<br> $( "#project-loader" ).hide();<br> updateProjectList( data );<br> }<br> }<br>});<br>(I think we had this topic already in the past, not too strong<br>feelings about this... but just wanted to mention this)<br></blockquote><div><br></div>The reason there isn't documentation and that it looks like jQuery.ajax is because it is. :) The ajax settings are basically a straight passthrough to jQuery ajax so that any of those settings can be overridden. We can discuss changing this but I figured why hide the fact that we're using jQuery.ajax or add another layer of complexity over the already large list of settings that can be changed on jQuery.ajax<br><blockquote type="cite"><br>Oh, one last question, is there a decent/easy way to generate API docs<br>out of the JavaScript API?<br></blockquote><div><br></div>I have not found one that I like. Most solutions require adding a bunch of garbage to the source which I am not a fan of because it makes the source itself harder to read. That being said, I am also not a fan of maintaining that documentation by hand so hoping I can find some middle ground. Again, open to suggestions.<br><blockquote type="cite"><br>Thanks!<br><br>[1] <a href="https://gist.github.com/3084134">https://gist.github.com/3084134</a><br>[2] <a href="https://github.com/aerogear/aerogear-js/blob/master/src/pipeline/adapters/rest.js#L74">https://github.com/aerogear/aerogear-js/blob/master/src/pipeline/adapters/rest.js#L74</a><br><br>-- <br>Matthias Wessendorf<br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf">http://twitter.com/mwessendorf</a><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev<br></blockquote></div><br></div></body></html>