incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Trice (JIRA)" <>
Subject [jira] [Commented] (CB-676) Improve PhoneGap migration guidance
Date Thu, 10 May 2012 18:34:50 GMT


Andrew Trice commented on CB-676:

I agree, what is there is great, and extremely helpful. I wasn't critiquing the work that
has been done.  What I am suggesting is that it be more easily found online.  I am aware that
the content is in the dmg, but not everyone looks there, they look online/to Google first.
  I am suggesting that we make it easier to find this same information online.

Currently, the workflow to find this is to download the zip file, go to lib/ios/, open the
DMG, then go to "guides".  This isn't intuitive or easy to find - (not a criticism of any
work that has been done to date).  Typically users open the DMG, run the installer, close
the DMG, then never open it again.    

What I am hearing from people who are currently using PhoneGap is that they didn't even know
this content existed, so we should make it easier for them to find.
> Improve PhoneGap migration guidance
> -----------------------------------
>                 Key: CB-676
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Docs
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.6.1, 1.7.0, 1.8.0
>            Reporter: Andrew Trice
> Guidance of migrating an old PhoneGap project to a new version is not easy to find. It
would be nice to have resources identifying how to upgrade a project that are easily accessible
on the web (docs or phonegap download page) - this could be simple instructions which libraries
to swap out, and what JS files have changed.   Since there isn't much content out and easy
to find now, this probably would go a long way to help PhoneGap users who want to upgrade
to a newer SDK.
> (Feedback based on communication with Adobe customers)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message