Nubies' Corner

     Everyone in the computer world has already heard about Mac OS X (Macintosh Operating System Ten). While people fuss about properly calling it "ten" or "X", it is a departure from the traditional (Classic) Mac interface. It is more Unix and Windows like than Classic Mac in its basic structure. One must log in to use the system, and there are permissions for everything like a Unix box. To make drastic changes, one must log in as the sytem administrator (in this case, "Computer God" is not too far off from the accurate interpretation). Prepare for a case of multiple personalities..........
     Not everyone is pleased with new interface. Apple has been very insistant on the concept of the userless menu bar. Everything in the menu bar is system defined. This means that the Apple Menu contains no user entries. There are no third party extensions that can add user implemented commands. What you see is what you get, period. Instead of allowing navigation through the Apple Menu, or select items from the status menu (in the upper right on Classic), it forces the user to operate from the Dock, a Launcher like device that can severely limit user navigation. The Dock has a number of commands that make it functional, but there is no cascading with the Dock like there is with the Apple Menu. This makes OS X a more single minded system. It's better to run just a few applications, making each count for as much as possible (every application being a Swiss Army Knife in terms of process environment, sort of like Photoshop). OS X is not everyone's system. OS X is its own system. And it's making chaos on many a Classic Mac user's habits. The masses are preparing to lock horns with Apple over the future of the system design.
     However, OS X contains Classic as a module, which means that when a PPC application is launched in X, Mac 9.21 (using current OS X 10.1) will launch the classic system and perform the task. It is a paired system that can work together or separately. But for that to take place, a minimum of 400M of RAM is required to run them together effectively. This pretty much makes OS X a system for the tower G3's and G4's that can expand to a gig or more of RAM and host multiple hard drives to make it production effective. If you have a dual G4 with a gig of RAM, by all means, install it. If you have an iMac with 128M of RAM, forget it. Stay with Classic until you can afford the hardware upgrade.
     What OS X brings to Macintosh is direct internet function. If one is using Macintosh for the net, they should be using OS X. It has lots of Unix goodies in its FreeBDS kernal, like packet coding (showing every data transfer logged), and is Java 2 savvy (where no Mac has gone before). This allows for the ultimate fine tuning for a computer used with high speed internet (cable, DSL, T1.....). It also makes it a networking dream, making the 10/100 Base-T ethernet a heaven-sent.
     Lots of techno babel? These are important implications of the new system, and if they baffle you, then you're probably not ready for it yet. And I do stress "new". It's a Mac made for moving data while feeling the strength of the Mac of times now past. It's two set of tricks to learn, so it's definitely not for those who haven't learned one set first.
     The system is a super-structure, capable of hosting multiple systems as modules, with very efficient networking capabilities. But it keeps all the graphic, animation, rendering, word processing, audio,
     My advice is to stay with Classic until you know that you're ready for the transition. It should coincide with a new machine and the finances to acquire one. You'll know when it's time to step up. If you have doubts, wait, and learn Classic Mac better. You'll need it. If you're past due, my condolences.
     And Apple is working on 10.1.1, to make more of the Classic Mac tools and interfaces (like Firewire) available to the OS X environment. It is still a new system and a work in progress. It is one heck of a work that will be hard for anyone to top. Being a work in progress for the last eight years, it will be a while before anyone can match the stability and functionality of this new system.






Systems/Software

     Web Objects 5.0 comes of age in OS X 10.1 with update 3. The cutting edge of interactive internet server design, WebObjects 5.0, is now 10.1 and 10.1 Server compatible with both the Development and Deployment installations.

     I'm going to discuss the Development installation, since this is where all the design decisions are made. Deployment is something better left to the Unix Server crowd to discuss. Deployment is a multi-processor, requiring at least two boxes, one for managing the connections, and one to hold the database and to manage the connecting server. This makes the server more secure and less vulnerable to hack and other types of attack on the server system. If you want to get a taste for the server system in operation, visit Apple's new Knowledge Base (k-base) (Apple Care free registration is required.) That will give you an eyeful for the way it works. (If you are interested in seeing the update 3 specs, you'll need to be registered.)

     WebObjects 5 requires OS X and OS X Developer Tools installed onto the hard drive to operate on OS X 10.0.x. For it to operate on OS X 10.1, it also requires WebObject 5.0 update 3. All of the post system installations require System Administrator level access (short name) to install. Without it, the packages on the CD's won't be functional as applications, and no installation can take place.
     After installation takes place, the Developer folder created with the OS X Development Tools installation is where Web Objects is based. The Applications sub-folder contain WebObjects Builder, ProjectBuilder WO, EOModeler, and Rule Editor nestled in among the basic developer tools. These four applications are the heart of WebObjects 5 Development.
     WebObjects has a functional heirarchy on the server. ProjectBuilder WO creates the core mappings that generate the SQL commands for the installed database on the server. WebObjects Builder generates the page templates that the database will use for presentation. EOModeler creates the complex logic arrays on which the SQL operates. Rules Editor edits the navagational directives within the database.

Diagram of a simple dynamic html server configuration.
(From WebObjectsOverview.pdf, © 2001 Apple Computer, Inc)
Save image to enlarge.

     WebObjects can be used for both internet and intranet. Java 2 is a native tool for WO 5.0, which is why OS X 10.1 is currently the preferred environment, as the 10.1 upgrade solved a few of the Java 2 problems of prior versions. There are basically four approaches to WebObjects. HTML internet, HTML intranet, Java internet, Java intranet. Because of its strong Java use in the interface, it is an ideal server developmental environment. Java Applets can be used profusely throughout the server system, making it extremely efficient in creating interactive server applications based on the user end. This reduces bandwidth on the server end, making it a faster server with full interactive capabilities. The structure can follow user progress in a site without the use of cookies, making the visits more personal without permanently cluttering the user's hard drive.
      While WebObjects is more than capable of hosting vast static web sites, it excels in creating dynamic HTML and Java based web sites. The WebObjects interactive server offers visitors a very interactive experience, allowing for active streaming media, server applications, store fronts, and much more. As with any database based system, it must be the first step in design. Changing the database before the construction of the supporting framework is much easier than modifying the framework to accommodate modifications to the database after the support is already in place. One change in the database can send the need to modify the framework throughout all phases. So it is best built from the ground up, creating the database structure, then the Enterprise objects, which are limited by the governing rules. Once the project has a proper framework, then the page templates can be created, giving the presentations their aesthetic atmosphere and navigation tools. This is not to say that the site can't grow, but it should be previsualized to the maximum extend before the construction process begins.
     For basic sites that don't need a lot of custom features, there are an ample amount of default modules in the installation that can be employed for areas of the site's framework. However, the learning curve goes way up in a big hurry when custom modules are needed. Java developmental skills are a must to tackle the creation of custom applets, modules, clients, etc. It's a flexible system that most HTML authors can use, but one with which the Java designers can use to generate unheralded interactive sites. It's a fairly complex system for a wide range of user skills. Streaming media, CGI, Java, scripting, remote applications, functional custom server clients, and more are available for building impressive web sites with full business facilities. Finally, the whole ball of wax in one package................

     In essence, if you are looking to create a cutting edge, dynamic, interactive website, this is where the learning curve should be. There just isn't anything quite as advanced and complete.