Rhapsody Support/Development Site

[#1 Rhapsody]

Originally Posted by RacerX

Personally, I would think that going with a PowerPC system would be a good start.

Can you emulate Rhapsody for PPC? My old PowerPC computers are in my garage and I don't wan't to bring them inside. I can run the emulator on Windows, Linux, and Mac OS X

Have you tested my site in Rhapsody? I didn't realize that DR2 doesn't have OmniWeb on it. How do I get it?

[#1 Rhapsody]

What about using YellowBox? Would it be better for developing than DR2?

[RacerX]

Originally Posted by #1 Rhapsody

Can you emulate Rhapsody for PPC? My old PowerPC computers are in my garage and I don't wan't to bring them inside. I can run the emulator on Windows, Linux, and Mac OS X

Have you tested my site in Rhapsody? I didn't realize that DR2 doesn't have OmniWeb on it. How do I get it?

Rhapsody for PowerPC systems can't be run in emulation as there is no emulator that emulates Open Firmware correctly (some don't even attempt to provide actual drive images, but rather emulate large floppy drives). But the point of using the PowerPC version would be to use it on a real stable hardware platform rather than something jury-rigged together. Emulation (or any type) is worse in this regard, not better.

There is a copy of OmniWeb on the DR2 CD, but it is a demo version that is timed out if you are using the current date... I'm not sure where the Omni Group is keeping their older software these days, so you might have to wait for me to finish putting together my applications site.

And yes, when you first put up the site I checked... it looks okay in Rhapsody.

What about using YellowBox? Would it be better for developing than DR2?

Rhapsody applications are Yellow Box applications... unless you are talking about Yellow Box for Windows, in which case you are talking about Windows applications.

If that is the path you want to go down, then Rhapsody isn't where you want to be... you should be using some version of WebObjects on Windows.

Honestly, this was the problem I had with the Rhapsody Project and other things like it... they weren't using Rhapsody to begin with. I was using Rhapsody as a work-a-day operating system long before I started my Rhapsody site.

I mean, think about it this way... I don't own a Windows system, the newest copy of Windows I own is Windows 2000 Professional, and I haven't touched a Windows system since 2002. If I started up a Windows Support/Development Site today, would you take me seriously? I'm not even a Windows user at the moment and don't have a functioning Windows system.

I see you putting the cart before the horse here. You should first become a user of Rhapsody. Learn how to make it do the things that it needs to do to be a useful part of your computing environment. Learn how to side step problems and get the most from the system.

When I started using Rhapsody, I did it without a safety net. I used my ThinkPad with Rhapsody (and nothing else) as the system I brought with me to help me fix other people's computers. It had to function perfectly (you can't have a crashing computer and keep clients faith in your abilities to fit their systems), store and display all my manuals (which were PDF or HTML documents), and let me do some on the fly graphic design while working with clients. I had no other system with me away from home, so it was Rhapsody or nothing. I had to make it work.

At one point in time I was pretty good with Linux, and I could help others... but today, today I know next to nothing about Linux. I surely wouldn't attempt to help people with Linux until I was able to help myself first.

I would suggest this (and it is what I suggest for anyone looking at other platforms)... take a week to figure out what you might need on the new platform, and then ONLY use that platform for a week or two. Whatever you normally use for computing, pack it up in a box and put it in storage during that time.

You learn to swim by getting into the water and doing it... and you better know how to swim before you attempt to teach others. Same thing here.