[Interest] Swift and Qt? (formally?)

Diego Iastrubni diegoiast at gmail.com
Tue Sep 27 12:16:29 CEST 2016


Sorry for asking the obvious... but... You should be able to use the ObjC
bridges in Swift. As a developer - you should not really care, Swift is
"mostly compatible" with ObjC.

What is the exact problem with this approach?

On Tue, Sep 20, 2016 at 2:51 PM, Jason H <jhihn at gmx.com> wrote:

> > Sent: Tuesday, September 20, 2016 at 1:35 PM
> > From: "Jason H" <jhihn at gmx.com>
> > To: "Till Oliver Knoll" <till.oliver.knoll at gmail.com>
> > Cc: "Qt Project" <interest at qt-project.org>
> > Subject: Re: [Interest] Swift and Qt? (formally?)
> >
> > > Sent: Tuesday, September 20, 2016 at 7:39 AM
> > > From: "Till Oliver Knoll" <till.oliver.knoll at gmail.com>
> > > To: "Qt Project" <interest at qt-project.org>
> > > Subject: Re: [Interest] Swift and Qt? (formally?)
> > >
> > > Am 19.09.16 um 18:52 schrieb Robert Iakobashvili:
> > > > On Mon, Sep 19, 2016 at 5:25 PM, Jason H <jhihn at gmx.com> wrote:
> > > >> There is a 9-month old github; https://github.com/msorvig/qt-
> and-swift for integrating the two.
> > > >>
> > > >> Are there any plans for formal Qt support of Swift? Obj-C is
> painful.
> > > >
> > > > +2
> > >
> > > As far as I know there is no "Swift++" compiler available, that is a
> > > compiler which can compile "Swift + C++", right? In analogy to ObjC++.
> > >
> > > So unless that's the case the common denominator between "Qt" and
> > > "Swift" is C. Of course one could "wrap" the Qt objects - somehow -
> into
> > > C structures and make them "look" like objects (and vice versa). But
> > > that would be a clumsy approach.
> > >
> > > So unless we do have C++ support in Swift my guess is that Qt can do
> > > little here.
> > >
> >
> > Well it is on the roadmap, but out of scope for 3.0, which was just
> released.
> >
> > I don't think I need full-interop, just enough to let me avoid coding
> Obj-c, which for me is mainly AppDelegate. But I can see how in the short
> term it is zero-sum. The app however would mirror how interop is done with
> Android static classes though. That might be something?
>
> I could also restate the problem entirely. It would really be appreciated
> if Qt supplied an AppDelegate that I can hook into and supply handlers for
> without having to write Obj-C. That would satisfy my (and I think others'
> wishes) It would also tie into my long-running gripe about Qt's incomplete
> platform integration on Mobile. If such an AppDelegate plugin approach were
> developed, it should also be able to plug into Android well. (The  plugin*,
> not the AppDelegate. Android would need it's own version of app delegate)
>
> *Not strictly a QPlugin.
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160927/15004aea/attachment.html>


More information about the Interest mailing list