Thank you for that clarification. I was confused about where it fitted in.
I discuss it on swift-users.
On Tue, Oct 11, 2016 at 2:51 PM, Chris Lattner wrote:
>
> > On Oct 11, 2016, at 2:34 PM, Tony Constantinides via swift-evolution <
> swift-evolution@swift.org> wrote:
> >
> > Ok,
> > Any o
> On Oct 11, 2016, at 2:34 PM, Tony Constantinides via swift-evolution
> wrote:
>
> Ok,
> 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
>
Tony--
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 cont
Ok,
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
on Mon Oct 10 2016, Tony Constantinides wrote:
> Its a nice cop-out, but this framework is an extension of the standard
> library of Swift as it will allow Swift developers to target new mobile
> platforms.
It's not a cop-out. We would never include UIKit in Swift's standard
library, which is
Ok,
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
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
e
> On Oct 10, 2016, at 2:04 PM, Tony Constantinides via swift-evolution
> wrote:
>
> Its a nice cop-out, but this framework is an extension of the standard
> library of Swift
Then it requires a proposal as much. Bear in mind that the Swift Standard
Library is platform-agnostic. Adding suppo
Its a nice cop-out, but this framework is an extension of the standard
library of Swift as it will allow Swift developers to target new mobile
platforms. This is the mailing lists for the evolution of Swift which is
what this is. I not sure any of the other Swift mailing lists suits this
goal. I no
> On Oct 9, 2016, at 9:45 PM, Tony Constantinides via swift-evolution
> wrote:
>
> In Swift 3.0 you can build Android apps in Linux but only console apps as
> there is no framework to build GUI apps using JNI.
> What I propose is to build an initial limited framework coded in C that calls
> e
In Swift 3.0 you can build Android apps in Linux but only console apps as
there is no framework to build GUI apps using JNI.
What I propose is to build an initial limited framework coded in C that
calls enough of the Java Android API via JNI to bootstrap the android app
and to create widgets and la
11 matches
Mail list logo
