Hi,
This is a suggestion for the PhoneGap as well as PhoneGap Build developers (documentation). When developing with PhoneGap e.g. Android using Eclipse with the the Android SDK (or other approach) it appears clear what to do with the Phonegap.js, Phonegap.jar and the web assets like making a link from index.html to the Phonegap.js, like placing the plugins.xml to the /res folder etc. When using PhoneGap Deploy nothing (appears) has to be modified/changed/included in the web assets to be wrapped. I think it would be appropriate to mention what PhoneGap Deploy does or does not do/need, like so that no PhoneGap code has to be included and(or linked before submitting to deploy. This to avoid stuffing the package with dead assets (and avoid confusion).
This will of course change when it becomes possible to use plugins with deploy and when that day comes it would appear clear in the documentation,
Disclaimer: I may have missed the above mentioned when reading the Wiki or comments on the web, but to better be safe about an important usability issue.
Regards
/Ralf
This is a suggestion for the PhoneGap as well as PhoneGap Build developers (documentation). When developing with PhoneGap e.g. Android using Eclipse with the the Android SDK (or other approach) it appears clear what to do with the Phonegap.js, Phonegap.jar and the web assets like making a link from index.html to the Phonegap.js, like placing the plugins.xml to the /res folder etc. When using PhoneGap Deploy nothing (appears) has to be modified/changed/included in the web assets to be wrapped. I think it would be appropriate to mention what PhoneGap Deploy does or does not do/need, like so that no PhoneGap code has to be included and(or linked before submitting to deploy. This to avoid stuffing the package with dead assets (and avoid confusion).
This will of course change when it becomes possible to use plugins with deploy and when that day comes it would appear clear in the documentation,
Disclaimer: I may have missed the above mentioned when reading the Wiki or comments on the web, but to better be safe about an important usability issue.
Regards
/Ralf

