| « Hardware Support | :: INDEX :: | Improvements Since ZETA RC1 » |
I created a small iconic overview of the applications that come installed with the "normal" choice in the Installer. Would you believe that the games section consumes a whopping 179 megs?!? Most of the games are crappy SDL types, some are defunct and haven't been updated in YEARS. Please, yellowTAB, for the love of Pete, take em away. Focus on the core OS.
I find it amazing that yellowTAB can pretend these are even close to up-to-date, and not feel shame in trying to foist these are quality products. While on this topic, can someone please explain how Cortex makes its way into a Development Application? It's a utility or tool to aid in playing with Multimedia nodes. It is NOT a compiler or editing environment.
 The Be debugger, circa 2000. |
 BeDC, circa 2000. |
 Be Integrated Development Environment, circa 1999. |
 MeTOS. Note that high version number. |
 Globe 0.4.0 from October 21st, 2004. |
 Package Builder, circa 1999. |
 |
 BeHappy. :) |
 QuickRes, circa 2001. |
 Spy-O-Matic from Be, Inc.! Sneaky. |
 I didn't know we could wire our C++ apps now. Oh yeah.. circa 2000. |
|
ZETA 1.0 comes with Firefox but for some strange reason it uses Japanese menus. I thought perhaps it was just a glitch on my part so I verified in a later install, and no matter what language I chose, Firefox displayed Japanese menus. Quite weird. I suspect there is a Language file leftover from the Japanese distribution that remained in this ZETA 1.0 burn.
For developers there is GCC 2.9-beos-000224 (GNU C Compiler, from Feb 24, 2000) installed. I could not switch from 2.9 to 3.x with the setgcc utility introduced in ZETA RC1, as that utility has been removed, it appears. A much newer version of GCC can of course be downloaded and installed by visiting BeBits.
It seems strange that in earlier versions of ZETA the yellowTAB propoganda stated that one would have the ability to use the brand new GCC 3.x series of compiler, but now it is missing entirely. I could not find any reference to GCC in their FAQ (Frequently Asked Questions) section on yellowTAB.com either. What is a developer to think?
There is also the Spy-O-Matic utility which allows one to view running threads, BMessages, and get a better handle on what their application is doing in memory.
As I already mentioned I used the JABA program to burn a CD. It is an excellent program and one I would recommend for anyone who doesn't want to directly use the command-line cdrecord utility.
You do have to go through a few steps to ensure the burning device can be used optimally by JABA. Fortunately the settings window is simple and to the point, making choosing what settings to use for your device a snap.
|
|
The interface to JABA can be used in either Standard mode or Advanced mode, which simply means there can be more or less buttons to clutter it. Like most CD burning applications JABA allows you to make projects, burn data image files (x.img), and of course regular audio discs. |
|
|
|
There is much more in ZETA than this, such as Gobe Productive 2, Whisper (VoIP), eXposer, a half dozen emulators, and more. I feel there is simply no use in wading through the dozens of other applications in ZETA that shouldn't be here. Take a look at the icon overview above and try to imagine using them. Now consider they come standard with ZETA 1.0 if you do not venture customizing your choices.
I feel pretty terrible in hammering this point again and again, but I must say it once more. We do not need this bloat.
| « Hardware Support | :: INDEX :: | Improvements Since ZETA RC1 » |
