I'm with you, Brian... CLI for CLI, project scripts for IDEs. Anything else will just lead to madness.. On 03/01/2014 12:21 pm, "Brian LeRoux" <b...@brian.io> wrote:
> idk, if ppl want to use the cli I would reccomend using a text editor and > our build chain > > if they want to use IDE's then they should not use the cli and just use the > project scripts > > (at least, this was the intent of the design as I originally saw it) > > not sure I see much benefit to making the cli ultra configurable > > > On Thu, Jan 2, 2014 at 4:10 PM, Andrew Grieve <agri...@chromium.org> > wrote: > > > We've had a bunch of users confused by Xcode and Eclipse showing only the > > output www/ and not the www/ that they are supposed to edit. > > > > There's bugs tracking addressing this for: > > iOS: https://issues.apache.org/jira/browse/CB-5397 > > Android: https://issues.apache.org/jira/browse/CB-5715 > > > > I've now taken a stab at addressing both of them through adding in > > references to the root www/, merges/ and config.xml for CLI projects > (using > > a separate project template for normal vs CLI projects). > > > > For Xcode, the build still works fine if you delete the reference to the > > output www/, but I've left it in by default. > > For Eclipse, there's no such option. > > > > If anyone wants to give it a whirl & provide feedback, that'd be great! > > > > Andrew > > >
