Question Re: text Editors for G-Force in OS X

Discussion forum for G-Force users

Moderators: BTT, andy55, b.dwall, juxtiphi

Post Reply
User avatar
JayPro
Posts: 738
Joined: Sat May 01, 2004 10:51 pm
Location: Huntington Station, Long Island, New York

Question Re: text Editors for G-Force in OS X

Post by JayPro »

I've been using Colormonger to make *tons* of potential new colormaps. The only concern I have is that the new map files can only be saved as a BBEdit doc, which in my computer can only be opened in the Classic Environment.
So what I do as a potential hedge against GF crashing is re-open the new docs in an OS X-compatible text editor and re-saving after making the perfunctory edits (i.e. I merely re-type the first digit in the top RGB triad).

That said, my question is this with regard to G-Force as used in OS X:

Would it have any difficulty calling up and processing config files created by Classic-only text apps, even after making sure that Classic is off?
"God is syntax."

cellness
Posts: 19
Joined: Mon Jan 03, 2005 9:08 pm

Post by cellness »

My first question is why can BBEdit only run under classic on your computer? I use BBEdit lite 6.1 on Mac OS X with no problems.

Second, the issue most likely to cause any problem is how G-Force expects to read the text files. Classic Mac text apps usually save files in the "Mac" text format unless they have options to save as DOS or UNIX format. Under Mac OS X, text editors seem to use either format depending on what OS their roots are in (UNIX or Mac). Only Andy can really answer that, but I think G-Force will read both Mac and UNIX text formats without problem. Just a random sampling of text files from within my G-Force install show both types of text formats.

Otherwise, I don't think G-Force should have any problems, but again, only Andy can really answer that for certain.

Marcel

Post Reply