Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of shazron@gmail.com designates
 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHYtTq=4rxTTx4iN+41AVu5e2yOJk8F+QH9WTs+1jPpHWuqNqg@mail.gmail.com>
References: <3486BFDE-97B4-4744-95A3-FBFD8090CC16@redhat.com>
 <CAE6O_-bV3Hbq-CncUWaz9TvUE1P+yr9-F=_ek9b1PmAiWAHCEw@mail.gmail.com>
 <CAHYtTq=4rxTTx4iN+41AVu5e2yOJk8F+QH9WTs+1jPpHWuqNqg@mail.gmail.com>
From: Shazron <shazron@gmail.com>
Date: Thu, 28 Aug 2014 09:54:56 -0700
Message-ID: 
 <CAE6O_-bf+Xe8BOtWYvb4jML2kmRAXwOitdSHqhA-mm1pzK3NNw@mail.gmail.com>
Subject: Re: plugin with swift
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree, the time for messing with pbxproj files is over. In hindsight
we should have moved to workspaces and xcconfig files, but what can
you do. We should get rid of this technical debt asap by 4.0

On Thu, Aug 28, 2014 at 9:44 AM, Carlos Santana <csantana23@gmail.com> wrot=
e:
> I guess I need to pay more attention to JIRA issues :-)
>
> I think using xcconfig files is huge step forward in managing xcode
> projects.
>
> xcconfig is the same pattern use by cocoapods, it allows more flexibility
> and and at the same time not messing up user's pbxproj
>
> One thing to also look is to flow information from plugin.xml into xcconf=
ig
> and not use node-xcode.
>
>
>
> On Thu, Aug 28, 2014 at 12:03 PM, Shazron <shazron@gmail.com> wrote:
>
>> Right now - no. Although you could write a post-install hook that will
>> directly update the project file using node-xcode I suppose.
>>
>> In the future, we can just add this to the template (please file a
>> feature request so we don't forget). But I think the approach in this
>> issue is better, and will be simpler for the CLI to add items:
>> https://issues.apache.org/jira/browse/CB-5520
>>
>>
>> On Thu, Aug 28, 2014 at 2:19 AM, Erik Jan de Wit <edewit@redhat.com>
>> wrote:
>> > Hi all,
>> >
>> > I=E2=80=99ve been experimenting with swift and ported the HelloWorld p=
lugin [1]
>> to Swift. There was one trick to make it work together with cordova, tha=
t
>> was to specify the name of the class to export it under so it could be
>> referenced:
>> >
>> > @objc(HWPHello) class Hello : CDVPlugin {
>> >
>> > Then it=E2=80=99s =E2=80=98exported=E2=80=99 under =E2=80=9CHWPHello=
=E2=80=9D that is what we put into the
>> plugin.xml that can then be found at runtime by cordova
>> >
>> > There remains one problem in order to use CDVPlugin in Swift one needs
>> to add a bridging header file and add that to the swift compiler options=
.
>> The file can be part of the plugin but can cordova on plugin install add
>> the needed compiler settings?
>> >
>> > [1] https://github.com/edewit/cordova-plugin-hello/tree/swift
>>
>
>
>
> --
> Carlos Santana
> <csantana23@gmail.com>