Sure. I think there are advantages to be had from bundling, obviously, but those don't really exist right now. +1 from me.
www.qinetic.com.au - Qt And QML User Experience Specialists On Tue, Dec 2, 2014 at 6:55 PM, Simon Hausmann < [email protected]> wrote: > Hi, > > I'd like to revive an old thread about Qml and the "bundle" feature we > have in > the code base. The last time this was discussed (August last year, > http://lists.qt-project.org/pipermail/development/2013-August/012261.html > ) I > think no conclusion was reached regarding whether this feature should be > kept > around or not. > > >From what I remember from discussions around the feature and from the code > that I've seen meanwhile, the intentions of the bundle system were good. > Save > parsing time, make room for architecture specific output, all encapsulated > in > one file. > > However I'm at the point where I don't think the bundle feature adds any > value > anymore, but it does add cost to the code base in terms of maintenance. You > can argue about the actual price, but it is greater than zero :) > > Meanwhile nobody has worked on it, the tooling supporting beyond the > command > line tool is still non-existent and the feature remains undocumented. > Therefore I propose to remove the command line tool, the bundle loading > support in the engine as well as the auto-tests from the dev branch. > > What do we have to loose? If somebody really wants to pick it up again, > then > they can revive it from the git history and play with it. > > Any opinions? :) > > > Simon > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
