Wrapper Suggestion

Oct 6, 2008 at 5:48 PM
Move it to the core project.  No reason to separate them into 2 projects as far as I can tell. 
Oct 7, 2008 at 2:15 PM
I think its also useful to have it seperate in some ways because it allows people to make their own wrappers and put their own logic in there.

Hecne by having them seperate them dont need to have the existing wrapper at all.
Oct 16, 2008 at 12:47 AM
I agree with MXMissle. throw it into the core project. There's no way i want to have TWO dll's :(

Gedw99 -> to answer your problem, the developer needs to make an IWrapper interface. Then the developer can include the CURRENT Wrapper class in the core project. if anyone wants to impliment their own, then they can just impliment the interface and program up their own logic.

it's waaaay silly having the wrapper in a seperate project. i've currently moved it into the main core project, fixed the namespace, and then recompiled in release mode. viola. That said, i should have to do that, but just download a single release dll IMO.
Oct 16, 2008 at 12:47 AM
Edited Oct 16, 2008 at 12:48 AM
<snip> Double post. appologies.