Re: SeaMonkey 2.42.9

[email protected] Sun, 18 Jun 2017 09:22:06 -0700 (PDT)
Newsgroups gmane.comp.mozilla.devel.os2
Message-ID <[email protected]>
On Thursday, 15 June 2017 00:18:16 UTC-5, Steve Wendt  wrote:
> On 06/14/2017 08:22 PM, [email protected] wrote:
> 
> > hard coded to be \\unixroot\* (etc/usr/var) in the SeaMonkey drive.  > This is not well documented, and the fora have much confusion
> 
> If you have a suggestion for how best to describe this in the 
> mozsupport.txt file, I'm open to it.  The simple answer is to unzip it 

Thanks Steve for your commendable efforts to make
this installation easier and possible.  The problem
from my perspective, is that there are many actual and
potential complexities which easily confuse and trip an
inexperienced user.  With multiple versions released
with many configuration, library and installation
changes, the task to successfully try new versions is
daunting, time consuming, and usually unsuccessful.

You made a huge improvement with the two new moz*
packages, and they were instrumental with me getting a
viable browser.  My suggestion is that each package
release includes all the requisite files and libraries,
and with default configuration files if required, so
all that is required from the user is to unzip the
package and run it.  If desired, the whole folder could
subsequently be discarded if desired or upgraded.

> to the root of the drive that has SeaMonkey, but it's not hard-coded to 
> that if you have %UNIXROOT% etc. configured.

I unsuccessfully tried several options using
different environment variables from within the
SeaMonkey directory.  Possibly, a hard coded
environment is required from within CONFIG.SYS?

Ultimately, I copied the directory tree from
"@unixroot" to several locations and names (unixroot,
@unixroot, %unixroot%), and "@unixroot\*" on the
applications drive succeeded.
 
> > A) There was a insta-crash accessing the "Download" menu.
> 
> Try removing downloads.(rdf|sqlite) from your profile, and see if that 
> helps.

The download still functions as configured, but just 
accessing the menu item crashes only 42.9.

> > B) There was a insta-crash on the OpenSteetMap edit page the instant
> > the mouse was moved.
> 
> Did you get a *.trp crash log?

No, I never.

> > C) There was a insta-crash accessing video.
> 
> What kind of video?

All the videos on this page:

https://www.theguardian.com/world

Embedded videos still seem to work.
 
> > D) The stability is still not prime time.
> 
> Nope.
> 
> > I also would like to change the default browser and display fonts to
> > bigger sans-serif, but was unsuccessful.
> 
> Using the preferences UI, or userChrome.css?  You may want to describe 
> in more detail what you are trying.

This is interesting, as I had previously thought that 
the newer browsers required TTF, and that was a big 
reason they wouldn't work, as my franken
system uses Adobe PostScript, and I cannot add TTF.

I finally was able to go to the SeaMonkey font settings 
page, and successfully configure all the fonts as
PostScript, and on restarting SeaMonkey, all the
application fonts also changed.

Note that there are never any complaints on font
quality, anti-aliasing, etc. from me.  {:-)
 
thanks,
Baden