Bernd Korz, yellowTAB's CEO, was over here tonight and we had a little talk about the progress of the yellowTAB business and the upcoming Zeta 1.0 (screenshots included).
Permalink for comment
To read all comments associated with this story, please click here.
Do you mean make Zeta/BeOS open source? That's not going to happen! At least, not with anything (for certain) that yT didn't put in there, whether they wrote it themselves or grabbed it from Haiku, as they can't.
As to Haiku, it's under the MIT/BSD license, and I'm not sure what licenses GTK/QT require of the underlying system.
Besides, unless GTK and QT have a separate thread per window as BeOS does in all cases, porting them will be a real pain, and will be a bastard solution at best. Chances are, a lot of applications that use GTK/QT aren't pure users of only those frameworks: probably a lot of them use system-specific calls that make porting those applications rather interesting anyway, so it's most likely easier to just write a native application, assuming you've got the GUI logic properly abstracted from the engine.
Do you mean make Zeta/BeOS open source? That's not going to happen! At least, not with anything (for certain) that yT didn't put in there, whether they wrote it themselves or grabbed it from Haiku, as they can't.
As to Haiku, it's under the MIT/BSD license, and I'm not sure what licenses GTK/QT require of the underlying system.
Besides, unless GTK and QT have a separate thread per window as BeOS does in all cases, porting them will be a real pain, and will be a bastard solution at best. Chances are, a lot of applications that use GTK/QT aren't pure users of only those frameworks: probably a lot of them use system-specific calls that make porting those applications rather interesting anyway, so it's most likely easier to just write a native application, assuming you've got the GUI logic properly abstracted from the engine.