Robert Kaiser wrote:
Rufus wrote:
So I really don't get why they've knuckled under and merely imported TB
and FF code instead of maintaining their own, based on that code...this
is all open source, right?
Right, it is. And even maintaining al bunch of code you don't really
know and which is sometimes written in strange ways is a quite hard job,
have you ever tried that?
Yes, that I understand...try porting functionality written in raw
machine code to C++ for an entire integrated system and then maintaining
like configurations on a dual path for each - where the requirement is
that the two interfaces remain EXACT duplicates of each other for common
functions. I'm not saying it's easy, I'm saying that there is a
required discipline, order, and approach to doing the job in order to
get it done.
But SM has been going on for some years...decades? That should have
been enough time to shape it up. If people have been focused.
The SeaMonkey project mostly consists of people who have never worked on
many parts of the code that the old suite had, most of us worked only in
user interface ("frontend") parts and never in the platform code
("backend") those interfaces build on, so we are simply unable to
maintain it.
Again, understood. But yet another reason for shaping up the code along
the way so that the next volunteer can figure it out. That should be a
common overall goal/responsibility. And I assume you can feedback input
to the backend coders?
Our only chance of keeping SeaMonkey alive at all was to reduce the
amount of unknown code we cannot maintain and replace it with code that
is being maintained by someone else - which meant switching to the newer
Mozilla platform, of which e.g. the new form management code is a part of.
If you're talking about the Forms Manager, I noted it's not in Firefox
either, so I can only assume it's gone for good - unless the SM team is
coding it anew. Which I doubt, given what you've said.
Now, that we have switched to that base and can let the old stuff die,
we can look into ways to improve the newly acquired things and those
parts of code that we have in the application now and should be able to
maintain.
Robert Kaiser
I'd be even more pleased if people were looking into ways to port
familiar and popular feature sets into the new code structure...which it
doesn't sound like is going to happen - not when I hear things about
"old stuff dying".
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
