MAExternalFileModel class >> baseDirectory update responsibility

[Reza RAZAVI]

At 08:59 26/02/2010, you wrote:
>Maybe using FileDirectory wasn't such a good idea in the first place.
>Maybe we should change it to a string to do a relative/absolute lookup
>from the image directory? Or, oh well, we could use the Filesystem
>framework

Thank you for your prompt response!

The current implementation works just fine. It looks like that we 
just need to separate the *default base directory*, from another 
*application-specific base directory*. I'd *simply* do the followings:
- Add MAExternalFileModel to the Smalltalk start-up list to ensure 
that the default value gets automatically updated.
- Add an alternative class instance variable, for those applications 
that would need to reference a specific directory (without automated update).

Does this make sense?

Otherwise, the issue appeared since I'm used to copy my image from a 
*dev* directory to a *prod* directory, before executing my 
distribution generation script (sort of "PRDistribution new 
register"). I addressed the issue by simply adding to that script 
*MAExternalFileModel initialize*.

Regards,
Reza