<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jay Balunas" <tech4j@gmail.com><br><b>To: </b>"AeroGear Developer Mailing List" <aerogear-dev@lists.jboss.org><br><b>Cc: </b>"Matt Carrano" <mcarrano@redhat.com><br><b>Sent: </b>Monday, February 24, 2014 9:16:38 AM<br><b>Subject: </b>Re: [aerogear-dev] AeroGear project structure and the website<br><div><br></div><br><div><div>On Feb 20, 2014, at 12:06 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hylke amazing work, I can’t wait to see it in production.<br></div></blockquote><div><br></div><div>+1 Hylke - good stuff, and a lot to get through!</div></div></blockquote><div>+1 this is great!<br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>-- <br>abstractj<br><div><br></div>On February 20, 2014 at 11:06:34 AM, Hylke Bons (<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>) wrote:<br><blockquote><br>TL;DR: The most important questions that we need to answer are <br>these:<br>- "If I download a library on one platform, what must I download <br>to use<br>the same features on an other platform?"<br></blockquote></div></blockquote><div><br></div><div>I like this approach. I'd rather be feature driven than library driven. I think most yours will be looking for what we can do for them before looking at what native libs we provide.</div><div><br></div><div>Lets get this breakdown together for Hylke - using the eitherpad or a gist seems the best approach here.</div></div></blockquote><div><br></div><div>As the noob to the group... perhaps another way to think of this could be by platform -> type of resource needed -> then desired feature? </div><div><br></div><div>So If I'm a Cordova developer and I want to learn how-to setup UnifiedPush Server and integrate Push within my hybrid app I don't care about the native Android & iOS libraries, guides, etc.. I just want everything that is relevant to hybrid apps. I actually ran into this exact issue this last weekend when I created my first push notification app. Its hard to keep track of what guides and sample code I needed. This may solve that. I kind of like the way <a href="http://devcenter.kinvey.com/" data-mce-href="http://devcenter.kinvey.com/">http://devcenter.kinvey.com/</a> does this. When I first go there it allows me to select my dev platform and it sets a cookie so when I come back its still on that platform. I can swap at any time, but as a developer I really liked the Kinvey experience because I could find what I needed. Nothing more nothing less. <br></div><div><br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div><br><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote>-"Is this a part I use on the client, or on the server side?”<br></blockquote><br>Not sure if I understood your question correctly, but to get the full solution, you need to download both<br></div></blockquote><div><br></div><div>I think he means for each feature is there a client and a server part and if so how do we offer them. Then we can get the info and links for the solution in one place. Hylke - is that it or something else?</div><br><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br><blockquote>-"What do we mean when talking about different AeroGear<br>subprojects/modules?”<br></blockquote><br>By subprojects I understand as exactly like you did at <a href="https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-modules.png" target="_blank">https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-modules.png</a>.<br><div><br></div><blockquote><br>One solution might be:<br><a href="https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-modules.png" target="_blank">https://raw2.github.com/hbons/aerogear-design/master/website-restructure/aerogear-modules.png</a><br>I've made a lot of assumptions here, and it might not work, but <br>I'd like<br>to hear your thoughts on it.<br><div><br></div>It would clarify a lot if we could harmonise the different downloads <br>across platforms, either by providing single download solutions <br>or<br>splitting everything up and naming all the parts consistently. <br>I'm<br>interested in what the technical issues might be, as I wasn't <br>around<br>when most of these decisions were made, or I simply missed them. <br><div><br></div>Thoughts or other ideas? :)<br></blockquote><br>I don’t have any idea, because I liked the way how it was organized. No disagreement here.<br></div></blockquote><div><br></div><div>+1 keep up the good work!</div><br><blockquote><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br><blockquote><br>Thanks,<br><div><br></div>Hylke<br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><span class="Apple-converted-space"> </span><br></blockquote><br><div><br></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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 data-mce-bogus="1"></div></blockquote></div><br><br>_______________________________________________<br>aerogear-dev mailing list<br>aerogear-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote><div><br></div></div></body></html>