I did think about this in the back of my mind when moving the config.xml. I don't think bending this spec and letting the paths in config.xml continue to be relative to www/ is that terrible. We break the Widget spec in a quite a number of other ways anyway.
It would be a tiny change to put it back, since I abstracted the location of the config.xml into utils. Braden On Tue, Apr 9, 2013 at 4:08 PM, Michael Brooks <mich...@michaelbrooks.ca>wrote: > I'm still not sold on the new directory structure, but I would need to > review the previous thread on why we are interested in adopting it. > > A minor concern on my part is the placement of `config.xml`. > > The path to `index.html` must be referenced relative to `config.xml` [1]. > Since `config.xml` is outside of www/ the the default <content> path [2] > must become "www/index.html", which is breaking the default start path > defined by the Widget spec. > > I'm not sure which platform's support the <content> element, but BlackBerry > does and I imagine we will have full coverage in the future. > > However, this also brings up the question of whether we are continuing with > the Widget spec or supporting the SysApps work. Fil will have more insight > into this when we gets back from the SysApps F2F. > > [1] http://www.w3.org/TR/widgets/#start-files > [2] http://www.w3.org/TR/widgets/#the-content-element-and-its-attributes > > Michael > > > > On Tue, Apr 9, 2013 at 11:51 AM, Braden Shepherdson <bra...@chromium.org > >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> 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 > > > <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 > > <javascript:;>> > > > > wrote: > > > > > > > > > >> How will we communicate this change to our existing users? > > > > >> > > > > >> On 4/9/13 5:22 PM, "Braden Shepherdson" <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, > > > > >>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 > > > > >> > > > > >> > > > > > > > > > > > > > >
