<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 19, 2014 at 9:11 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 18 Feb 2014, at 18:05, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br>
<br>
> Hi Folks !<br>
><br>
> While I was watching Matzew's screencast[1] about using the AeroGear iOS Template (which bootstrap/help to create a new iOS project) I was thinking about pushing the concept even further.<br>
><br>
> Wouldn't it be nice to be able to scaffold a complete CRUD Native iOS app ? And of course by using the bullets we already have : Forge.<br>
<br>
</div>You would generate server and client side at once?<br></blockquote><div><br></div><div>Well, the iOS generation will be just one specific forge command, the rest are just "existing/vanilla" forge commands (entiies creation, REST endpoints creation) </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">><br>
> The idea would be to have the same stuff as the HTML5 Scaffolding plugin/addon but instead of generating JS and html files we generate *.h and *.m files (and of course a complete iOS app structure). The general workflow would stay the same : create a JEE project, generate entities, generate REST endpoints and scaffold the client.<br>
><br>
> So basically all we would have to do is to write those templates (+ some code to write to the correct location / create the skeleton).<br>
><br>
<br>
</div>I would start with an app generated with iOS template for simple Pipe, and then add to it. See my questions below.<br>
<div class=""><br>
> I will be glad to start on this but I would need some help from the iOS gurus for one thing : having a clean iOS CRUD App from which I could reverse engineer/extract the templates. This app, while staying simple, should contain all the possible use cases : String, numbers, boolean, Date but also some relation between entities (1-to-1, 1-to-many) :<br>
<br>
</div>With Pipes and Stores, we use more a Key/Value approach. Not sure what you have in mind to represent relation.<br></blockquote><div>Well, not sure how it is implemented in iOS but for instance when you choose a team, a list of players should also be retrieved. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
In term of UI what do you want to see?<br>
first screen: Team TableView with static table cell, Players and Tournaments cell link to second screen TableView<br>
second screen: Player TableView with a list of player displaying only name, selecting a player will go to third screen Player details<br>
third screen: Player Details static table view with date display etc…<br>
<br>
Then we might need a descriptive/configurable way of saying to forge this is my main screen, on that list display ‘player name’ etc…<br>
What’s your view on that?<br></blockquote><div><br></div><div>We could do like the grails html5 scaffold plugin : the main screen contains a list of the entities, when you select an entity by default you go to the list view and in the bottom bar you have a button to create a new one.</div>
<div>When a entity entry is selected in the bottom bar you can : edit or delete </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
><br>
> I started with this simple idea :<br>
> Team {<br>
> name : String<br>
> hasMany : Player<br>
> hasMany: Tournamenent // many-to-many<br>
> }<br>
><br>
> Player {<br>
> name : String<br>
> dateOfBirth: Date<br>
> injured: boolean<br>
> hasOne : Team<br>
> }<br>
><br>
> Tournament {<br>
> name: String<br>
> price : number<br>
> hasMany: Team<br>
> }<br>
><br>
><br>
><br>
> The gist is here <a href="https://gist.github.com/sebastienblanc/9074932" target="_blank">https://gist.github.com/sebastienblanc/9074932</a><br>
><br>
> So, if anyone would like to create this app, I could start from there with a first draft. I will also try on my side but my objective-c skills are not really good enough right now ;)<br>
<br>
</div>team work :)<br>
<div class=""><br>
><br>
> I think that could be a very cool feature.<br>
><br>
> A last very important remark : you can reread this message and replace iOS with Android because once we got it shaped for iOS we could do exactly the same for Android.<br>
<br>
</div>make sense<br>
<br>
><br>
> Sebi<br>
><br>
><br>
> [1] <a href="https://vimeo.com/86978742" target="_blank">https://vimeo.com/86978742</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>
_______________________________________________<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>
</blockquote></div><br></div></div>