Netscape's Plans for M14 and Beyond

Monday February 7th, 2000

Cmad writes, "Want to know more about Netscape's release plan? Another interesting article has been posted on that matter by Jim A. Roskind in the SeaMonkey newsgroup."

If the link above doesn't work for you, try this link.

Jim goes into detail about what Netscape is expecting to do with M14 - it could turn into an alpha Netscape product, a beta product, or, worst case, they might end up holding off to M15 for a branded version. They're expecting that M16 will be feature complete (presumably the skin-switching code and security module will be in by that time, too).

Beyond the obvious performance issues, I think Netscape should really try to address the usability issues with the current skin if they are looking to push out a beta product. For example, the toolbar buttons should be labeled, and the buttons themselves should not extend over the grey space below the main toolbar -- it looks like an unintended effect (or defect).

What do you think? Post your thoughts and ideas in the forum for this news item, but since this has been a contentious issue in the past, I'm asking that you please keep your post civil.


#20 Chris's entire post, boiled down into one point.

by FrodoB

Monday February 7th, 2000 4:17 PM

You are replying to this message

If native widgets are used, the Mac and Linux ports of Mozilla are dead. Mike Pinkerton, Mac weenie, made this crystal clear at the UI IRC session. Without Netscape actively porting them, the following consequences will happen:

1) At best, we can hope for someone to pick up the ports. But who would hold out hope that the ports would even partially keep up with Windows, if they lose a couple dozen dedicated programmers who are getting paid to work on nothing but those areas?

2) Because of the dropping of the Linux port, we lose all the other various Unixes, as the Linux port is used as a base for most of the other ports. Best case scenario is that we keep the ones that are supported by commercial entities (like Sun, for instance) but lose the rest.

3) Mozilla is put SEVERAL months back, if somehow the Mac and Linux ports don't get whacked, because it has to redesign a new UI for every platform.

4) Mozilla won't be CSS compliant. The specs require styleable widgets, to my knowledge (IE 5.0's widgets are actually a lot like gfx [they're not native], except that they only support one platform each [the Mac and Windows versions are separate] and can devote their resources to making their widgets look and feel exactly like that platform).