There are a few advantages to this separation:
* it would force us to clean up the interface between the user-
interface (Cucumber::Cli::*) and the core feature parsing / running
stuff, which right now is quite messy.
* it would give us a clear place to start writing rdoc: for the core.
* it would allow tools like testjour to depend on just the cucumber-
core gem, rather than having the UI stuff as well.
* it might help people / us to think about building other UIs for
Cucumber than the CLI.
WDYT?
cheers,
Matt Wynne
+1. Maybe +2, if I get enough points for that.
--
Have Fun,
Steve Eley (sfe...@gmail.com)
ESCAPE POD - The Science Fiction Podcast Magazine
http://www.escapepod.org
I'll loan you mine just in case.
+1
--j
If I follow you, you're saying that 'gem install cucumber' should
install all the basics required to write and execute a feature from
the command line as we do now; under the hood it's really a thin
dependancy wrapper to install cucumber-{core,cli} and gherkin, which
makes it easy for other gems to just pull in cucumber-core.
+1 for that, and apologies if I've got your intent wrong.
--j
>
>> If I follow you, you're saying that 'gem install cucumber' should
>> install all the basics required to write and execute a feature from
>> the command line as we do now; under the hood it's really a thin
>> dependancy wrapper to install cucumber-{core,cli} and gherkin, which
>> makes it easy for other gems to just pull in cucumber-core.
>
> Exactly! Things "just work" great right now, and I think that it
> should stay that way.
Yes, that's exactly what I'm suggesting. I'd just like the layers
underneath, should you care to look down there, to have clearer
separation which will make Cucumber more extensible in the long game.
cheers,
Matt