This is why Mozilla is so naturally cross-platform, since its UI widgets are all done by Gecko and are naturally OS-independent (though there is skinning to match the OS style I had worked on code in Gecko that uses the raw widget drawing APIs in Windows to render things like buttons in the native OS style).Īnd along the way, they also developed a framework that ran atop the engine, that they appropriately (and not too cleverly) called "toolkit". That user interface that you see? It's laid out using a markup language like XUL (not unlike Microsoft's XAML, and both bear resemblances to HTML), styled using CSS, and programmed using JavaScript. Phoenix uses the exact same core/engine (Gecko) as Suite-Mozilla products run using the same core rendering engine that is used for web content. Then a group of developers decided to create a new project called Phoenix (because it's Mozilla reborn) where they took Suite and started to strip out everything that wasn't related to the browser (so no e-mail client, no editor, etc.), simplified the UI (hacked out a ton of menu items, simplified the options, etc.). It was called the Mozilla Suite, and for a while, the Suite was Mozilla's flagship product. So when Netscape gave way to Mozilla, things started out as a single big program that did everything and had a gazillion different features and options all rolled into one. ![]() The Netscape 4 Communicator suite was a browser, an e-mail client, a newsgroup reader, and a WYSIWYG HTML editor, all rolled up into one big happy package. Back before Mozilla, in the days of Netscape 4, the fad was to have a big all-in-one package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |