On 10/10/2019 3:39 PM, Dirk Fieldhouse wrote:
On 10/10/19 20:03, EE wrote:
Edward Diener wrote:
Is it possible to open the Composer window window of SeaMonkey
without starting SeaMonkey itself ?
Why would you expect to be able to open part of SeaMonkey without
starting SeaMonkey?
From the user perspective, you can start SeaMonkey with -edit to open
the Composer component alone, as noted earlier in this thread.
As you suggest, a SeaMonkey process is nonetheless started that will
also host any other SeaMonkey apps that the user might launch: browser,
mail, etc.
The problem with this is that the browser component is (a) much more
exposed to web idiocy that will crash the entire SeaMonkey process (b)
more likely to use a lot of memory with multiple windows and tabs that
will exhaust either available RAM or 32-bit address space.
So if OP is going to do a lot of editing in Composer, he should make
sure to minimise his browsing activity with SM; or try Blue Griffon, or
as suggested here
<https://www.dedoimedo.com/computers/html-wysiwyg-2018.html>, KompoZer,
both of which are derived from the same codebase as SM Composer.
I have not tried SM Composer yet but I know that Blue Griffon has had a
bug nearly from its first release where making visual changes in its
Windows version ends some lines in the corresponding HTML file with
<cr><lf><lf> instead of just <cr><lf>. I had reported this on the Blue
Griffon Google group and had been told it is a problem with the
underlying Mozilla codebase, with the implication that it could not be
fixed. As I stayed with Blue Griffon for a few releases the problem was
always still there and when I tried to notify them of the fact in their
Google Group my post would never get accepted and displayed. I guess
they felt that if they could not fix the problem it was better if the
fact that it existed was not publicized. So I finally decided to try
something else and found out about SM and Composer. I have not tested
yet to see if the problem exists in Composer, but if it does I will
report it here. I realize this is a long-winded explanation of why I am
certainly not interested in using Blue Griffon.
I am not that concerned in any memory issues using Composer, and
although I am sure the SM browser is great, the reason I am using SM is
in order to use composer for WYSIWYG web page editing. So opening the
composer window with the -edit option works fine for me and is what I
will do.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
