On 2006-08-10, at 5:07 AM, Thom McGrath wrote:
Well, trying filing a report/request again. Now that Joe doesn't
work at REAL anymore, I think their biggest advocate of File Type/
Creator codes is now 3rd-party. (Sorry Joe, nothing personal)
In reality, REALbasic is still sticking to old-world standards.
It's not a matter of what is believed to be right or wrong, it what
*is* right and wrong. Apple has depreciated resource forks, and is
moving away from type codes. This is for compatibility with Linux
and Windows. It is to improve the Mac experience, especially for
all those switchers who are importing files from their old PCs
which do not have creator codes. REALbasic simply needs to be
updated to accommodate OS X instead of Classic in this case. We
have developers coming from VB who are not use to type codes and
likely forget them as well.
--
Thom McGrath, <http://www.thezaz.com/>
"You don't need eyes to see, you need vision" - Maxi Jazz in
"Reverence" by Faithless
On Aug 9, 2006, at 9:49 PM, Phil M wrote:
I think that the problem is that REALbasic assumes that any new
file would be a TEXT file, and in the modern OS X age this is an
incorrect assumption. I would much rather have REALbasic use NULL
type and creator codes.
I would prefer that REALbasic treats file extensions as full first
class file type identifiers just like Apple does.
Could some write a Feature Request on this, this is to IMPORTANT to
get to works as soon as possible, so I want not to do this (perhaps
closed).. I support it to 110%
Sven E
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
