[Maf] File Extension Clashes

[Ramez Labib-Sami]

Greetings Christopher,

Even as a Windows user(*) I had no idea *.maf is being used by Access -- I 
had never used Access! I discovered it as I created an archive then tried to 
open it...

Regards,

- rls

(*) Life is simply too short for SUN-OS, DOS, Windows and now Linux!
=========================================================================
Christopher Ottley wrote:

> Hello Ramez,
> 
> You make a good point about being able to share MAFs back and forth. I 
> honestly didn't expect my extension to become as popular as it is and 
> the last thing I was thinking about when developing this was file 
> extension clashes with MS Access on Windows. I have lots of features 
> that I want to implement (but avoid as much bloat as possible) and since 
> the 0.3.0 release I've been eMailed with quite a few additional 
> suggestions/requests. My logs show me over 82% of the people who visit 
> the Mozdev site use Windows, so I'd admit that "out-of-the-box" 
> usability is key for them.
>    My suggestion to Mark wasn't a long term solution for the file 
> extension conflict, but something Mark could do until it's resolved. 
> Heck, he could go ahead of the curve and instead of *.moa, start using 
> *.maff. Heh. I don't expect end users to use about:config to change MAF 
> preferences. I just don't have the time to code the GUI for managing the 
> settings I mentioned.
>    The next release (0.3.1) was going to be mostly an additional locale 
> (it-IT) and one or two bug fixes that annoy my mafsearch extension, but 
> I'll reconsider the priority of adding the *.maff as the default. Now, 
> if anyone out there knows of an app that uses *.maff please eMail me 
> now, or forever hold your peace. ;).
> 
> Regards,
> Chris.