Pretty much the brute force copy/paste. You never get exposed to the native build artifacts/projects with build.phonegap.com --- something we'd like to gun for in the phonegap project itself but recognize that access to the tooling local to the device platform is still super important. For now. ;)
On Mon, Nov 28, 2011 at 12:26 AM, Christian Grobmeier <[email protected]> wrote: > Thanks Brian for explaining my options, now I can decide how to deal with it. > I am curious how build@phonegap handles this? > > On Mon, Nov 28, 2011 at 2:59 AM, Filip Maj <[email protected]> wrote: >> If more people contribute to http://github.com/callback/callback-js we can >> bring the future sooner :D > > Thanks for pointing me to that :-) I would love to help, but I am > unsure if I have the skills/time to do so. But I will look into that, > thanks again. > > Cheers > >> >> On 11-11-26 8:09 AM, "Brian LeRoux" <[email protected]> wrote: >> >>>> And how do I deal with that now? >>> >>>There are three ways: >>> >>>- simlink www (and phonegap.js gets built/copied into your project on >>>platform by platform basis) >>>- git submodules (or if you prefer svn externals) >>>- brute force copy/past of www into appropriate native directories >>>using a bash script (example of such a project can be seen here: >>>https://github.com/brianleroux/Cordova/tree/master/generate-template >>>w/ scripts living in the bin directory) >>> >>>Like Simon said, we're hoping to unify the JS (as per the other email >>>threads) sometime in the near future. >> > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de >
