I liked the idea you mentioned earlier with having one wrapper script, that way there is one entry point for the given commands for the needed functionality. Then it doesn't matter what underlying scripts actually do the work.
Then our only focus would be on the commands and not so much the name of the scripts. On Wed, Mar 20, 2013 at 7:36 PM, Andrew Grieve <agri...@chromium.org> wrote: > I really like Anis's suggestion of just four scripts. What's the motivation > for having many scripts? Having fewer will dramatically reduce copy & paste > bugs. It will also aid discoverability (since you'll get --help instead of > just "ls" and infer from the name what they do). > > > On Wed, Mar 20, 2013 at 7:06 PM, Filip Maj <f...@adobe.com> wrote: > > > Ya ya ya we're all on agreement on this specific issue. The underlying > > platform scripts can be used regardless of whether you're using > > cordova-cli or not. > > > > On 3/20/13 3:51 PM, "Anis KADRI" <anis.ka...@gmail.com> wrote: > > > > >On Wed, Mar 20, 2013 at 3:43 PM, Benn Mapes <benn.ma...@gmail.com> > wrote: > > > > > >> I know that sounds > > >> like a lot > > >> of scripts but we're building them for the cordova-cli to use, so i > > >>like > > >> the idea of breaking > > >> them out so each script does a *very specific* task with as > > >>little-to-no > > >> > > > > > >No we're not. cordova-cli is a cool tool that people can use but it > should > > >not be the only way of building Cordova apps in my opinion. > > > > >
