I agree with Jesse proposal. 1. Clean up ghost copies of config.xml 2. Document a single Table in docs/config_ref_index.md.html Two columns "CLI", "Not CLI" location of config.xml to be edit by user
--Carlos On Thu, Sep 26, 2013 at 12:03 PM, Jesse <purplecabb...@gmail.com> wrote: > Personally, when I refer to the www folder I am referring to the folder as > part of the app package at runtime, which is usually the same as the device > specific project layout. > > iOS: AppRoot/www > wp7: AppRoot/www > wp8: AppRoot/www > windows8: AppRoot/www > Android: AppRoot/assets/www ? > > The fact that even the www folder can live in different places on different > devices implies that it is okay for config.xml to live in different places > also. > I don't think it would be worthwhile to move files at loadtime, as Joe > warns. > I also don't think it is worth having a build time script to 'magically' > move files around before they get packaged. > > > @purplecabbage > risingj.com > > > On Thu, Sep 26, 2013 at 8:57 AM, Joe Bowser <bows...@gmail.com> wrote: > > > On Thu, Sep 26, 2013 at 8:53 AM, Lindsey Simon <els...@gmail.com> wrote: > > > > > > When you say www are you referring to project/www or > > > project/platform/android/assets/www? > > > > > > > That's the kicker, isn't it? If you're using the CLI, we're talking > > project/www, but not everyone uses the CLI, or should use the CLI. I > > think we should tell people not using the CLI where it's located on > > each of the platforms. The CLI can play pretend with the spec, and > > the platforms can move on with actually making things more usable. > > > -- Carlos Santana <csantan...@gmail.com>
