I can't say I have strong feelings one way or the other. I will say that having config.xml inside www *does* feel odd. So I'd be all for moving it to the project's root directory (but that breaks spec. Is that good? Bad?). Which is a breaking change, and so we'd still have to deal with older projects. But there are times that's going to happen anyway (though I think the tone "it's alpha, expect it" is a little odd, since it comes off as a shipping product; so I would echo a lot that Tommy wrote. If we're going to do that, cordova-cli should have a v0.# instead of v2.6.0 or the like.)
Ultimately, I think if the change is breaking, the bare minimum must be a well-defined failure *up-front* that indicates to the user that they need to do something with their directory structure (the gravy would be letting the user say to the script, "yes, I want you to do this for me"). We should never rely on a "we hope it fails", because there will be a case where it won't, and will seriously screw something up. That will equal several unhappy users. <semi-rant>I know, that if we use this directory structure, that the way to get your project up-to-date isn't hard. But there are plenty of users who already have an aversion to the command line, and this is going to be too much. It's hard enough to convince them to use cordova-cli in the first place, the main idea being "it'll be easier to manage your cross-platform projects". But there are plenty of users who are still upset that there's no GUI way to do this (nor a GUI way to create a single-platform project), and so we do risk having too much of a starting obstacle when it comes to getting started with Phonegap. Clearly there are loads of users in the forum who are not experts when it comes to understanding the command line, and I do think that at some point, we need to be sensitive to those needs. </semi-rant> Finally, let me just say this: I wouldn't use versioning as an argument. I can easily tell Git what to ignore, and it does so happily. So to me that's a non-starter. ___________________________________ Kerri Shotts photoKandy Studios, LLC On the Web: http://www.photokandy.com/ Social Media: Twitter: @photokandy, http://twitter.com/photokandy Tumblr: http://photokandy.tumblr.com/ Github: https://github.com/kerrishotts https://github.com/organizations/photokandyStudios CoderWall: https://coderwall.com/kerrishotts Apps on the Apple Store: https://itunes.apple.com/us/artist/photokandy-studios-llc/id498577828 Books: http://www.packtpub.com/phonegap-2-mobile-application-hotshot/book http://www.packtpub.com/phonegap-social-app-development/book On Tuesday, April 9, 2013 at 1:51 PM, Braden Shepherdson wrote: > That's now how I recalled the discussion. It certainly wasn't clear-cut, > but I thought the conclusion was that this was fine. > > Well, then this is now a discussion thread. What are the counterarguments? > > Braden > > > On Tue, Apr 9, 2013 at 2:49 PM, Brian LeRoux <b...@brian.io > (mailto:b...@brian.io)> wrote: > > > :( > > > > We never had full consensus to do this Braden. > > > > On Tuesday, April 9, 2013, Filip Maj wrote: > > > > > For a couple months now the npm package has had about 1000 downloads per > > > month [1]. > > > > > > We do have upgrade guides in our docs for each version for each platform. > > > Maybe we could add a CLI section? Then we can reference those guides in > > > the CLI's readme? Just thinking out loud. > > > > > > [1] http://npmjs.org/package/cordova > > > > > > On 4/9/13 5:40 PM, "Braden Shepherdson" <bra...@chromium.org > > > (mailto:bra...@chromium.org) > > <javascript:;>> > > > wrote: > > > > > > > This mailing list post is, or will shortly be, indexed by Google and > > > > others. Any newcomers will see the new docs and create new projects. > > > > > > > > As I mentioned on IRC, existing users are either accepting or ignoring > > the > > > > "alpha" warnings that this software is new and under heavy development, > > > > and > > > > if they want to jump on it early they're going to have to expect some > > > > pain. > > > > > > > > That said, I don't really know of any better way to socialize it. Is > > there > > > > anywhere where a brief blog post on this would make sense? > > > > > > > > I don't know how many people are using these tools and not on the > > mailing > > > > list, though certainly some turn up on IRC occasionally. > > > > > > > > Braden > > > > > > > > > > > > On Tue, Apr 9, 2013 at 11:24 AM, Filip Maj <f...@adobe.com > > > > (mailto:f...@adobe.com)<javascript:;>> > > > wrote: > > > > > > > > > How will we communicate this change to our existing users? > > > > > > > > > > On 4/9/13 5:22 PM, "Braden Shepherdson" <bra...@chromium.org > > > > > (mailto:bra...@chromium.org) > > <javascript:;>> > > > wrote: > > > > > > > > > > > I've just pushed a change to the future branch that changes the > > > > > directory > > > > > > structure to: > > > > > > > > > > > > app/ > > > > > > merges/ > > > > > > android/ > > > > > > ios/ > > > > > > www/ > > > > > > config.xml > > > > > > > > > > > > As was discussed at our video conference meeting a couple of weeks > > ago, > > > > > > this has a number of advantages: > > > > > > - config.xml is no longer in the www/ directory > > > > > > - One can easily version control the whole app/ directory, and get > > > > > > > > > > > > > > > > their > > > > > > web assets, merges and so on into the repo. > > > > > > - That repo can contain additional information: a README.md > > > > > > (http://README.md), > > > > > > > > > > > > > > > > supplementary > > > > > > documentation, tests, whatever. The CLI will ignore anything outside > > > > > > > > > > > > > > > > > > > > > of > > > > > > the > > > > > > merges and www directories. > > > > > > > > > > > > > > > > > > The downside is that this is a breaking change: running the new > > > > > version of > > > > > > the tools on an old project will fail (but I think in a harmless > > > > > > way) > > > > > > until > > > > > > you rearrange the directories. You can do that with the following > > > > > > commands: > > > > > > > > > > > > $ mkdir app > > > > > > $ mv www/config.xml app > > > > > > $ mv www app > > > > > > $ mv merges app > > > > > > > > > > > > All docs and tests are updated as well. Any problems should be > > > > > reported on > > > > > > JIRA and assigned to me. > > > > > > > > > > > > Braden
