<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We can have more than 1 quickstart for Aerogear :-)<div><br></div><div>There should be one key/core archetype that shows up on JBoss Central - but there can be a dozen quickstarts to focus on different aspects of Aerogear capabilities. </div><div><br></div><div><div><div>On Jan 2, 2013, at 11:01 AM, Sebastien Blanc wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Sure ! I will do a blog post about Weinre and on how to integrate it nicely.<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 2, 2013 at 4:57 PM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 02/01/2013, at 12:15, Kris Borchers <<a href="mailto:kris@redhat.com">kris@redhat.com</a>> wrote:<br>
<br>
> Weinre is an amazing tool. I would say it is much more useful for hybrid apps as opposed to web apps since, for the most part, you can just run your web app in a desktop browser to debug it. There are definitely cases where testing on the device is useful though and Weinre makes it much easier.<br>
</div>+1<br>
<div class="im">><br>
> I would prefer to not add this to the quickstart. I think the extra code will mostly just get in the way of someone trying to grok the JS, especially non-JS devs. I would prefer to see this as a blog post/tutorial/article on <a href="http://AeroGear.org">AeroGear.org</a> instead as the info is very valuable I just think it needs to be outside of the actual quickstart.<br>
<br>
</div>Indeed, a blog post on weinre would be rad - wanna give it a run sebi?<br>
+1<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Any other thoughts from anyone?<br>
><br>
> On Jan 2, 2013, at 7:58 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
><br>
>> Hi,<br>
>> A few weeks ago, on the IRC channel there was a question about Weinre . For those who don't know what Weinre is (definition from Weinre's homepage) :<br>
>><br>
>> weinre is a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow you debug web pages on a mobile device such as a phone.<br>
>><br>
>> So it's extremely useful and totally in the scope of Aerogear (Web/Hybrid) which targets mobile development .<br>
>> It's easy to setup :<br>
>><br>
>> 1. Install the Weinre server , if you have npm : sudo npm -g install weinre<br>
>> 2. Start the Weinre server : weinre --httPort 8081<br>
>> 3. Instrument your web page to act as a debug target by adding the following :<br>
>> <script src="<a href="http://a.b.c:8081/target/target-script-min.js" target="_blank">http://a.b.c:8081/target/target-script-min.js</a>"></script><br>
>><br>
>> To make things even easier, I've created a new branch on the kitchensink app where step 3 is not needed anymore[1]. Instead of this you can just activate remote debugging by passing an parameter in the URL :<br>
>><br>
>> <a href="http://a.b.c:8080/jboss-as-kitchensink-aerogear-js/index.html?debug=d.e.f:8081" target="_blank">http://a.b.c:8080/jboss-as-kitchensink-aerogear-js/index.html?debug=d.e.f:8081</a><br>
>><br>
>> Where d.e.f is the IP of the server where Weinre is running.<br>
>><br>
>> Then you can access the debug page : <a href="http://localhost:8081/client" target="_blank">http://localhost:8081/client</a><br>
>><br>
>> The little tweak I made give more flexibility on how you can integrate your app with Weinre :<br>
>> - No hardcoding in your script.<br>
>> - You can easily change the IP of the debug server<br>
>> - The client makes only make requests to the debug servers (and there are a lot of requests :) ) if debugging is activated.<br>
>><br>
>> If more people find this useful maybe we could merge it for the next release. comments welcome !<br>
>><br>
>> Seb<br>
>><br>
>> [1] <a href="http://people.apache.org/~pmuellr/weinre/docs/latest/" target="_blank">http://people.apache.org/~pmuellr/weinre/docs/latest/</a>)<br>
>> [2] <a href="https://github.com/sebastienblanc/as-quickstarts/tree/weinre/kitchensink-aerogear-js" target="_blank">https://github.com/sebastienblanc/as-quickstarts/tree/weinre/kitchensink-aerogear-js</a><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<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>