Change API in config & project file

[devboy]

I want to change a few things in the gator config and project files.
First problem that arises right now is the scope:

project = Project.new

won't work as it will create a new local var instead of using the provided setter. Thats why we use this right now:

project(Project.new)

I will go and attach all these properties to another object, so we can do stuff like this:

gator.project = Project.new
gator.config = ...

We then could think about introducin something like this:

gator.project do |p|
p.name = "name"
end

Additionally I want to get rid of the require syntax to add generators as it is probably better to associate extensions to a project, so a generator for example can be configured via a property it adds to gator.project.

gator.project.generators do |g|
g.test_with :asunit4
end

[Simon Bailey]

Sounds good....

--
Cheers,

Simon

[ http://newtriks.com ]

[devboy]

Cool! ;)

Ihave been working on this over the weekend, but it's quite a big change which will affect a lot of internal things of gator. For the better i hope!

Cheers

[devboy]

I have just implemented this.

Here's the commit: https://github.com/devboy/gator/commit/c23fc309fbfdec652888dcafdd60c1760640483b

[devboy]

The api right now is not perfect yet, but it works as intended:

gator.configuration.project do |p|

  p.name = "MyProject"

  p.layout = ...

end

We need to think about how we want to have configurations accessible in the buildfile,

do we want everything to be on the top-level? Like this:

project do |project| ...

Or do we want to at least put it inside the gator object like:

gator.project do |p| ...

We also need to consider how this is gonna work with plugins like gator-as3-robotlegs and their own configurations.