Darrell, Awesome news, I'm loving it!
As to the project files, I think the opinions are about 50% in favour, 50% against ;-) As an example: some of the SDK projects do have Flash Builder project files, some don't. Personally I like them in version control, as they give new contributors an easier start, providing at least some of the needed settings to get a project to build. That said, you preferably add them to .gitignore right after committing them, preventing a continuous string of commits, one for each new committer adjusting the project to their local machine ;-) EdB On Tue, Mar 17, 2015 at 1:38 PM, Darrell Loverin <darrell.love...@gmail.com> wrote: > I've been working on improving the existing Code Coverage Tool in utilities. > I'm getting ready to commit the work but I'm not sure whether to commit the > Eclipse project files with the code. Are they considered helpful or clutter? > > I've attached an example code coverage report from the tool I took while > running a mustella test on components/Button. > > Thanks, > > -Darrell -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
