RunRev versus WinRar

[Richard Gaskin]

MisterX wrote:
>>>On Apr 8, 2005, at 10:33 PM, Richard Gaskin wrote:
>>>
>>>>The real culprit here is Microsoft, for not bothering to create a 
>>>>registry for file types to be associated with specific 
>>
>>applications.
> 
> There is no global registry but there are plenty of sites with the links or
> reference to any file extensions. On Windows, it's your job to know, not
> Apple's or Microsofts

Precisely.  But without the OS vendor managing a central registry, we 
must rely on the goodwill of third parties and their various ad hoc 
substitutes; i.e., it may not be possible to "know"; at best we can only 
guess, and hope.

To the degree that Apple maintains support for creator codes in a file's 
Finder metadata, the situation is less ambiguous:  either the developer 
registered their creator code with Apple, or the developer chose to risk 
user confusion.

Microsoft developers have no such choice; the ambiguity being part of 
the design, risk of user confusion is ever-present.

There are rumors of an internal warfare within Apple over whether to 
maintain creator codes for the long term (indeed heated debate over this 
critical issue was cause for Apple to shut down the HI Dev list); if the 
NeXT team wins the same ambiguity will be introduced into Mac OS X.


> Rev still can't open stacks normally on PCs when you double click on it's
> documents - the stacks or your application's stack-documents... Win32 always
> opens another session of Rev, this is still not handled correctly on windows
> since 4 years and there's no alternative. Im pretty sure I mentioned it
> before to Scott or Kevin but haven't seen complains and made my own
> solution...  But you can't send shell commands to runrev or double click a
> second document or you'll have this second runrev session and you'll surely
> get a stack-overwrite problem... Now, that's a security risk for file
> integrity if I've ever seen one!

How does this differ from Notepad or Internet Explorer?

Try this:

1. Open Notepad
2. Type something in the new document
3. Save it to the desktop, but leave it open
4. In the desktop, double-click the saved document
    - it opens a second instance; changes saved in either instance
      will overwrite the file, but neither instance will let the
      other know

I can't find verse and chapter on this behavior in the Win HIG, but it's 
a documented part of the OS (Ken, still have that reference handy?).

--
  Richard Gaskin
  Fourth World Media Corporation
  __________________________________________________
  Rev tools and more: http://www.fourthworld.com/rev