haiku有意放弃beos兼容改投qt门下

[流浪风雨]

Evaluate Qt as a potential Haiku R2 API ¶
While in comparison with other frameworks the BeOS API was quite nice back in the day, save for a few additions (like layout management, an improved archiving mechanism, tool tips) very little has changed since.

Particularly the interface kit leaves a lot to be desired these days, both in general design and completeness.
The Qt toolkit on the other hand has evolved quite nicely over time and now presents a very complete and well designed API.
This project shall evaluate Qt as a potential native Haiku R2 API, replacing partially or even completely the previous BeOS/Haiku API.

Analyze the current state of the Qt port and add/complete what is missing/incomplete.
• Add extension in or on top of the Qt API to provide access to Haiku specific functionality (attributes, entry_refs, resources, translators, etc.)
As a proof of concept port an existing Haiku application (eg StyledEdit) over to the extended Qt API
不知这样做haiku还是haiku吗？至少beos爱好者不会乐意这么做。qt现在作为第三方平台已经另很多人不满了。。

[枫叶饭团]

- -，这是啥

[灰色小狼]

Qt招谁惹谁了

[qy117121]

Qt招谁惹谁了

[ReiFFEXzyx]

Qt招谁惹谁了

[陽光院景仁]

我覺得分支可以，但不應該掛著Haiku的名字背叛BeOS。因為Haiku這個名字就是模仿BeOS的發行代號來起的。

[photor]

Evaluate Qt as a potential Haiku R2 API ¶
While in comparison with other frameworks the BeOS API was quite nice back in the day, save for a few additions (like layout management, an improved archiving mechanism, tool tips) very little has changed since.

Particularly the interface kit leaves a lot to be desired these days, both in general design and completeness.
The Qt toolkit on the other hand has evolved quite nicely over time and now presents a very complete and well designed API.
This project shall evaluate Qt as a potential native Haiku R2 API, replacing partially or even completely the previous BeOS/Haiku API.

Analyze the current state of the Qt port and add/complete what is missing/incomplete.
• Add extension in or on top of the Qt API to provide access to Haiku specific functionality (attributes, entry_refs, resources, translators, etc.)
As a proof of concept port an existing Haiku application (eg StyledEdit) over to the extended Qt API
不知这样做haiku还是haiku吗？至少beos爱好者不会乐意这么做。qt现在作为第三方平台已经另很多人不满了。。

还是用enlightenment foundation library吧，轻巧又漂亮，qt太笨重了，老机吃不消的

[sqbing]

看了haiku的wiki页面，还是不明白这个操作系统和基于linux内核的系统的区别，请高人指教，如果可以，请从个人用户而非开发者角度展开解释。

[流浪风雨]

Evaluate Qt as a potential Haiku R2 API ¶
While in comparison with other frameworks the BeOS API was quite nice back in the day, save for a few additions (like layout management, an improved archiving mechanism, tool tips) very little has changed since.

Particularly the interface kit leaves a lot to be desired these days, both in general design and completeness.
The Qt toolkit on the other hand has evolved quite nicely over time and now presents a very complete and well designed API.
This project shall evaluate Qt as a potential native Haiku R2 API, replacing partially or even completely the previous BeOS/Haiku API.

Analyze the current state of the Qt port and add/complete what is missing/incomplete.
• Add extension in or on top of the Qt API to provide access to Haiku specific functionality (attributes, entry_refs, resources, translators, etc.)
As a proof of concept port an existing Haiku application (eg StyledEdit) over to the extended Qt API
不知这样做haiku还是haiku吗？至少beos爱好者不会乐意这么做。qt现在作为第三方平台已经另很多人不满了。。

还是用enlightenment foundation library吧，轻巧又漂亮，qt太笨重了，老机吃不消的

用qt也未必用kde，桌面大概还是他们自己开发。。

[流浪风雨]

看了haiku的wiki页面，还是不明白这个操作系统和基于linux内核的系统的区别，请高人指教，如果可以，请从个人用户而非开发者角度展开解释。

大概就是统一轻快桌面内核二合一只有一个桌面没有其他选择，内核只针对个人用户开发而非基于服务器。。。应用软件看不到区别，看图形界面和
别的系统没啥区别。。

[photor]

Evaluate Qt as a potential Haiku R2 API ¶
While in comparison with other frameworks the BeOS API was quite nice back in the day, save for a few additions (like layout management, an improved archiving mechanism, tool tips) very little has changed since.

Particularly the interface kit leaves a lot to be desired these days, both in general design and completeness.
The Qt toolkit on the other hand has evolved quite nicely over time and now presents a very complete and well designed API.
This project shall evaluate Qt as a potential native Haiku R2 API, replacing partially or even completely the previous BeOS/Haiku API.

Analyze the current state of the Qt port and add/complete what is missing/incomplete.
• Add extension in or on top of the Qt API to provide access to Haiku specific functionality (attributes, entry_refs, resources, translators, etc.)
As a proof of concept port an existing Haiku application (eg StyledEdit) over to the extended Qt API
不知这样做haiku还是haiku吗？至少beos爱好者不会乐意这么做。qt现在作为第三方平台已经另很多人不满了。。

还是用enlightenment foundation library吧，轻巧又漂亮，qt太笨重了，老机吃不消的

用qt也未必用kde，桌面大概还是他们自己开发。。

我说的就是qt对于老机已经笨重了，还没有说kde

[流浪风雨]

Evaluate Qt as a potential Haiku R2 API ¶
While in comparison with other frameworks the BeOS API was quite nice back in the day, save for a few additions (like layout management, an improved archiving mechanism, tool tips) very little has changed since.

Particularly the interface kit leaves a lot to be desired these days, both in general design and completeness.
The Qt toolkit on the other hand has evolved quite nicely over time and now presents a very complete and well designed API.
This project shall evaluate Qt as a potential native Haiku R2 API, replacing partially or even completely the previous BeOS/Haiku API.

Analyze the current state of the Qt port and add/complete what is missing/incomplete.
• Add extension in or on top of the Qt API to provide access to Haiku specific functionality (attributes, entry_refs, resources, translators, etc.)
As a proof of concept port an existing Haiku application (eg StyledEdit) over to the extended Qt API
不知这样做haiku还是haiku吗？至少beos爱好者不会乐意这么做。qt现在作为第三方平台已经另很多人不满了。。

还是用enlightenment foundation library吧，轻巧又漂亮，qt太笨重了，老机吃不消的

用qt也未必用kde，桌面大概还是他们自己开发。。

我说的就是qt对于老机已经笨重了，还没有说kde

老机用Haiku R1就好了，Haiku R2 是给新机器用的估计是几年后的事了。