Ken Rudolph wrote:
Look, I've been a Netscape and SeaMonkey user from the very beginning.
I've dutifully upgraded to every version through SM 2.0.14. But given
all the problems people have had (for me, crucially with html Composer)
that I've read about on this newsgroup, I've decided not to upgrade to
SM 2.2 or 2.3.
Yes, I know that I'm taking a security risk. But I also feel about SM
2.0.14 "it's not broke so why fix it". I know this is totally forlorn;
but I do wish that the powers that be would come up with SM 2.0.15 with
just the security fixes. Since that isn't ever going to happen (and I'll
bet I'm not the only person by a long shot in SM-land who thinks this
way), I'm sure I'll eventually have to reconsider my dedication to
SeaMonkey itself. Thank you for your time reading this.
I guess it's up to the beholder to judge well SM 2.1 / 2.2 / 2.3 work.
I've had no trouble with them (except for the link properties problem in
Composer, for which there's a workaround and which is apparently to be
fixed), but of course YMMV, and what's important to you is up to you.
If you abandon SM, you may find the work effort to move is greater than
that to workaround SM problems. Again YMMV.
I haven't tried KompoZer recently. I tried BlueGriffon, which I
understand to be a from-the-ground-up reimplementation, but I found
BlueGriffon to make some "elementary" some things way too difficult,
e.g., changing fonts or font sizes (Having to define a CSS style sheet
and element ID to change a font seems grossly excessive to me - but I'd
be happy for correction if I misunderstand the BG function).
RL
--
Rob Lindauer
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
