Re: Re: Feature request !

On 8/25/05, Vlaaad <[email protected]> wrote:
> Le jeudi 25 août 2005 à 18:42 +0200, Michael Mauch a écrit :
> > Daniel Westermann-Clark wrote:
> >
> > > On 2005-08-24 19:05:20 +0200, Vlaaad wrote:
> > > > I know that I'm very stupid to close the window whereas I don't want
> > > > it, but sometimes, that happens... :=) And this is often very
> > > > annoying.
> > >
> > > Galeon has an option to save your session, so you shouldn't lose any
> > > tabs if you accidentally close it.
> >
> > But it doesn't work if you use your window manager's close button (or
> > e.g. Alt-F4 in KDE), only with Ctrl-q.
> >
> > Regards...
> >               Michael
> >
> Well, I know that there is an option to save the session but this
> doesn't work in all cases, afaik. Example (I just tried) :
> - Open three differents galeon windows
> - Open several tabs in all windows
> - Close one window with the close button of the window title bar
> - Close galeon with "quit" in file menu or CTRL+Q
> - Reopen galeon, you will have only two windows restored

Juste two remarks about loading sessions (note that I use tens of tabs)
 - When starting galeon, I get "time out" windows. Why are they modal?
What I mean is ok, the related tab cannot be loaded, but why the whole
galeon should be stopped for that ??? (Same with : form & password
choice for a page)
 - Loading lots of tabs is long, and I do not watch them at any
session. I guess others do the same : bookmarks make us forget pages
that become obsoletes (press articles for example) or technical
references (API ...) we may use soon. So, here is my suggestion : why
not implementing a lazy loading of pages?
session_(saved|crashed).xml contains url and title of each page. So it
is possible to create all session's tabs at the galeon opening but
without actually loading them, only setting them their title. Then
when a tab becomes visible, galeon loads it, setting a "loaded flag"
at true. I think it has several advantages :
       - it is quite invisible for the user. 
       - it is faster (only one tab per window is open at the beginning)
       - it uses less memory (not all tabs will be loaded at every session)
       - it avoids problem #1 (modal windows)
  I have tried to implement it, but I have to admit I am not very
familiar with the event based programming of galeon (I had some
problems like pages  reloading infinitely)
So if nobody can do that, I'll try to post a patch a patch but not
immediately (I have higher priority tasks to accomplish before).

regards.
Youp


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf