Mate QT?

[Edward78]

So how hard would it be to do, I heard the whole DE would need rewritteb.

[Ralphred]

Well, yes. I'm not a huge Mate expert but I know it's written using GTK, meaning to say GUI API used is GTK(3/4?). QT is "the other popular" GUI API, so a re-write of all the seen interface parts, and backend parts that need gconf etc to their QT counterparts.

IMHO it would be easier to start with LXQT and add functionality to match Mate.

[10leej]

15 hours ago, Edward78 said:

So how hard would it be to do, I heard the whole DE would need rewritteb.

Yep, basically it'd be a whole new project hence why LXDE became LXQT

[PCGamer2727]

Rewriting Mate in Qt would be completely impractical.  At least, it would be not that much less work than just creating a new DE.

 

More importantly, why would you want to?

[Edward78]

11 hours ago, PCGamer2727 said:

Rewriting Mate in Qt would be completely impractical.  At least, it would be not that much less work than just creating a new DE.

 

More importantly, why would you want to?

I like the look, but KDE can look the same right?

[The Hope]

On 8/27/2023 at 3:41 AM, PCGamer2727 said:

Rewriting Mate in Qt would be completely impractical.  At least, it would be not that much less work than just creating a new DE.

 

More importantly, why would you want to?

Maybe if you want the MATE desktop experience but with better integration for Qt apps?

Or maybe because MATE has serious performance issues in many graphical apps and games?

 

I use LXQt because it is a lightweight KDE and I think it is very underrated.

I don't really use desktop environments frequently. But if I need to use a DE I always pick LXQt right now.