Re: Sessions usage paths

> anyway, i use sessions, so count me as one of the users you are looking
> for.  i can't say that it's a make or break feature for me, and i
> certainly wont stop using galeon if it disappears (i've been using it
> since the .6 days :)
> since it's buried in the File menu, i dont think it adds any unnecessary
> cruft or crack, and it doesnt, in my opinion, add any usability
> problems.  
> 

As someone pointed out in a bug it add quite a bit of cruft to menu File
(a menu where we could decide to add more stuff later, see Offline
mode). 

Saving the application state (or a list of documents, it depend on how
you look at it) to a file appear like an unnecessary exposure of
implementation details. 
You save a document, you dont save application state in a file. Yeah
that's what we actually does in the code, but I dont think it should be
exposed in the user interface.
A folder of bookmarks looks like a more appropriate representation of a
list of urls that you want to keep around to look later. It even allow
you to have more control over them (open only some of them ...).

Anyway thanks a lot for the feedback. It's exactly what I was asking
for. I'll keep thinking at this, I hope we can find a way to get the
same functionality in a less confusing and cleaner way.

Marco




-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD