<div dir="ltr"><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 25, 2013 at 12:42 AM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Hylke, I'm not sure if I'm completely understanding your question.<br>
But the main concern on AeroGear is to make our implementations portable<br>
between serveral backends for example: Node.js<br>
(<a href="https://github.com/abstractj/todo-aerogear-node" target="_blank">https://github.com/abstractj/todo-aerogear-node</a>), Ruby<br>
(<a href="https://github.com/abstractj/todo-aerogear-sinatra" target="_blank">https://github.com/abstractj/todo-aerogear-sinatra</a>), Java with JBoss,<br>
Python (like summers did).<br>
<br></blockquote><div class="gmail_quote"><br></div>Just to make the picture complete AeroGear with Grails ;) <div><a href="https://github.com/sebastienblanc/todo-aerogear-grails">https://github.com/sebastienblanc/todo-aerogear-grails</a><br>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I don't think our main page must be tied with any kind of specific<br>
backend. JBoss is our first class citizen, but mobile is not tied to<br>
the backend, for this reason we do not mention JBoss at the main page.<br>
<br>
Makes sense?<br>
<div class=""><div class="h5"><br>
Hylke Bons wrote:<br>
> Hey Kris,<br>
><br>
> Ok, it seems that we're mostly on the same page on this.<br>
><br>
> You are right that the main line about AeroGear+JBoss doesn't make sense<br>
> when keeping other implementations of backends in mind. Do you have any<br>
> other suggestions? Perhaps "server" or backend"? I think we have to be<br>
> careful to be too generic as well though, as these terms can mean anything.<br>
><br>
> That said, I do think there's a role to play for JBoss AS as an example<br>
> implementation (and probably something that a lot of people would use).<br>
> We could put it somewhere lower on that page?<br>
><br>
> For anyone following up on this: it's mostly about the content, I<br>
> wouldn't worry too much about how things are going to look in the<br>
> current layout as the CSS can be changed easily to accomodate (and I'm<br>
> happy to take this on or help out).<br>
><br>
> Thanks,<br>
><br>
> Hylke<br>
><br>
><br>
> On 24/05/2013 20:15, Kris Borchers wrote:<br>
>> On May 24, 2013, at 2:01 PM, Hylke Bons<<a href="mailto:hbons@redhat.com">hbons@redhat.com</a>> wrote:<br>
>><br>
>>> Hey Kris,<br>
>>><br>
>>> On 24/05/2013 18:40, Kris Borchers wrote:<br>
>>>> We are not specific to any back end so we won't mention JBoss here.<br>
>>>>> Get started with a library for your platform…<br>
>>>> Is that line really necessary?<br>
>>> Right now, it's not very clear where these buttons will take you.<br>
>>> Visitors can find out, but it's friendlier to point out where you're<br>
>>> going to be taken in advance. "'Javascript', 'Android' what?".<br>
>> I can agree that something is needed but still not sure if I like that sentence fragment floating there.<br>
>>>>> [[---platform buttons here---]]<br>
>>>>><br>
>>>>> == Why? ==<br>
>>>> Again, is this necessary? What does it add? Both of those lines add more vertical scroll on mobile devices so I don't see the benefit, if any, outweighing that.<br>
>>> To transition from the "What is" section to the "Why you should care"<br>
>>> section. It's not strictly necessary, but I like some kind of transition<br>
>>> between sections.<br>
>> Again, I'm not sure how I feel about a little piece of text just floating in the page but I am willing to go along with it and see what you come up with.<br>
>>> It does add a few pixels of vertical space, but this is something we<br>
>>> should look at from a higher level. There are many elements that take a<br>
>>> lot of vertical space currently, so I'd like to keep the discussion on<br>
>>> the functional level instead of going into the details of scale or<br>
>>> pixels. We can make CSS tweaks later on as well if a certain vertical<br>
>>> height is a requirement.<br>
>> Agree<br>
>>>>> === Unify mobile development ===<br>
>>>>><br>
>>>>> AeroGear provides flexible and extensible libraries to simplify mobile<br>
>>>>> development across platforms and cut common repetitive infrastructure<br>
>>>>> tasks. Integrate with the most exotic of endpoints.<br>
>>>>> [[ Get started>> ]]<br>
>>>> Where would this link go? We have multiple paths for getting started, thus, the platform buttons at the top.<br>
>>> To "Get the gear" or a page that is a little bit more in between a<br>
>>> download page and a first run tutorial (I don't think this exists yet,<br>
>>> but I'm happy to take that on as well).<br>
>> If you are willing to dive in on a page like that I think we would all appreciate it. Otherwise, Get the Gear is probably ok too.<br>
>>>>> === Simple API ===<br>
>>>>><br>
>>>>> Talking to [[ RESTful ]] (1) backends couldn't be easier. We've<br>
>>>>> abstracted all of the plumbing into a simple programmatic API for doing<br>
>>>>> [[ CRUD ]] (2) operations and paginating large amounts of data.<br>
>>>>> [[ Browse API documentation>> ]]<br>
>>>> Which set of API docs? Each platform has their own, again, we have the buttons at the top.<br>
>>> This goes to the API Docs page that's already in present in the top<br>
>>> menu. There can be more entry points to the same thing. Maybe it's a<br>
>>> filler, but it's good for consistency to let every paragraph be followed<br>
>>> by a link. I'm open to any other links if you can think of something better.<br>
>> Duh, that makes sense. Main API docs index is fine.<br>
>>> Thanks,<br>
>>><br>
>>> Hylke<br>
>>><br>
>>>>> === Mobility and security, both ===<br>
>>>>><br>
>>>>> Integrate with your existing enterprise environment. AeroGear provides<br>
>>>>> Two-Factor Authentication and One-Time-Password features to improve your<br>
>>>>> application's security.<br>
>>>>> [[ Learn about AeroGear Security>> ]]<br>
>>>>><br>
>>>>> === Easy server routing ===<br>
>>>>><br>
>>>>> Define HTTP routes with a simple Java Internal [[ Domain-Specific<br>
>>>>> Language ]] (3). The perfect fit for client-heavy applications where you<br>
>>>>> have very few entry points and delegate logic to the client tiers.<br>
>>>>> [[ Learn about AeroGear Controller>> ]]<br>
>>>>><br>
>>>> I will leave security and controller comments to Bruno and Dan. These changes would also probably require imagery changes as well.<br>
>>>>> ------------------------------------------------------------<br>
>>>>> (1) <a href="http://en.wikipedia.org/wiki/RESTful" target="_blank">http://en.wikipedia.org/wiki/RESTful</a><br>
>>>>> (2) <a href="http://en.wikipedia.org/wiki/Create,_read,_update_and_delete" target="_blank">http://en.wikipedia.org/wiki/Create,_read,_update_and_delete</a><br>
>>>>> (3) <a href="http://en.wikipedia.org/wiki/Domain-specific_language" target="_blank">http://en.wikipedia.org/wiki/Domain-specific_language</a><br>
>>>>><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>
>>>> _______________________________________________<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>
>>> 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>
>> 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>
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></div>