Re: Changes in galeon 1.3 over mozilla compiled with gtk2

Lindsay Haisley <[email protected]> Sat, 11 Oct 2003 13:50:37 -0500
Newsgroups gmane.comp.web.galeon.devel
Organization FMP Computer Services
Message-ID <[email protected]>
Thus spake Crispin Flowerday on Sat, Oct 11, 2003 at 12:39:23PM CDT
> Hi,
> 
> > *  The "Clear location" toolbar widgit/button is gone. 
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=110350

OK, cool.  Someone has filed a formal bug on this.  I'll simply raise my
hand and vote "yes" on restoring this feature.
 
> 
> > *  The "Find entry" toolbar widgit/button is also gone, another small but
> >    one of my favorite galeon convenience features.  Several more mouse
> >    clicks in different places are now required to find text in a page.
> 
> Doesn't mozilla's type-ahead-find (or whatever it is called) solve this
> problem? Just press '/' and start searching when the focus is in the web
> page.
> 
> If that doesn't solve your needs, you probably want to file an
> enhancement request in bugzilla.

Thanks!  This is apparently new in the lastest versions of mozilla, so I
didn't know about it.  It isn't in galeon 1.2.5 (Debian testing) which I'm
using on my other desktop box.  It pretty much solves the problem, and
requires fewer keystrokes than using the find box, although it looks as if
the ability to switch case-sensitive searches on and off is missing -
sometimes useful when looking for acronyms.  I can live with that.

> 
> > *  Text entry fields in smart bookmarks aren't persistent and the fields 
> >    are cleared on each use cycle.  I much preferred them to retain text so
> >    that, for instance, I could use the google smart bookmark, to perform a
> >    series of related look-ups, even if I were browsing a referenced page
> >    rather than at a google results page.
> 
> You could use the smart bookmark history, IIRC we couldn't think of a
> decent use-case for preserving the text, although tko may remember why
> exactly it didn't get back in.

The "Enable smart bookkmarks history" checkbox is available in the galeon
1.2 general preferences dialog, where there's a dialog page on general
bookmark preferences.  I can't find any comprable page in the galeon 1.3.9
preferences dialog set, nor is such an option available on a per-bookmark
basis in the Bookmarks Editor or Bookmarks Properties dialogs.

My example above is probably the best one in my experience.  If I'm googling
using more than a word or two as my search expression and I'm several links
away from my search results page and decide that I'm coming up with nada,
but based on what I've seen a small tweak to my search expression would be
more productive, it's very nice to be able to make the change and re-query
on google (or wherever) without having to lean on the back button to get
back to my results page and edit the contents google search text box.  I use
this feature _a lot_.

> > *  I note that favicon.ico reading is strange.  I guess there's no
> >    'standard' on this, however I believe SOP is for a browser which supports
> >    them to request favicon.ico in the document root even if a URL is a 
> >    request for a page in a subdirectory.  galeon 1.2 worked as expected
> >    in this regard, however galeon 1.3 won't fetch favicon.ico from the 
> >    document root if the URL is a request for a page in a subdirectory.
> >    Galeon 1.3 (or possibly it's in the gekko rendering engine) also 
> >    appears considerably lest robust in handling the various favicon.ico 
> >    multiple image formats which galeon 1.2 handled OK.
> 
> Galeon will use favicons that are setup using the <link rel=...> stuff
> that sites such as http://www.gnomedesktop.com/ uses. If you can find a
> favicon image that isn't used properly, then you need to file a bug.

OK, I'll look at it further.  I think Microsoft defined what "used properly"
means in this regard, so all bets are off ;-) Is there a published standard
for this that you or anyone else knows of?
 
> > In general, I've seen a lot of applications which seem to have lost lots of
> > bits and pieces of functionality in the move from gtk1.2 to gtk2.  Is this
> > because of the need for radical rewriting of code in the apps, because these
> > features are difficult to support in gtk2, or what?  Is this situation
> > expected to improve so that we can expect refinements lost in the migration
> > to be restored at some point?
> 
> Galeon 1.3 is an almost complete re-write of galeon 1.2, so features are
> added, rather than there being a decision to remove them. Most
> applications try and follow the HIG, which likes applications to be
> simple with sensible defaults.

Sometimes it seems that simplicity has taken precedence over functionality. 
I can handle complexity if it's done with smarts.  Galeon 1.2 is pretty
complex, but everything makes extremely good sense, so it's no problem.

-- 
Lindsay Haisley       | "Everything works    |     PGP public key
FMP Computer Services |       if you let it" |      available at
512-259-1190          |    (The Roadie)      | <http://www.fmp.com/pubkeys>
http://www.fmp.com    |                      |


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php