Re: Cordova has a Blog/News! Announce 3.0?

2013-07-23 Thread Carlos Santana
Thansk Andrew, I could never figure out the svn fiasco


On Tue, Jul 23, 2013 at 1:48 PM, Andrew Grieve agri...@chromium.org wrote:

 Better late than never. This is now live: http://cordova.apache.org/#news

 Might need to hard-refresh the page to see the update.


 On Fri, Jul 19, 2013 at 1:31 PM, Carlos Santana csantan...@gmail.com
 wrote:

  cool everyday I learn something new !
 
  published
 
  Set to false if you don’t want a specific post to show up when the site
 is
  generated.
 
 
  On Fri, Jul 19, 2013 at 1:24 PM, Brian LeRoux b...@brian.io wrote:
 
   You can also set a published bool in the front matter. [1] The svn
   publish seems down and not getting an answer from infra .
  
   =(
  
   [1] http://jekyllrb.com/docs/frontmatter/
  
  
   On Fri, Jul 19, 2013 at 8:54 AM, Carlos Santana csantan...@gmail.com
   wrote:
Cool I was just looking at the svn repo found the issues, but it
 looks
   like
they are fix now
   
   
To avoid a post to go live just rename file with _ in front
  www/_posts/_
2013-07-08-cordova-has-a-blog.md
   
When is ready to publish  just remove '_' from the front and rebuild
  site
`rake build`
and then svn commit
   
   
   
On Fri, Jul 19, 2013 at 11:47 AM, Brian LeRoux b...@brian.io wrote:
   
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,
 

Re: Cordova has a Blog/News! Announce 3.0?

2013-07-23 Thread Brian LeRoux
thx breauxs

methinks we book a little time to revisit this site. svn uploading
gigs of docs and junk is mega uncool.

On Tue, Jul 23, 2013 at 2:13 PM, Carlos Santana csantan...@gmail.com wrote:
 Thansk Andrew, I could never figure out the svn fiasco


 On Tue, Jul 23, 2013 at 1:48 PM, Andrew Grieve agri...@chromium.org wrote:

 Better late than never. This is now live: http://cordova.apache.org/#news

 Might need to hard-refresh the page to see the update.


 On Fri, Jul 19, 2013 at 1:31 PM, Carlos Santana csantan...@gmail.com
 wrote:

  cool everyday I learn something new !
 
  published
 
  Set to false if you don’t want a specific post to show up when the site
 is
  generated.
 
 
  On Fri, Jul 19, 2013 at 1:24 PM, Brian LeRoux b...@brian.io wrote:
 
   You can also set a published bool in the front matter. [1] The svn
   publish seems down and not getting an answer from infra .
  
   =(
  
   [1] http://jekyllrb.com/docs/frontmatter/
  
  
   On Fri, Jul 19, 2013 at 8:54 AM, Carlos Santana csantan...@gmail.com
   wrote:
Cool I was just looking at the svn repo found the issues, but it
 looks
   like
they are fix now
   
   
To avoid a post to go live just rename file with _ in front
  www/_posts/_
2013-07-08-cordova-has-a-blog.md
   
When is ready to publish  just remove '_' from the front and rebuild
  site
`rake build`
and then svn commit
   
   
   
On Fri, Jul 19, 2013 at 11:47 AM, Brian LeRoux b...@brian.io wrote:
   
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 

Re: Cordova has a Blog/News! Announce 3.0?

2013-07-19 Thread Ian Clelland
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.comwrote:

 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.iojavascript:;
  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



Re: Cordova has a Blog/News! Announce 3.0?

2013-07-19 Thread Carlos Santana
Cool I was just looking at the svn repo found the issues, but it looks like
they are fix now


To avoid a post to go live just rename file with _ in front www/_posts/_
2013-07-08-cordova-has-a-blog.md

When is ready to publish  just remove '_' from the front and rebuild site
`rake build`
and then svn commit



On Fri, Jul 19, 2013 at 11:47 AM, Brian LeRoux b...@brian.io wrote:

 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
 




-- 
Carlos Santana
csantan...@gmail.com


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-19 Thread Brian LeRoux
You can also set a published bool in the front matter. [1] The svn
publish seems down and not getting an answer from infra .

=(

[1] http://jekyllrb.com/docs/frontmatter/


On Fri, Jul 19, 2013 at 8:54 AM, Carlos Santana csantan...@gmail.com wrote:
 Cool I was just looking at the svn repo found the issues, but it looks like
 they are fix now


 To avoid a post to go live just rename file with _ in front www/_posts/_
 2013-07-08-cordova-has-a-blog.md

 When is ready to publish  just remove '_' from the front and rebuild site
 `rake build`
 and then svn commit



 On Fri, Jul 19, 2013 at 11:47 AM, Brian LeRoux b...@brian.io wrote:

 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
 




 --
 Carlos Santana
 csantan...@gmail.com


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-19 Thread Carlos Santana
cool everyday I learn something new !

published

Set to false if you don’t want a specific post to show up when the site is
generated.


On Fri, Jul 19, 2013 at 1:24 PM, Brian LeRoux b...@brian.io wrote:

 You can also set a published bool in the front matter. [1] The svn
 publish seems down and not getting an answer from infra .

 =(

 [1] http://jekyllrb.com/docs/frontmatter/


 On Fri, Jul 19, 2013 at 8:54 AM, Carlos Santana csantan...@gmail.com
 wrote:
  Cool I was just looking at the svn repo found the issues, but it looks
 like
  they are fix now
 
 
  To avoid a post to go live just rename file with _ in front www/_posts/_
  2013-07-08-cordova-has-a-blog.md
 
  When is ready to publish  just remove '_' from the front and rebuild site
  `rake build`
  and then svn commit
 
 
 
  On Fri, Jul 19, 2013 at 11:47 AM, Brian LeRoux b...@brian.io wrote:
 
  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
  
 
 
 
 
  --
  Carlos Santana
  csantan...@gmail.com




-- 
Carlos Santana
csantan...@gmail.com


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-19 Thread Brian LeRoux
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.comwrote:

 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.iojavascript:;
  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



Re: Cordova has a Blog/News! Announce 3.0?

2013-07-18 Thread Brian LeRoux
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 wrote:
 On Wed, Jul 17, 2013 at 12:12 PM, Joe Bowser bows...@gmail.com 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


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-18 Thread Carlos Santana
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.comjavascript:;
 wrote:
  On Wed, Jul 17, 2013 at 12:12 PM, Joe Bowser 
  bows...@gmail.comjavascript:;
 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


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Andrew Grieve
I've been hit with some pretty unplanned baby duties today, so don't expect
to have much time today to work. I would like to urge someone to take
ownership of this task though.

Thoughts on what we should say:

- Snapshot available on [[download page]]
- Introducing new command line tools: plugman  CLI
- Plugman for existing projects, CLI for those wanting a cross-platform
project
- Both tools are new, so please expect some and file bugs on [[JIRA]]
- Links to upgrade guides
- Core plugins no longer exist by default in new projects
- Can create your own plugins via [[plugin guide / plugman spec]]
- Known Issues:
  - merges to change soon
  - whitelist format will be unified soon, but isn't yet
  - IDE's show generated files
  - No way to upgrade existing CLI projects
  - Anything else?




On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve agri...@chromium.org wrote:

 Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276

 Will update the wiki once we're through this release (to flesh out the
 process)

 Thank YOU Carlos!


 On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.comwrote:

 The Cordova Blog is live

 http://cordova.apache.org/#news
 You can use your RSS reader to subscribe

 A new blog post needs to be added when cutting a new release

 The step should be added to the Wiki (but I don't access)
 https://wiki.apache.org/cordova/CuttingReleases

 A tasks you be added to the JIRA item for announcing release (but I can't
 find the JIRA #)

 I want to thank Andrew with putting up with me on setting up the blog, me
 being a noob to the Cordova community

 --
 Carlos Santana
 csantan...@gmail.com





Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Brian LeRoux
I'll do a draft and send a review out sometime this afternoon.


On Wed, Jul 17, 2013 at 11:01 AM, Andrew Grieve agri...@chromium.org wrote:
 I've been hit with some pretty unplanned baby duties today, so don't expect
 to have much time today to work. I would like to urge someone to take
 ownership of this task though.

 Thoughts on what we should say:

 - Snapshot available on [[download page]]
 - Introducing new command line tools: plugman  CLI
 - Plugman for existing projects, CLI for those wanting a cross-platform
 project
 - Both tools are new, so please expect some and file bugs on [[JIRA]]
 - Links to upgrade guides
 - Core plugins no longer exist by default in new projects
 - Can create your own plugins via [[plugin guide / plugman spec]]
 - Known Issues:
   - merges to change soon
   - whitelist format will be unified soon, but isn't yet
   - IDE's show generated files
   - No way to upgrade existing CLI projects
   - Anything else?




 On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve agri...@chromium.org wrote:

 Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276

 Will update the wiki once we're through this release (to flesh out the
 process)

 Thank YOU Carlos!


 On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.comwrote:

 The Cordova Blog is live

 http://cordova.apache.org/#news
 You can use your RSS reader to subscribe

 A new blog post needs to be added when cutting a new release

 The step should be added to the Wiki (but I don't access)
 https://wiki.apache.org/cordova/CuttingReleases

 A tasks you be added to the JIRA item for announcing release (but I can't
 find the JIRA #)

 I want to thank Andrew with putting up with me on setting up the blog, me
 being a noob to the Cordova community

 --
 Carlos Santana
 csantan...@gmail.com





Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Carlos Santana
Do we need to expose plugman? or can we just talk about CLI

Its my understanding that everything can be done with CLI (plugin
[{add|remove|rm} PATH|URI] )

The simpler the better in my opinion.

These two statements contradict to me as noobie (I assume we want to
advertise cordova 3.0.0 first one with official cli support)
- No way to upgrade existing CLI projects
- Plugman for existing projects,

most people should not have existing CLI projects, I vote to keep it simple
and generic
Create a new cordova project using CLI, then use upgrade guide to merge
your existing cordova project with new 3.0.0 generated project.





On Wed, Jul 17, 2013 at 2:16 PM, Brian LeRoux b...@brian.io wrote:

 I'll do a draft and send a review out sometime this afternoon.


 On Wed, Jul 17, 2013 at 11:01 AM, Andrew Grieve agri...@chromium.org
 wrote:
  I've been hit with some pretty unplanned baby duties today, so don't
 expect
  to have much time today to work. I would like to urge someone to take
  ownership of this task though.
 
  Thoughts on what we should say:
 
  - Snapshot available on [[download page]]
  - Introducing new command line tools: plugman  CLI
  - Plugman for existing projects, CLI for those wanting a cross-platform
  project
  - Both tools are new, so please expect some and file bugs on [[JIRA]]
  - Links to upgrade guides
  - Core plugins no longer exist by default in new projects
  - Can create your own plugins via [[plugin guide / plugman spec]]
  - Known Issues:
- merges to change soon
- whitelist format will be unified soon, but isn't yet
- IDE's show generated files
- No way to upgrade existing CLI projects
- Anything else?
 
 
 
 
  On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve agri...@chromium.org
 wrote:
 
  Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276
 
  Will update the wiki once we're through this release (to flesh out the
  process)
 
  Thank YOU Carlos!
 
 
  On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.com
 wrote:
 
  The Cordova Blog is live
 
  http://cordova.apache.org/#news
  You can use your RSS reader to subscribe
 
  A new blog post needs to be added when cutting a new release
 
  The step should be added to the Wiki (but I don't access)
  https://wiki.apache.org/cordova/CuttingReleases
 
  A tasks you be added to the JIRA item for announcing release (but I
 can't
  find the JIRA #)
 
  I want to thank Andrew with putting up with me on setting up the blog,
 me
  being a noob to the Cordova community
 
  --
  Carlos Santana
  csantan...@gmail.com
 
 
 




-- 
Carlos Santana
csantan...@gmail.com


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Joe Bowser
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.



On Wed, Jul 17, 2013 at 11:36 AM, Carlos Santana csantan...@gmail.com wrote:
 Do we need to expose plugman? or can we just talk about CLI

 Its my understanding that everything can be done with CLI (plugin
 [{add|remove|rm} PATH|URI] )

 The simpler the better in my opinion.

 These two statements contradict to me as noobie (I assume we want to
 advertise cordova 3.0.0 first one with official cli support)
 - No way to upgrade existing CLI projects
 - Plugman for existing projects,

 most people should not have existing CLI projects, I vote to keep it simple
 and generic
 Create a new cordova project using CLI, then use upgrade guide to merge
 your existing cordova project with new 3.0.0 generated project.





 On Wed, Jul 17, 2013 at 2:16 PM, Brian LeRoux b...@brian.io wrote:

 I'll do a draft and send a review out sometime this afternoon.


 On Wed, Jul 17, 2013 at 11:01 AM, Andrew Grieve agri...@chromium.org
 wrote:
  I've been hit with some pretty unplanned baby duties today, so don't
 expect
  to have much time today to work. I would like to urge someone to take
  ownership of this task though.
 
  Thoughts on what we should say:
 
  - Snapshot available on [[download page]]
  - Introducing new command line tools: plugman  CLI
  - Plugman for existing projects, CLI for those wanting a cross-platform
  project
  - Both tools are new, so please expect some and file bugs on [[JIRA]]
  - Links to upgrade guides
  - Core plugins no longer exist by default in new projects
  - Can create your own plugins via [[plugin guide / plugman spec]]
  - Known Issues:
- merges to change soon
- whitelist format will be unified soon, but isn't yet
- IDE's show generated files
- No way to upgrade existing CLI projects
- Anything else?
 
 
 
 
  On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve agri...@chromium.org
 wrote:
 
  Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276
 
  Will update the wiki once we're through this release (to flesh out the
  process)
 
  Thank YOU Carlos!
 
 
  On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.com
 wrote:
 
  The Cordova Blog is live
 
  http://cordova.apache.org/#news
  You can use your RSS reader to subscribe
 
  A new blog post needs to be added when cutting a new release
 
  The step should be added to the Wiki (but I don't access)
  https://wiki.apache.org/cordova/CuttingReleases
 
  A tasks you be added to the JIRA item for announcing release (but I
 can't
  find the JIRA #)
 
  I want to thank Andrew with putting up with me on setting up the blog,
 me
  being a noob to the Cordova community
 
  --
  Carlos Santana
  csantan...@gmail.com
 
 
 




 --
 Carlos Santana
 csantan...@gmail.com


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Anis KADRI
On Wed, Jul 17, 2013 at 12:12 PM, Joe Bowser bows...@gmail.com 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


Re: Cordova has a Blog/News! Announce 3.0?

2013-07-17 Thread Brian LeRoux
I get in at the same time ...svn co on the train is slow but I'll
have a draft before the day is done.

On Wed, Jul 17, 2013 at 12:07 PM, Steven Gill stevengil...@gmail.com wrote:
 Brian, I can help with this in case you don't get a chance to do it. I will
 be landing in Portland around 3pm.
 On Jul 17, 2013 11:36 AM, Carlos Santana csantan...@gmail.com wrote:

 Do we need to expose plugman? or can we just talk about CLI

 Its my understanding that everything can be done with CLI (plugin
 [{add|remove|rm} PATH|URI] )

 The simpler the better in my opinion.

 These two statements contradict to me as noobie (I assume we want to
 advertise cordova 3.0.0 first one with official cli support)
 - No way to upgrade existing CLI projects
 - Plugman for existing projects,

 most people should not have existing CLI projects, I vote to keep it simple
 and generic
 Create a new cordova project using CLI, then use upgrade guide to merge
 your existing cordova project with new 3.0.0 generated project.





 On Wed, Jul 17, 2013 at 2:16 PM, Brian LeRoux b...@brian.io wrote:

  I'll do a draft and send a review out sometime this afternoon.
 
 
  On Wed, Jul 17, 2013 at 11:01 AM, Andrew Grieve agri...@chromium.org
  wrote:
   I've been hit with some pretty unplanned baby duties today, so don't
  expect
   to have much time today to work. I would like to urge someone to take
   ownership of this task though.
  
   Thoughts on what we should say:
  
   - Snapshot available on [[download page]]
   - Introducing new command line tools: plugman  CLI
   - Plugman for existing projects, CLI for those wanting a cross-platform
   project
   - Both tools are new, so please expect some and file bugs on [[JIRA]]
   - Links to upgrade guides
   - Core plugins no longer exist by default in new projects
   - Can create your own plugins via [[plugin guide / plugman spec]]
   - Known Issues:
 - merges to change soon
 - whitelist format will be unified soon, but isn't yet
 - IDE's show generated files
 - No way to upgrade existing CLI projects
 - Anything else?
  
  
  
  
   On Tue, Jul 16, 2013 at 5:07 PM, Andrew Grieve agri...@chromium.org
  wrote:
  
   Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276
  
   Will update the wiki once we're through this release (to flesh out the
   process)
  
   Thank YOU Carlos!
  
  
   On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.com
  wrote:
  
   The Cordova Blog is live
  
   http://cordova.apache.org/#news
   You can use your RSS reader to subscribe
  
   A new blog post needs to be added when cutting a new release
  
   The step should be added to the Wiki (but I don't access)
   https://wiki.apache.org/cordova/CuttingReleases
  
   A tasks you be added to the JIRA item for announcing release (but I
  can't
   find the JIRA #)
  
   I want to thank Andrew with putting up with me on setting up the
 blog,
  me
   being a noob to the Cordova community
  
   --
   Carlos Santana
   csantan...@gmail.com
  
  
  
 



 --
 Carlos Santana
 csantan...@gmail.com



Re: Cordova has a Blog/News! Announce 3.0?

2013-07-16 Thread Andrew Grieve
Created JIRA issue here https://issues.apache.org/jira/browse/CB-4276

Will update the wiki once we're through this release (to flesh out the
process)

Thank YOU Carlos!


On Tue, Jul 16, 2013 at 2:05 PM, Carlos Santana csantan...@gmail.comwrote:

 The Cordova Blog is live

 http://cordova.apache.org/#news
 You can use your RSS reader to subscribe

 A new blog post needs to be added when cutting a new release

 The step should be added to the Wiki (but I don't access)
 https://wiki.apache.org/cordova/CuttingReleases

 A tasks you be added to the JIRA item for announcing release (but I can't
 find the JIRA #)

 I want to thank Andrew with putting up with me on setting up the blog, me
 being a noob to the Cordova community

 --
 Carlos Santana
 csantan...@gmail.com