[piccolo2d-dev] Re: .Net version: tasks for 1.3?
> Hello Harold, > > Please create one or more issues in the tracker at > > http://code.google.com/p/piccolo2d/issues/list > > and attach one or more patches from your fork as necessary. As soon > as we get the mono build working we'll evaluate and commit. Do you need any help getting the mono build to work? I am downloading the suse/mono VMWare image, and will probably use that for my work. H^2 --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
Harold Howe wrote: >> 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. > > I would like to help how I can in this effort. I have a significant > investment in piccolo.net dating back to 2005 that is not going away > anytime soon. I have been maintaining my own fork of the 1.2 .net code > as needed, so I am familiar with some of the guts inside piccolo. But > I haven't had to do much to be honest, which is a tribute to how well > things were done in the first few versions of the library. Hello Harold, Please create one or more issues in the tracker at http://code.google.com/p/piccolo2d/issues/list and attach one or more patches from your fork as necessary. As soon as we get the mono build working we'll evaluate and commit. Alternatively, you may create a branch in say a git-hub mirror of the svn tree and link to that in your issue(s). Of course, if you end up being too helpful, you might end up with commit access. :) michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
> 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. I would like to help how I can in this effort. I have a significant investment in piccolo.net dating back to 2005 that is not going away anytime soon. I have been maintaining my own fork of the 1.2 .net code as needed, so I am familiar with some of the guts inside piccolo. But I haven't had to do much to be honest, which is a tribute to how well things were done in the first few versions of the library. H^2 --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
Mark wrote: > 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. This is great! Please attach a patch to issue 60 so that we can play along. > 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. I'd vote no. Does MonoDevelop work off a nant build? Is it worth using? > 2) I don't plan on supporting the Direct3D stuff, I'm okay with > dropping support for that. Is it possible to split this out into a seperate module? I'm guessing that we will need or want multiple implementations of PCanvas, for Winforms, Gtk#, Cocoa#, and maybe Qyoto. Some of those might need to be split into seperate modules for platform-specific compilation. michael --~--~-~--~~~---~--~~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
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 > > 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 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 -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
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 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 -~--~~~~--~~--~--~---
[piccolo2d-dev] Re: .Net version: tasks for 1.3?
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 -~--~~~~--~~--~--~---
