[aerogear-dev] iOS xCode Template

Thu Mar 14 10:00:02 EDT 2013

PERFECT ! :)

On Thu, Mar 14, 2013 at 2:48 PM, Christos Vasilakis <cvasilak at gmail.com>wrote:

> thanks for the feedback!
>
> answers inline
>
> On Mar 14, 2013, at 1:58 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
> A few comments
>
> 1) Change the mkdir/value to
> mkdir -p ~/Library/Developer/Xcode/Templates/Application/Project\
> Templates/
>
> ok
>
>
> 2) Not sure, but IMO the gray info on cocoapods can be easily missed. I
> know that AFNetworking uses that approach... but I prefer making this a bit
> more explicit.
> Especially with our JBoss background, we may target a different set of
> developers
>
>
> I put and "important notice" header and updated the doc  with why "pod
> install" is required and link to cocoapods web site
>
>
> 3) What about adding this as the first line of the PODFILE ?
> xcodeproj 'XXXX.xcodeproj'
> (where the XXXXXX is hte name of the chosen app name)
>
>
> ok
>
>
> 4) instead of "5.0" (double quotes), I'd prefer single quotes: '5.0' (the
> CocoaPod doc uses that format as well)
>
> https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/CocoaPods.xctemplate/TemplateInfo.plist#L15
>
>
> ok
>
>
> 5) Should this be ".gitignore" (the . is missing??)??
>
> https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/gitignore
>
>
> done on purpose so that the filename is visible when browsing. During the
> generation process it is converted to  .gitignore on the user's project
> directory.
>
>
> 6) use Xcode - not xCode, noXCode :)
> one example:
>
> https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/ViewController.h#L3
>
>
> ok :)
>
> Thanks!
>
> -
> Christos
>
>
>
> Cheers!
>
> Great works!!!
>
> On Thu, Mar 14, 2013 at 12:14 PM, Christos Vasilakis <cvasilak at gmail.com>wrote:
>
>> Hi,
>>
>> the Xcode template is ready[1],  I would appreciate if someone else gives
>> it a try too and let me know if there are any issues.
>> If not we can go ahead and merge in our organisation repo
>>
>> Thanks!
>> Christos
>>
>> [1] https://github.com/cvasilak/aerogear-ios-xcode-template
>>
>> On Mar 13, 2013, at 10:16 AM, Matthias Wessendorf <matzew at apache.org>
>> wrote:
>>
>> yup, I know... But I was curious if we want to encourage folks to use a
>> more liberal license :)
>>
>> In any case, we should at least add some header, like "generated by the
>> JBoss AeroGear team/plugin" etc...
>>
>> On Wed, Mar 13, 2013 at 9:08 AM, Christos Vasilakis <cvasilak at gmail.com>wrote:
>>
>>> Hi,
>>>
>>> from what I have seen (e.g. in AFNetworking case) the generated source
>>> code doesn't contain any license header so I guess it's left for the user
>>> to decide afterwards. I can easily go ahead and add it if we choose so
>>> though.
>>>
>>>
>>> On Mar 12, 2013, at 11:47 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>> +1 the application is easy and simple - exactly what we want.
>>>
>>> Question: Do we want to use our Apache licensed template ?
>>>
>>> On Tue, Mar 12, 2013 at 2:28 PM, Christos Vasilakis <cvasilak at gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> I've created an quick-start example here[1] that will be used as an
>>>> Xcode template [2] (think of it as maven archetype for iOS)  for our users
>>>> to easily get started with the framework. Prior to create the config
>>>> required to produce the template, I would like to have your opinion on what
>>>> else should be included in the base demo.
>>>>
>>>> Currently  it connects to our TODO demo, retrieves the tasks and
>>>> updates a table view component.  I think it serves as a good basis for
>>>> users to extend.
>>>>
>>>> Wdyt?
>>>>
>>>> Thanks
>>>> Christos
>>>>
>>>>
>>>> [1] https://github.com/cvasilak/AeroGearPrototype
>>>> [2]  http://tinyurl.com/bvhusuk
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog: http://matthiaswessendorf.wordpress.com/
>>> sessions: http://www.slideshare.net/mwessendorf
>>> twitter: http://twitter.com/mwessendorf
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130314/941dabba/attachment-0001.html 