LinuxMCE Forums
General => Developers => Topic started by: MediaEngineer on January 15, 2009, 12:24:32 am
-
Nokia announced that Qt is now LGPL (http://www.qtsoftware.com/about/news/lgpl-license-option-added-to-qt). Does that change remove any dependencies of LinuxMCE on the PPL or any other non-GPL license? Even if there remain some dependencies on non-GPL licenses, does Qt under LGPL remove any of them?
-
Not really, you would have to completely rewrite the Orbiter which is much more than just a UI, and a huge piece of code. Plus there are other pieces of LMCE unrelated to the UI that are covered by PPL. Why are you worried about PPL? It should only effect you if you intend to sell complete media/HA solutions bundled with hardware. Other than that, it has no effect on your usage of the system.
-
LinuxMCE proper does not use ANY of KDE or Qt whatsoever.
The only exception is the Launch Manager.
-Thom
-
Not really, you would have to completely rewrite the Orbiter which is much more than just a UI, and a huge piece of code.
LinuxMCE proper does not use ANY of KDE or Qt whatsoever.
The only exception is the Launch Manager.
I'm confused now: does the Orbiter use Qt? If not, what toolkit is the onscreen GUI built on? I thought all the old discussions of "UI3" were prioritizing Qt, because of some new Qt innovations (in KDE4). Maybe that was just because Aaron of Pluto was interested in cutting some deal with TrollTech (that I think never happened), and UI3 is still just an occasional discussion.
Not really, you would have to completely rewrite the Orbiter which is much more than just a UI, and a huge piece of code. Plus there are other pieces of LMCE unrelated to the UI that are covered by PPL. Why are you worried about PPL? It should only effect you if you intend to sell complete media/HA solutions bundled with hardware. Other than that, it has no effect on your usage of the system.
I'm generally interested in seeing any project come under a single license. I'd also like to see companies sponsor LinuxMCE which sell HW bundled with it, because they have the money and project management to move it along, market it to increase its popularity (which makes the community larger, which means more help and contributions).
I also think that the Orbiter code, which I've looked at (its messaging and network API, not its GUI), would be easier to upgrade if its UI were a discrete presentation layer, and not as integrated with the PPL code. The Pluto code remaining in LinuxMCE that I saw (in 0710) was written very badly, hard to trace or maintain.
-
Orbiter does not use Qt.
Why don't you actually dig into src/Orbiter ... spend some time looking at the code... and then come back to the discussion?
Your comments basically state that you are completely clueless as to what's actually going on underneath.
-Thom
p.s. You may want to check out everything in the Programmers Guide category on the wiki. There are various articles relating to the design of the rendering classes in orbiter which should shed some light on its design.
\
-
Orbiter does not use Qt.
Why don't you actually dig into src/Orbiter ... spend some time looking at the code... and then come back to the discussion?
Your comments basically state that you are completely clueless as to what's actually going on underneath.
-Thom
p.s. You may want to check out everything in the Programmers Guide category on the wiki. There are various articles relating to the design of the rendering classes in orbiter which should shed some light on its design.
\
Well, telling me that the Orbiter would need recoding when I asked about Qt was a clue that sent me off in the wrong direction. I'll look to the code rather than the forums for more info.
-
Actually, that was me that told you that, as that was my understanding - thom is the expert on this. The reason I said that is because the Orbiter isn't based on Qt (as Thom pointed out) so all that would need to be redone. Plus the Orbiter contains a lot of other functional logic that isn't related to rendering graphics and stuff, but to DCE messaging etc.
-
Not really, you would have to completely rewrite the Orbiter which is much more than just a UI, and a huge piece of code.
LinuxMCE proper does not use ANY of KDE or Qt whatsoever.
The only exception is the Launch Manager.
I'm confused now: does the Orbiter use Qt? If not, what toolkit is the onscreen GUI built on? I thought all the old discussions of "UI3" were prioritizing Qt, because of some new Qt innovations (in KDE4). Maybe that was just because Aaron of Pluto was interested in cutting some deal with TrollTech (that I think never happened), and UI3 is still just an occasional discussion.
Not really, you would have to completely rewrite the Orbiter which is much more than just a UI, and a huge piece of code. Plus there are other pieces of LMCE unrelated to the UI that are covered by PPL. Why are you worried about PPL? It should only effect you if you intend to sell complete media/HA solutions bundled with hardware. Other than that, it has no effect on your usage of the system.
I'm generally interested in seeing any project come under a single license. I'd also like to see companies sponsor LinuxMCE which sell HW bundled with it, because they have the money and project management to move it along, market it to increase its popularity (which makes the community larger, which means more help and contributions).
I also think that the Orbiter code, which I've looked at (its messaging and network API, not its GUI), would be easier to upgrade if its UI were a discrete presentation layer, and not as integrated with the PPL code. The Pluto code remaining in LinuxMCE that I saw (in 0710) was written very badly, hard to trace or maintain.
Your name is Matthew isn't it?
-
Your name is Matthew isn't it?
+1
-
+1
-
Thank you for confirming the IP-numbers match Hari. I've got a nack for recognizing dumbass motherfuckers who are stupid enough to think nobody will notice when they start a new account under another name.
Just in case anyone is wondering, Matthew is a fucking clueless arsehole wasting everyone's time with his moronic bullshit. Meanwhile badmouthing us behind our backs on his shitty blog (which nobody reads anyway), piss off loser!