TabBar-equivalent in Qt 5.6

  • I have been using Qt for almost 10 years now, but exclusively with C++. Now I'd like to give QML/Quick another shot with a simple stand-alone project, which has to run on 5.6.

    I want to display a form with a few tabs, each tab containing a table. I have found an example with a table view, it looks simple enough.
    However, I noticed that the TabBar QML Type has only been introduced in Qt 5.7. What did people use back in 5.6?

    From what I read, Qt Quick 1 and 2 are not compatible and cannot be mixed, and I certainly don't want to start a Qt Quick 1 project nowadays.

  • Is there a compelling reason to use old frameworks?
    Why would any software house put minor updates off, especially ones that have known desired features?

    Don't get me wrong, I've worked in a corporate environment where the default was unless every version is vetted and approved and if not a solid no. It doesn't mean it wasn't a stupid rationale, they'd deny dev tools, update desktop frameworks to latest religiously and servers : never. It was easier to commission a whole new server with a later OS and your framework major than get an update.

    My mindset is without a compelling break/reason to stay current. Otherwise you're here fighting/looking to recreate something everyone else already has for free?

    The whole reason for using these frameworks is so we don't have to, why fight it.

    I just looked through the source - yeah - I'd like to not have to think about it - it's already here in 5.10... just update tools already! Winge to your boss. Dare I say the advice you'd get to recreate is going to similar looking but unsupported code?

    I do remember when the empty templates got updated and thought - oh that's cool. My current app uses them now but until then I only needed a single dialog / project wasn't that far advanced. As we've developed we found utilizing this feature nice to have.

    Not sure this is exactly helpful but it's what I thought.

  • Well, the Rationale here is that Qt is extensively used on server side (Core, Network), and and there are no known issues we have related to Qt on that side. I would now add a small, not-so-important UI program to that.

    For the server people, updating to a newer version of Qt incurs costs (risks of regressions / new bugs, testing) but bring no apparent benefits (none of the new features is needed, no bugs of interest have been fixed).

    I have been offered to run my little tool on a separate Qt version, so I might have solved my problem that way.

Log in to reply