Most of HTML 4.0 is done. The JavaScript interpreter is there, but not all the DOM bindings are finshed. Java support is there (and is also available via the Java plugin). SSL is there. CSS 1 support is good, CSS2 is incomplete. Netscape plugin support is in.
Download it and try - I don't think you can call it vapourware when it's there for you to test. Pity you didn't do this before posting...
It is not possible to do this currently, but Troll Tech are developing a system called Qt/Embedded. There is quite a bit of interest in porting KDE to it, so it will probably happen it's just a question of when.
I checked out the stats for some apps I've written and I found they are way out. For example the analysis of kgui gives me 52.789% of the code despite the fact I am the sole author!
In general the handling of large packages such as KDE seem fairly poor. For example KDE apparantly has no authors according to the by-project listing. I think this is a great idea, but it needs a cleaner source of data, for example Coolo has been able to give some very interesting and detailed figures by running scripts on the KDE CVS repository. Perhaps this is the sort of thing they need to be using as the initial data set from which they make their analysis.
I posted a story here a few days back with a link to a rebuttal of the original article. Pity you didn't post the link Hemos! Anyway here it is again http://apps.cx/motifisdead.html
If I remember correctly, Tarantella is very similar to a GPL'd program released by ORL called VNC (http://www.orl.com/vnc). I would be interested to hear what makes Tarantella better in your opinion, that makes it worth buying rather than using the free alternative.
This will be easy when the KDE 2 version of KDevelop is released because it will use the KParts object framework. You will be able to embed anything that can be used as a part.
In fact if you want to embed emacs etc. you can already do it using the tools menu, but you lose lots of nice features such as the ability to navigate your code using the class viewer.
IIRC Tarantella is based on VNC, you can find out more about the technical details of VNC on the UK AT&T website. The basic idea is to use a very simple protocol with most of the work done at the server end allowing the clients to be very simple. For example I have seen pictures of KDE running on someones cell phone using VNC.
The overhead is actually pretty low - the themes are loaded and unloaded as needed. By default themes aren't used, so you have your lean mean system. Even when they are enabled the overhead of the non-pixmap themes is reasonable - the pixmap themes have a bigger overhead, but there is nothing that can be done about this.
Translation: 'We're making it look better, because we already think it works as well as it could. The Windows paradigm is good enough, no sense coming up with new ideas.'
That is not what I said, and is not even close to what I think. What you are totally missing is that people have to learn a new GUI paradigm. KDE is about getting things done now, and that is best handled through incremental changes.
That said however, because of the modular design of KDE it is perfectly possible for people to develop new paradigms within KDE. You could write a KWin module that implemented a 3D window manager if you wanted, but only a small number of people would use it. When 3D hardware is everywhere an extension like this could be incorperated into the default desktop, but not before. This is a much more practical way to advance the desktop IMHO
Download it and try - I don't think you can call it vapourware when it's there for you to test. Pity you didn't do this before posting...
It is not possible to do this currently, but Troll Tech are developing a system called Qt/Embedded. There is quite a bit of interest in porting KDE to it, so it will probably happen it's just a question of when.
In general the handling of large packages such as KDE seem fairly poor. For example KDE apparantly has no authors according to the by-project listing. I think this is a great idea, but it needs a cleaner source of data, for example Coolo has been able to give some very interesting and detailed figures by running scripts on the KDE CVS repository. Perhaps this is the sort of thing they need to be using as the initial data set from which they make their analysis.
Rich.
I posted a story here a few days back with a link
to a rebuttal of the original article. Pity you didn't post the link Hemos! Anyway here it is
again http://apps.cx/motifisdead.html
Hi David,
If I remember correctly, Tarantella is very similar to a GPL'd program released by ORL called VNC (http://www.orl.com/vnc). I would be interested to hear what makes Tarantella better in your opinion, that makes it worth buying rather than using the free alternative.
Thanks
Rich.
In fact if you want to embed emacs etc. you can already do it using the tools menu, but you lose lots of nice features such as the ability to navigate your code using the class viewer.
IIRC Tarantella is based on VNC, you can find out more about the technical details of VNC on the UK AT&T website. The basic idea is to use a very simple protocol with most of the work done at the server end allowing the clients to be very simple. For example I have seen pictures of KDE running on someones cell phone using VNC.
The overhead is actually pretty low - the themes are loaded and unloaded as needed. By default themes aren't used, so you have your lean mean system. Even when they are enabled the overhead of the non-pixmap themes is reasonable - the pixmap themes have a bigger overhead, but there is nothing that can be done about this.
That is not what I said, and is not even close to what I think. What you are totally missing is that people have to learn a new GUI paradigm. KDE is about getting things done now, and that is best handled through incremental changes.
That said however, because of the modular design of KDE it is perfectly possible for people to develop new paradigms within KDE. You could write a KWin module that implemented a 3D window manager if you wanted, but only a small number of people would use it. When 3D hardware is everywhere an extension like this could be incorperated into the default desktop, but not before. This is a much more practical way to advance the desktop IMHO