Re: io-slave design-problem

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: io-slave design-problem
by Philipp on Thursday 12/Apr/2007, @05:54

>Yes, it needs kernel support from BSD, Solaris, HP-UX, Linux and Win32.
If this would really be the case, then KDE would not be at all possible on these platforms.
If you can do it within KDE, then you can do it seperately as well.

Related Links

·   Articles on KDE Public Relations and Marketing
·   Also by Philipp
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: io-slave design-problem
by ac on Thursday 12/Apr/2007, @08:16

what?

its possible in kde on all platforms because kde is programmed to do it on all platforms. sure, you can do this with every application, but that means you need to change the code. thats the problem - you just can't change the code of all applications for half a dozen platforms...

so if you want something like kio that works with all applications, you need kernel support.

[ Reply To This | View ]

Re: io-slave design-problem
by Philipp on Friday 13/Apr/2007, @00:07

Kernelsupport? Nonsense. This is mostly pure userspace.

For sure some support is in the kernel, as some basic network- and filesupport is there for other reasons, but why on earth needs a kernel knowledge about IMAP or EXIF?
The kernel doesn't need to know all these different things.

What you want is a functionality available on Linux platforms and this can be done with a library as well.
You are worried it cannot be used in the bash? For sure bash needs then to be adjusted as well.

Yes, we can't change the code of all applications on all platforms. But if you keep it in KDE alone and in Gnome alone and in other Apps, it for sure will never happen.

[ Reply To This | View ]

Re: io-slave design-problem
by ac on Friday 13/Apr/2007, @13:33

you should read the whole of the thread...

just putting ioslaves into another library will not do anything. noone is going to rewrite their software just because some geeks like to really use networks and such.

the only way to make ioslaves fully work for non-kde software now (not in 10 years...) is to use kernel extensions. not because the kernel needs to know about imap or whatever, but because its the only common api for filesystems access every application uses. thats what fuse is about, to make things like that easier.

rewriting the ioslaves in pure c, with a minimum of depedencies - so that maybe someone else would use it, is not a good idea. the kde devs allready have enough work ahead. and you still won't get less-over-http anytime soon, because these apps arn't maintained anyway.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"I'm holding out for a computer interface that plugs directly into my cerebral cortex." -- Sirtaj Singh Kang
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.