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

List:       kde-devel
Subject:    Re: KGet imported to the CVS
From:       David Faure <David.Faure () insa-lyon ! fr>
Date:       1999-02-13 20:08:52
[Download RAW message or body]

On Sat, Feb 13, 1999 at 01:47:26PM -0500, Dawit Alemayehu wrote:
> Matt Koss wrote:
> 
> > [snipped]
> >  Offtopic : I miss the posibility to save the image from the html page displayed
> >      by kfm as well as the source text of this page.
> >      Of course that this has to be done by using cache. Today,  when I
> >      choose View source, kfm starts to get this file again, which is non-sense.
> >      My desire is to do it like in Netscape - right click on image offers Save
> >      Image and in the main menu there are Save source / Save frame /
> >      Save frameset  items.
> >
> > Comments ?
> 
> There was a conversation about the inability to save pages in KFMII.  The reason
> was that the feature was not implemented in time before the feature freeze date.
> David also mentioned at the time that we could not use KFileDialog to save pages
> because it caused SEGV in kfm.
This is not true anymore, thanks to Carsten Pfeiffer. Check out the current 
kfm from CVS : it now uses KFileDialog in the properties pages (for
directories and executables).

>  This feature is a must for many folks and I am sure
> will be implemented in the next version.  If you want a work around right now, you
> can do what you did ( View document source ) or alternatively right click on the
> link, click on "copy" and paste it to any folder you want ( I know this is too much
> work, but hey ... ).  You are right about kfm requesting the document again when
> trying to view the document source. This also has to be fixed.
Sure.

> Regarding the saving of images, I would even take it one step further.  When a user
> asks to save, there should be an option box on the "Save" dialog that allows to
> user to pull all the images from this web page as well.  I have spoken to many
> users and this is actually what they expect when they save the page ( save
> everything they see ...)  One possible obstacle for this feature is that many
> images on web pages are linked with a relative path.  So saving them would either
> require creating the relative paths or modifying the html <IMG SRC= ...> info to
> reflect the new address.  Maybe this is too much, but I think it is worth
> investigating.
This is exactly what kget does already. Hence the discussion about adding a 
"copy (kget)" - or something clearer - so that copying gets the images too.
But you're right, saving the page should allow to do that too.

Anyway, the point is that AFAIK kget already deals with the problem of
absolute/relative path to embedded images.

-- 
 ____________________________________________________________________
|                                                                    |
|  David FAURE                                                       |
|  E-mail : David.Faure@insa-lyon.fr, faure@kde.org                  |
|  http://www.insa-lyon.fr/People/AEDI/dfaure/index.html             |
|____________________________________________________________________|

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