That's great! In regards to the solution files, I think that's fine as long as there's a no fuss way of building it that won't scare away novice developers. If it's does, then we might want to keep around the VS.NET 2003 project and then just letting the IDE upgrade it on first open.
As for the Direct3D stuff, since Piccolo2d.java doesn't do any hardware acceleration by default, I don't see it as critical to the .NET stuff. Allain 2009/8/15 Mark <mtt...@gmail.com> > > Update: > > As a test I built piccolo, piccolox, and piccolo features with nant > and mono on win xp and everything seems to work (with zero code changes > (!)). So now I'll start working on the nant build for everything. I > also plan to test on Ubuntu. > > I have a some questions though: > > 1) should we keep the visual studio solution and project files? They > seem to be VS 2003 or VS 2005 and VS 2008 will convert them to VS 2008 > (which I have) format making them unusable to previous versions. I > think it's an unnecessary burden to be tied to 'the latest and > greatest' VS. Besides maintaining a nant build and an IDE build is > extra work. > > 2) I don't plan on supporting the Direct3D stuff, I'm okay with > dropping support for that. > > -Mark > > On Aug 12, 11:13 am, Michael Heuer <heue...@gmail.com> wrote: > > Mark wrote: > > > Regarding issue 115: > > > > >http://code.google.com/p/piccolo2d/issues/detail?id=115 > > > > > What task are needed to for the .Net version and the Piccolo 2D 1.3 > > > release? There were a few bugs reported for the 1.2 release, so those > > > would need fixed. All the milestones in the issue tracker for 1.3 are > > > for the Java version. > > > > > My interest: I have a project coming up later this year in which I > > > plan to use Piccolo.Net and I would like to see it stay current with > > > the other versions. So I'm willing to make some time to keep it > > > current. > > > > Most important in my mind is > > > > http://code.google.com/p/piccolo2d/issues/detail?id=60 > > > > The Piccolo2D devs can't work on the .Net version if we can't build > > it. None of the.Net issues have been assigned a version since we are > > unable to evaluate them. > > > > After that, the general tasks would be: > > > > Update the copyright/license headers > > Create a build process that can be automated (with NAnt, I suppose) > > Start creating a unit test suite (NUnit) > > Add build tools for calculating source code metrics, if available > > Evaluate issues fixed in Piccolo2D.Java since 1.2 to see if they are > > applicable to .Net versions > > Document a release process for .Net artifacts > > > > If there isn't much to fix in the .Net codebase other than the build > > stuff, we could release a version 1.2.1 fairly quickly. > > > > michael > > > --~--~---------~--~----~------------~-------~--~----~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~----------~----~----~----~------~----~------~--~---
