faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: kio-gio bridge
by Kevin Krammer on Tuesday 22/Jan/2008, @15:53
|
> First of all, there is no reason to rewrite anything.
I think he didn't mean to use the word "rewrite", i.e. replacing an existing implementation with a new one, I am quite certain he meant "from ground up", i.e. starting to implement a second stack starting at the wire level.
> And GIO is "Desktop independent"?
Again I think this is just unfortunate wording. In this context it more likely means "not linking against any GUI library", e.g. an implementation just linking with QtCore would also be "Desktop independent". |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: kio-gio bridge
by Norbert on Tuesday 22/Jan/2008, @17:27
|
>> First of all, there is no reason to rewrite anything.
>
> I think he didn't mean to use the word "rewrite", i.e. replacing an existing
> implementation with a new one, I am quite certain he meant "from ground up",
> i.e. starting to implement a second stack starting at the wire level.
Yes, thats right.
> And GIO is "Desktop independent"?
>
> Again I think this is just unfortunate wording. In this context it more likely
> means "not linking against any GUI library", e.g. an implementation just linking
> with QtCore would also be "Desktop independent".
Yes, exactly. It's not possible use KIO and it's protocol handlers without installing and running some KDE specific stuff at the moment. Perhaps that's all more on the edges of KIO, but it makes it less attractive for using it cross desktop.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|