On Wed, Sep 25, 2013 at 6:47 PM, Robert Park <robert.p...@canonical.com> wrote: > Is this something that you think would stabilise over the next cycle? > Because I would definitely need the QML types I create to be as > generic and re-usable as possible, without forcing everybody > downstream of me to be using Go if they don't want to.
There's a chance. The patches are up for review and have been postponed until the next release of Go is out, which is due this year still. > Ideally I would be authoring QML types, and then people downstream of > me could include them in pure-qml projects, without having to write > any C++ or Go at all in order to incorporate my work. Is that > possible? There are two routes for that. The one we're debating above, and then you could also have a qmlscene-like runner built in Go that includes all Go types. I'm not sure about how much of a good idea that is, though. Perhaps it depends on how much Go is buying you when developing those types, because you're certainly adding an extra layer. gustavo @ http://niemeyer.net -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
