Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-21 Thread Ant

On 6/20/2011 5:52 PM PT, Paul Bergsagel typed:


Check and see if NoSquint is available for 2.1


I'm using NoSquint with 2.1 and it works perfectly.


Are you using 
http://downloads.mozdev.org/xsidebar/mods/nosquint-1.93.2.1-mod.xpi from 
http://xsidebar.mozdev.org/modifiedmisc.html, or a different one?

--
Captain Marvel: Shazam. Billy Batson: Now put her down. Black Adam: See? 
Like an ant. --Superman/Shazam!: The Return of Black Adam

   /\___/\   Ant @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-21 Thread Paul Bergsagel

Ant wrote:

On 6/20/2011 5:52 PM PT, Paul Bergsagel typed:


Check and see if NoSquint is available for 2.1


I'm using NoSquint with 2.1 and it works perfectly.


Are you using
http://downloads.mozdev.org/xsidebar/mods/nosquint-1.93.2.1-mod.xpi from
http://xsidebar.mozdev.org/modifiedmisc.html, or a different one?


I am using NoSquint 1.93.2.1.  this is the one from Mozdev.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-21 Thread Ant

On 6/21/2011 6:12 PM PT, Paul Bergsagel typed:


Check and see if NoSquint is available for 2.1


I'm using NoSquint with 2.1 and it works perfectly.


Are you using
http://downloads.mozdev.org/xsidebar/mods/nosquint-1.93.2.1-mod.xpi from
http://xsidebar.mozdev.org/modifiedmisc.html, or a different one?


I am using NoSquint 1.93.2.1. this is the one from Mozdev.


Thanks. :)
--
You feel the faint grit of ants beneath your shoes, but keep on walking 
because in this world you have to decide what you're willing to kill. 
--Tony Hoagland from Candlelight

   /\___/\   Ant @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( ) If e-mailing, then axe ANT from its address if needed.
Ant is currently not listening to any songs on this computer.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-20 Thread cyberzen

Ed Mullen a écrit :

PhillipJones wrote:

Sridhar Ayengar wrote:


Hi. I just upgraded to Seamonkey 2.1, and I have to say, the experience
has been largely painless, and while Seamonkey 2.0.12 used to peg one
core of my CPU at 100% for hours at a time, and 2.1 doesn't. Kudos.

However, there are two things I'm finding irritating with the new
version.

First, the Ctrl+Plus to increase size function used to be able to go
much bigger. Now it stops me at a certain level. I run my monitor at an
extremely high resolution and often need to increase my size waaay
beyond the level at which it stops me. Is there any way to get it to let
me increase the size further? Perhaps an about:config setting?

Second, I don't like the new scrolling tab bar. I prefer the old
behavior where the tabs just become unreadably small. I tend not to pay
attention to what the tabs read. Rather, I memorize the *order* of my
tabs. In this case, being able to see, at a glance, *how many* tabs are
in the current window is more useful to me than being able to read each
tab's title. Is there any way to revert to the old behavior?

Thanks for the help.

Peace... Sridhar

Check and see if NoSquint is available for 2.1



It is not.

And, Robert Kaiser said that he coded into SM a limitation on zoom
settings simply because if they allowed the pref

toolkit.zoomManager.zoomValues

to be altered by users then the

View - Text Zoom display would not be accurate.

Peronally, that is unacceptable, as I've stated in another message
thread. My eyesight is MY eyesight. I need to be able to specify what I
need and I don't care a whit for making localization interfaces agree.

I need to be able to say:

- site A = x+ zoom
- site B = -x zoom
- site C = ...

Those are the sites I use, and I need to have the ability to fine tune
the zoom settings for those sites. I couldn't care in the least what the
VIEW - TEXT ZOOM menu says. I've been using this software in one
incarnation or another since at leat 1994. And I've NEVER looked at or
used that menu option.

If I change things via about:config, or even a UI access, (and SM's
ability to let me customize things is why I use it) I understand that I
can't expect the UI to track every tweak I make. I DON'T CARE.

But, to deny me that control over the interface is a deal breaker.

Even if I set that pref in a user.js file or the prefs.js file, on
program load those settings are ignored. This is horrible change to the
program.

And it is simply rude in ignoring users' control over their visual
experience with SeaMonkey.

MHO



I have nearly the same expectations, as displays are improving their 
resolutions, and viewing conditions may change in real life, why can't 
we change easily the zoom level and concurrently the text zoom level, in 
order to make a comfortable view.
to my opinion SM 2.0.* plus nosquint made it as we could use ctrl (shift 
for text only) mouse wheel up/down



--
cyberzen
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-20 Thread Paul Bergsagel

PhillipJones wrote:

Sridhar Ayengar wrote:


Hi. I just upgraded to Seamonkey 2.1, and I have to say, the experience
has been largely painless, and while Seamonkey 2.0.12 used to peg one
core of my CPU at 100% for hours at a time, and 2.1 doesn't. Kudos.

However, there are two things I'm finding irritating with the new
version.

First, the Ctrl+Plus to increase size function used to be able to go
much bigger. Now it stops me at a certain level. I run my monitor at an
extremely high resolution and often need to increase my size waaay
beyond the level at which it stops me. Is there any way to get it to let
me increase the size further? Perhaps an about:config setting?

Second, I don't like the new scrolling tab bar. I prefer the old
behavior where the tabs just become unreadably small. I tend not to pay
attention to what the tabs read. Rather, I memorize the *order* of my
tabs. In this case, being able to see, at a glance, *how many* tabs are
in the current window is more useful to me than being able to read each
tab's title. Is there any way to revert to the old behavior?

Thanks for the help.

Peace... Sridhar

Check and see if NoSquint is available for 2.1


I'm using NoSquint with 2.1 and it works perfectly.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-19 Thread PhillipJones

Sridhar Ayengar wrote:


Hi. I just upgraded to Seamonkey 2.1, and I have to say, the experience
has been largely painless, and while Seamonkey 2.0.12 used to peg one
core of my CPU at 100% for hours at a time, and 2.1 doesn't. Kudos.

However, there are two things I'm finding irritating with the new version.

First, the Ctrl+Plus to increase size function used to be able to go
much bigger. Now it stops me at a certain level. I run my monitor at an
extremely high resolution and often need to increase my size waaay
beyond the level at which it stops me. Is there any way to get it to let
me increase the size further? Perhaps an about:config setting?

Second, I don't like the new scrolling tab bar. I prefer the old
behavior where the tabs just become unreadably small. I tend not to pay
attention to what the tabs read. Rather, I memorize the *order* of my
tabs. In this case, being able to see, at a glance, *how many* tabs are
in the current window is more useful to me than being able to read each
tab's title. Is there any way to revert to the old behavior?

Thanks for the help.

Peace... Sridhar

Check and see if NoSquint is available for 2.1

--
Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it
http://www.phillipmjones.netmailto:pjon...@kimbanet.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-19 Thread David E. Ross
On 6/19/11 7:40 PM, Sridhar Ayengar wrote:
 
 Hi.  I just upgraded to Seamonkey 2.1, and I have to say, the experience 
 has been largely painless, and while Seamonkey 2.0.12 used to peg one 
 core of my CPU at 100% for hours at a time, and 2.1 doesn't.  Kudos.
 
 However, there are two things I'm finding irritating with the new version.
 
 First, the Ctrl+Plus to increase size function used to be able to go 
 much bigger.  Now it stops me at a certain level.  I run my monitor at 
 an extremely high resolution and often need to increase my size waaay 
 beyond the level at which it stops me.  Is there any way to get it to 
 let me increase the size further?  Perhaps an about:config setting?
 
 Second, I don't like the new scrolling tab bar.  I prefer the old 
 behavior where the tabs just become unreadably small.  I tend not to pay 
 attention to what the tabs read.  Rather, I memorize the *order* of my 
 tabs.  In this case, being able to see, at a glance, *how many* tabs are 
 in the current window is more useful to me than being able to read each 
 tab's title.  Is there any way to revert to the old behavior?
 
 Thanks for the help.
 
 Peace...  Sridhar

Your first problem is caused by the fact that you can now only zoom
larger or zoom smaller by at most three steps:  120%, 150%, and 200% and
also 95%, 75%, and 50%.  However, if you go to the menu bar and select
[View  Text Zoom  Other], you can get custom zooms between 30% and
300%.  You could likely code a custom button in PrefBar to allow input
of custom zooms without having always to navigate from the menu bar.

For your second problem, you can see the entire list of tabs by
selecting the tiny down-pointing triangle at the right end of the tab
bar just to the left of the X that closes the current tab.  (In the
viewed list, the current tab will be bold.)  While this takes a small
extra effort, you can then count the entries.

-- 

David E. Ross
http://www.rossde.com/

On occasion, I might filter and ignore all newsgroup messages
posted through GoogleGroups via Google's G2/1.0 user agent
because of spam from that source.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-19 Thread Ed Mullen

PhillipJones wrote:

Sridhar Ayengar wrote:


Hi. I just upgraded to Seamonkey 2.1, and I have to say, the experience
has been largely painless, and while Seamonkey 2.0.12 used to peg one
core of my CPU at 100% for hours at a time, and 2.1 doesn't. Kudos.

However, there are two things I'm finding irritating with the new
version.

First, the Ctrl+Plus to increase size function used to be able to go
much bigger. Now it stops me at a certain level. I run my monitor at an
extremely high resolution and often need to increase my size waaay
beyond the level at which it stops me. Is there any way to get it to let
me increase the size further? Perhaps an about:config setting?

Second, I don't like the new scrolling tab bar. I prefer the old
behavior where the tabs just become unreadably small. I tend not to pay
attention to what the tabs read. Rather, I memorize the *order* of my
tabs. In this case, being able to see, at a glance, *how many* tabs are
in the current window is more useful to me than being able to read each
tab's title. Is there any way to revert to the old behavior?

Thanks for the help.

Peace... Sridhar

Check and see if NoSquint is available for 2.1



It is not.

And, Robert Kaiser said that he coded into SM a limitation on zoom 
settings simply because if they allowed the pref


toolkit.zoomManager.zoomValues

to be altered by users then the

View - Text Zoom display would not be accurate.

Peronally, that is unacceptable, as I've stated in another message 
thread.  My eyesight is MY eyesight.  I need to be able to specify what 
I need and I don't care a whit for making localization interfaces agree.


I need to be able to say:

- site A = x+ zoom
- site B = -x zoom
- site C = ...

Those are the sites I use, and I need to have the ability to fine tune 
the zoom settings for those sites.  I couldn't care in the least what 
the VIEW - TEXT ZOOM menu says.  I've been using this software in one 
incarnation or another since at leat 1994.  And I've NEVER looked at or 
used that menu option.


If I change things via about:config, or even a UI access, (and SM's 
ability to let me customize things is why I use it) I understand that I 
can't expect the UI to track every tweak I make.  I DON'T CARE.


But, to deny me that control over the interface is a deal breaker.

Even if I set that pref in a user.js file or the prefs.js file, on 
program load those settings are ignored.  This is horrible change to the 
program.


And it is simply rude in ignoring users' control over their visual 
experience with SeaMonkey.


MHO

--
Ed Mullen
http://edmullen.net/
Why doesn't the glue stick to the inside of the bottle?
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: Two Problems I'm Having With Seamonkey 2.1

2011-06-19 Thread Philipp van Hüllen

Sridhar Ayengar schrieb:

Second, I don't like the new scrolling tab bar. I prefer the old
behavior where the tabs just become unreadably small. I tend not to pay
attention to what the tabs read. Rather, I memorize the *order* of my
tabs. In this case, being able to see, at a glance, *how many* tabs are
in the current window is more useful to me than being able to read each
tab's title. Is there any way to revert to the old behavior?


I don't have the time now to try it out, but maybe:

browser.tabs.tabMinWidth  -  100 (default)

helps with this? Settng a smaller minimum should show more tabs...?

BR/Philipp



___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey