incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Beusterien <>
Subject Re: CommandLine Tooling Design
Date Mon, 09 Apr 2012 22:24:43 GMT
Great start!

A few comments:

   - Any aspirations to have "cordova deploy" and "cordova run" or would
   that be too hard on non-Android?
   - It would be useful to support the concept of cordova version,
   including querying, updating, and validation
   - As you imply, the directory structure doesn't work in conjunction with
   the Eclipse Android Development Tools where the www directory needs to be
   part of the Android assets directory hierarchy and plugins in the src


On Mon, Apr 9, 2012 at 10:10 AM, Patrick Mueller <> wrote:

> I've done a little brain dump of what I've been thinking about re: command
> line tooling, here:
> Lots of unanswered questions, design holes, etc, but nice to have at least
> much this written down.
> There's also lots of assumptions:
> - plugins/platforms packaged in a similar way as npm packages
> - how the directories are laid out
> Those assumptions are what I actually think of as the "command line API",
> since I see a 'cordova' command-line utility to be really just a reference
> implementation.  If someone wants to be able to do Eclipse tooling for this
> kind of structure, they aren't dependent on the command-line tool, but the
> structure of the directories and files.
> It would be really useful to get feedback from folks who already package
> tools around PhoneGap/Cordova, to see if this kind of directory/file
> structure is useful/terrible/etc.  Eg, PhoneGap build, AppLaud, WorkLight,
> Toura Mobile, etc.
> --
> Patrick Mueller

Paul Beusterien
twitter: @paulbeusterien

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message