[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: File not read completely when opening?
From:       Hamish Rodda <meddie () yoyo ! its ! monash ! edu ! au>
Date:       2003-02-16 3:53:08
[Download RAW message or body]

Christoph Cullmann wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sunday 09 February 2003 12:52, Hamish Rodda wrote:
>> Andras Mantia wrote:
>> > Andras Mantia wrote:
>> >
>> > ...
>> >
>> >> According to the ReadOnlyPart code the signal is emited when the
>> >> openFile() returns. So if openFile() wait until the whole file is
>> >> read, then everything's fine. But in case we don't even need the
>> >> completed(), as we can just wait for openURL() to return.
>> >
>> > ...
>> >
>> > The ReadOnlyPart::openURL() documentation says:
>> >
>> > "Only reimplement openURL if you don't want synchronous network
>> > transparency Otherwise, reimplement openFile() only ."
>> >
>> > And later for openFile():
>> >
>> > "If the part uses the standard implementation of openURL(), it must
>> > reimplement this, to open m_file. Otherwise simply define it to {
>> > return false; } "
>> >
>> > Kate uses the standard openURL() implementation, and reimplements
>> > openFile(). According to the above, in this case the opening should be
>> > done in a synchronous way.
> I thought the syncronoous would be for the network transparent part of it,
> which means: openURL defaults to use the syncronous downloading before it
> calls openFile for remote files, that says nothing about the whole
> openFile implementation. But in the part.cpp implementation of openURL it
> seems they
> want that openFile is syncrounous, too,  too bad. Perhaps kate should
> overwrite the standard openURL implementation with one that only emtis
> completed() after the stuff has really enended in the buffer. That would
> still allow to handle the stuff asyncronous per default but let the apps
> connect to the completed thingy.

So, where are we with this? Any volunteers, or can you explain what should
be done...

Cheers,
Hamish.
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]