[openbeos] Re: Konqueror update (plus radical proposal)
- From: "Yuri Titov" <yurititov@xxxxxxxxxx>
- To: <openbeos@xxxxxxxxxxxxx>
- Date: Sun, 2 Sep 2001 07:09:24 -0500
it is a good idea, but thats one of the things that would be done a little
later on. The only bad thing about qt is that it wasnt meant to be
multithreaded like the app kit. I'm sure that could be overcome though.
Not a big deal. As a programmer though, i love the app kit. If we port QT
then people might start making programs (for x-platform mobility) using only
QT and not the app kit.
if someone would start porting qt though, a big question would be. do you
build it on top of app kit? reason I ask is if helmar gets that license,
then it would mean a port for beos (as long as it is build with app kit in
mind). The testing would be easier too :)
-yt
----- Original Message -----
From: "Zenja Solaja" <zenja@xxxxxxxxxxxxxxxx>
To: "OpenBeOS" <openbeos@xxxxxxxxxxxxx>
Sent: Sunday, September 02, 2001 4:11 PM
Subject: [openbeos] Konqueror update (plus radical proposal)
>
> Hi everyone. Just a quick note that I've uploaded BeBits with a weely
> snapshot of konqueror-embedded (http://www.bebits.com/app/2422). There
> is also a touchy screenshot at: http://members.optushome.com.au/beoz/
> konqueror.jpg.
>
> Having said that, I'm about to start a 'dangerous' thread on this list.
> I'm pretty sure that it will flush out some of the lurkers on this
> list, and may even entice Helmar to start posting again :-)
>
> Here is my proposal - OpenBeOS urgently tackles the port of native Qt
> (without X11) to BeOS. A native port of Qt-2.3.1 will open the
> floodgates of hundreds of KDE applications, including a more functional
> Konqueror, a port of KOffice (and its components) and countless other
> apps. This is a perfect project to mould the OpenBeOS group (emphasis
> on MOULD). The Interface Kit group can gain experience porting a
> foreign display API to BeOS, and the networking team can also gain
> valuable experience with refining the Konqueror port.
>
> I can think of hundreds of reasons why OpenBeOS should tackle this
> project, and only one reason why it shouldn't. As I've previously
> stated, this project will help MOULD the OpenBeOS group, and everyone
> will benefit from the experience (developers and whats left of the
> community).
>
> I apologise for infecting the list with my sinister motives.
>
Other related posts:
