[Biococoa-dev] New Structure for BioCocoa

Koen van der Drift kvddrift at earthlink.net
Sun Jul 3 14:58:58 EDT 2005

I understand the Cocoa framework structure. But I still don't get *why* 
the IO seems to be intertwined with the other code (or maybe I am 
confused by the name BCFoundationIO, BCSequenceIO could be better). To 
me IO code should just be another framework a user can add. Whatever is 
done with the outcome from the IO should be independent of the rest of 
the framework (execpt of course BCFoundation).

- Koen.

On Jul 3, 2005, at 2:41 PM, Philipp Seibel wrote:

> Am 03.07.2005 um 20:30 schrieb Koen van der Drift:
>> On Jul 3, 2005, at 2:22 PM, Philipp Seibel wrote:
>>> The BCParser.framework also contains Parsers for HMMs, Phylogenetic 
>>> structures etc, the BCFoundationIO only uses the Parsers for basic 
>>> structures.
>>> If we would put all our io in one framework, the framework
> framework == BCFoundationIO (probably solves misunderstanding :-))
>>> will depend on all frameworks (BCFoundation and all 
>>> BCXXXFrameworks)----> not a really good design
>> What I probably do not yet understand is why in the last case the 
>> framework (I assume you mean BioCocoa) will depend on all 
>> BCXXXFrameworks.
> The idea is like the cocoa framework. The cocoa framework header just 
> consists of
> #import <Foundation/Foundation.h>
> #import <AppKit/AppKit.h>
> but you can of course only use one of it's components
> The BioCocoa framework header will contain
> #import <BCParser/BCParser.h>
> #import <BCFoundation/BCFoundation.h>
> #import <BCFoundationIO/BCFoundationIO.h>
> #import <BCXXX/BCXXX.h>
> #import < BCXXXIO/ BCXXXIO.h>
> and you can also use all Frameworks seperately. This allows you only 
> choose the frameworks u really need in your application.
> Phil
> _______________________________________________
> Biococoa-dev mailing list
> Biococoa-dev at bioinformatics.org
> https://bioinformatics.org/mailman/listinfo/biococoa-dev

More information about the Biococoa-dev mailing list