[swift-evolution] [Pitch]Building a limited framework to develop Android Apps in Swift 3.0
xiaodi.wu at gmail.com
Tue Oct 11 16:50:58 CDT 2016
First off, welcome to the Swift community! Second, I think you're
misunderstanding the feedback here. The swift-evolution list is not a
mailing list for Swift community discussions in general. It's a mailing
list for proposals to change the core language (how do generics work? how
does control flow work? what about arrays, dictionaries, strings?). You'll
want to write to swift-users, or another forum where the Swift community is
active, to get feedback and participation about other libraries. If there's
something in the core language that you'll need to hook into to make
Android apps work better, then this is a great place to propose those
specific changes, and you could demonstrate a compelling use case by
describing how it enables critical features in your third-party library.
On Tue, Oct 11, 2016 at 4:34 PM, Tony Constantinides via swift-evolution <
swift-evolution at swift.org> wrote:
> Any other feedback from the Swift community other than it does not belong
> as part of Swift? Or get the hell out of here?
> I discussing this issue so people in the Swift community are aware of what
> I am planning to do and have the ability to shape if they they so wish.
> Some Technical points
> Keep in mind when I say framework I do NOT mean a OSX like framework like
> XCTest, I mean a third party library that doing two way communication with
> your app.
> a) It's not an Android Binding as that will not work, its a framework
> wrapped up in a library using the bridging pattern
> b) I want Swift to bootstrap the Android runtime indirectly when using the
> framework. I want to make the Swift source the driving code and not the
> Android Code. All events that the device sends out we be rerouted to Swift
> code which will call the Java API using JNI in response
> c) Android apps have a directory structure that must be maintained by the
> framework to be valid. This will be handled by the framework.
> d) Packages of Swift code will wrap the calls to the Java API which will
> cause the need for a large library on the Swift side. The Swift developer
> will use the Swift Library like any other and be unaware of its internal
> routing to the Android API
> e) This library will only work on Linux as there is where the Android
> compilers are for ARM
> Please provide input as it is welcome.
> Right now I getting *crickets* which is not good.
> I will be releasing a statement to the press when this work is working.
> I want to state that the Swift Community actively supported it, including
> Apple employees
> I wish that statement to be true!
> Sincerely yours,
> Tony Constantinides
> On Mon, Oct 10, 2016 at 12:08 PM, Tony Constantinides <
> constantinnovationsinc at gmail.com> wrote:
>> I was trying to follow the evolution process which states to "discuss
>> your idea on the mailing lists" before i begin work on it.That is what I am
>> doing. If you feel this work is not part of swift-evolution I shall bother
>> this group no longer. You have to remember I am very new to interfacing
>> with the Swift team hence the cautious approach. I do realize this is a
>> proposal and not a pitch and I am prepare to provide a great many more
>> details in a proposal. If you wish to point me to another swift mailing
>> list then please do so. If you feel this a "third party lib" then tell me
>> where it slots in. In other words be helpful and not react like a teen age
>> Of course I will begin development of this feature on github and give
>> talks to my local developer group. When I create a github with this
>> framework I going to have to add a licence. Making the software
>> copyrighted to my company and not link to the swift.org project in any
>> way seem odd to me. Not my idea of "open source" or contributing to a
>> "major open source project". You state that the Swift community members
>> have spent a great deal of time and effort in getting getting Swift to even
>> build on Android. Congrats! I here to take it to the next level.
>> If there is Swift community interest the code will be free via open
>> source. If there is none and judging by the response from the developers in
>> my "Bay Area Android Developer meetup group" that hard to believe then I
>> make it it commercial software to be sold.
>> Many thanks in advance.
>> Sincerely yours,
>> Tony Constantinides
>> On Mon, Oct 10, 2016 at 11:15 AM, Adrian Zubarev <
>> adrian.zubarev at devandartist.com> wrote:
>>> It’s disappointing that you seem not to understand what this mailing
>>> list is for. Building a Framework does not require the evolution process.
>>> It’s all up to you to open a GitHub repository and just start building.
>>> Sure you can ask for help, but I believe other platforms like
>>> stackoverflow or even swift-users would be a better place for that.
>>> And I think your statement about rejection is totally wrong. The core
>>> team has enough work and responsibility to care about.
>>> Adrian Zubarev
>>> Sent with Airmail
>>> Am 10. Oktober 2016 um 20:06:26, Tony Constantinides via swift-evolution
>>> (swift-evolution at swift.org) schrieb:
>>> I find it extremely disappointing if Swift core members reject enhancing
>>> Swift to target additional mobile platforms as making Swift cross-platform
>>> is a stated goal.
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution