On Wed, Apr 30, 2014 at 5:26 AM, Wayne Merricks <[email protected]> wrote: > > QT3 is a bit of a worry longer term though. To put it into perspective QT4 > was released 6 or 7 years ago and QT5 in 2012. There is a migration path to > QT4 with automated tools to handle the tedious work but doing a quick scout > through several hundred thousand lines of Rivendell, it will be a huge effort > to port to QT4. > > I'm sure theres many more years of building from source left in QT3 but it > will be a barrier that will only get harder to overcome. > > Wasn't there talk of a QT4 branch in the SVN at one point? I'm fairly > certain development stalled but does anyone know the current status of that?
Getting off topic, but at this point, if someone were to put in the development effort, I'd probably recommend going straight to QT5 and skipping QT4 all together. Otherwise we'll be in the same boat again in another year or two. As you mention, even QT4 is over 5 years old at this point. How well separated is the Rivendell UI code from the rest of the code base? Is it fairly well encapsulated such that writing a new UI layer is a relatively straightforward process, or is it intermingled with all of the core logic, audio engine, etc? We generally have a handfull of coders interested in working on specific projects, but it would be an easier sell if teh system was already set up for straightforward UI layer swapping. Or else Rivendell should just apply as a Google Summer of Code project next summer and try to recruit a GSoC intern to work on it. _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
