OK, -1.
I don't see the need to abstract this into an interface. The proposal in myrmidon has a Project builder interface with one method build(File) I'm not sure builds will be coming from a File. They may be from a URL, a GUIProjectModel, JackSprattProjectRepository, who knows? Why not just say the execution engine operates on a Project instance and how that project instance is created is outside the scope of the execution engine. It is the responsibility of the front-end. I would see the different front-ends creating whatever sort of object is appropriate, which can deliver it a Project object. A GUI will most likely have some form of ProjectModel from which it can extract a Project object to pass to the execution engine. What is the benefit of abstracting this? Conor ----- Original Message ----- From: "Peter Donald" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, May 13, 2001 6:19 PM Subject: Re: [Vote] ProjectBuilder abstraction > > Just reminding peeps that there is a few votes that didn't get discussed > ... I would like it if everyone gave their opinions on these before I added > new topics ;) > > Cheers, > > Pete > > *-----------------------------------------------------* > | "Faced with the choice between changing one's mind, | > | and proving that there is no need to do so - almost | > | everyone gets busy on the proof." | > | - John Kenneth Galbraith | > *-----------------------------------------------------* > >
