Good feedback: thx Ian and Carlos. Just pushed an update.
On Fri, Jul 19, 2013 at 6:46 AM, Ian Clelland <iclell...@google.com> wrote: > MIssed this earlier, but here goes: > >> If you are working with a `cordova` generated project then you can install >> using it. (Plugman is included in the Cordova install.) > > I don't think this makes sense as a stand-alone paragraph -- I had to read > it four times to figure out what the word "it" refers to. Maybe something > like > > "If you are working with a `cordova`-generated project, then you can > install plugins using the `cordova` tool as well. (`plugman` is included > with `cordova`, and is used by `cordova` internally to manage plugins)" > >> You know we release regularily > > "regularly" > >> - various native IDE's show generated files > > I don't know if this means much without mentioning the difference between > the `www` directory and the `platforms` directories. Should there be a > paragraph earlier about editing the code in `www` and running prepare? > >> - no way to upgrade existing CLI projects > > Maybe append "(this only affects you if you have been beta-testing the > `corvoda` tool with Cordova 2.9)" > > >> - plugin discovery > > What issue is this referring to? I think it could be worded more clearly, > but I'm not sure what it is saying. > > Maybe we just need to point to a "known issues" page, where we can detail > all of these issues and the current workarounds. Or create JIRA issues for > them and link each bullet point to the appropriate bug. > > Otherwise, it looks good! > > Ian > > On Fri, Jul 19, 2013 at 12:32 AM, Carlos Santana <csantan...@gmail.com>wrote: > >> Contents about 3.0 looks awsome but Minor thing the content its swap, it >> will mess up the permalinks >> >> The contents of 2013-07-08-cordova-has-a-blog.md goes in >> 2013-07-19-cordova-3.md >> The contents of 2013-07-19-cordova-3.md goes in >> 2013-07-08-cordova-has-a-blog.md >> >> --Carlos >> >> >> On Thursday, July 18, 2013, Brian LeRoux wrote: >> >> > Fuck, its here: >> > >> > https://svn.apache.org/repos/asf/cordova/site/www/_posts/ >> > >> > svn. I tell ya. >> > >> > >> > On Thu, Jul 18, 2013 at 1:37 PM, Brian LeRoux <b...@brian.io<javascript:;>> >> > wrote: >> > > Pls review all: >> > > >> > > >> > >> https://svn.apache.org/repos/asf/cordova/site/www/_posts/2013-07-08-cordova-has-a-blog.md >> > > >> > > >> > > On Wed, Jul 17, 2013 at 12:18 PM, Anis KADRI <anis.ka...@gmail.com >> <javascript:;>> >> > wrote: >> > >> On Wed, Jul 17, 2013 at 12:12 PM, Joe Bowser <bows...@gmail.com >> <javascript:;>> >> > wrote: >> > >> >> > >>> The CLI treats the platform code as a build artifact. While this is >> > >>> the goal, the reality is that people modify the code, and people rely >> > >>> on old plugins. There will be users who NEVER use the CLI because of >> > >>> this fact, and will need to use plugman. Just because you want to >> > >>> have people use the software in a particular way doesn't mean that >> > >>> they will, and we should provide some support for people who want to >> > >>> not use the CLI. I don't use the CLI, because I actually work with >> > >>> the platform source on a regular basis and I don't want to constantly >> > >>> destroy and rebuild the project that I hooked the framework source >> to. >> > >>> >> > >>> I know that people will say that I'm a special case, but the bug >> > >>> tracker says otherwise. Also, we have CordovaWebView, which is a >> > >>> component that isn't even supported with the CLI flow. Just because >> > >>> the CLI is the new hawtness doesn't mean that we should neglect >> > >>> everyone who chooses to actually hack Cordova into something they >> > >>> want. >> > >>> >> > >> >> > >> +1 >> > >> >> >> -- >> Carlos Santana >> <csantan...@gmail.com> >>
