Re: Updated wishlist items

On Wed, 2005-02-16 at 19:34 -0800, Karsten M. Self wrote:

>     - Toggling off full-screen option.  State loss / Controls: F11 is a
>       reserved keybinding in WindowMaker.  There should be a control,
>       hotkey, escape key, or other option.  In 1.2.x, menu hotkeys
>       worked even when the menubar wasn't visible in fullscreen view.
>       In 1.3.x, they don't.  So:  <alt>-V-U (view => fUll screen) would
>       escape fullscreen mode in 1.2.  This should be restored.  Only
>       current option appears to be killing the entire browser session.
>
This works fine for me.

>Menus
>-----
>
>    Enable detachable menus.
>
As AdamH pointed out this is easily enabled.

>Confirmations
>-------------
>
>    Allow specification for close confirmation.
>
>    Rationale:  it's too easy to close a browser session by
>    inadvertantly hitting a window's close control, or by miskeying C-q
>    for C-w.  This can result in significant loss of session state,
>    particularly as browser sessions are not saved by default and
>    cannot be saved conditionally.  My own pref would be to have this
>    confirmation *on* by default, with a "don't ask me again" option.
>
We have though about this before, but one thing I can't stand about some
browsers is them poping up "are you sure you want to close this window"
alerts. We warn when the user will lose data they have typed in
(although this isn't perfect). Having "Don't ask me again" options
aren't very good either, as you then need a UI somewhere else to turn on
the dialog again.


>Tabbed Browsing
>---------------
>
>  - Navigation.  Allow scrolling of tabslist *without* changing current
>    tab focus.  
This is GtkNotebook behaviour


>Allow context-action (e.g.: right click)  on tab
>    *without* changing current tab focus.  
>
In other parts of a Gtk UI, when you right click on an item it gets
selected, this is the behaviour we are following, and this was a
conscious decision .

>  - Tab submenu.  Provide tablist on tab context menu.
>
A context menu is supposed to act on the object, that's why it is called
a 'context' menu. I never thought the tablist fitted when we did have
it, it changes the current view, so really shouldn't be on the context
menu.


>MIME types / Open With
>----------------------
>
>  - If MIME types are going to be managed within GNOME, *DO* provide
>    access to the GNOME MIME type editor from within Galeon.  Similar to
>    the proxy configuration tool.
>
There is no Gnome MIME editor at the moment, I'm not saying I like that
situation (because I don't).

>Bookmarks
>---------
>
>  - Restore sub-portal feature of My Portal.
>
>    <strike>Severity:  2.</strike>
>    Completed.
>
>
>  - Provide a bookmarks search capability.  A keyword/filter similar to
>    how the about:config window or history window would be useful.

Huh, what about the Find box in the bookmark editor ?

>Cookies
>-------
>
>  - Current cookie management (Remove / Remove and block) 
>    Controls, Privacy.  Is _painfully_ slow.  I'm seeing a minute or
>    more to delete a single cookie.  Any reason for this?  Makes
>    operations pretty much infeasible.  Improve performance.

I don't know why it takes a while, perhaps someone would care to do some
research.

>
>  - There's also the question of where cookie dialogs should appear.  My
>    suggestion is that a separate popup window should be replaced with a
>    dialog bar across the requesting webpage or tab.  
>    Controls.
>
You need to have a popup, as the page load _has_ to block until the user
has decided what to do with the cookie (Imagine a site that sets a
cookie on the main page, then expects it to be there when loading
images).

>  - If the cookie dialog is cancelled, the cookie is discarded.  If the
>    dialog is accepted, the cookie is retained as the
>    user prefers:  session or persistant.
>    Avoid Repeating.

I don't understand what you mean here, we have options in the cookie
dialog for remembering the option.
   
>Passwords
>---------
>
>    Performance is as with cookies:  painfully slow.  Improve.
>    Controls, Privacy.
Again, if anyone can research this we would be grateful.

>    Ability to search for specific sites / users (e.g.:  history search)
>    would be useful.  I need to weed out some dupe entries.
You can search for passwords...


>Advanced features.
>------------------------------------------------------------------------
>
>The following features are advanced and/or somewhat undefined, but
>should be kept in mind in looking at future Galeon development.
>
>
>
>RSS
>---
>
>   Galeon largely lacks RSS features.  I'm not entirely sure what we
>   want to see here, but it's a topic which should be on the table.

There are certainly more important things to do before implementing RSS
feeds.


>
>Google
>------
>
>   Google is becoming one of the major factors in pushing web features,
>   with its smart search, gmail, maps, and other features, and is become
>   a de facto establisher of standards.  Making Galeon compatible with
>   the tricks Google is shoving down browser-designer's throats is going
>   to be an increasing concern.
>
Do you have any particular problems with galeon and google ? or are you
just spreading FUD ?


>Firefox Extensions
>------------------
>
>    Firefox's extensions are useful.  Documenting how to use same,
>    and/or providing ability to use same, and/or providing a similar
>    extensions interface into Galeon would be a major win.

There is no way that most FF extensions can (or ever will work). I have
toyed with adding an interface similar to Ephy's extensions interface to
galeon, but time is always lacking ....


Although there are some good ideas here, most are just pipe-dreams
unless the number of active galeon developers increases.

Actually in the long-term I would like to see Epiphany and Galeon
merging back together. Epiphany has (IMO) been slated as not providing
lots of features, and it is true that it doesn't provide as many as
Galeon, however it does have:

 - An extension interface (with python bindings, and the start of mono
bindings)
 - More active development (chpe is just amazing).

Of course, there are things in Epiphany that I don't like, and I'm
hoping that in the next Ephy release cycle I can sit down with chpe and
work out how best to add hooks for extensions to alter things. I would
love to see a 'Galeon' extension to epiphany to bring back all the
things galeon provides.

The above doesn't mean I'm going to stop developing galeon, but I
haven't been quite as active recently due to various other 'life'
distractions.

Crispin







-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click