[Rubycocoa-devel 1338] Potential changes to require_framework

Back to archive index

Scott Thompson easco****@mac*****
Sat Apr 12 11:55:17 JST 2008


Now that I've taken a good look at require_framework,  I wanted to  
suggest some changes to the mechanism that I think would be  
beneficial.  Not having been involved with the initial design of the  
code, however, I don't know what's an intentional feature of the  
library, and what might just be casual functionality.  If these ideas  
would adversely affect something that was intentionally designed into  
the framework, please tell me to go jump in a lake :-)

I would be more than happy to participate in the Open Source nature of  
this project, and change the code myself, then submit it through the  
process.  I wanted to discuss those changes here first before  
embarking on the coding effort.

1) The first feature suggestion I would make is to have  
require_framework take advantage of the Cocoa mechanisms for finding  
resources in the different file domains, rather than using hard-coded  
paths.  By that I mean, it should take advantage of  
NSSearchPathForDirectoriesInDomains.

2) The second feature suggestion, related to the first, is to change  
require_framework so that it searches the Framework directories in the  
order that Apple suggests in the "Searching Within the File-System  
Domains" section of the File System Overview documentation:

<http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/Articles/Domains.html 
 >

(This change is potentially dangerous as there may be existing  
RubyCocoa applications that depend on the search order as it currently  
exists.)

3) The third feature suggestion would be to automatically load the  
subframeworks of umbrella frameworks.  This would also allow the  
shortcuts to popular frameworks to go away and would allow the  
umbrella frameworks to function as they were intended.

My goal is to bring the framework loading for RubyCocoa more in line  
with the spirit of the Cocoa frameworks.  The hope being that Cocoa  
developers will find that behavior more predictable.

Are any of these changes of interest to the RubyCocoa community?

Scott


-------------- next part --------------
An HTML attachment was scrubbed...
Descargar 


More information about the Rubycocoa-devel mailing list
Back to archive index