You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Mike Reinstein <re...@gmail.com> on 2012/09/01 16:13:44 UTC
Re: plugin tooling/specification
Ah ok, thanks for the clarification. I've had a chance to review the docs
more carefully. I'm really impressed with how well written they are. What I
*think* makes the most sense is to consolidate into fewer documents so that
it's not necessary to look at so many seperate places. Here's what I
propose:
* merge the cordova-plugin-spec into the alunny/pluginstall README.md
* merge the command line tooling design doc into the cordova-client
README.md
* pull apart the cordova/PluginDesign wiki page and merge parts of it into
the above 2 docs
I think what this gets us is 2 docs instead of 5, and it still maintains
the nice loose coupling between alunny's pluginstall utility and the larger
cordova-client. I'm assuming this separation was the original intent,
rather than having one monolithic tool.
Would love feedback on this, I don't want to waste time doing it and find
out this isn't appropriate. :)
On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
> Cordova-client depends on pluginstall. Pluginstall does the hard work for
> programmatic plugin installation, which is just one of the apis available
> in cordova-client. So, cordova=client "shells out" to pluginstall.
>
> The client also handles app creation, platform removal/addition, and
> interpolating information from app's config.xml into the necessary spots
> in each native project.
>
> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >Hey Filip,
> >
> >One thing I"m curious about, whats the difference between
> >https://github.com/alunny/pluginstall and
> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >
> >there seems to be some overlap there. Is pluginstall a subset of
> >functionality just related to plugins that has moved into cordova-client
> >or
> >is it different?
> >
> >It seems like cordova-client is the most mature codebase that incorporates
> >a lot of ideas, so I'm just chasing down code I'm finding to see if
> >everythign is in cordova-client or not. Said differently, is it safe to
> >assume that just about all the worthwhile code is in cordova-client?
> >
> >-Mike
> >
> >
> >
> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> All looks good to me Mike.
> >>
> >> I think the "PluginDesign" wiki article would be a great place to
> >> summarize / revamp all this info. Appreciate you tackling this!
> >>
> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com> wrote:
> >>
> >> >Hey Filip, Brian:
> >> >
> >> >I think where I'd like to start is on documentation. I may be wrong
> >>about
> >> >this, but it seems like there are bits and pieces of docs in various
> >> >places, and some may be stale or irrelevant. Maybe a good start is for
> >>me
> >> >to find all these pieces, consolidate into a "master" document, and
> >>cull
> >> >out the outdated bits? As a start, here's my rephrasing of the various
> >> >links, etc that you've sent to me. Please take a look and let me know
> >>if
> >> >I've characterised the content/purpose of these various links:
> >> >
> >> >
> >> >*The spec for how plugins are declared is here:
> >> >https://github.com/alunny/cordova-plugin-spec
> >> >
> >> >The implementation that manages plugin usage is here:
> >> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >This project encompasses more than just plugins because it also handles
> >> >everything related to building, deploying, and managing cordova
> >> >applications
> >> >
> >> >These plugins are most popular, and should ideally work with the
> >> >cordova-client implemenation:
> >> >http://github.com/phonegap/phonegap-plugins*
> >> >*
> >> >*
> >> >This implementation by Drew was an initial proof of concept, which only
> >> >works for blackberry and has been abandoned in favor of cordova-client,
> >> >with much of his ideas having made it into cordova-client:
> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
> >> >
> >> >This doc contains some info on the format of the command line interface
> >> >and
> >> >directory structure of cordova-client:
> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >
> >> >This doc contains some documentation on Drew's old implementation, and
> >>is
> >> >out of date now:
> >> >http://wiki.apache.org/cordova/PluginDesign
> >> >
> >> >
> >> >I want to emphasize that I'm just trying to get a handle on what docs
> >>are
> >> >relevant and which links contain what. I'm not judging anyone's work or
> >> >anything like that. :) If I've got the wrong idea about what these
> >>links
> >> >represent or contain, _please_ let me know.
> >> >
> >> >-Mike
> >> >
> >> >*
> >> >*
> >> >*
> >> >*
> >> >*
> >> >*
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >
> >> >> The cordova client CLI tooling top-level project goes hand-in-hand
> >>with
> >> >> this spec. Code here:
> >> >>
> >> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=sh
> >> >>or
> >> >> tlog;h=refs/heads/cordova-client
> >> >>
> >> >> Essentially: vet the spec out to make sure popular plugins out in the
> >> >>wild
> >> >> (see github.com/phonegap/phonegap-plugins) work with this spec. Do
> we
> >> >>need
> >> >> to account for anything else?
> >> >>
> >> >> I think the one outstanding question is how to handle installation /
> >> >> compatibility with different versions of cordova.
> >> >>
> >> >> Documentation for the tool as well as the spec (put it on the wiki,
> >> >> perhaps) would be awesome!
> >> >>
> >> >> On 8/25/12 10:23 AM, "Mike Reinstein" <re...@gmail.com>
> >>wrote:
> >> >>
> >> >> >Hi Brian, Filip,
> >> >> >
> >> >> >Thanks for the pointers to those projects. I'd love to dig in and
> >>start
> >> >> >helping, where do you feel the most help is needed at the moment?
> >> >> >Documentation? Any specific code tasks?
> >> >> >
> >> >> >-Mike
> >> >> >
> >> >> >
> >> >> >
> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >> >
> >> >> >> Also, this is the current de-facto plugin "spec" we are working
> >> >>towards:
> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >> >> >>
> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >> >> >>
> >> >> >> >Hi Mike, you've come to the right place! Currently the plugin
> >> >>tooling
> >> >> >> >is being implemented by Anis, Fil, Michael, and myself. (sorry
> >>for
> >> >>the
> >> >> >> >delayed response / many of us are on a summer break after
> >>shipping
> >> >> >> >2.0)
> >> >> >> >
> >> >> >> >We're loosely collaborating using this list, git, and these wiki
> >> >>pages:
> >> >> >> >
> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >> >> >
> >> >> >> >The dev is taking place a Cordova/Labs branch which you can
> >>preview
> >> >>on
> >> >> >> >the Github mirror here:
> >> >> >> >
> >> >> >> >
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >> >> >
> >> >> >> >You will want to start by reading up on our contrib process in
> >>the
> >> >> >>wiki:
> >> >> >> >
> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
> >> >> >> >
> >> >> >> >And in the case of labs projects everything stays on its own
> >>branch
> >> >> >> >until such a time that we feel its solid for its own repo.
> >> >> >> >
> >> >> >> >* * *
> >> >> >> >
> >> >> >> >Let me know any q's!
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> >> >> >> ><re...@gmail.com> wrote:
> >> >> >> >> Hey there,
> >> >> >> >>
> >> >> >> >> I'm interested in contributing to the plugin system that is
> >> >> >> >>forthcoming. Is
> >> >> >> >> this the right place to bring it up? Who are the right people
> >>to
> >> >>talk
> >> >> >> >>to?
> >> >> >> >> Where do you need the most help? I'm an experienced developer,
> >> >>have
> >> >> >> >>worked
> >> >> >> >> on a few phonegap based projects, and would love to give back
> >>to
> >> >>the
> >> >> >> >> community.
> >> >> >> >>
> >> >> >> >> cheers,
> >> >> >> >>
> >> >> >> >> -Mike
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
Re: plugin tooling/specification
Posted by Andrew Lunny <al...@gmail.com>.
Thanks for taking a stab at all this Mike - I've been on vacation, so I'm
just catching up on everything now.
A few points:
* pluginstall is not going to be a part of Apache Cordova any time soon.
It's a dependency of the PhoneGap Build web service, and we often need to
iterate quickly on features. If it reaches a point of much greater
stability, we may consider donating it to the ASF, but it's not there yet.
* that said, it's all liberally licensed, and cordova-client is free to
depend on it, or a fork of it
* I think the plugin-spec should remain separate from pluginstall -
pluginstall may implement features that aren't generally useful for all
plugin authors/users, and the spec may have suggestions that pluginstall
ignores. I don't think there's a ton of benefit for conflating the two. The
pluginstall README links directly to the spec - perhaps the spec can link
to pluginstall also, if the current structure is confusing
* again, the plugin-spec is liberally licensed and can be reproduced, in
full or in a modified form, in the Cordova docs or on the Apache wiki
On 11 September 2012 14:59, Filip Maj <fi...@adobe.com> wrote:
> Agree with everything that's been said in here.
>
> I will merge this stuff into the labs cordova-client tree.
>
> Thanks Michal + Mike!
>
> On 9/11/12 1:16 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >Dang, my markdown editor (Mou) has this nasty habit of auto-closing all
> >open brackets immediately. Anyway, good catches, pushed fixes for all 3.
> >
> >-Mike
> >
> >On Tue, Sep 11, 2012 at 2:02 PM, Michal Mocny <mm...@chromium.org>
> wrote:
> >
> >> I no longer see missing commits, very odd! I assume that they had just
> >> backed up from some older version in time and rolled changes forward or
> >> something..
> >>
> >> Anyway, final comments:
> >> * create <directory> [<id> []<name>]] -- spurious ']' (after "<id> [")
> >> * "scordova" -- spurious 's'
> >> * also noticed a missing space in the file and directory structure ascii
> >> tree before ".cordova/" (trivial detail, I know!)
> >>
> >> -Michal
> >>
> >>
> >> On Tue, Sep 11, 2012 at 1:48 PM, Mike Reinstein
> >><reinstein.mike@gmail.com
> >> >wrote:
> >>
> >> > Looks like Github is back to normal. Michal, I don't see any missing
> >> > commits though...maybe I forgot to include changes from your original
> >> > feedback? What seems to be missing?
> >> >
> >> > -Mike
> >> >
> >> > On Tue, Sep 11, 2012 at 11:32 AM, Mike Reinstein
> >> > <re...@gmail.com>wrote:
> >> >
> >> > > Oof, major service disruption in progress on github:
> >> > > https://status.github.com/
> >> > >
> >> > > I really hope my changes weren't reverted! Wish I could check. :(
> >> > >
> >> > > -Mike
> >> > >
> >> > >
> >> > > On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mmocny@chromium.org
> >> > >wrote:
> >> > >
> >> > >> Maybe I am getting lost with all the urls/branches listed here
> >> (*cough*
> >> > >> surprise *cough), but it seems as though all the changes made
> >>recently
> >> > >> have
> >> > >> been reverted (
> >> > >>
> >> >
> >>https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> > >> )?
> >> > >>
> >> > >> Anyway, I agree with changing the wiki to point to these new
> >> > instructions,
> >> > >> but am not sure where else those instructions may exist.
> >> > >>
> >> > >> Anyway, good job Mike, instructions are looking good.
> >> > >>
> >> > >> -Michal
> >> > >>
> >> > >>
> >> > >> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
> >> > >> <re...@gmail.com>wrote:
> >> > >>
> >> > >> > I'd like to propose we replace the contents of this wiki page
> >> > >> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> >> > simple
> >> > >> > note
> >> > >> > that points at the correct url "This documentation has merged
> >>into
> >> > >> >
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >> > >> >
> >> > >> > Are there any other copies of this doc in other places? Other
> >>forks
> >> > we
> >> > >> can
> >> > >> > eliminate to reduce confusion?
> >> > >> >
> >> > >> > Has anyone heard from Andrew Lunny recently? I still have my
> >>change
> >> > docs
> >> > >> > that I submitted as a pull request but havent gotten any
> >>feedback,
> >> and
> >> > >> it
> >> > >> > seems like he hasn't been active on github in a few weeks. I'd
> >> prefer
> >> > to
> >> > >> > get the changes for pluginstall merged in so I can remove my
> >>copy.
> >> > >> >
> >> > >> > -Mike
> >> > >> >
> >> > >> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
> >> > >> > <re...@gmail.com>wrote:
> >> > >> >
> >> > >> > > > Subcommand argument formats still look off a bit
> >> > >> > > Fixed
> >> > >> > >
> >> > >> > > > I think the $ is unneeded. All the other shell code
> >> > >> > > > examples don't include the leading shell character.
> >> > >> > >
> >> > >> > > Actually, the opposite. Every example did have leading $ except
> >> for
> >> > >> the
> >> > >> > > first usage, which was inconsistent. But I agree $ is
> >>essentially
> >> > just
> >> > >> > > noise and have removed all instances from the doc. :)
> >> > >> > >
> >> > >> > > It would be nice to clean up the Random notes section. I think
> >> there
> >> > >> may
> >> > >> > > be some context associated with those chat discussion snippets
> >> that
> >> > >> were
> >> > >> > > copy/pasted in, so expanding on those points would be helpful
> >>for
> >> > >> > everyone
> >> > >> > > else (including me.)
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <
> >> mmocny@chromium.org
> >> > >> > >wrote:
> >> > >> > >
> >> > >> > >> Subcommand argument formats still look off a bit, I think they
> >> > should
> >> > >> > look
> >> > >> > >> as follows:
> >> > >> > >>
> >> > >> > >> create <directory> [<id> [<name>]]
> >> > >> > >> platform ls
> >> > >> > >> platform add <platform>
> >> > >> > >> platform remove <platform>
> >> > >> > >> plugin ls
> >> > >> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here?
> >> Seems
> >> > >> > >> inconsistant with the other examples of add/remove)
> >> > >> > >> plugin remove <plugin>
> >> > >> > >> build
> >> > >> > >> emulate
> >> > >> > >>
> >> > >> > >>
> >> > >> > >>
> >> > >> > >> Also, in the line "you can access the tool via $ cordova" I
> >> think
> >> > >> the $
> >> > >> > >> is
> >> > >> > >> unneeded. All the other shell code examples don't include the
> >> > >> leading
> >> > >> > >> shell character. Alternatively we can add shell character to
> >>all
> >> > the
> >> > >> > >> other
> >> > >> > >> shell command examples.
> >> > >> > >>
> >> > >> > >>
> >> > >> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> >> > >> > >> <re...@gmail.com>wrote:
> >> > >> > >>
> >> > >> > >> > I've updated my copy of the README.md, pulling changes from
> >> > Filip,
> >> > >> > >> Michal,
> >> > >> > >> > and Brian:
> >> > >> > >> >
> >> > >> > >>
> >> > >> >
> >> > >>
> >> >
> >>https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> > >> > >> >
> >> > >> > >> > If I've missed anything please let me know.
> >> > >> > >> >
> >> > >> > >> > -Mike
> >> > >> > >> >
> >> > >> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <
> >> > >> mmocny@chromium.org>
> >> > >> > >> > wrote:
> >> > >> > >> >
> >> > >> > >> > > I'm still unsure what a "baked in" plugin/platform would
> >>be,
> >> in
> >> > >> that
> >> > >> > >> > > context. Anyway, its not super important as the actual
> >> > argument
> >> > >> > types
> >> > >> > >> > may
> >> > >> > >> > > change over time. The gist of it is just that you can
> >> > reference
> >> > >> a
> >> > >> > >> > > plugin/platform using various typical methods and I think
> >> that
> >> > >> point
> >> > >> > >> gets
> >> > >> > >> > > across well enough.
> >> > >> > >> > >
> >> > >> > >> > >
> >> > >> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b@brian.io
> >
> >> > >> wrote:
> >> > >> > >> > >
> >> > >> > >> > > > Considering the source I'd say 'baked' was intentional.
> >> > >> > >> > > >
> >> > >> > >> > > >
> >> > >> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> >> > >> > >> > > > <re...@gmail.com> wrote:
> >> > >> > >> > > > >> assumed to be a 'backed in' platform/plugin
> >> > >> > >> > > > >
> >> > >> > >> > > > > This must be a typo, eh? 'baked' was intended?
> >> > >> > >> > > > >
> >> > >> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <
> >> b@brian.io>
> >> > >> > wrote:
> >> > >> > >> > > > >
> >> > >> > >> > > > >> > * You will be able to access the client interface
> >> via: $
> >> > >> > >> > > ./bin/cordova
> >> > >> > >> > > > >> > * * suggest replacing ./ with
> >>$(CORDOVA_CLIENT_DIR)/
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> Agree...tho the npm install should be global (in
> >> > >> > /usr/local/bin)
> >> > >> > >> > > > >> ....maybe we say as much?
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > * Subcommands section
> >> > >> > >> > > > >> > * * Typical unix manpage style is to use [] to
> >> surround
> >> > >> > >> optional
> >> > >> > >> > > > >> arguments
> >> > >> > >> > > > >> > <> to surround explanations and nothing for
> >>keywords.
> >> > >> > Examples
> >> > >> > >> > that
> >> > >> > >> > > > need
> >> > >> > >> > > > >> > fixing include:
> >> > >> > >> > > > >> > * * * create <directory> [<id>] [<name>]
> >> > >> > >> > > > >> > * * * platform ls
> >> > >> > >> > > > >> > * * * platform add <platform>
> >> > >> > >> > > > >> > * * * etc
> >> > >> > >> > > > >> > * * even if we aren't aiming for manpage style
> >>here,
> >> > there
> >> > >> > >> > > > >> > are inconsistencies
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> Sure
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > * * File and Directory Structure ascii tree diagram
> >> > >> > >> > > > >> > * * * suggest appending / after directory names
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> +1
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > * * ... it's assumed to be a 'backed in'
> >> > platform/plugin.
> >> > >> > >> > Otherwise,
> >> > >> > >> > > > it's
> >> > >> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
> >> > >> > >> > > > >> > * * * Not sure what 'backed in' means here, nor
> >>how to
> >> > >> > identify
> >> > >> > >> > > > something
> >> > >> > >> > > > >> > as not being backed in so as to fallback to gzipped
> >> tar
> >> > >> > >> > > > >> > * * * Also wording sounds more like "else .. else"
> >> > >> instead of
> >> > >> > >> > "else
> >> > >> > >> > > > if ..
> >> > >> > >> > > > >> > else" (if that makes sense) :P
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> Ya not sure what this is about?
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
> >> > >> > >> > > > >> > * * * based on my understanding of the text, the
> >> > >> ios/android
> >> > >> > >> > > platforms
> >> > >> > >> > > > >> > should be subdirs of platforms/ and there should
> >>also
> >> > be a
> >> > >> > >> subdir
> >> > >> > >> > > > listed
> >> > >> > >> > > > >> in
> >> > >> > >> > > > >> > plugins/
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> Yes.
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > * * Running tests warning
> >> > >> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to
> >> have
> >> > >> > >> failing
> >> > >> > >> > > tests
> >> > >> > >> > > > >> > instead of assuming the reverse?
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> Yes.
> >> > >> > >> > > > >>
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> > Also, I will look into bash completions in some
> >>spare
> >> > >> cycles
> >> > >> > >> and
> >> > >> > >> > if
> >> > >> > >> > > it
> >> > >> > >> > > > >> > looks reasonable I may volunteer for the task.
> >>I've
> >> > been
> >> > >> > >> curious
> >> > >> > >> > to
> >> > >> > >> > > > >> learn
> >> > >> > >> > > > >> > how those work :)
> >> > >> > >> > > > >>
> >> > >> > >> > > > >> That'd be awesome...but I'm thinking in a future
> >> iteration
> >> > >> once
> >> > >> > >> the
> >> > >> > >> > > > >> actual CLI API is more solid. (But knock yourself
> >>out!)
> >> > >> > >> > > > >>
> >> > >> > >> > > >
> >> > >> > >> > >
> >> > >> > >> >
> >> > >> > >>
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Agree with everything that's been said in here.
I will merge this stuff into the labs cordova-client tree.
Thanks Michal + Mike!
On 9/11/12 1:16 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>Dang, my markdown editor (Mou) has this nasty habit of auto-closing all
>open brackets immediately. Anyway, good catches, pushed fixes for all 3.
>
>-Mike
>
>On Tue, Sep 11, 2012 at 2:02 PM, Michal Mocny <mm...@chromium.org> wrote:
>
>> I no longer see missing commits, very odd! I assume that they had just
>> backed up from some older version in time and rolled changes forward or
>> something..
>>
>> Anyway, final comments:
>> * create <directory> [<id> []<name>]] -- spurious ']' (after "<id> [")
>> * "scordova" -- spurious 's'
>> * also noticed a missing space in the file and directory structure ascii
>> tree before ".cordova/" (trivial detail, I know!)
>>
>> -Michal
>>
>>
>> On Tue, Sep 11, 2012 at 1:48 PM, Mike Reinstein
>><reinstein.mike@gmail.com
>> >wrote:
>>
>> > Looks like Github is back to normal. Michal, I don't see any missing
>> > commits though...maybe I forgot to include changes from your original
>> > feedback? What seems to be missing?
>> >
>> > -Mike
>> >
>> > On Tue, Sep 11, 2012 at 11:32 AM, Mike Reinstein
>> > <re...@gmail.com>wrote:
>> >
>> > > Oof, major service disruption in progress on github:
>> > > https://status.github.com/
>> > >
>> > > I really hope my changes weren't reverted! Wish I could check. :(
>> > >
>> > > -Mike
>> > >
>> > >
>> > > On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mmocny@chromium.org
>> > >wrote:
>> > >
>> > >> Maybe I am getting lost with all the urls/branches listed here
>> (*cough*
>> > >> surprise *cough), but it seems as though all the changes made
>>recently
>> > >> have
>> > >> been reverted (
>> > >>
>> >
>>https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> > >> )?
>> > >>
>> > >> Anyway, I agree with changing the wiki to point to these new
>> > instructions,
>> > >> but am not sure where else those instructions may exist.
>> > >>
>> > >> Anyway, good job Mike, instructions are looking good.
>> > >>
>> > >> -Michal
>> > >>
>> > >>
>> > >> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
>> > >> <re...@gmail.com>wrote:
>> > >>
>> > >> > I'd like to propose we replace the contents of this wiki page
>> > >> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
>> > simple
>> > >> > note
>> > >> > that points at the correct url "This documentation has merged
>>into
>> > >> >
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> > >> >
>> > >> > Are there any other copies of this doc in other places? Other
>>forks
>> > we
>> > >> can
>> > >> > eliminate to reduce confusion?
>> > >> >
>> > >> > Has anyone heard from Andrew Lunny recently? I still have my
>>change
>> > docs
>> > >> > that I submitted as a pull request but havent gotten any
>>feedback,
>> and
>> > >> it
>> > >> > seems like he hasn't been active on github in a few weeks. I'd
>> prefer
>> > to
>> > >> > get the changes for pluginstall merged in so I can remove my
>>copy.
>> > >> >
>> > >> > -Mike
>> > >> >
>> > >> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
>> > >> > <re...@gmail.com>wrote:
>> > >> >
>> > >> > > > Subcommand argument formats still look off a bit
>> > >> > > Fixed
>> > >> > >
>> > >> > > > I think the $ is unneeded. All the other shell code
>> > >> > > > examples don't include the leading shell character.
>> > >> > >
>> > >> > > Actually, the opposite. Every example did have leading $ except
>> for
>> > >> the
>> > >> > > first usage, which was inconsistent. But I agree $ is
>>essentially
>> > just
>> > >> > > noise and have removed all instances from the doc. :)
>> > >> > >
>> > >> > > It would be nice to clean up the Random notes section. I think
>> there
>> > >> may
>> > >> > > be some context associated with those chat discussion snippets
>> that
>> > >> were
>> > >> > > copy/pasted in, so expanding on those points would be helpful
>>for
>> > >> > everyone
>> > >> > > else (including me.)
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <
>> mmocny@chromium.org
>> > >> > >wrote:
>> > >> > >
>> > >> > >> Subcommand argument formats still look off a bit, I think they
>> > should
>> > >> > look
>> > >> > >> as follows:
>> > >> > >>
>> > >> > >> create <directory> [<id> [<name>]]
>> > >> > >> platform ls
>> > >> > >> platform add <platform>
>> > >> > >> platform remove <platform>
>> > >> > >> plugin ls
>> > >> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here?
>> Seems
>> > >> > >> inconsistant with the other examples of add/remove)
>> > >> > >> plugin remove <plugin>
>> > >> > >> build
>> > >> > >> emulate
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >> Also, in the line "you can access the tool via $ cordova" I
>> think
>> > >> the $
>> > >> > >> is
>> > >> > >> unneeded. All the other shell code examples don't include the
>> > >> leading
>> > >> > >> shell character. Alternatively we can add shell character to
>>all
>> > the
>> > >> > >> other
>> > >> > >> shell command examples.
>> > >> > >>
>> > >> > >>
>> > >> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
>> > >> > >> <re...@gmail.com>wrote:
>> > >> > >>
>> > >> > >> > I've updated my copy of the README.md, pulling changes from
>> > Filip,
>> > >> > >> Michal,
>> > >> > >> > and Brian:
>> > >> > >> >
>> > >> > >>
>> > >> >
>> > >>
>> >
>>https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> > >> > >> >
>> > >> > >> > If I've missed anything please let me know.
>> > >> > >> >
>> > >> > >> > -Mike
>> > >> > >> >
>> > >> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <
>> > >> mmocny@chromium.org>
>> > >> > >> > wrote:
>> > >> > >> >
>> > >> > >> > > I'm still unsure what a "baked in" plugin/platform would
>>be,
>> in
>> > >> that
>> > >> > >> > > context. Anyway, its not super important as the actual
>> > argument
>> > >> > types
>> > >> > >> > may
>> > >> > >> > > change over time. The gist of it is just that you can
>> > reference
>> > >> a
>> > >> > >> > > plugin/platform using various typical methods and I think
>> that
>> > >> point
>> > >> > >> gets
>> > >> > >> > > across well enough.
>> > >> > >> > >
>> > >> > >> > >
>> > >> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io>
>> > >> wrote:
>> > >> > >> > >
>> > >> > >> > > > Considering the source I'd say 'baked' was intentional.
>> > >> > >> > > >
>> > >> > >> > > >
>> > >> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
>> > >> > >> > > > <re...@gmail.com> wrote:
>> > >> > >> > > > >> assumed to be a 'backed in' platform/plugin
>> > >> > >> > > > >
>> > >> > >> > > > > This must be a typo, eh? 'baked' was intended?
>> > >> > >> > > > >
>> > >> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <
>> b@brian.io>
>> > >> > wrote:
>> > >> > >> > > > >
>> > >> > >> > > > >> > * You will be able to access the client interface
>> via: $
>> > >> > >> > > ./bin/cordova
>> > >> > >> > > > >> > * * suggest replacing ./ with
>>$(CORDOVA_CLIENT_DIR)/
>> > >> > >> > > > >>
>> > >> > >> > > > >> Agree...tho the npm install should be global (in
>> > >> > /usr/local/bin)
>> > >> > >> > > > >> ....maybe we say as much?
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > * Subcommands section
>> > >> > >> > > > >> > * * Typical unix manpage style is to use [] to
>> surround
>> > >> > >> optional
>> > >> > >> > > > >> arguments
>> > >> > >> > > > >> > <> to surround explanations and nothing for
>>keywords.
>> > >> > Examples
>> > >> > >> > that
>> > >> > >> > > > need
>> > >> > >> > > > >> > fixing include:
>> > >> > >> > > > >> > * * * create <directory> [<id>] [<name>]
>> > >> > >> > > > >> > * * * platform ls
>> > >> > >> > > > >> > * * * platform add <platform>
>> > >> > >> > > > >> > * * * etc
>> > >> > >> > > > >> > * * even if we aren't aiming for manpage style
>>here,
>> > there
>> > >> > >> > > > >> > are inconsistencies
>> > >> > >> > > > >>
>> > >> > >> > > > >> Sure
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > * * File and Directory Structure ascii tree diagram
>> > >> > >> > > > >> > * * * suggest appending / after directory names
>> > >> > >> > > > >>
>> > >> > >> > > > >> +1
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > * * ... it's assumed to be a 'backed in'
>> > platform/plugin.
>> > >> > >> > Otherwise,
>> > >> > >> > > > it's
>> > >> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
>> > >> > >> > > > >> > * * * Not sure what 'backed in' means here, nor
>>how to
>> > >> > identify
>> > >> > >> > > > something
>> > >> > >> > > > >> > as not being backed in so as to fallback to gzipped
>> tar
>> > >> > >> > > > >> > * * * Also wording sounds more like "else .. else"
>> > >> instead of
>> > >> > >> > "else
>> > >> > >> > > > if ..
>> > >> > >> > > > >> > else" (if that makes sense) :P
>> > >> > >> > > > >>
>> > >> > >> > > > >> Ya not sure what this is about?
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
>> > >> > >> > > > >> > * * * based on my understanding of the text, the
>> > >> ios/android
>> > >> > >> > > platforms
>> > >> > >> > > > >> > should be subdirs of platforms/ and there should
>>also
>> > be a
>> > >> > >> subdir
>> > >> > >> > > > listed
>> > >> > >> > > > >> in
>> > >> > >> > > > >> > plugins/
>> > >> > >> > > > >>
>> > >> > >> > > > >> Yes.
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > * * Running tests warning
>> > >> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to
>> have
>> > >> > >> failing
>> > >> > >> > > tests
>> > >> > >> > > > >> > instead of assuming the reverse?
>> > >> > >> > > > >>
>> > >> > >> > > > >> Yes.
>> > >> > >> > > > >>
>> > >> > >> > > > >>
>> > >> > >> > > > >> > Also, I will look into bash completions in some
>>spare
>> > >> cycles
>> > >> > >> and
>> > >> > >> > if
>> > >> > >> > > it
>> > >> > >> > > > >> > looks reasonable I may volunteer for the task.
>>I've
>> > been
>> > >> > >> curious
>> > >> > >> > to
>> > >> > >> > > > >> learn
>> > >> > >> > > > >> > how those work :)
>> > >> > >> > > > >>
>> > >> > >> > > > >> That'd be awesome...but I'm thinking in a future
>> iteration
>> > >> once
>> > >> > >> the
>> > >> > >> > > > >> actual CLI API is more solid. (But knock yourself
>>out!)
>> > >> > >> > > > >>
>> > >> > >> > > >
>> > >> > >> > >
>> > >> > >> >
>> > >> > >>
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Dang, my markdown editor (Mou) has this nasty habit of auto-closing all
open brackets immediately. Anyway, good catches, pushed fixes for all 3.
-Mike
On Tue, Sep 11, 2012 at 2:02 PM, Michal Mocny <mm...@chromium.org> wrote:
> I no longer see missing commits, very odd! I assume that they had just
> backed up from some older version in time and rolled changes forward or
> something..
>
> Anyway, final comments:
> * create <directory> [<id> []<name>]] -- spurious ']' (after "<id> [")
> * "scordova" -- spurious 's'
> * also noticed a missing space in the file and directory structure ascii
> tree before ".cordova/" (trivial detail, I know!)
>
> -Michal
>
>
> On Tue, Sep 11, 2012 at 1:48 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > Looks like Github is back to normal. Michal, I don't see any missing
> > commits though...maybe I forgot to include changes from your original
> > feedback? What seems to be missing?
> >
> > -Mike
> >
> > On Tue, Sep 11, 2012 at 11:32 AM, Mike Reinstein
> > <re...@gmail.com>wrote:
> >
> > > Oof, major service disruption in progress on github:
> > > https://status.github.com/
> > >
> > > I really hope my changes weren't reverted! Wish I could check. :(
> > >
> > > -Mike
> > >
> > >
> > > On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mmocny@chromium.org
> > >wrote:
> > >
> > >> Maybe I am getting lost with all the urls/branches listed here
> (*cough*
> > >> surprise *cough), but it seems as though all the changes made recently
> > >> have
> > >> been reverted (
> > >>
> > https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> > >> )?
> > >>
> > >> Anyway, I agree with changing the wiki to point to these new
> > instructions,
> > >> but am not sure where else those instructions may exist.
> > >>
> > >> Anyway, good job Mike, instructions are looking good.
> > >>
> > >> -Michal
> > >>
> > >>
> > >> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
> > >> <re...@gmail.com>wrote:
> > >>
> > >> > I'd like to propose we replace the contents of this wiki page
> > >> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> > simple
> > >> > note
> > >> > that points at the correct url "This documentation has merged into
> > >> >
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> > >> >
> > >> > Are there any other copies of this doc in other places? Other forks
> > we
> > >> can
> > >> > eliminate to reduce confusion?
> > >> >
> > >> > Has anyone heard from Andrew Lunny recently? I still have my change
> > docs
> > >> > that I submitted as a pull request but havent gotten any feedback,
> and
> > >> it
> > >> > seems like he hasn't been active on github in a few weeks. I'd
> prefer
> > to
> > >> > get the changes for pluginstall merged in so I can remove my copy.
> > >> >
> > >> > -Mike
> > >> >
> > >> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
> > >> > <re...@gmail.com>wrote:
> > >> >
> > >> > > > Subcommand argument formats still look off a bit
> > >> > > Fixed
> > >> > >
> > >> > > > I think the $ is unneeded. All the other shell code
> > >> > > > examples don't include the leading shell character.
> > >> > >
> > >> > > Actually, the opposite. Every example did have leading $ except
> for
> > >> the
> > >> > > first usage, which was inconsistent. But I agree $ is essentially
> > just
> > >> > > noise and have removed all instances from the doc. :)
> > >> > >
> > >> > > It would be nice to clean up the Random notes section. I think
> there
> > >> may
> > >> > > be some context associated with those chat discussion snippets
> that
> > >> were
> > >> > > copy/pasted in, so expanding on those points would be helpful for
> > >> > everyone
> > >> > > else (including me.)
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <
> mmocny@chromium.org
> > >> > >wrote:
> > >> > >
> > >> > >> Subcommand argument formats still look off a bit, I think they
> > should
> > >> > look
> > >> > >> as follows:
> > >> > >>
> > >> > >> create <directory> [<id> [<name>]]
> > >> > >> platform ls
> > >> > >> platform add <platform>
> > >> > >> platform remove <platform>
> > >> > >> plugin ls
> > >> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here?
> Seems
> > >> > >> inconsistant with the other examples of add/remove)
> > >> > >> plugin remove <plugin>
> > >> > >> build
> > >> > >> emulate
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> Also, in the line "you can access the tool via $ cordova" I
> think
> > >> the $
> > >> > >> is
> > >> > >> unneeded. All the other shell code examples don't include the
> > >> leading
> > >> > >> shell character. Alternatively we can add shell character to all
> > the
> > >> > >> other
> > >> > >> shell command examples.
> > >> > >>
> > >> > >>
> > >> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> > >> > >> <re...@gmail.com>wrote:
> > >> > >>
> > >> > >> > I've updated my copy of the README.md, pulling changes from
> > Filip,
> > >> > >> Michal,
> > >> > >> > and Brian:
> > >> > >> >
> > >> > >>
> > >> >
> > >>
> > https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> > >> > >> >
> > >> > >> > If I've missed anything please let me know.
> > >> > >> >
> > >> > >> > -Mike
> > >> > >> >
> > >> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <
> > >> mmocny@chromium.org>
> > >> > >> > wrote:
> > >> > >> >
> > >> > >> > > I'm still unsure what a "baked in" plugin/platform would be,
> in
> > >> that
> > >> > >> > > context. Anyway, its not super important as the actual
> > argument
> > >> > types
> > >> > >> > may
> > >> > >> > > change over time. The gist of it is just that you can
> > reference
> > >> a
> > >> > >> > > plugin/platform using various typical methods and I think
> that
> > >> point
> > >> > >> gets
> > >> > >> > > across well enough.
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io>
> > >> wrote:
> > >> > >> > >
> > >> > >> > > > Considering the source I'd say 'baked' was intentional.
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> > >> > >> > > > <re...@gmail.com> wrote:
> > >> > >> > > > >> assumed to be a 'backed in' platform/plugin
> > >> > >> > > > >
> > >> > >> > > > > This must be a typo, eh? 'baked' was intended?
> > >> > >> > > > >
> > >> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <
> b@brian.io>
> > >> > wrote:
> > >> > >> > > > >
> > >> > >> > > > >> > * You will be able to access the client interface
> via: $
> > >> > >> > > ./bin/cordova
> > >> > >> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> > >> > >> > > > >>
> > >> > >> > > > >> Agree...tho the npm install should be global (in
> > >> > /usr/local/bin)
> > >> > >> > > > >> ....maybe we say as much?
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > * Subcommands section
> > >> > >> > > > >> > * * Typical unix manpage style is to use [] to
> surround
> > >> > >> optional
> > >> > >> > > > >> arguments
> > >> > >> > > > >> > <> to surround explanations and nothing for keywords.
> > >> > Examples
> > >> > >> > that
> > >> > >> > > > need
> > >> > >> > > > >> > fixing include:
> > >> > >> > > > >> > * * * create <directory> [<id>] [<name>]
> > >> > >> > > > >> > * * * platform ls
> > >> > >> > > > >> > * * * platform add <platform>
> > >> > >> > > > >> > * * * etc
> > >> > >> > > > >> > * * even if we aren't aiming for manpage style here,
> > there
> > >> > >> > > > >> > are inconsistencies
> > >> > >> > > > >>
> > >> > >> > > > >> Sure
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > * * File and Directory Structure ascii tree diagram
> > >> > >> > > > >> > * * * suggest appending / after directory names
> > >> > >> > > > >>
> > >> > >> > > > >> +1
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > * * ... it's assumed to be a 'backed in'
> > platform/plugin.
> > >> > >> > Otherwise,
> > >> > >> > > > it's
> > >> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
> > >> > >> > > > >> > * * * Not sure what 'backed in' means here, nor how to
> > >> > identify
> > >> > >> > > > something
> > >> > >> > > > >> > as not being backed in so as to fallback to gzipped
> tar
> > >> > >> > > > >> > * * * Also wording sounds more like "else .. else"
> > >> instead of
> > >> > >> > "else
> > >> > >> > > > if ..
> > >> > >> > > > >> > else" (if that makes sense) :P
> > >> > >> > > > >>
> > >> > >> > > > >> Ya not sure what this is about?
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
> > >> > >> > > > >> > * * * based on my understanding of the text, the
> > >> ios/android
> > >> > >> > > platforms
> > >> > >> > > > >> > should be subdirs of platforms/ and there should also
> > be a
> > >> > >> subdir
> > >> > >> > > > listed
> > >> > >> > > > >> in
> > >> > >> > > > >> > plugins/
> > >> > >> > > > >>
> > >> > >> > > > >> Yes.
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > * * Running tests warning
> > >> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to
> have
> > >> > >> failing
> > >> > >> > > tests
> > >> > >> > > > >> > instead of assuming the reverse?
> > >> > >> > > > >>
> > >> > >> > > > >> Yes.
> > >> > >> > > > >>
> > >> > >> > > > >>
> > >> > >> > > > >> > Also, I will look into bash completions in some spare
> > >> cycles
> > >> > >> and
> > >> > >> > if
> > >> > >> > > it
> > >> > >> > > > >> > looks reasonable I may volunteer for the task. I've
> > been
> > >> > >> curious
> > >> > >> > to
> > >> > >> > > > >> learn
> > >> > >> > > > >> > how those work :)
> > >> > >> > > > >>
> > >> > >> > > > >> That'd be awesome...but I'm thinking in a future
> iteration
> > >> once
> > >> > >> the
> > >> > >> > > > >> actual CLI API is more solid. (But knock yourself out!)
> > >> > >> > > > >>
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
I no longer see missing commits, very odd! I assume that they had just
backed up from some older version in time and rolled changes forward or
something..
Anyway, final comments:
* create <directory> [<id> []<name>]] -- spurious ']' (after "<id> [")
* "scordova" -- spurious 's'
* also noticed a missing space in the file and directory structure ascii
tree before ".cordova/" (trivial detail, I know!)
-Michal
On Tue, Sep 11, 2012 at 1:48 PM, Mike Reinstein <re...@gmail.com>wrote:
> Looks like Github is back to normal. Michal, I don't see any missing
> commits though...maybe I forgot to include changes from your original
> feedback? What seems to be missing?
>
> -Mike
>
> On Tue, Sep 11, 2012 at 11:32 AM, Mike Reinstein
> <re...@gmail.com>wrote:
>
> > Oof, major service disruption in progress on github:
> > https://status.github.com/
> >
> > I really hope my changes weren't reverted! Wish I could check. :(
> >
> > -Mike
> >
> >
> > On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mmocny@chromium.org
> >wrote:
> >
> >> Maybe I am getting lost with all the urls/branches listed here (*cough*
> >> surprise *cough), but it seems as though all the changes made recently
> >> have
> >> been reverted (
> >>
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> )?
> >>
> >> Anyway, I agree with changing the wiki to point to these new
> instructions,
> >> but am not sure where else those instructions may exist.
> >>
> >> Anyway, good job Mike, instructions are looking good.
> >>
> >> -Michal
> >>
> >>
> >> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
> >> <re...@gmail.com>wrote:
> >>
> >> > I'd like to propose we replace the contents of this wiki page
> >> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> simple
> >> > note
> >> > that points at the correct url "This documentation has merged into
> >> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >> >
> >> > Are there any other copies of this doc in other places? Other forks
> we
> >> can
> >> > eliminate to reduce confusion?
> >> >
> >> > Has anyone heard from Andrew Lunny recently? I still have my change
> docs
> >> > that I submitted as a pull request but havent gotten any feedback, and
> >> it
> >> > seems like he hasn't been active on github in a few weeks. I'd prefer
> to
> >> > get the changes for pluginstall merged in so I can remove my copy.
> >> >
> >> > -Mike
> >> >
> >> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
> >> > <re...@gmail.com>wrote:
> >> >
> >> > > > Subcommand argument formats still look off a bit
> >> > > Fixed
> >> > >
> >> > > > I think the $ is unneeded. All the other shell code
> >> > > > examples don't include the leading shell character.
> >> > >
> >> > > Actually, the opposite. Every example did have leading $ except for
> >> the
> >> > > first usage, which was inconsistent. But I agree $ is essentially
> just
> >> > > noise and have removed all instances from the doc. :)
> >> > >
> >> > > It would be nice to clean up the Random notes section. I think there
> >> may
> >> > > be some context associated with those chat discussion snippets that
> >> were
> >> > > copy/pasted in, so expanding on those points would be helpful for
> >> > everyone
> >> > > else (including me.)
> >> > >
> >> > >
> >> > >
> >> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mmocny@chromium.org
> >> > >wrote:
> >> > >
> >> > >> Subcommand argument formats still look off a bit, I think they
> should
> >> > look
> >> > >> as follows:
> >> > >>
> >> > >> create <directory> [<id> [<name>]]
> >> > >> platform ls
> >> > >> platform add <platform>
> >> > >> platform remove <platform>
> >> > >> plugin ls
> >> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
> >> > >> inconsistant with the other examples of add/remove)
> >> > >> plugin remove <plugin>
> >> > >> build
> >> > >> emulate
> >> > >>
> >> > >>
> >> > >>
> >> > >> Also, in the line "you can access the tool via $ cordova" I think
> >> the $
> >> > >> is
> >> > >> unneeded. All the other shell code examples don't include the
> >> leading
> >> > >> shell character. Alternatively we can add shell character to all
> the
> >> > >> other
> >> > >> shell command examples.
> >> > >>
> >> > >>
> >> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> >> > >> <re...@gmail.com>wrote:
> >> > >>
> >> > >> > I've updated my copy of the README.md, pulling changes from
> Filip,
> >> > >> Michal,
> >> > >> > and Brian:
> >> > >> >
> >> > >>
> >> >
> >>
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> > >> >
> >> > >> > If I've missed anything please let me know.
> >> > >> >
> >> > >> > -Mike
> >> > >> >
> >> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <
> >> mmocny@chromium.org>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > I'm still unsure what a "baked in" plugin/platform would be, in
> >> that
> >> > >> > > context. Anyway, its not super important as the actual
> argument
> >> > types
> >> > >> > may
> >> > >> > > change over time. The gist of it is just that you can
> reference
> >> a
> >> > >> > > plugin/platform using various typical methods and I think that
> >> point
> >> > >> gets
> >> > >> > > across well enough.
> >> > >> > >
> >> > >> > >
> >> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io>
> >> wrote:
> >> > >> > >
> >> > >> > > > Considering the source I'd say 'baked' was intentional.
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> >> > >> > > > <re...@gmail.com> wrote:
> >> > >> > > > >> assumed to be a 'backed in' platform/plugin
> >> > >> > > > >
> >> > >> > > > > This must be a typo, eh? 'baked' was intended?
> >> > >> > > > >
> >> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io>
> >> > wrote:
> >> > >> > > > >
> >> > >> > > > >> > * You will be able to access the client interface via: $
> >> > >> > > ./bin/cordova
> >> > >> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> >> > >> > > > >>
> >> > >> > > > >> Agree...tho the npm install should be global (in
> >> > /usr/local/bin)
> >> > >> > > > >> ....maybe we say as much?
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > * Subcommands section
> >> > >> > > > >> > * * Typical unix manpage style is to use [] to surround
> >> > >> optional
> >> > >> > > > >> arguments
> >> > >> > > > >> > <> to surround explanations and nothing for keywords.
> >> > Examples
> >> > >> > that
> >> > >> > > > need
> >> > >> > > > >> > fixing include:
> >> > >> > > > >> > * * * create <directory> [<id>] [<name>]
> >> > >> > > > >> > * * * platform ls
> >> > >> > > > >> > * * * platform add <platform>
> >> > >> > > > >> > * * * etc
> >> > >> > > > >> > * * even if we aren't aiming for manpage style here,
> there
> >> > >> > > > >> > are inconsistencies
> >> > >> > > > >>
> >> > >> > > > >> Sure
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > * * File and Directory Structure ascii tree diagram
> >> > >> > > > >> > * * * suggest appending / after directory names
> >> > >> > > > >>
> >> > >> > > > >> +1
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > * * ... it's assumed to be a 'backed in'
> platform/plugin.
> >> > >> > Otherwise,
> >> > >> > > > it's
> >> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
> >> > >> > > > >> > * * * Not sure what 'backed in' means here, nor how to
> >> > identify
> >> > >> > > > something
> >> > >> > > > >> > as not being backed in so as to fallback to gzipped tar
> >> > >> > > > >> > * * * Also wording sounds more like "else .. else"
> >> instead of
> >> > >> > "else
> >> > >> > > > if ..
> >> > >> > > > >> > else" (if that makes sense) :P
> >> > >> > > > >>
> >> > >> > > > >> Ya not sure what this is about?
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
> >> > >> > > > >> > * * * based on my understanding of the text, the
> >> ios/android
> >> > >> > > platforms
> >> > >> > > > >> > should be subdirs of platforms/ and there should also
> be a
> >> > >> subdir
> >> > >> > > > listed
> >> > >> > > > >> in
> >> > >> > > > >> > plugins/
> >> > >> > > > >>
> >> > >> > > > >> Yes.
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > * * Running tests warning
> >> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to have
> >> > >> failing
> >> > >> > > tests
> >> > >> > > > >> > instead of assuming the reverse?
> >> > >> > > > >>
> >> > >> > > > >> Yes.
> >> > >> > > > >>
> >> > >> > > > >>
> >> > >> > > > >> > Also, I will look into bash completions in some spare
> >> cycles
> >> > >> and
> >> > >> > if
> >> > >> > > it
> >> > >> > > > >> > looks reasonable I may volunteer for the task. I've
> been
> >> > >> curious
> >> > >> > to
> >> > >> > > > >> learn
> >> > >> > > > >> > how those work :)
> >> > >> > > > >>
> >> > >> > > > >> That'd be awesome...but I'm thinking in a future iteration
> >> once
> >> > >> the
> >> > >> > > > >> actual CLI API is more solid. (But knock yourself out!)
> >> > >> > > > >>
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> > >
> >> >
> >>
> >
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Looks like Github is back to normal. Michal, I don't see any missing
commits though...maybe I forgot to include changes from your original
feedback? What seems to be missing?
-Mike
On Tue, Sep 11, 2012 at 11:32 AM, Mike Reinstein
<re...@gmail.com>wrote:
> Oof, major service disruption in progress on github:
> https://status.github.com/
>
> I really hope my changes weren't reverted! Wish I could check. :(
>
> -Mike
>
>
> On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mm...@chromium.org>wrote:
>
>> Maybe I am getting lost with all the urls/branches listed here (*cough*
>> surprise *cough), but it seems as though all the changes made recently
>> have
>> been reverted (
>> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> )?
>>
>> Anyway, I agree with changing the wiki to point to these new instructions,
>> but am not sure where else those instructions may exist.
>>
>> Anyway, good job Mike, instructions are looking good.
>>
>> -Michal
>>
>>
>> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
>> <re...@gmail.com>wrote:
>>
>> > I'd like to propose we replace the contents of this wiki page
>> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
>> > note
>> > that points at the correct url "This documentation has merged into
>> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> >
>> > Are there any other copies of this doc in other places? Other forks we
>> can
>> > eliminate to reduce confusion?
>> >
>> > Has anyone heard from Andrew Lunny recently? I still have my change docs
>> > that I submitted as a pull request but havent gotten any feedback, and
>> it
>> > seems like he hasn't been active on github in a few weeks. I'd prefer to
>> > get the changes for pluginstall merged in so I can remove my copy.
>> >
>> > -Mike
>> >
>> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
>> > <re...@gmail.com>wrote:
>> >
>> > > > Subcommand argument formats still look off a bit
>> > > Fixed
>> > >
>> > > > I think the $ is unneeded. All the other shell code
>> > > > examples don't include the leading shell character.
>> > >
>> > > Actually, the opposite. Every example did have leading $ except for
>> the
>> > > first usage, which was inconsistent. But I agree $ is essentially just
>> > > noise and have removed all instances from the doc. :)
>> > >
>> > > It would be nice to clean up the Random notes section. I think there
>> may
>> > > be some context associated with those chat discussion snippets that
>> were
>> > > copy/pasted in, so expanding on those points would be helpful for
>> > everyone
>> > > else (including me.)
>> > >
>> > >
>> > >
>> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mmocny@chromium.org
>> > >wrote:
>> > >
>> > >> Subcommand argument formats still look off a bit, I think they should
>> > look
>> > >> as follows:
>> > >>
>> > >> create <directory> [<id> [<name>]]
>> > >> platform ls
>> > >> platform add <platform>
>> > >> platform remove <platform>
>> > >> plugin ls
>> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
>> > >> inconsistant with the other examples of add/remove)
>> > >> plugin remove <plugin>
>> > >> build
>> > >> emulate
>> > >>
>> > >>
>> > >>
>> > >> Also, in the line "you can access the tool via $ cordova" I think
>> the $
>> > >> is
>> > >> unneeded. All the other shell code examples don't include the
>> leading
>> > >> shell character. Alternatively we can add shell character to all the
>> > >> other
>> > >> shell command examples.
>> > >>
>> > >>
>> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
>> > >> <re...@gmail.com>wrote:
>> > >>
>> > >> > I've updated my copy of the README.md, pulling changes from Filip,
>> > >> Michal,
>> > >> > and Brian:
>> > >> >
>> > >>
>> >
>> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> > >> >
>> > >> > If I've missed anything please let me know.
>> > >> >
>> > >> > -Mike
>> > >> >
>> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <
>> mmocny@chromium.org>
>> > >> > wrote:
>> > >> >
>> > >> > > I'm still unsure what a "baked in" plugin/platform would be, in
>> that
>> > >> > > context. Anyway, its not super important as the actual argument
>> > types
>> > >> > may
>> > >> > > change over time. The gist of it is just that you can reference
>> a
>> > >> > > plugin/platform using various typical methods and I think that
>> point
>> > >> gets
>> > >> > > across well enough.
>> > >> > >
>> > >> > >
>> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io>
>> wrote:
>> > >> > >
>> > >> > > > Considering the source I'd say 'baked' was intentional.
>> > >> > > >
>> > >> > > >
>> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
>> > >> > > > <re...@gmail.com> wrote:
>> > >> > > > >> assumed to be a 'backed in' platform/plugin
>> > >> > > > >
>> > >> > > > > This must be a typo, eh? 'baked' was intended?
>> > >> > > > >
>> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io>
>> > wrote:
>> > >> > > > >
>> > >> > > > >> > * You will be able to access the client interface via: $
>> > >> > > ./bin/cordova
>> > >> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
>> > >> > > > >>
>> > >> > > > >> Agree...tho the npm install should be global (in
>> > /usr/local/bin)
>> > >> > > > >> ....maybe we say as much?
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > * Subcommands section
>> > >> > > > >> > * * Typical unix manpage style is to use [] to surround
>> > >> optional
>> > >> > > > >> arguments
>> > >> > > > >> > <> to surround explanations and nothing for keywords.
>> > Examples
>> > >> > that
>> > >> > > > need
>> > >> > > > >> > fixing include:
>> > >> > > > >> > * * * create <directory> [<id>] [<name>]
>> > >> > > > >> > * * * platform ls
>> > >> > > > >> > * * * platform add <platform>
>> > >> > > > >> > * * * etc
>> > >> > > > >> > * * even if we aren't aiming for manpage style here, there
>> > >> > > > >> > are inconsistencies
>> > >> > > > >>
>> > >> > > > >> Sure
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > * * File and Directory Structure ascii tree diagram
>> > >> > > > >> > * * * suggest appending / after directory names
>> > >> > > > >>
>> > >> > > > >> +1
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
>> > >> > Otherwise,
>> > >> > > > it's
>> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
>> > >> > > > >> > * * * Not sure what 'backed in' means here, nor how to
>> > identify
>> > >> > > > something
>> > >> > > > >> > as not being backed in so as to fallback to gzipped tar
>> > >> > > > >> > * * * Also wording sounds more like "else .. else"
>> instead of
>> > >> > "else
>> > >> > > > if ..
>> > >> > > > >> > else" (if that makes sense) :P
>> > >> > > > >>
>> > >> > > > >> Ya not sure what this is about?
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
>> > >> > > > >> > * * * based on my understanding of the text, the
>> ios/android
>> > >> > > platforms
>> > >> > > > >> > should be subdirs of platforms/ and there should also be a
>> > >> subdir
>> > >> > > > listed
>> > >> > > > >> in
>> > >> > > > >> > plugins/
>> > >> > > > >>
>> > >> > > > >> Yes.
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > * * Running tests warning
>> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to have
>> > >> failing
>> > >> > > tests
>> > >> > > > >> > instead of assuming the reverse?
>> > >> > > > >>
>> > >> > > > >> Yes.
>> > >> > > > >>
>> > >> > > > >>
>> > >> > > > >> > Also, I will look into bash completions in some spare
>> cycles
>> > >> and
>> > >> > if
>> > >> > > it
>> > >> > > > >> > looks reasonable I may volunteer for the task. I've been
>> > >> curious
>> > >> > to
>> > >> > > > >> learn
>> > >> > > > >> > how those work :)
>> > >> > > > >>
>> > >> > > > >> That'd be awesome...but I'm thinking in a future iteration
>> once
>> > >> the
>> > >> > > > >> actual CLI API is more solid. (But knock yourself out!)
>> > >> > > > >>
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Oof, major service disruption in progress on github:
https://status.github.com/
I really hope my changes weren't reverted! Wish I could check. :(
-Mike
On Tue, Sep 11, 2012 at 11:26 AM, Michal Mocny <mm...@chromium.org> wrote:
> Maybe I am getting lost with all the urls/branches listed here (*cough*
> surprise *cough), but it seems as though all the changes made recently have
> been reverted (
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client)?
>
> Anyway, I agree with changing the wiki to point to these new instructions,
> but am not sure where else those instructions may exist.
>
> Anyway, good job Mike, instructions are looking good.
>
> -Michal
>
>
> On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
> <re...@gmail.com>wrote:
>
> > I'd like to propose we replace the contents of this wiki page
> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
> > note
> > that points at the correct url "This documentation has merged into
> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >
> > Are there any other copies of this doc in other places? Other forks we
> can
> > eliminate to reduce confusion?
> >
> > Has anyone heard from Andrew Lunny recently? I still have my change docs
> > that I submitted as a pull request but havent gotten any feedback, and it
> > seems like he hasn't been active on github in a few weeks. I'd prefer to
> > get the changes for pluginstall merged in so I can remove my copy.
> >
> > -Mike
> >
> > On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
> > <re...@gmail.com>wrote:
> >
> > > > Subcommand argument formats still look off a bit
> > > Fixed
> > >
> > > > I think the $ is unneeded. All the other shell code
> > > > examples don't include the leading shell character.
> > >
> > > Actually, the opposite. Every example did have leading $ except for the
> > > first usage, which was inconsistent. But I agree $ is essentially just
> > > noise and have removed all instances from the doc. :)
> > >
> > > It would be nice to clean up the Random notes section. I think there
> may
> > > be some context associated with those chat discussion snippets that
> were
> > > copy/pasted in, so expanding on those points would be helpful for
> > everyone
> > > else (including me.)
> > >
> > >
> > >
> > > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mmocny@chromium.org
> > >wrote:
> > >
> > >> Subcommand argument formats still look off a bit, I think they should
> > look
> > >> as follows:
> > >>
> > >> create <directory> [<id> [<name>]]
> > >> platform ls
> > >> platform add <platform>
> > >> platform remove <platform>
> > >> plugin ls
> > >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
> > >> inconsistant with the other examples of add/remove)
> > >> plugin remove <plugin>
> > >> build
> > >> emulate
> > >>
> > >>
> > >>
> > >> Also, in the line "you can access the tool via $ cordova" I think
> the $
> > >> is
> > >> unneeded. All the other shell code examples don't include the leading
> > >> shell character. Alternatively we can add shell character to all the
> > >> other
> > >> shell command examples.
> > >>
> > >>
> > >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> > >> <re...@gmail.com>wrote:
> > >>
> > >> > I've updated my copy of the README.md, pulling changes from Filip,
> > >> Michal,
> > >> > and Brian:
> > >> >
> > >>
> > https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> > >> >
> > >> > If I've missed anything please let me know.
> > >> >
> > >> > -Mike
> > >> >
> > >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mmocny@chromium.org
> >
> > >> > wrote:
> > >> >
> > >> > > I'm still unsure what a "baked in" plugin/platform would be, in
> that
> > >> > > context. Anyway, its not super important as the actual argument
> > types
> > >> > may
> > >> > > change over time. The gist of it is just that you can reference a
> > >> > > plugin/platform using various typical methods and I think that
> point
> > >> gets
> > >> > > across well enough.
> > >> > >
> > >> > >
> > >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
> > >> > >
> > >> > > > Considering the source I'd say 'baked' was intentional.
> > >> > > >
> > >> > > >
> > >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> > >> > > > <re...@gmail.com> wrote:
> > >> > > > >> assumed to be a 'backed in' platform/plugin
> > >> > > > >
> > >> > > > > This must be a typo, eh? 'baked' was intended?
> > >> > > > >
> > >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io>
> > wrote:
> > >> > > > >
> > >> > > > >> > * You will be able to access the client interface via: $
> > >> > > ./bin/cordova
> > >> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> > >> > > > >>
> > >> > > > >> Agree...tho the npm install should be global (in
> > /usr/local/bin)
> > >> > > > >> ....maybe we say as much?
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > * Subcommands section
> > >> > > > >> > * * Typical unix manpage style is to use [] to surround
> > >> optional
> > >> > > > >> arguments
> > >> > > > >> > <> to surround explanations and nothing for keywords.
> > Examples
> > >> > that
> > >> > > > need
> > >> > > > >> > fixing include:
> > >> > > > >> > * * * create <directory> [<id>] [<name>]
> > >> > > > >> > * * * platform ls
> > >> > > > >> > * * * platform add <platform>
> > >> > > > >> > * * * etc
> > >> > > > >> > * * even if we aren't aiming for manpage style here, there
> > >> > > > >> > are inconsistencies
> > >> > > > >>
> > >> > > > >> Sure
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > * * File and Directory Structure ascii tree diagram
> > >> > > > >> > * * * suggest appending / after directory names
> > >> > > > >>
> > >> > > > >> +1
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
> > >> > Otherwise,
> > >> > > > it's
> > >> > > > >> > assumed to be a URL to a gzipped tar archive...
> > >> > > > >> > * * * Not sure what 'backed in' means here, nor how to
> > identify
> > >> > > > something
> > >> > > > >> > as not being backed in so as to fallback to gzipped tar
> > >> > > > >> > * * * Also wording sounds more like "else .. else" instead
> of
> > >> > "else
> > >> > > > if ..
> > >> > > > >> > else" (if that makes sense) :P
> > >> > > > >>
> > >> > > > >> Ya not sure what this is about?
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > * * KewlApp directory structure ascii tree diagram
> > >> > > > >> > * * * based on my understanding of the text, the
> ios/android
> > >> > > platforms
> > >> > > > >> > should be subdirs of platforms/ and there should also be a
> > >> subdir
> > >> > > > listed
> > >> > > > >> in
> > >> > > > >> > plugins/
> > >> > > > >>
> > >> > > > >> Yes.
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > * * Running tests warning
> > >> > > > >> > * * * Perhaps explain how to bootstrap so as not to have
> > >> failing
> > >> > > tests
> > >> > > > >> > instead of assuming the reverse?
> > >> > > > >>
> > >> > > > >> Yes.
> > >> > > > >>
> > >> > > > >>
> > >> > > > >> > Also, I will look into bash completions in some spare
> cycles
> > >> and
> > >> > if
> > >> > > it
> > >> > > > >> > looks reasonable I may volunteer for the task. I've been
> > >> curious
> > >> > to
> > >> > > > >> learn
> > >> > > > >> > how those work :)
> > >> > > > >>
> > >> > > > >> That'd be awesome...but I'm thinking in a future iteration
> once
> > >> the
> > >> > > > >> actual CLI API is more solid. (But knock yourself out!)
> > >> > > > >>
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> > >
> >
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
Maybe I am getting lost with all the urls/branches listed here (*cough*
surprise *cough), but it seems as though all the changes made recently have
been reverted (
https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client)?
Anyway, I agree with changing the wiki to point to these new instructions,
but am not sure where else those instructions may exist.
Anyway, good job Mike, instructions are looking good.
-Michal
On Tue, Sep 11, 2012 at 11:05 AM, Mike Reinstein
<re...@gmail.com>wrote:
> I'd like to propose we replace the contents of this wiki page
> http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
> note
> that points at the correct url "This documentation has merged into
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>
> Are there any other copies of this doc in other places? Other forks we can
> eliminate to reduce confusion?
>
> Has anyone heard from Andrew Lunny recently? I still have my change docs
> that I submitted as a pull request but havent gotten any feedback, and it
> seems like he hasn't been active on github in a few weeks. I'd prefer to
> get the changes for pluginstall merged in so I can remove my copy.
>
> -Mike
>
> On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
> <re...@gmail.com>wrote:
>
> > > Subcommand argument formats still look off a bit
> > Fixed
> >
> > > I think the $ is unneeded. All the other shell code
> > > examples don't include the leading shell character.
> >
> > Actually, the opposite. Every example did have leading $ except for the
> > first usage, which was inconsistent. But I agree $ is essentially just
> > noise and have removed all instances from the doc. :)
> >
> > It would be nice to clean up the Random notes section. I think there may
> > be some context associated with those chat discussion snippets that were
> > copy/pasted in, so expanding on those points would be helpful for
> everyone
> > else (including me.)
> >
> >
> >
> > On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mmocny@chromium.org
> >wrote:
> >
> >> Subcommand argument formats still look off a bit, I think they should
> look
> >> as follows:
> >>
> >> create <directory> [<id> [<name>]]
> >> platform ls
> >> platform add <platform>
> >> platform remove <platform>
> >> plugin ls
> >> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
> >> inconsistant with the other examples of add/remove)
> >> plugin remove <plugin>
> >> build
> >> emulate
> >>
> >>
> >>
> >> Also, in the line "you can access the tool via $ cordova" I think the $
> >> is
> >> unneeded. All the other shell code examples don't include the leading
> >> shell character. Alternatively we can add shell character to all the
> >> other
> >> shell command examples.
> >>
> >>
> >> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> >> <re...@gmail.com>wrote:
> >>
> >> > I've updated my copy of the README.md, pulling changes from Filip,
> >> Michal,
> >> > and Brian:
> >> >
> >>
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> >
> >> > If I've missed anything please let me know.
> >> >
> >> > -Mike
> >> >
> >> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mm...@chromium.org>
> >> > wrote:
> >> >
> >> > > I'm still unsure what a "baked in" plugin/platform would be, in that
> >> > > context. Anyway, its not super important as the actual argument
> types
> >> > may
> >> > > change over time. The gist of it is just that you can reference a
> >> > > plugin/platform using various typical methods and I think that point
> >> gets
> >> > > across well enough.
> >> > >
> >> > >
> >> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
> >> > >
> >> > > > Considering the source I'd say 'baked' was intentional.
> >> > > >
> >> > > >
> >> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> >> > > > <re...@gmail.com> wrote:
> >> > > > >> assumed to be a 'backed in' platform/plugin
> >> > > > >
> >> > > > > This must be a typo, eh? 'baked' was intended?
> >> > > > >
> >> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io>
> wrote:
> >> > > > >
> >> > > > >> > * You will be able to access the client interface via: $
> >> > > ./bin/cordova
> >> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> >> > > > >>
> >> > > > >> Agree...tho the npm install should be global (in
> /usr/local/bin)
> >> > > > >> ....maybe we say as much?
> >> > > > >>
> >> > > > >>
> >> > > > >> > * Subcommands section
> >> > > > >> > * * Typical unix manpage style is to use [] to surround
> >> optional
> >> > > > >> arguments
> >> > > > >> > <> to surround explanations and nothing for keywords.
> Examples
> >> > that
> >> > > > need
> >> > > > >> > fixing include:
> >> > > > >> > * * * create <directory> [<id>] [<name>]
> >> > > > >> > * * * platform ls
> >> > > > >> > * * * platform add <platform>
> >> > > > >> > * * * etc
> >> > > > >> > * * even if we aren't aiming for manpage style here, there
> >> > > > >> > are inconsistencies
> >> > > > >>
> >> > > > >> Sure
> >> > > > >>
> >> > > > >>
> >> > > > >> > * * File and Directory Structure ascii tree diagram
> >> > > > >> > * * * suggest appending / after directory names
> >> > > > >>
> >> > > > >> +1
> >> > > > >>
> >> > > > >>
> >> > > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
> >> > Otherwise,
> >> > > > it's
> >> > > > >> > assumed to be a URL to a gzipped tar archive...
> >> > > > >> > * * * Not sure what 'backed in' means here, nor how to
> identify
> >> > > > something
> >> > > > >> > as not being backed in so as to fallback to gzipped tar
> >> > > > >> > * * * Also wording sounds more like "else .. else" instead of
> >> > "else
> >> > > > if ..
> >> > > > >> > else" (if that makes sense) :P
> >> > > > >>
> >> > > > >> Ya not sure what this is about?
> >> > > > >>
> >> > > > >>
> >> > > > >> > * * KewlApp directory structure ascii tree diagram
> >> > > > >> > * * * based on my understanding of the text, the ios/android
> >> > > platforms
> >> > > > >> > should be subdirs of platforms/ and there should also be a
> >> subdir
> >> > > > listed
> >> > > > >> in
> >> > > > >> > plugins/
> >> > > > >>
> >> > > > >> Yes.
> >> > > > >>
> >> > > > >>
> >> > > > >> > * * Running tests warning
> >> > > > >> > * * * Perhaps explain how to bootstrap so as not to have
> >> failing
> >> > > tests
> >> > > > >> > instead of assuming the reverse?
> >> > > > >>
> >> > > > >> Yes.
> >> > > > >>
> >> > > > >>
> >> > > > >> > Also, I will look into bash completions in some spare cycles
> >> and
> >> > if
> >> > > it
> >> > > > >> > looks reasonable I may volunteer for the task. I've been
> >> curious
> >> > to
> >> > > > >> learn
> >> > > > >> > how those work :)
> >> > > > >>
> >> > > > >> That'd be awesome...but I'm thinking in a future iteration once
> >> the
> >> > > > >> actual CLI API is more solid. (But knock yourself out!)
> >> > > > >>
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hey Andrew,
I have some questions/thoughts on pluginstall and it's related spec that
I'd like to run by you (and anyone else here that feels they have insight
to add.)
I noticed that the source and destination are explicitly specified (e.g.,
copy src/android/ChildBrowser.java to src/com/phonegap/plugins/childBrowser
It seems to me that there are 2 ways this could be done. The current way
(explicitly specify where a file is copied from/to) and also an implicit
structure, where the structure of the plugin's directory layout would
automatically determine where it goes in the destination app. I think both
approaches have some pros and cons. The explicit copying is more flexible
because you have a lot more power over where to put files. It also doesn't
require modification to an existing plugin's source code; you can simply
build a plugin manifest file, wrap it up, and bam! you've got a workable
plugin archive. The downside to this appproach is there's not namespacing
of plugins, and increases the likelihood of native/www asset collisions. It
also means the plugin manifest is a bit more verbose.
My thoughts are, given how few plugins are really supported in an automated
fashion, it may make sense to revisit the expected structure of plugins and
make changes to prepare for a likely future where cordova plugin
installation is similar to npm; lots of packages installable in an
automated way. Now seems like a really good time to prepare for this given
how few people are probably using this tool manually, and given that it's
likely to increase in adoption. What are your thoughts on this idea of
auto-namespacing plugins and removing some of the explicit file pathing
stuff? I looked at childbrowser and pgsqlite as the only 2 working examples
of this plugin manifest and don't see why it coudln't work, but I didnt
want to just jump in an start re-architecting this tool without getting
your feedback because you've spent time in the trenches making this work in
a production environment.
By the way, for anyone else that has read this far, is this still the right
place for this discussion, or is this too in-depth, and belonging in a JIRA
ticket or some other place? I hate the idea of slamming the general dev
list with questions and traffic not relevant to a large portion of the
contributors.
-Mike
On Sat, Sep 15, 2012 at 10:47 PM, Anis KADRI <an...@gmail.com> wrote:
> Right. In that case, we could make those cordova command tools slightly
> smarter ;)
>
> On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
>
> > Right. I'm ok with this but wanted to keep the exact cordova-powered
> > platform projects as untouched as possible, so you could cd into those
> > directories and do whatever you want (run usual cordova project commands,
> > compile, etc). So removing the www from there forces everyone to always
> go
> > through the tool.
> >
> > On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
> >
> > >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
> > >
> > >>
> > >> >Ohhh I think I understand. So basically it packages the www resources
> > >>into
> > >> >the binary at build time?
> > >>
> > >> Correct. Each platform's underlying implementation has its own "www"
> > >> folder. At build time, the top-level www of your project gets copied
> > >>into
> > >> each platform before doing a compile for that platform.
> > >>
> > >> >> platforms/xxx/www gets destroyed and recreated on every build. See
> > >> >> here<http://bit.ly/PFKQvS>.
> > >> >> It's needed to build packages for every platform. It could arguably
> > >>be
> > >> >> destroyed after every build though. Fil is there a reason why
> that's
> > >>not
> > >> >> the case ?
> > >>
> > >> That is the case is it not? Line 57?
> > >>
> > >> Or do you mean, we should delete the platforms/<platform>/www (or
> > >> equivalent) after building?
> > >>
> > >
> > >Yes that's what I meant.
> > >
> > >
> > >>
> > >> If the latter, I don't see the point.
> > >>
> > >
> > >To avoid confusion. The reason why we're discussing this is because Mike
> > >got confused after seeing the root www and a www in each platform
> > >subfolder. There is also no reason to keep them around since they get
> > >destroyed before every build anyway. So maybe they should just get
> > >destroyed _after_ every build. You'd just recursively copy the folder
> > >before every build. I don't really care either way. Just trying to avoid
> > >the "Where do I drop my code?" scenario.
> >
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hi Brian,
> They then add, and subsequently modify, the
> generated native bits in the platforms folder.
Can you please give me more specifics here? Are you describing a cordova
plugin writer's use case here, where they are continually updating native
files in their project, or something else? Or is "they" referring to the
SDK maintainers changing things like Android or ios team? It's not clear to
me how these native bits are being changed.
-Mike
On Mon, Sep 17, 2012 at 5:09 AM, Brian LeRoux <b...@brian.io> wrote:
> Consider this scenario. A developer generates a new Cordova project.
> They then add, and subsequently modify, the generated native bits in
> the platforms folder. Google changes something, perhaps how
> AndroidManifest works. Or maybe Apple deprecates a library. The
> developer now needs to regenerate their native bits in the platforms
> folder. But they modified stuff---now, we could track their changes
> but this would lead us down a path of either depending on or
> implementing a revision control system (which we do not want to do).
> Easiest path for us here, and open to alternatives of course, is that
> we treat the native bits as throwaway compile junk.
>
> This means more work for us. We have to stay on top of the stuff we're
> painting over. But nobody said this project was easy! Interestingly,
> none of Cordova is really all that technically hard (in hindsight).
> Its just pain in the ass hard.
>
>
> On Mon, Sep 17, 2012 at 12:03 AM, Mike Reinstein
> <re...@gmail.com> wrote:
> > Brian I'm confused. Can you elaborate a bit more?
> >
> > On Mon, Sep 17, 2012 at 2:07 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> >> TL;DR
> >>
> >> +1 for building in functionality that clobbers the native bits every
> >> time and treats them as a build artifact.
> >>
> >> ***
> >> FWIW, this was the cause of bugs in the cordova prototype stuff I did.
> >> Ppl would generate a native project, then modify the native bits,
> >> while using the tools to copy in fresh WWW assets... then when an
> >> upgrade happened everything was fucked.
> >>
> >> Our goal should be to make it so that the only path to modifying
> >> generated native bits should be either plugins, or upgrades to cordova
> >> config.xml.
> >>
> >>
> >>
> >> On Sun, Sep 16, 2012 at 4:47 AM, Anis KADRI <an...@gmail.com>
> wrote:
> >> > Right. In that case, we could make those cordova command tools
> slightly
> >> > smarter ;)
> >> >
> >> > On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >
> >> >> Right. I'm ok with this but wanted to keep the exact cordova-powered
> >> >> platform projects as untouched as possible, so you could cd into
> those
> >> >> directories and do whatever you want (run usual cordova project
> >> commands,
> >> >> compile, etc). So removing the www from there forces everyone to
> always
> >> go
> >> >> through the tool.
> >> >>
> >> >> On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
> >> >>
> >> >> >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >> >
> >> >> >>
> >> >> >> >Ohhh I think I understand. So basically it packages the www
> >> resources
> >> >> >>into
> >> >> >> >the binary at build time?
> >> >> >>
> >> >> >> Correct. Each platform's underlying implementation has its own
> "www"
> >> >> >> folder. At build time, the top-level www of your project gets
> copied
> >> >> >>into
> >> >> >> each platform before doing a compile for that platform.
> >> >> >>
> >> >> >> >> platforms/xxx/www gets destroyed and recreated on every build.
> See
> >> >> >> >> here<http://bit.ly/PFKQvS>.
> >> >> >> >> It's needed to build packages for every platform. It could
> >> arguably
> >> >> >>be
> >> >> >> >> destroyed after every build though. Fil is there a reason why
> >> that's
> >> >> >>not
> >> >> >> >> the case ?
> >> >> >>
> >> >> >> That is the case is it not? Line 57?
> >> >> >>
> >> >> >> Or do you mean, we should delete the platforms/<platform>/www (or
> >> >> >> equivalent) after building?
> >> >> >>
> >> >> >
> >> >> >Yes that's what I meant.
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> If the latter, I don't see the point.
> >> >> >>
> >> >> >
> >> >> >To avoid confusion. The reason why we're discussing this is because
> >> Mike
> >> >> >got confused after seeing the root www and a www in each platform
> >> >> >subfolder. There is also no reason to keep them around since they
> get
> >> >> >destroyed before every build anyway. So maybe they should just get
> >> >> >destroyed _after_ every build. You'd just recursively copy the
> folder
> >> >> >before every build. I don't really care either way. Just trying to
> >> avoid
> >> >> >the "Where do I drop my code?" scenario.
> >> >>
> >> >>
> >>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Yeah I'm not trying to exclude anyone from the process, just thinking it
might be more efficient and faster if a few of us could realtime chat about
this. :) I'm in there now as mikenstein.
On Mon, Sep 17, 2012 at 3:32 PM, Filip Maj <fi...@adobe.com> wrote:
> We can chat anytime. I'm in #phonegap on irc.freenode.net all the time.
>
> That said, any _decisions_ that come out of our chat needs to be brought
> back to the list so everyone gets a chance to chime in and influence that
> decision.
>
> On 9/17/12 12:29 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >I'd like to setup a time on irc to chat about the state of the plugin
> >system. I've made a lot of progress on several fronts, but I'd like to get
> >feedback from relevant/interested parties before I proceed. How do you
> >folks usually set up these group chats? Informally or is there some Apache
> >process I need to follow?
> >
> >-Mike
> >
> >On Mon, Sep 17, 2012 at 3:17 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Another good example of this use case is modifying an iOS app to
> >>register
> >> for push notifications. You need to change code in the AppDelegate to do
> >> this.
> >>
> >> The use case for formalizing/automating this is something in the plugin
> >> spec like a giant block of code inside an xml tag. That doesn't sound
> >>cool
> >> :(
> >>
> >> E.g.
> >>
> >> <code target="AppDelegate.m">
> >> // Delegation methods
> >> - (void)application:(UIApplication *)app
> >> didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)devToken {
> >> const void *devTokenBytes = [devToken bytes];
> >> self.registered = YES;
> >> [self sendProviderDeviceToken:devTokenBytes];
> >> // custom method
> >> }
> >>
> >> </code>
> >>
> >> .. And then we'd need escaping of characters in the xml.. Blarghhh
> >>
> >> >> Our goal should be to make it so that the only path to modifying
> >> >> generated native bits should be either plugins, or upgrades to
> >>cordova
> >> >> config.xml.
> >>
> >> This plus a million.
> >>
> >>
> >> On 9/17/12 9:28 AM, "Brion Vibber" <bv...@wikimedia.org> wrote:
> >>
> >> >On Sep 17, 2012 2:10 AM, "Brian LeRoux" <b...@brian.io> wrote:
> >> >>
> >> >> Consider this scenario. A developer generates a new Cordova project.
> >> >> They then add, and subsequently modify, the generated native bits in
> >> >> the platforms folder. Google changes something, perhaps how
> >> >> AndroidManifest works. Or maybe Apple deprecates a library. The
> >> >> developer now needs to regenerate their native bits in the platforms
> >> >> folder. But they modified stuff--
> >> >
> >> >The AndroidManifest is an example of a file that we'd *need* to modify
> >>in
> >> >many cases; unless there's tooling to patch it with custom
> >>modifications
> >> >every time it's regenerated that'd be uncomfortable.
> >> >
> >> >-- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
> >>
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
We can chat anytime. I'm in #phonegap on irc.freenode.net all the time.
That said, any _decisions_ that come out of our chat needs to be brought
back to the list so everyone gets a chance to chime in and influence that
decision.
On 9/17/12 12:29 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>I'd like to setup a time on irc to chat about the state of the plugin
>system. I've made a lot of progress on several fronts, but I'd like to get
>feedback from relevant/interested parties before I proceed. How do you
>folks usually set up these group chats? Informally or is there some Apache
>process I need to follow?
>
>-Mike
>
>On Mon, Sep 17, 2012 at 3:17 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Another good example of this use case is modifying an iOS app to
>>register
>> for push notifications. You need to change code in the AppDelegate to do
>> this.
>>
>> The use case for formalizing/automating this is something in the plugin
>> spec like a giant block of code inside an xml tag. That doesn't sound
>>cool
>> :(
>>
>> E.g.
>>
>> <code target="AppDelegate.m">
>> // Delegation methods
>> - (void)application:(UIApplication *)app
>> didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)devToken {
>> const void *devTokenBytes = [devToken bytes];
>> self.registered = YES;
>> [self sendProviderDeviceToken:devTokenBytes];
>> // custom method
>> }
>>
>> </code>
>>
>> .. And then we'd need escaping of characters in the xml.. Blarghhh
>>
>> >> Our goal should be to make it so that the only path to modifying
>> >> generated native bits should be either plugins, or upgrades to
>>cordova
>> >> config.xml.
>>
>> This plus a million.
>>
>>
>> On 9/17/12 9:28 AM, "Brion Vibber" <bv...@wikimedia.org> wrote:
>>
>> >On Sep 17, 2012 2:10 AM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>
>> >> Consider this scenario. A developer generates a new Cordova project.
>> >> They then add, and subsequently modify, the generated native bits in
>> >> the platforms folder. Google changes something, perhaps how
>> >> AndroidManifest works. Or maybe Apple deprecates a library. The
>> >> developer now needs to regenerate their native bits in the platforms
>> >> folder. But they modified stuff--
>> >
>> >The AndroidManifest is an example of a file that we'd *need* to modify
>>in
>> >many cases; unless there's tooling to patch it with custom
>>modifications
>> >every time it's regenerated that'd be uncomfortable.
>> >
>> >-- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
I'd like to setup a time on irc to chat about the state of the plugin
system. I've made a lot of progress on several fronts, but I'd like to get
feedback from relevant/interested parties before I proceed. How do you
folks usually set up these group chats? Informally or is there some Apache
process I need to follow?
-Mike
On Mon, Sep 17, 2012 at 3:17 PM, Filip Maj <fi...@adobe.com> wrote:
> Another good example of this use case is modifying an iOS app to register
> for push notifications. You need to change code in the AppDelegate to do
> this.
>
> The use case for formalizing/automating this is something in the plugin
> spec like a giant block of code inside an xml tag. That doesn't sound cool
> :(
>
> E.g.
>
> <code target="AppDelegate.m">
> // Delegation methods
> - (void)application:(UIApplication *)app
> didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)devToken {
> const void *devTokenBytes = [devToken bytes];
> self.registered = YES;
> [self sendProviderDeviceToken:devTokenBytes];
> // custom method
> }
>
> </code>
>
> .. And then we'd need escaping of characters in the xml.. Blarghhh
>
> >> Our goal should be to make it so that the only path to modifying
> >> generated native bits should be either plugins, or upgrades to cordova
> >> config.xml.
>
> This plus a million.
>
>
> On 9/17/12 9:28 AM, "Brion Vibber" <bv...@wikimedia.org> wrote:
>
> >On Sep 17, 2012 2:10 AM, "Brian LeRoux" <b...@brian.io> wrote:
> >>
> >> Consider this scenario. A developer generates a new Cordova project.
> >> They then add, and subsequently modify, the generated native bits in
> >> the platforms folder. Google changes something, perhaps how
> >> AndroidManifest works. Or maybe Apple deprecates a library. The
> >> developer now needs to regenerate their native bits in the platforms
> >> folder. But they modified stuff--
> >
> >The AndroidManifest is an example of a file that we'd *need* to modify in
> >many cases; unless there's tooling to patch it with custom modifications
> >every time it's regenerated that'd be uncomfortable.
> >
> >-- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Another good example of this use case is modifying an iOS app to register
for push notifications. You need to change code in the AppDelegate to do
this.
The use case for formalizing/automating this is something in the plugin
spec like a giant block of code inside an xml tag. That doesn't sound cool
:(
E.g.
<code target="AppDelegate.m">
// Delegation methods
- (void)application:(UIApplication *)app
didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)devToken {
const void *devTokenBytes = [devToken bytes];
self.registered = YES;
[self sendProviderDeviceToken:devTokenBytes];
// custom method
}
</code>
.. And then we'd need escaping of characters in the xml.. Blarghhh
>> Our goal should be to make it so that the only path to modifying
>> generated native bits should be either plugins, or upgrades to cordova
>> config.xml.
This plus a million.
On 9/17/12 9:28 AM, "Brion Vibber" <bv...@wikimedia.org> wrote:
>On Sep 17, 2012 2:10 AM, "Brian LeRoux" <b...@brian.io> wrote:
>>
>> Consider this scenario. A developer generates a new Cordova project.
>> They then add, and subsequently modify, the generated native bits in
>> the platforms folder. Google changes something, perhaps how
>> AndroidManifest works. Or maybe Apple deprecates a library. The
>> developer now needs to regenerate their native bits in the platforms
>> folder. But they modified stuff--
>
>The AndroidManifest is an example of a file that we'd *need* to modify in
>many cases; unless there's tooling to patch it with custom modifications
>every time it's regenerated that'd be uncomfortable.
>
>-- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
Re: plugin tooling/specification
Posted by Brion Vibber <bv...@wikimedia.org>.
On Sep 17, 2012 2:10 AM, "Brian LeRoux" <b...@brian.io> wrote:
>
> Consider this scenario. A developer generates a new Cordova project.
> They then add, and subsequently modify, the generated native bits in
> the platforms folder. Google changes something, perhaps how
> AndroidManifest works. Or maybe Apple deprecates a library. The
> developer now needs to regenerate their native bits in the platforms
> folder. But they modified stuff--
The AndroidManifest is an example of a file that we'd *need* to modify in
many cases; unless there's tooling to patch it with custom modifications
every time it's regenerated that'd be uncomfortable.
-- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org)
Re: plugin tooling/specification
Posted by Brian LeRoux <b...@brian.io>.
Consider this scenario. A developer generates a new Cordova project.
They then add, and subsequently modify, the generated native bits in
the platforms folder. Google changes something, perhaps how
AndroidManifest works. Or maybe Apple deprecates a library. The
developer now needs to regenerate their native bits in the platforms
folder. But they modified stuff---now, we could track their changes
but this would lead us down a path of either depending on or
implementing a revision control system (which we do not want to do).
Easiest path for us here, and open to alternatives of course, is that
we treat the native bits as throwaway compile junk.
This means more work for us. We have to stay on top of the stuff we're
painting over. But nobody said this project was easy! Interestingly,
none of Cordova is really all that technically hard (in hindsight).
Its just pain in the ass hard.
On Mon, Sep 17, 2012 at 12:03 AM, Mike Reinstein
<re...@gmail.com> wrote:
> Brian I'm confused. Can you elaborate a bit more?
>
> On Mon, Sep 17, 2012 at 2:07 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> TL;DR
>>
>> +1 for building in functionality that clobbers the native bits every
>> time and treats them as a build artifact.
>>
>> ***
>> FWIW, this was the cause of bugs in the cordova prototype stuff I did.
>> Ppl would generate a native project, then modify the native bits,
>> while using the tools to copy in fresh WWW assets... then when an
>> upgrade happened everything was fucked.
>>
>> Our goal should be to make it so that the only path to modifying
>> generated native bits should be either plugins, or upgrades to cordova
>> config.xml.
>>
>>
>>
>> On Sun, Sep 16, 2012 at 4:47 AM, Anis KADRI <an...@gmail.com> wrote:
>> > Right. In that case, we could make those cordova command tools slightly
>> > smarter ;)
>> >
>> > On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> Right. I'm ok with this but wanted to keep the exact cordova-powered
>> >> platform projects as untouched as possible, so you could cd into those
>> >> directories and do whatever you want (run usual cordova project
>> commands,
>> >> compile, etc). So removing the www from there forces everyone to always
>> go
>> >> through the tool.
>> >>
>> >> On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
>> >>
>> >> >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >
>> >> >>
>> >> >> >Ohhh I think I understand. So basically it packages the www
>> resources
>> >> >>into
>> >> >> >the binary at build time?
>> >> >>
>> >> >> Correct. Each platform's underlying implementation has its own "www"
>> >> >> folder. At build time, the top-level www of your project gets copied
>> >> >>into
>> >> >> each platform before doing a compile for that platform.
>> >> >>
>> >> >> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> >> >> here<http://bit.ly/PFKQvS>.
>> >> >> >> It's needed to build packages for every platform. It could
>> arguably
>> >> >>be
>> >> >> >> destroyed after every build though. Fil is there a reason why
>> that's
>> >> >>not
>> >> >> >> the case ?
>> >> >>
>> >> >> That is the case is it not? Line 57?
>> >> >>
>> >> >> Or do you mean, we should delete the platforms/<platform>/www (or
>> >> >> equivalent) after building?
>> >> >>
>> >> >
>> >> >Yes that's what I meant.
>> >> >
>> >> >
>> >> >>
>> >> >> If the latter, I don't see the point.
>> >> >>
>> >> >
>> >> >To avoid confusion. The reason why we're discussing this is because
>> Mike
>> >> >got confused after seeing the root www and a www in each platform
>> >> >subfolder. There is also no reason to keep them around since they get
>> >> >destroyed before every build anyway. So maybe they should just get
>> >> >destroyed _after_ every build. You'd just recursively copy the folder
>> >> >before every build. I don't really care either way. Just trying to
>> avoid
>> >> >the "Where do I drop my code?" scenario.
>> >>
>> >>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Brian I'm confused. Can you elaborate a bit more?
On Mon, Sep 17, 2012 at 2:07 AM, Brian LeRoux <b...@brian.io> wrote:
> TL;DR
>
> +1 for building in functionality that clobbers the native bits every
> time and treats them as a build artifact.
>
> ***
> FWIW, this was the cause of bugs in the cordova prototype stuff I did.
> Ppl would generate a native project, then modify the native bits,
> while using the tools to copy in fresh WWW assets... then when an
> upgrade happened everything was fucked.
>
> Our goal should be to make it so that the only path to modifying
> generated native bits should be either plugins, or upgrades to cordova
> config.xml.
>
>
>
> On Sun, Sep 16, 2012 at 4:47 AM, Anis KADRI <an...@gmail.com> wrote:
> > Right. In that case, we could make those cordova command tools slightly
> > smarter ;)
> >
> > On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Right. I'm ok with this but wanted to keep the exact cordova-powered
> >> platform projects as untouched as possible, so you could cd into those
> >> directories and do whatever you want (run usual cordova project
> commands,
> >> compile, etc). So removing the www from there forces everyone to always
> go
> >> through the tool.
> >>
> >> On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
> >>
> >> >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >
> >> >>
> >> >> >Ohhh I think I understand. So basically it packages the www
> resources
> >> >>into
> >> >> >the binary at build time?
> >> >>
> >> >> Correct. Each platform's underlying implementation has its own "www"
> >> >> folder. At build time, the top-level www of your project gets copied
> >> >>into
> >> >> each platform before doing a compile for that platform.
> >> >>
> >> >> >> platforms/xxx/www gets destroyed and recreated on every build. See
> >> >> >> here<http://bit.ly/PFKQvS>.
> >> >> >> It's needed to build packages for every platform. It could
> arguably
> >> >>be
> >> >> >> destroyed after every build though. Fil is there a reason why
> that's
> >> >>not
> >> >> >> the case ?
> >> >>
> >> >> That is the case is it not? Line 57?
> >> >>
> >> >> Or do you mean, we should delete the platforms/<platform>/www (or
> >> >> equivalent) after building?
> >> >>
> >> >
> >> >Yes that's what I meant.
> >> >
> >> >
> >> >>
> >> >> If the latter, I don't see the point.
> >> >>
> >> >
> >> >To avoid confusion. The reason why we're discussing this is because
> Mike
> >> >got confused after seeing the root www and a www in each platform
> >> >subfolder. There is also no reason to keep them around since they get
> >> >destroyed before every build anyway. So maybe they should just get
> >> >destroyed _after_ every build. You'd just recursively copy the folder
> >> >before every build. I don't really care either way. Just trying to
> avoid
> >> >the "Where do I drop my code?" scenario.
> >>
> >>
>
Re: plugin tooling/specification
Posted by Brian LeRoux <b...@brian.io>.
TL;DR
+1 for building in functionality that clobbers the native bits every
time and treats them as a build artifact.
***
FWIW, this was the cause of bugs in the cordova prototype stuff I did.
Ppl would generate a native project, then modify the native bits,
while using the tools to copy in fresh WWW assets... then when an
upgrade happened everything was fucked.
Our goal should be to make it so that the only path to modifying
generated native bits should be either plugins, or upgrades to cordova
config.xml.
On Sun, Sep 16, 2012 at 4:47 AM, Anis KADRI <an...@gmail.com> wrote:
> Right. In that case, we could make those cordova command tools slightly
> smarter ;)
>
> On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Right. I'm ok with this but wanted to keep the exact cordova-powered
>> platform projects as untouched as possible, so you could cd into those
>> directories and do whatever you want (run usual cordova project commands,
>> compile, etc). So removing the www from there forces everyone to always go
>> through the tool.
>>
>> On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
>>
>> >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >>
>> >> >Ohhh I think I understand. So basically it packages the www resources
>> >>into
>> >> >the binary at build time?
>> >>
>> >> Correct. Each platform's underlying implementation has its own "www"
>> >> folder. At build time, the top-level www of your project gets copied
>> >>into
>> >> each platform before doing a compile for that platform.
>> >>
>> >> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> >> here<http://bit.ly/PFKQvS>.
>> >> >> It's needed to build packages for every platform. It could arguably
>> >>be
>> >> >> destroyed after every build though. Fil is there a reason why that's
>> >>not
>> >> >> the case ?
>> >>
>> >> That is the case is it not? Line 57?
>> >>
>> >> Or do you mean, we should delete the platforms/<platform>/www (or
>> >> equivalent) after building?
>> >>
>> >
>> >Yes that's what I meant.
>> >
>> >
>> >>
>> >> If the latter, I don't see the point.
>> >>
>> >
>> >To avoid confusion. The reason why we're discussing this is because Mike
>> >got confused after seeing the root www and a www in each platform
>> >subfolder. There is also no reason to keep them around since they get
>> >destroyed before every build anyway. So maybe they should just get
>> >destroyed _after_ every build. You'd just recursively copy the folder
>> >before every build. I don't really care either way. Just trying to avoid
>> >the "Where do I drop my code?" scenario.
>>
>>
Re: plugin tooling/specification
Posted by Anis KADRI <an...@gmail.com>.
Right. In that case, we could make those cordova command tools slightly
smarter ;)
On Sat, Sep 15, 2012 at 7:29 PM, Filip Maj <fi...@adobe.com> wrote:
> Right. I'm ok with this but wanted to keep the exact cordova-powered
> platform projects as untouched as possible, so you could cd into those
> directories and do whatever you want (run usual cordova project commands,
> compile, etc). So removing the www from there forces everyone to always go
> through the tool.
>
> On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
>
> >On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >>
> >> >Ohhh I think I understand. So basically it packages the www resources
> >>into
> >> >the binary at build time?
> >>
> >> Correct. Each platform's underlying implementation has its own "www"
> >> folder. At build time, the top-level www of your project gets copied
> >>into
> >> each platform before doing a compile for that platform.
> >>
> >> >> platforms/xxx/www gets destroyed and recreated on every build. See
> >> >> here<http://bit.ly/PFKQvS>.
> >> >> It's needed to build packages for every platform. It could arguably
> >>be
> >> >> destroyed after every build though. Fil is there a reason why that's
> >>not
> >> >> the case ?
> >>
> >> That is the case is it not? Line 57?
> >>
> >> Or do you mean, we should delete the platforms/<platform>/www (or
> >> equivalent) after building?
> >>
> >
> >Yes that's what I meant.
> >
> >
> >>
> >> If the latter, I don't see the point.
> >>
> >
> >To avoid confusion. The reason why we're discussing this is because Mike
> >got confused after seeing the root www and a www in each platform
> >subfolder. There is also no reason to keep them around since they get
> >destroyed before every build anyway. So maybe they should just get
> >destroyed _after_ every build. You'd just recursively copy the folder
> >before every build. I don't really care either way. Just trying to avoid
> >the "Where do I drop my code?" scenario.
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Right. I'm ok with this but wanted to keep the exact cordova-powered
platform projects as untouched as possible, so you could cd into those
directories and do whatever you want (run usual cordova project commands,
compile, etc). So removing the www from there forces everyone to always go
through the tool.
On 9/15/12 7:23 PM, "Anis KADRI" <an...@gmail.com> wrote:
>On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
>
>>
>> >Ohhh I think I understand. So basically it packages the www resources
>>into
>> >the binary at build time?
>>
>> Correct. Each platform's underlying implementation has its own "www"
>> folder. At build time, the top-level www of your project gets copied
>>into
>> each platform before doing a compile for that platform.
>>
>> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> here<http://bit.ly/PFKQvS>.
>> >> It's needed to build packages for every platform. It could arguably
>>be
>> >> destroyed after every build though. Fil is there a reason why that's
>>not
>> >> the case ?
>>
>> That is the case is it not? Line 57?
>>
>> Or do you mean, we should delete the platforms/<platform>/www (or
>> equivalent) after building?
>>
>
>Yes that's what I meant.
>
>
>>
>> If the latter, I don't see the point.
>>
>
>To avoid confusion. The reason why we're discussing this is because Mike
>got confused after seeing the root www and a www in each platform
>subfolder. There is also no reason to keep them around since they get
>destroyed before every build anyway. So maybe they should just get
>destroyed _after_ every build. You'd just recursively copy the folder
>before every build. I don't really care either way. Just trying to avoid
>the "Where do I drop my code?" scenario.
Re: plugin tooling/specification
Posted by Anis KADRI <an...@gmail.com>.
On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fi...@adobe.com> wrote:
>
> >Ohhh I think I understand. So basically it packages the www resources into
> >the binary at build time?
>
> Correct. Each platform's underlying implementation has its own "www"
> folder. At build time, the top-level www of your project gets copied into
> each platform before doing a compile for that platform.
>
> >> platforms/xxx/www gets destroyed and recreated on every build. See
> >> here<http://bit.ly/PFKQvS>.
> >> It's needed to build packages for every platform. It could arguably be
> >> destroyed after every build though. Fil is there a reason why that's not
> >> the case ?
>
> That is the case is it not? Line 57?
>
> Or do you mean, we should delete the platforms/<platform>/www (or
> equivalent) after building?
>
Yes that's what I meant.
>
> If the latter, I don't see the point.
>
To avoid confusion. The reason why we're discussing this is because Mike
got confused after seeing the root www and a www in each platform
subfolder. There is also no reason to keep them around since they get
destroyed before every build anyway. So maybe they should just get
destroyed _after_ every build. You'd just recursively copy the folder
before every build. I don't really care either way. Just trying to avoid
the "Where do I drop my code?" scenario.
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
I think that might have been a feature that Anis added. If anything the
documentation just needs updating :)
On 9/15/12 6:00 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>Hi Fil, Anis,
>
>> Each platform's underlying implementation
>> has its own "www"
>
>Okay, makes sense to me. I'm at the point where I'd like to install a
>plugin. In the docs it shows:
>
>cordova plugin add http://example.org/Kewlio-1.2.3.tar.gz
>
>Is there a link somewhere to a real package I can try this with? I"m
>assuming childbrowser is the only supported plugin at the moment?
>
>I'm also wondering how this statement in the documentation "You having the
>plugin code locally on your computer" relates to the example above? The
>first one seems to imply I can just pull a tar/gzipped copy of the file,
>the second seems to imply that I need to pull it down manually.
>
>-Mike
>
>On Sat, Sep 15, 2012 at 8:32 PM, Filip Maj <fi...@adobe.com> wrote:
>
>>
>> >Ohhh I think I understand. So basically it packages the www resources
>>into
>> >the binary at build time?
>>
>> Correct. Each platform's underlying implementation has its own "www"
>> folder. At build time, the top-level www of your project gets copied
>>into
>> each platform before doing a compile for that platform.
>>
>> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> here<http://bit.ly/PFKQvS>.
>> >> It's needed to build packages for every platform. It could arguably
>>be
>> >> destroyed after every build though. Fil is there a reason why that's
>>not
>> >> the case ?
>>
>> That is the case is it not? Line 57?
>>
>> Or do you mean, we should delete the platforms/<platform>/www (or
>> equivalent) after building?
>>
>> If the latter, I don't see the point.
>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hi Fil, Anis,
> Each platform's underlying implementation
> has its own "www"
Okay, makes sense to me. I'm at the point where I'd like to install a
plugin. In the docs it shows:
cordova plugin add http://example.org/Kewlio-1.2.3.tar.gz
Is there a link somewhere to a real package I can try this with? I"m
assuming childbrowser is the only supported plugin at the moment?
I'm also wondering how this statement in the documentation "You having the
plugin code locally on your computer" relates to the example above? The
first one seems to imply I can just pull a tar/gzipped copy of the file,
the second seems to imply that I need to pull it down manually.
-Mike
On Sat, Sep 15, 2012 at 8:32 PM, Filip Maj <fi...@adobe.com> wrote:
>
> >Ohhh I think I understand. So basically it packages the www resources into
> >the binary at build time?
>
> Correct. Each platform's underlying implementation has its own "www"
> folder. At build time, the top-level www of your project gets copied into
> each platform before doing a compile for that platform.
>
> >> platforms/xxx/www gets destroyed and recreated on every build. See
> >> here<http://bit.ly/PFKQvS>.
> >> It's needed to build packages for every platform. It could arguably be
> >> destroyed after every build though. Fil is there a reason why that's not
> >> the case ?
>
> That is the case is it not? Line 57?
>
> Or do you mean, we should delete the platforms/<platform>/www (or
> equivalent) after building?
>
> If the latter, I don't see the point.
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
>Ohhh I think I understand. So basically it packages the www resources into
>the binary at build time?
Correct. Each platform's underlying implementation has its own "www"
folder. At build time, the top-level www of your project gets copied into
each platform before doing a compile for that platform.
>> platforms/xxx/www gets destroyed and recreated on every build. See
>> here<http://bit.ly/PFKQvS>.
>> It's needed to build packages for every platform. It could arguably be
>> destroyed after every build though. Fil is there a reason why that's not
>> the case ?
That is the case is it not? Line 57?
Or do you mean, we should delete the platforms/<platform>/www (or
equivalent) after building?
If the latter, I don't see the point.
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Ohhh I think I understand. So basically it packages the www resources into
the binary at build time?
-Mike
On Sat, Sep 15, 2012 at 6:47 PM, Anis KADRI <an...@gmail.com> wrote:
> platforms/xxx/www gets destroyed and recreated on every build. See
> here<http://bit.ly/PFKQvS>.
> It's needed to build packages for every platform. It could arguably be
> destroyed after every build though. Fil is there a reason why that's not
> the case ?
>
> On Sat, Sep 15, 2012 at 3:19 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > Sorry, I sent that prematurely. Damn Chrome shortcuts! Anyway in my
> example
> > i was trying to illustrate that I have myproject/platforms/ios/www/ and I
> > also have myproject/www/ I'm assuming I only need myproject/www/ and the
> > former is just a bug having to do with how the templated copy of a new
> > project gets copied in?
> >
> > thanks,
> >
> > -Mike
> >
> > On Sat, Sep 15, 2012 at 6:16 PM, Mike Reinstein <
> reinstein.mike@gmail.com
> > >wrote:
> >
> > > Hey Fil,
> > >
> > > I've got the code running locally, I'm able to create projects, add
> > > platforms, etc. I'm going through the code now, doing some cleanup, etc
> > and
> > > will have a pull request pretty soon (maybe later tonight.)
> > >
> > > I have a question, I noticed that the platforms directories include a
> > www/
> > > in each one. I'm wondering why. For example:
> > >
> > > myproject
> > > |- platforms
> > > `- ios
> > > | - build
> > >
> > >
> > >
> > > On Fri, Sep 14, 2012 at 5:02 PM, Filip Maj <fi...@adobe.com> wrote:
> > >
> > >> Nope I think that's fine. That was the latest tag when I wrote that
> code
> > >> :)
> > >>
> > >> On 9/14/12 1:56 PM, "Mike Reinstein" <re...@gmail.com>
> wrote:
> > >>
> > >> >Hey Fil,
> > >> >
> > >> >I see this in the platform checkout code:
> > >> >cd "%s" && git checkout 2.1.0rc1
> > >> >
> > >> >Do you think this is ok to change to 2.1.0, or are there specific
> > things
> > >> >in
> > >> >rc1 that prevent us from moving up to this newer tag?
> > >> >
> > >> >
> > >> >
> > >> >On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
> > >> >
> > >> >> http://people.apache.org/~steven/
> > >> >>
> > >> >> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
> > >> >> <re...@gmail.com> wrote:
> > >> >> > This is probably a stupid question, but is the 2.1 release
> package
> > >> >> > available somewhere for download yet? I'd like to start basing my
> > >> >>work on
> > >> >> > that.
> > >> >> >
> > >> >> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
> > >> >> reinstein.mike@gmail.com>wrote:
> > >> >> >
> > >> >> >> Thanks Fil. I'll start taking cordova-client for a spin, and see
> > how
> > >> >> that
> > >> >> >> goes. :)
> > >> >> >>
> > >> >> >>
> > >> >> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com>
> wrote:
> > >> >> >>
> > >> >> >>> If you ask me, just give the tools a spin and let me know what
> > >> >> >>> issues/problems/feature requests you could use.
> > >> >> >>>
> > >> >> >>> Last I checked there was an issue with installing iOS resource
> > >> files
> > >> >> via
> > >> >> >>> the pluginstall tool. This could be a reasonable thing to
> tackle
> > if
> > >> >>you
> > >> >> >>> enjoy mucking about with xcodeproj files.
> > >> >> >>>
> > >> >> >>> I'm informally tracking issues on my fork of cordova-client on
> > >> >>github
> > >> >> >>> here:
> https://github.com/filmaj/cordova-client/issues?state=open
> > >> >> >>>
> > >> >> >>> Logging issues would be awesome. Resolving some would be even
> > >> >>better :)
> > >> >> >>>
> > >> >> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <reinstein.mike@gmail.com
> >
> > >> >>wrote:
> > >> >> >>>
> > >> >> >>> >Apparently I wasn't logged into the wiki, so it wasn't some
> > finer
> > >> >> grained
> > >> >> >>> >permissions issue. I've updated the doc to point at the right
> > >> >>place:
> > >> >> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> >> >>> >
> > >> >> >>> >What should I work on next? Based on Andrew's feedback my doc
> > work
> > >> >>on
> > >> >> >>> >merging pluginstall with it's spec isnt helpful at this point,
> > so
> > >> >>I'm
> > >> >> >>> >ready
> > >> >> >>> >for more tasks. Any suggestions? I could start hacking on
> > >> >> cordova-client,
> > >> >> >>> >or working on some kind of central plugin repo which cordova
> > >> really
> > >> >> needs
> > >> >> >>> >(IMO), or something else. Where do you folks feel the plugin
> > >> >>project
> > >> >> >>> could
> > >> >> >>> >use the most "love" ?
> > >> >> >>> >
> > >> >> >>> >-Mike
> > >> >> >>> >
> > >> >> >>> >
> > >> >> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
> > >> >> >>> ><re...@gmail.com>wrote:
> > >> >> >>> >
> > >> >> >>> >> I've signed up for the wiki, but it's listing the page as
> > >> >>immutable.
> > >> >> >>> I'm
> > >> >> >>> >> assuming someone with write permissions would have to make
> the
> > >> >> changes.
> > >> >> >>> >>
> > >> >> >>> >>
> > >> >> >>> >>
> > >> >> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
> > >> >> >>> >><mi...@michaelbrooks.ca>wrote:
> > >> >> >>> >>
> > >> >> >>> >>> >
> > >> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will
> my
> > >> >>jira
> > >> >> >>> >>> > credentials work?
> > >> >> >>> >>>
> > >> >> >>> >>>
> > >> >> >>> >>> You need to sign up. The account name convention has been a
> > >> >> camel-case
> > >> >> >>> >>>of
> > >> >> >>> >>> your first and last name. e.g. MichaelBrooks. However,
> you're
> > >> >>free
> > >> >> to
> > >> >> >>> >>>do
> > >> >> >>> >>> whatever you want.
> > >> >> >>> >>>
> > >> >> >>> >>> I just got back from vacation and read through this
> > discussion.
> > >> >> >>> Amazing
> > >> >> >>> >>> for
> > >> >> >>> >>> Mike, Michal, and Fil!
> > >> >> >>> >>>
> > >> >> >>> >>> Michael
> > >> >> >>> >>>
> > >> >> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
> > >> >> >>> >>><reinstein.mike@gmail.com
> > >> >> >>> >>> >wrote:
> > >> >> >>> >>>
> > >> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will
> my
> > >> >>jira
> > >> >> >>> >>> > credentials work?
> > >> >> >>> >>> >
> > >> >> >>> >>> > -Mike
> > >> >> >>> >>> >
> > >> >> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
> > >> >> >>> pmuellr@gmail.com>
> > >> >> >>> >>> > wrote:
> > >> >> >>> >>> >
> > >> >> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> > >> >> >>> >>> > reinstein.mike@gmail.com
> > >> >> >>> >>> > > >wrote:
> > >> >> >>> >>> > >
> > >> >> >>> >>> > > > I'd like to propose we replace the contents of this
> > wiki
> > >> >>page
> > >> >> >>> >>> > > >
> > http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> >>with a
> > >> >> >>> >>> simple
> > >> >> >>> >>> > > > note
> > >> >> >>> >>> > > > that points at the correct url "This documentation
> has
> > >> >>merged
> > >> >> >>> >>>into
> > >> >> >>> >>> > > >
> > >> >> >>> >>>
> > >> >>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > "
> > >> >> >>> >>> > > >
> > >> >> >>> >>> > >
> > >> >> >>> >>> > > I was just looking at the wiki page
> > >> >> >>> >>> > >
> > http://wiki.apache.org/cordova/CommandLineToolingDesignand
> > >> >> >>> >>>thought -
> > >> >> >>> >>> > > "wow,
> > >> >> >>> >>> > > that's the same thing I was thinking about", then
> > scrolled
> > >> >>down
> > >> >> >>> and
> > >> >> >>> >>> > noticed
> > >> >> >>> >>> > > it was written by me. :-)
> > >> >> >>> >>> > >
> > >> >> >>> >>> > > Feel free to delete, this was a dump of some of my
> > thoughts
> > >> >> around
> > >> >> >>> >>>the
> > >> >> >>> >>> > > command-line tooling. I haven't had time to even
> follow
> > >> the
> > >> >> >>> >>>current
> > >> >> >>> >>> CLI
> > >> >> >>> >>> > > work, but mean to catch up soon, so if nothing is
> > relevant,
> > >> >> pitch
> > >> >> >>> >>>it.
> > >> >> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure
> I'll
> > >> >>have
> > >> >> >>> >>> comments
> > >> >> >>> >>> > :-)
> > >> >> >>> >>> > >
> > >> >> >>> >>> > > --
> > >> >> >>> >>> > > Patrick Mueller
> > >> >> >>> >>> > > http://muellerware.org
> > >> >> >>> >>> > >
> > >> >> >>> >>> >
> > >> >> >>> >>>
> > >> >> >>> >>
> > >> >> >>> >>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>
> > >> >>
> > >>
> > >>
> > >
> >
>
Re: plugin tooling/specification
Posted by Anis KADRI <an...@gmail.com>.
platforms/xxx/www gets destroyed and recreated on every build. See
here<http://bit.ly/PFKQvS>.
It's needed to build packages for every platform. It could arguably be
destroyed after every build though. Fil is there a reason why that's not
the case ?
On Sat, Sep 15, 2012 at 3:19 PM, Mike Reinstein <re...@gmail.com>wrote:
> Sorry, I sent that prematurely. Damn Chrome shortcuts! Anyway in my example
> i was trying to illustrate that I have myproject/platforms/ios/www/ and I
> also have myproject/www/ I'm assuming I only need myproject/www/ and the
> former is just a bug having to do with how the templated copy of a new
> project gets copied in?
>
> thanks,
>
> -Mike
>
> On Sat, Sep 15, 2012 at 6:16 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > Hey Fil,
> >
> > I've got the code running locally, I'm able to create projects, add
> > platforms, etc. I'm going through the code now, doing some cleanup, etc
> and
> > will have a pull request pretty soon (maybe later tonight.)
> >
> > I have a question, I noticed that the platforms directories include a
> www/
> > in each one. I'm wondering why. For example:
> >
> > myproject
> > |- platforms
> > `- ios
> > | - build
> >
> >
> >
> > On Fri, Sep 14, 2012 at 5:02 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Nope I think that's fine. That was the latest tag when I wrote that code
> >> :)
> >>
> >> On 9/14/12 1:56 PM, "Mike Reinstein" <re...@gmail.com> wrote:
> >>
> >> >Hey Fil,
> >> >
> >> >I see this in the platform checkout code:
> >> >cd "%s" && git checkout 2.1.0rc1
> >> >
> >> >Do you think this is ok to change to 2.1.0, or are there specific
> things
> >> >in
> >> >rc1 that prevent us from moving up to this newer tag?
> >> >
> >> >
> >> >
> >> >On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
> >> >
> >> >> http://people.apache.org/~steven/
> >> >>
> >> >> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
> >> >> <re...@gmail.com> wrote:
> >> >> > This is probably a stupid question, but is the 2.1 release package
> >> >> > available somewhere for download yet? I'd like to start basing my
> >> >>work on
> >> >> > that.
> >> >> >
> >> >> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
> >> >> reinstein.mike@gmail.com>wrote:
> >> >> >
> >> >> >> Thanks Fil. I'll start taking cordova-client for a spin, and see
> how
> >> >> that
> >> >> >> goes. :)
> >> >> >>
> >> >> >>
> >> >> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >> >>
> >> >> >>> If you ask me, just give the tools a spin and let me know what
> >> >> >>> issues/problems/feature requests you could use.
> >> >> >>>
> >> >> >>> Last I checked there was an issue with installing iOS resource
> >> files
> >> >> via
> >> >> >>> the pluginstall tool. This could be a reasonable thing to tackle
> if
> >> >>you
> >> >> >>> enjoy mucking about with xcodeproj files.
> >> >> >>>
> >> >> >>> I'm informally tracking issues on my fork of cordova-client on
> >> >>github
> >> >> >>> here: https://github.com/filmaj/cordova-client/issues?state=open
> >> >> >>>
> >> >> >>> Logging issues would be awesome. Resolving some would be even
> >> >>better :)
> >> >> >>>
> >> >> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com>
> >> >>wrote:
> >> >> >>>
> >> >> >>> >Apparently I wasn't logged into the wiki, so it wasn't some
> finer
> >> >> grained
> >> >> >>> >permissions issue. I've updated the doc to point at the right
> >> >>place:
> >> >> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >> >>> >
> >> >> >>> >What should I work on next? Based on Andrew's feedback my doc
> work
> >> >>on
> >> >> >>> >merging pluginstall with it's spec isnt helpful at this point,
> so
> >> >>I'm
> >> >> >>> >ready
> >> >> >>> >for more tasks. Any suggestions? I could start hacking on
> >> >> cordova-client,
> >> >> >>> >or working on some kind of central plugin repo which cordova
> >> really
> >> >> needs
> >> >> >>> >(IMO), or something else. Where do you folks feel the plugin
> >> >>project
> >> >> >>> could
> >> >> >>> >use the most "love" ?
> >> >> >>> >
> >> >> >>> >-Mike
> >> >> >>> >
> >> >> >>> >
> >> >> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
> >> >> >>> ><re...@gmail.com>wrote:
> >> >> >>> >
> >> >> >>> >> I've signed up for the wiki, but it's listing the page as
> >> >>immutable.
> >> >> >>> I'm
> >> >> >>> >> assuming someone with write permissions would have to make the
> >> >> changes.
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
> >> >> >>> >><mi...@michaelbrooks.ca>wrote:
> >> >> >>> >>
> >> >> >>> >>> >
> >> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
> >> >>jira
> >> >> >>> >>> > credentials work?
> >> >> >>> >>>
> >> >> >>> >>>
> >> >> >>> >>> You need to sign up. The account name convention has been a
> >> >> camel-case
> >> >> >>> >>>of
> >> >> >>> >>> your first and last name. e.g. MichaelBrooks. However, you're
> >> >>free
> >> >> to
> >> >> >>> >>>do
> >> >> >>> >>> whatever you want.
> >> >> >>> >>>
> >> >> >>> >>> I just got back from vacation and read through this
> discussion.
> >> >> >>> Amazing
> >> >> >>> >>> for
> >> >> >>> >>> Mike, Michal, and Fil!
> >> >> >>> >>>
> >> >> >>> >>> Michael
> >> >> >>> >>>
> >> >> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
> >> >> >>> >>><reinstein.mike@gmail.com
> >> >> >>> >>> >wrote:
> >> >> >>> >>>
> >> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
> >> >>jira
> >> >> >>> >>> > credentials work?
> >> >> >>> >>> >
> >> >> >>> >>> > -Mike
> >> >> >>> >>> >
> >> >> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
> >> >> >>> pmuellr@gmail.com>
> >> >> >>> >>> > wrote:
> >> >> >>> >>> >
> >> >> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> >> >> >>> >>> > reinstein.mike@gmail.com
> >> >> >>> >>> > > >wrote:
> >> >> >>> >>> > >
> >> >> >>> >>> > > > I'd like to propose we replace the contents of this
> wiki
> >> >>page
> >> >> >>> >>> > > >
> http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>with a
> >> >> >>> >>> simple
> >> >> >>> >>> > > > note
> >> >> >>> >>> > > > that points at the correct url "This documentation has
> >> >>merged
> >> >> >>> >>>into
> >> >> >>> >>> > > >
> >> >> >>> >>>
> >> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> "
> >> >> >>> >>> > > >
> >> >> >>> >>> > >
> >> >> >>> >>> > > I was just looking at the wiki page
> >> >> >>> >>> > >
> http://wiki.apache.org/cordova/CommandLineToolingDesignand
> >> >> >>> >>>thought -
> >> >> >>> >>> > > "wow,
> >> >> >>> >>> > > that's the same thing I was thinking about", then
> scrolled
> >> >>down
> >> >> >>> and
> >> >> >>> >>> > noticed
> >> >> >>> >>> > > it was written by me. :-)
> >> >> >>> >>> > >
> >> >> >>> >>> > > Feel free to delete, this was a dump of some of my
> thoughts
> >> >> around
> >> >> >>> >>>the
> >> >> >>> >>> > > command-line tooling. I haven't had time to even follow
> >> the
> >> >> >>> >>>current
> >> >> >>> >>> CLI
> >> >> >>> >>> > > work, but mean to catch up soon, so if nothing is
> relevant,
> >> >> pitch
> >> >> >>> >>>it.
> >> >> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll
> >> >>have
> >> >> >>> >>> comments
> >> >> >>> >>> > :-)
> >> >> >>> >>> > >
> >> >> >>> >>> > > --
> >> >> >>> >>> > > Patrick Mueller
> >> >> >>> >>> > > http://muellerware.org
> >> >> >>> >>> > >
> >> >> >>> >>> >
> >> >> >>> >>>
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >>
> >>
> >>
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Sorry, I sent that prematurely. Damn Chrome shortcuts! Anyway in my example
i was trying to illustrate that I have myproject/platforms/ios/www/ and I
also have myproject/www/ I'm assuming I only need myproject/www/ and the
former is just a bug having to do with how the templated copy of a new
project gets copied in?
thanks,
-Mike
On Sat, Sep 15, 2012 at 6:16 PM, Mike Reinstein <re...@gmail.com>wrote:
> Hey Fil,
>
> I've got the code running locally, I'm able to create projects, add
> platforms, etc. I'm going through the code now, doing some cleanup, etc and
> will have a pull request pretty soon (maybe later tonight.)
>
> I have a question, I noticed that the platforms directories include a www/
> in each one. I'm wondering why. For example:
>
> myproject
> |- platforms
> `- ios
> | - build
>
>
>
> On Fri, Sep 14, 2012 at 5:02 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Nope I think that's fine. That was the latest tag when I wrote that code
>> :)
>>
>> On 9/14/12 1:56 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>
>> >Hey Fil,
>> >
>> >I see this in the platform checkout code:
>> >cd "%s" && git checkout 2.1.0rc1
>> >
>> >Do you think this is ok to change to 2.1.0, or are there specific things
>> >in
>> >rc1 that prevent us from moving up to this newer tag?
>> >
>> >
>> >
>> >On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
>> >
>> >> http://people.apache.org/~steven/
>> >>
>> >> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
>> >> <re...@gmail.com> wrote:
>> >> > This is probably a stupid question, but is the 2.1 release package
>> >> > available somewhere for download yet? I'd like to start basing my
>> >>work on
>> >> > that.
>> >> >
>> >> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
>> >> reinstein.mike@gmail.com>wrote:
>> >> >
>> >> >> Thanks Fil. I'll start taking cordova-client for a spin, and see how
>> >> that
>> >> >> goes. :)
>> >> >>
>> >> >>
>> >> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >>
>> >> >>> If you ask me, just give the tools a spin and let me know what
>> >> >>> issues/problems/feature requests you could use.
>> >> >>>
>> >> >>> Last I checked there was an issue with installing iOS resource
>> files
>> >> via
>> >> >>> the pluginstall tool. This could be a reasonable thing to tackle if
>> >>you
>> >> >>> enjoy mucking about with xcodeproj files.
>> >> >>>
>> >> >>> I'm informally tracking issues on my fork of cordova-client on
>> >>github
>> >> >>> here: https://github.com/filmaj/cordova-client/issues?state=open
>> >> >>>
>> >> >>> Logging issues would be awesome. Resolving some would be even
>> >>better :)
>> >> >>>
>> >> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com>
>> >>wrote:
>> >> >>>
>> >> >>> >Apparently I wasn't logged into the wiki, so it wasn't some finer
>> >> grained
>> >> >>> >permissions issue. I've updated the doc to point at the right
>> >>place:
>> >> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> >>> >
>> >> >>> >What should I work on next? Based on Andrew's feedback my doc work
>> >>on
>> >> >>> >merging pluginstall with it's spec isnt helpful at this point, so
>> >>I'm
>> >> >>> >ready
>> >> >>> >for more tasks. Any suggestions? I could start hacking on
>> >> cordova-client,
>> >> >>> >or working on some kind of central plugin repo which cordova
>> really
>> >> needs
>> >> >>> >(IMO), or something else. Where do you folks feel the plugin
>> >>project
>> >> >>> could
>> >> >>> >use the most "love" ?
>> >> >>> >
>> >> >>> >-Mike
>> >> >>> >
>> >> >>> >
>> >> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
>> >> >>> ><re...@gmail.com>wrote:
>> >> >>> >
>> >> >>> >> I've signed up for the wiki, but it's listing the page as
>> >>immutable.
>> >> >>> I'm
>> >> >>> >> assuming someone with write permissions would have to make the
>> >> changes.
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
>> >> >>> >><mi...@michaelbrooks.ca>wrote:
>> >> >>> >>
>> >> >>> >>> >
>> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
>> >>jira
>> >> >>> >>> > credentials work?
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> You need to sign up. The account name convention has been a
>> >> camel-case
>> >> >>> >>>of
>> >> >>> >>> your first and last name. e.g. MichaelBrooks. However, you're
>> >>free
>> >> to
>> >> >>> >>>do
>> >> >>> >>> whatever you want.
>> >> >>> >>>
>> >> >>> >>> I just got back from vacation and read through this discussion.
>> >> >>> Amazing
>> >> >>> >>> for
>> >> >>> >>> Mike, Michal, and Fil!
>> >> >>> >>>
>> >> >>> >>> Michael
>> >> >>> >>>
>> >> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
>> >> >>> >>><reinstein.mike@gmail.com
>> >> >>> >>> >wrote:
>> >> >>> >>>
>> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
>> >>jira
>> >> >>> >>> > credentials work?
>> >> >>> >>> >
>> >> >>> >>> > -Mike
>> >> >>> >>> >
>> >> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
>> >> >>> pmuellr@gmail.com>
>> >> >>> >>> > wrote:
>> >> >>> >>> >
>> >> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>> >> >>> >>> > reinstein.mike@gmail.com
>> >> >>> >>> > > >wrote:
>> >> >>> >>> > >
>> >> >>> >>> > > > I'd like to propose we replace the contents of this wiki
>> >>page
>> >> >>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>with a
>> >> >>> >>> simple
>> >> >>> >>> > > > note
>> >> >>> >>> > > > that points at the correct url "This documentation has
>> >>merged
>> >> >>> >>>into
>> >> >>> >>> > > >
>> >> >>> >>>
>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> >> >>> >>> > > >
>> >> >>> >>> > >
>> >> >>> >>> > > I was just looking at the wiki page
>> >> >>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesignand
>> >> >>> >>>thought -
>> >> >>> >>> > > "wow,
>> >> >>> >>> > > that's the same thing I was thinking about", then scrolled
>> >>down
>> >> >>> and
>> >> >>> >>> > noticed
>> >> >>> >>> > > it was written by me. :-)
>> >> >>> >>> > >
>> >> >>> >>> > > Feel free to delete, this was a dump of some of my thoughts
>> >> around
>> >> >>> >>>the
>> >> >>> >>> > > command-line tooling. I haven't had time to even follow
>> the
>> >> >>> >>>current
>> >> >>> >>> CLI
>> >> >>> >>> > > work, but mean to catch up soon, so if nothing is relevant,
>> >> pitch
>> >> >>> >>>it.
>> >> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll
>> >>have
>> >> >>> >>> comments
>> >> >>> >>> > :-)
>> >> >>> >>> > >
>> >> >>> >>> > > --
>> >> >>> >>> > > Patrick Mueller
>> >> >>> >>> > > http://muellerware.org
>> >> >>> >>> > >
>> >> >>> >>> >
>> >> >>> >>>
>> >> >>> >>
>> >> >>> >>
>> >> >>>
>> >> >>>
>> >> >>
>> >>
>>
>>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hey Fil,
I've got the code running locally, I'm able to create projects, add
platforms, etc. I'm going through the code now, doing some cleanup, etc and
will have a pull request pretty soon (maybe later tonight.)
I have a question, I noticed that the platforms directories include a www/
in each one. I'm wondering why. For example:
myproject
|- platforms
`- ios
| - build
On Fri, Sep 14, 2012 at 5:02 PM, Filip Maj <fi...@adobe.com> wrote:
> Nope I think that's fine. That was the latest tag when I wrote that code :)
>
> On 9/14/12 1:56 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >Hey Fil,
> >
> >I see this in the platform checkout code:
> >cd "%s" && git checkout 2.1.0rc1
> >
> >Do you think this is ok to change to 2.1.0, or are there specific things
> >in
> >rc1 that prevent us from moving up to this newer tag?
> >
> >
> >
> >On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
> >
> >> http://people.apache.org/~steven/
> >>
> >> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
> >> <re...@gmail.com> wrote:
> >> > This is probably a stupid question, but is the 2.1 release package
> >> > available somewhere for download yet? I'd like to start basing my
> >>work on
> >> > that.
> >> >
> >> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
> >> reinstein.mike@gmail.com>wrote:
> >> >
> >> >> Thanks Fil. I'll start taking cordova-client for a spin, and see how
> >> that
> >> >> goes. :)
> >> >>
> >> >>
> >> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >>> If you ask me, just give the tools a spin and let me know what
> >> >>> issues/problems/feature requests you could use.
> >> >>>
> >> >>> Last I checked there was an issue with installing iOS resource files
> >> via
> >> >>> the pluginstall tool. This could be a reasonable thing to tackle if
> >>you
> >> >>> enjoy mucking about with xcodeproj files.
> >> >>>
> >> >>> I'm informally tracking issues on my fork of cordova-client on
> >>github
> >> >>> here: https://github.com/filmaj/cordova-client/issues?state=open
> >> >>>
> >> >>> Logging issues would be awesome. Resolving some would be even
> >>better :)
> >> >>>
> >> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com>
> >>wrote:
> >> >>>
> >> >>> >Apparently I wasn't logged into the wiki, so it wasn't some finer
> >> grained
> >> >>> >permissions issue. I've updated the doc to point at the right
> >>place:
> >> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>> >
> >> >>> >What should I work on next? Based on Andrew's feedback my doc work
> >>on
> >> >>> >merging pluginstall with it's spec isnt helpful at this point, so
> >>I'm
> >> >>> >ready
> >> >>> >for more tasks. Any suggestions? I could start hacking on
> >> cordova-client,
> >> >>> >or working on some kind of central plugin repo which cordova really
> >> needs
> >> >>> >(IMO), or something else. Where do you folks feel the plugin
> >>project
> >> >>> could
> >> >>> >use the most "love" ?
> >> >>> >
> >> >>> >-Mike
> >> >>> >
> >> >>> >
> >> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
> >> >>> ><re...@gmail.com>wrote:
> >> >>> >
> >> >>> >> I've signed up for the wiki, but it's listing the page as
> >>immutable.
> >> >>> I'm
> >> >>> >> assuming someone with write permissions would have to make the
> >> changes.
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
> >> >>> >><mi...@michaelbrooks.ca>wrote:
> >> >>> >>
> >> >>> >>> >
> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
> >>jira
> >> >>> >>> > credentials work?
> >> >>> >>>
> >> >>> >>>
> >> >>> >>> You need to sign up. The account name convention has been a
> >> camel-case
> >> >>> >>>of
> >> >>> >>> your first and last name. e.g. MichaelBrooks. However, you're
> >>free
> >> to
> >> >>> >>>do
> >> >>> >>> whatever you want.
> >> >>> >>>
> >> >>> >>> I just got back from vacation and read through this discussion.
> >> >>> Amazing
> >> >>> >>> for
> >> >>> >>> Mike, Michal, and Fil!
> >> >>> >>>
> >> >>> >>> Michael
> >> >>> >>>
> >> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
> >> >>> >>><reinstein.mike@gmail.com
> >> >>> >>> >wrote:
> >> >>> >>>
> >> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
> >>jira
> >> >>> >>> > credentials work?
> >> >>> >>> >
> >> >>> >>> > -Mike
> >> >>> >>> >
> >> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
> >> >>> pmuellr@gmail.com>
> >> >>> >>> > wrote:
> >> >>> >>> >
> >> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> >> >>> >>> > reinstein.mike@gmail.com
> >> >>> >>> > > >wrote:
> >> >>> >>> > >
> >> >>> >>> > > > I'd like to propose we replace the contents of this wiki
> >>page
> >> >>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>with a
> >> >>> >>> simple
> >> >>> >>> > > > note
> >> >>> >>> > > > that points at the correct url "This documentation has
> >>merged
> >> >>> >>>into
> >> >>> >>> > > >
> >> >>> >>>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >> >>> >>> > > >
> >> >>> >>> > >
> >> >>> >>> > > I was just looking at the wiki page
> >> >>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
> >> >>> >>>thought -
> >> >>> >>> > > "wow,
> >> >>> >>> > > that's the same thing I was thinking about", then scrolled
> >>down
> >> >>> and
> >> >>> >>> > noticed
> >> >>> >>> > > it was written by me. :-)
> >> >>> >>> > >
> >> >>> >>> > > Feel free to delete, this was a dump of some of my thoughts
> >> around
> >> >>> >>>the
> >> >>> >>> > > command-line tooling. I haven't had time to even follow the
> >> >>> >>>current
> >> >>> >>> CLI
> >> >>> >>> > > work, but mean to catch up soon, so if nothing is relevant,
> >> pitch
> >> >>> >>>it.
> >> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll
> >>have
> >> >>> >>> comments
> >> >>> >>> > :-)
> >> >>> >>> > >
> >> >>> >>> > > --
> >> >>> >>> > > Patrick Mueller
> >> >>> >>> > > http://muellerware.org
> >> >>> >>> > >
> >> >>> >>> >
> >> >>> >>>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >> >>
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Nope I think that's fine. That was the latest tag when I wrote that code :)
On 9/14/12 1:56 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>Hey Fil,
>
>I see this in the platform checkout code:
>cd "%s" && git checkout 2.1.0rc1
>
>Do you think this is ok to change to 2.1.0, or are there specific things
>in
>rc1 that prevent us from moving up to this newer tag?
>
>
>
>On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
>
>> http://people.apache.org/~steven/
>>
>> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
>> <re...@gmail.com> wrote:
>> > This is probably a stupid question, but is the 2.1 release package
>> > available somewhere for download yet? I'd like to start basing my
>>work on
>> > that.
>> >
>> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
>> reinstein.mike@gmail.com>wrote:
>> >
>> >> Thanks Fil. I'll start taking cordova-client for a spin, and see how
>> that
>> >> goes. :)
>> >>
>> >>
>> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >>> If you ask me, just give the tools a spin and let me know what
>> >>> issues/problems/feature requests you could use.
>> >>>
>> >>> Last I checked there was an issue with installing iOS resource files
>> via
>> >>> the pluginstall tool. This could be a reasonable thing to tackle if
>>you
>> >>> enjoy mucking about with xcodeproj files.
>> >>>
>> >>> I'm informally tracking issues on my fork of cordova-client on
>>github
>> >>> here: https://github.com/filmaj/cordova-client/issues?state=open
>> >>>
>> >>> Logging issues would be awesome. Resolving some would be even
>>better :)
>> >>>
>> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com>
>>wrote:
>> >>>
>> >>> >Apparently I wasn't logged into the wiki, so it wasn't some finer
>> grained
>> >>> >permissions issue. I've updated the doc to point at the right
>>place:
>> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>> >
>> >>> >What should I work on next? Based on Andrew's feedback my doc work
>>on
>> >>> >merging pluginstall with it's spec isnt helpful at this point, so
>>I'm
>> >>> >ready
>> >>> >for more tasks. Any suggestions? I could start hacking on
>> cordova-client,
>> >>> >or working on some kind of central plugin repo which cordova really
>> needs
>> >>> >(IMO), or something else. Where do you folks feel the plugin
>>project
>> >>> could
>> >>> >use the most "love" ?
>> >>> >
>> >>> >-Mike
>> >>> >
>> >>> >
>> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
>> >>> ><re...@gmail.com>wrote:
>> >>> >
>> >>> >> I've signed up for the wiki, but it's listing the page as
>>immutable.
>> >>> I'm
>> >>> >> assuming someone with write permissions would have to make the
>> changes.
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
>> >>> >><mi...@michaelbrooks.ca>wrote:
>> >>> >>
>> >>> >>> >
>> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
>>jira
>> >>> >>> > credentials work?
>> >>> >>>
>> >>> >>>
>> >>> >>> You need to sign up. The account name convention has been a
>> camel-case
>> >>> >>>of
>> >>> >>> your first and last name. e.g. MichaelBrooks. However, you're
>>free
>> to
>> >>> >>>do
>> >>> >>> whatever you want.
>> >>> >>>
>> >>> >>> I just got back from vacation and read through this discussion.
>> >>> Amazing
>> >>> >>> for
>> >>> >>> Mike, Michal, and Fil!
>> >>> >>>
>> >>> >>> Michael
>> >>> >>>
>> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
>> >>> >>><reinstein.mike@gmail.com
>> >>> >>> >wrote:
>> >>> >>>
>> >>> >>> > Do I need to sign up for a cordova wiki account, or will my
>>jira
>> >>> >>> > credentials work?
>> >>> >>> >
>> >>> >>> > -Mike
>> >>> >>> >
>> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
>> >>> pmuellr@gmail.com>
>> >>> >>> > wrote:
>> >>> >>> >
>> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>> >>> >>> > reinstein.mike@gmail.com
>> >>> >>> > > >wrote:
>> >>> >>> > >
>> >>> >>> > > > I'd like to propose we replace the contents of this wiki
>>page
>> >>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign
>>with a
>> >>> >>> simple
>> >>> >>> > > > note
>> >>> >>> > > > that points at the correct url "This documentation has
>>merged
>> >>> >>>into
>> >>> >>> > > >
>> >>> >>>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> >>> >>> > > >
>> >>> >>> > >
>> >>> >>> > > I was just looking at the wiki page
>> >>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
>> >>> >>>thought -
>> >>> >>> > > "wow,
>> >>> >>> > > that's the same thing I was thinking about", then scrolled
>>down
>> >>> and
>> >>> >>> > noticed
>> >>> >>> > > it was written by me. :-)
>> >>> >>> > >
>> >>> >>> > > Feel free to delete, this was a dump of some of my thoughts
>> around
>> >>> >>>the
>> >>> >>> > > command-line tooling. I haven't had time to even follow the
>> >>> >>>current
>> >>> >>> CLI
>> >>> >>> > > work, but mean to catch up soon, so if nothing is relevant,
>> pitch
>> >>> >>>it.
>> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll
>>have
>> >>> >>> comments
>> >>> >>> > :-)
>> >>> >>> > >
>> >>> >>> > > --
>> >>> >>> > > Patrick Mueller
>> >>> >>> > > http://muellerware.org
>> >>> >>> > >
>> >>> >>> >
>> >>> >>>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>> >>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hey Fil,
I see this in the platform checkout code:
cd "%s" && git checkout 2.1.0rc1
Do you think this is ok to change to 2.1.0, or are there specific things in
rc1 that prevent us from moving up to this newer tag?
On Fri, Sep 14, 2012 at 3:16 PM, Shazron <sh...@gmail.com> wrote:
> http://people.apache.org/~steven/
>
> On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
> <re...@gmail.com> wrote:
> > This is probably a stupid question, but is the 2.1 release package
> > available somewhere for download yet? I'd like to start basing my work on
> > that.
> >
> > On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <
> reinstein.mike@gmail.com>wrote:
> >
> >> Thanks Fil. I'll start taking cordova-client for a spin, and see how
> that
> >> goes. :)
> >>
> >>
> >> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >>> If you ask me, just give the tools a spin and let me know what
> >>> issues/problems/feature requests you could use.
> >>>
> >>> Last I checked there was an issue with installing iOS resource files
> via
> >>> the pluginstall tool. This could be a reasonable thing to tackle if you
> >>> enjoy mucking about with xcodeproj files.
> >>>
> >>> I'm informally tracking issues on my fork of cordova-client on github
> >>> here: https://github.com/filmaj/cordova-client/issues?state=open
> >>>
> >>> Logging issues would be awesome. Resolving some would be even better :)
> >>>
> >>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com> wrote:
> >>>
> >>> >Apparently I wasn't logged into the wiki, so it wasn't some finer
> grained
> >>> >permissions issue. I've updated the doc to point at the right place:
> >>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>> >
> >>> >What should I work on next? Based on Andrew's feedback my doc work on
> >>> >merging pluginstall with it's spec isnt helpful at this point, so I'm
> >>> >ready
> >>> >for more tasks. Any suggestions? I could start hacking on
> cordova-client,
> >>> >or working on some kind of central plugin repo which cordova really
> needs
> >>> >(IMO), or something else. Where do you folks feel the plugin project
> >>> could
> >>> >use the most "love" ?
> >>> >
> >>> >-Mike
> >>> >
> >>> >
> >>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
> >>> ><re...@gmail.com>wrote:
> >>> >
> >>> >> I've signed up for the wiki, but it's listing the page as immutable.
> >>> I'm
> >>> >> assuming someone with write permissions would have to make the
> changes.
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
> >>> >><mi...@michaelbrooks.ca>wrote:
> >>> >>
> >>> >>> >
> >>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
> >>> >>> > credentials work?
> >>> >>>
> >>> >>>
> >>> >>> You need to sign up. The account name convention has been a
> camel-case
> >>> >>>of
> >>> >>> your first and last name. e.g. MichaelBrooks. However, you're free
> to
> >>> >>>do
> >>> >>> whatever you want.
> >>> >>>
> >>> >>> I just got back from vacation and read through this discussion.
> >>> Amazing
> >>> >>> for
> >>> >>> Mike, Michal, and Fil!
> >>> >>>
> >>> >>> Michael
> >>> >>>
> >>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
> >>> >>><reinstein.mike@gmail.com
> >>> >>> >wrote:
> >>> >>>
> >>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
> >>> >>> > credentials work?
> >>> >>> >
> >>> >>> > -Mike
> >>> >>> >
> >>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
> >>> pmuellr@gmail.com>
> >>> >>> > wrote:
> >>> >>> >
> >>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> >>> >>> > reinstein.mike@gmail.com
> >>> >>> > > >wrote:
> >>> >>> > >
> >>> >>> > > > I'd like to propose we replace the contents of this wiki page
> >>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> >>> >>> simple
> >>> >>> > > > note
> >>> >>> > > > that points at the correct url "This documentation has merged
> >>> >>>into
> >>> >>> > > >
> >>> >>>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >>> >>> > > >
> >>> >>> > >
> >>> >>> > > I was just looking at the wiki page
> >>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
> >>> >>>thought -
> >>> >>> > > "wow,
> >>> >>> > > that's the same thing I was thinking about", then scrolled down
> >>> and
> >>> >>> > noticed
> >>> >>> > > it was written by me. :-)
> >>> >>> > >
> >>> >>> > > Feel free to delete, this was a dump of some of my thoughts
> around
> >>> >>>the
> >>> >>> > > command-line tooling. I haven't had time to even follow the
> >>> >>>current
> >>> >>> CLI
> >>> >>> > > work, but mean to catch up soon, so if nothing is relevant,
> pitch
> >>> >>>it.
> >>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
> >>> >>> comments
> >>> >>> > :-)
> >>> >>> > >
> >>> >>> > > --
> >>> >>> > > Patrick Mueller
> >>> >>> > > http://muellerware.org
> >>> >>> > >
> >>> >>> >
> >>> >>>
> >>> >>
> >>> >>
> >>>
> >>>
> >>
>
Re: plugin tooling/specification
Posted by Shazron <sh...@gmail.com>.
http://people.apache.org/~steven/
On Fri, Sep 14, 2012 at 12:15 PM, Mike Reinstein
<re...@gmail.com> wrote:
> This is probably a stupid question, but is the 2.1 release package
> available somewhere for download yet? I'd like to start basing my work on
> that.
>
> On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <re...@gmail.com>wrote:
>
>> Thanks Fil. I'll start taking cordova-client for a spin, and see how that
>> goes. :)
>>
>>
>> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>>> If you ask me, just give the tools a spin and let me know what
>>> issues/problems/feature requests you could use.
>>>
>>> Last I checked there was an issue with installing iOS resource files via
>>> the pluginstall tool. This could be a reasonable thing to tackle if you
>>> enjoy mucking about with xcodeproj files.
>>>
>>> I'm informally tracking issues on my fork of cordova-client on github
>>> here: https://github.com/filmaj/cordova-client/issues?state=open
>>>
>>> Logging issues would be awesome. Resolving some would be even better :)
>>>
>>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>>
>>> >Apparently I wasn't logged into the wiki, so it wasn't some finer grained
>>> >permissions issue. I've updated the doc to point at the right place:
>>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>>> >
>>> >What should I work on next? Based on Andrew's feedback my doc work on
>>> >merging pluginstall with it's spec isnt helpful at this point, so I'm
>>> >ready
>>> >for more tasks. Any suggestions? I could start hacking on cordova-client,
>>> >or working on some kind of central plugin repo which cordova really needs
>>> >(IMO), or something else. Where do you folks feel the plugin project
>>> could
>>> >use the most "love" ?
>>> >
>>> >-Mike
>>> >
>>> >
>>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
>>> ><re...@gmail.com>wrote:
>>> >
>>> >> I've signed up for the wiki, but it's listing the page as immutable.
>>> I'm
>>> >> assuming someone with write permissions would have to make the changes.
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
>>> >><mi...@michaelbrooks.ca>wrote:
>>> >>
>>> >>> >
>>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
>>> >>> > credentials work?
>>> >>>
>>> >>>
>>> >>> You need to sign up. The account name convention has been a camel-case
>>> >>>of
>>> >>> your first and last name. e.g. MichaelBrooks. However, you're free to
>>> >>>do
>>> >>> whatever you want.
>>> >>>
>>> >>> I just got back from vacation and read through this discussion.
>>> Amazing
>>> >>> for
>>> >>> Mike, Michal, and Fil!
>>> >>>
>>> >>> Michael
>>> >>>
>>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
>>> >>><reinstein.mike@gmail.com
>>> >>> >wrote:
>>> >>>
>>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
>>> >>> > credentials work?
>>> >>> >
>>> >>> > -Mike
>>> >>> >
>>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
>>> pmuellr@gmail.com>
>>> >>> > wrote:
>>> >>> >
>>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>>> >>> > reinstein.mike@gmail.com
>>> >>> > > >wrote:
>>> >>> > >
>>> >>> > > > I'd like to propose we replace the contents of this wiki page
>>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
>>> >>> simple
>>> >>> > > > note
>>> >>> > > > that points at the correct url "This documentation has merged
>>> >>>into
>>> >>> > > >
>>> >>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>>> >>> > > >
>>> >>> > >
>>> >>> > > I was just looking at the wiki page
>>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
>>> >>>thought -
>>> >>> > > "wow,
>>> >>> > > that's the same thing I was thinking about", then scrolled down
>>> and
>>> >>> > noticed
>>> >>> > > it was written by me. :-)
>>> >>> > >
>>> >>> > > Feel free to delete, this was a dump of some of my thoughts around
>>> >>>the
>>> >>> > > command-line tooling. I haven't had time to even follow the
>>> >>>current
>>> >>> CLI
>>> >>> > > work, but mean to catch up soon, so if nothing is relevant, pitch
>>> >>>it.
>>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
>>> >>> comments
>>> >>> > :-)
>>> >>> > >
>>> >>> > > --
>>> >>> > > Patrick Mueller
>>> >>> > > http://muellerware.org
>>> >>> > >
>>> >>> >
>>> >>>
>>> >>
>>> >>
>>>
>>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
This is probably a stupid question, but is the 2.1 release package
available somewhere for download yet? I'd like to start basing my work on
that.
On Fri, Sep 14, 2012 at 1:34 PM, Mike Reinstein <re...@gmail.com>wrote:
> Thanks Fil. I'll start taking cordova-client for a spin, and see how that
> goes. :)
>
>
> On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> If you ask me, just give the tools a spin and let me know what
>> issues/problems/feature requests you could use.
>>
>> Last I checked there was an issue with installing iOS resource files via
>> the pluginstall tool. This could be a reasonable thing to tackle if you
>> enjoy mucking about with xcodeproj files.
>>
>> I'm informally tracking issues on my fork of cordova-client on github
>> here: https://github.com/filmaj/cordova-client/issues?state=open
>>
>> Logging issues would be awesome. Resolving some would be even better :)
>>
>> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>
>> >Apparently I wasn't logged into the wiki, so it wasn't some finer grained
>> >permissions issue. I've updated the doc to point at the right place:
>> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >
>> >What should I work on next? Based on Andrew's feedback my doc work on
>> >merging pluginstall with it's spec isnt helpful at this point, so I'm
>> >ready
>> >for more tasks. Any suggestions? I could start hacking on cordova-client,
>> >or working on some kind of central plugin repo which cordova really needs
>> >(IMO), or something else. Where do you folks feel the plugin project
>> could
>> >use the most "love" ?
>> >
>> >-Mike
>> >
>> >
>> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
>> ><re...@gmail.com>wrote:
>> >
>> >> I've signed up for the wiki, but it's listing the page as immutable.
>> I'm
>> >> assuming someone with write permissions would have to make the changes.
>> >>
>> >>
>> >>
>> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
>> >><mi...@michaelbrooks.ca>wrote:
>> >>
>> >>> >
>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
>> >>> > credentials work?
>> >>>
>> >>>
>> >>> You need to sign up. The account name convention has been a camel-case
>> >>>of
>> >>> your first and last name. e.g. MichaelBrooks. However, you're free to
>> >>>do
>> >>> whatever you want.
>> >>>
>> >>> I just got back from vacation and read through this discussion.
>> Amazing
>> >>> for
>> >>> Mike, Michal, and Fil!
>> >>>
>> >>> Michael
>> >>>
>> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
>> >>><reinstein.mike@gmail.com
>> >>> >wrote:
>> >>>
>> >>> > Do I need to sign up for a cordova wiki account, or will my jira
>> >>> > credentials work?
>> >>> >
>> >>> > -Mike
>> >>> >
>> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <
>> pmuellr@gmail.com>
>> >>> > wrote:
>> >>> >
>> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>> >>> > reinstein.mike@gmail.com
>> >>> > > >wrote:
>> >>> > >
>> >>> > > > I'd like to propose we replace the contents of this wiki page
>> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
>> >>> simple
>> >>> > > > note
>> >>> > > > that points at the correct url "This documentation has merged
>> >>>into
>> >>> > > >
>> >>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> >>> > > >
>> >>> > >
>> >>> > > I was just looking at the wiki page
>> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
>> >>>thought -
>> >>> > > "wow,
>> >>> > > that's the same thing I was thinking about", then scrolled down
>> and
>> >>> > noticed
>> >>> > > it was written by me. :-)
>> >>> > >
>> >>> > > Feel free to delete, this was a dump of some of my thoughts around
>> >>>the
>> >>> > > command-line tooling. I haven't had time to even follow the
>> >>>current
>> >>> CLI
>> >>> > > work, but mean to catch up soon, so if nothing is relevant, pitch
>> >>>it.
>> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
>> >>> comments
>> >>> > :-)
>> >>> > >
>> >>> > > --
>> >>> > > Patrick Mueller
>> >>> > > http://muellerware.org
>> >>> > >
>> >>> >
>> >>>
>> >>
>> >>
>>
>>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Thanks Fil. I'll start taking cordova-client for a spin, and see how that
goes. :)
On Fri, Sep 14, 2012 at 1:25 PM, Filip Maj <fi...@adobe.com> wrote:
> If you ask me, just give the tools a spin and let me know what
> issues/problems/feature requests you could use.
>
> Last I checked there was an issue with installing iOS resource files via
> the pluginstall tool. This could be a reasonable thing to tackle if you
> enjoy mucking about with xcodeproj files.
>
> I'm informally tracking issues on my fork of cordova-client on github
> here: https://github.com/filmaj/cordova-client/issues?state=open
>
> Logging issues would be awesome. Resolving some would be even better :)
>
> On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >Apparently I wasn't logged into the wiki, so it wasn't some finer grained
> >permissions issue. I've updated the doc to point at the right place:
> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >
> >What should I work on next? Based on Andrew's feedback my doc work on
> >merging pluginstall with it's spec isnt helpful at this point, so I'm
> >ready
> >for more tasks. Any suggestions? I could start hacking on cordova-client,
> >or working on some kind of central plugin repo which cordova really needs
> >(IMO), or something else. Where do you folks feel the plugin project could
> >use the most "love" ?
> >
> >-Mike
> >
> >
> >On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
> ><re...@gmail.com>wrote:
> >
> >> I've signed up for the wiki, but it's listing the page as immutable. I'm
> >> assuming someone with write permissions would have to make the changes.
> >>
> >>
> >>
> >> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
> >><mi...@michaelbrooks.ca>wrote:
> >>
> >>> >
> >>> > Do I need to sign up for a cordova wiki account, or will my jira
> >>> > credentials work?
> >>>
> >>>
> >>> You need to sign up. The account name convention has been a camel-case
> >>>of
> >>> your first and last name. e.g. MichaelBrooks. However, you're free to
> >>>do
> >>> whatever you want.
> >>>
> >>> I just got back from vacation and read through this discussion. Amazing
> >>> for
> >>> Mike, Michal, and Fil!
> >>>
> >>> Michael
> >>>
> >>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
> >>><reinstein.mike@gmail.com
> >>> >wrote:
> >>>
> >>> > Do I need to sign up for a cordova wiki account, or will my jira
> >>> > credentials work?
> >>> >
> >>> > -Mike
> >>> >
> >>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pmuellr@gmail.com
> >
> >>> > wrote:
> >>> >
> >>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> >>> > reinstein.mike@gmail.com
> >>> > > >wrote:
> >>> > >
> >>> > > > I'd like to propose we replace the contents of this wiki page
> >>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> >>> simple
> >>> > > > note
> >>> > > > that points at the correct url "This documentation has merged
> >>>into
> >>> > > >
> >>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >>> > > >
> >>> > >
> >>> > > I was just looking at the wiki page
> >>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
> >>>thought -
> >>> > > "wow,
> >>> > > that's the same thing I was thinking about", then scrolled down and
> >>> > noticed
> >>> > > it was written by me. :-)
> >>> > >
> >>> > > Feel free to delete, this was a dump of some of my thoughts around
> >>>the
> >>> > > command-line tooling. I haven't had time to even follow the
> >>>current
> >>> CLI
> >>> > > work, but mean to catch up soon, so if nothing is relevant, pitch
> >>>it.
> >>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
> >>> comments
> >>> > :-)
> >>> > >
> >>> > > --
> >>> > > Patrick Mueller
> >>> > > http://muellerware.org
> >>> > >
> >>> >
> >>>
> >>
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
If you ask me, just give the tools a spin and let me know what
issues/problems/feature requests you could use.
Last I checked there was an issue with installing iOS resource files via
the pluginstall tool. This could be a reasonable thing to tackle if you
enjoy mucking about with xcodeproj files.
I'm informally tracking issues on my fork of cordova-client on github
here: https://github.com/filmaj/cordova-client/issues?state=open
Logging issues would be awesome. Resolving some would be even better :)
On 9/13/12 7:14 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>Apparently I wasn't logged into the wiki, so it wasn't some finer grained
>permissions issue. I've updated the doc to point at the right place:
>http://wiki.apache.org/cordova/CommandLineToolingDesign
>
>What should I work on next? Based on Andrew's feedback my doc work on
>merging pluginstall with it's spec isnt helpful at this point, so I'm
>ready
>for more tasks. Any suggestions? I could start hacking on cordova-client,
>or working on some kind of central plugin repo which cordova really needs
>(IMO), or something else. Where do you folks feel the plugin project could
>use the most "love" ?
>
>-Mike
>
>
>On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein
><re...@gmail.com>wrote:
>
>> I've signed up for the wiki, but it's listing the page as immutable. I'm
>> assuming someone with write permissions would have to make the changes.
>>
>>
>>
>> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks
>><mi...@michaelbrooks.ca>wrote:
>>
>>> >
>>> > Do I need to sign up for a cordova wiki account, or will my jira
>>> > credentials work?
>>>
>>>
>>> You need to sign up. The account name convention has been a camel-case
>>>of
>>> your first and last name. e.g. MichaelBrooks. However, you're free to
>>>do
>>> whatever you want.
>>>
>>> I just got back from vacation and read through this discussion. Amazing
>>> for
>>> Mike, Michal, and Fil!
>>>
>>> Michael
>>>
>>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein
>>><reinstein.mike@gmail.com
>>> >wrote:
>>>
>>> > Do I need to sign up for a cordova wiki account, or will my jira
>>> > credentials work?
>>> >
>>> > -Mike
>>> >
>>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pm...@gmail.com>
>>> > wrote:
>>> >
>>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>>> > reinstein.mike@gmail.com
>>> > > >wrote:
>>> > >
>>> > > > I'd like to propose we replace the contents of this wiki page
>>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
>>> simple
>>> > > > note
>>> > > > that points at the correct url "This documentation has merged
>>>into
>>> > > >
>>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>>> > > >
>>> > >
>>> > > I was just looking at the wiki page
>>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and
>>>thought -
>>> > > "wow,
>>> > > that's the same thing I was thinking about", then scrolled down and
>>> > noticed
>>> > > it was written by me. :-)
>>> > >
>>> > > Feel free to delete, this was a dump of some of my thoughts around
>>>the
>>> > > command-line tooling. I haven't had time to even follow the
>>>current
>>> CLI
>>> > > work, but mean to catch up soon, so if nothing is relevant, pitch
>>>it.
>>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
>>> comments
>>> > :-)
>>> > >
>>> > > --
>>> > > Patrick Mueller
>>> > > http://muellerware.org
>>> > >
>>> >
>>>
>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Apparently I wasn't logged into the wiki, so it wasn't some finer grained
permissions issue. I've updated the doc to point at the right place:
http://wiki.apache.org/cordova/CommandLineToolingDesign
What should I work on next? Based on Andrew's feedback my doc work on
merging pluginstall with it's spec isnt helpful at this point, so I'm ready
for more tasks. Any suggestions? I could start hacking on cordova-client,
or working on some kind of central plugin repo which cordova really needs
(IMO), or something else. Where do you folks feel the plugin project could
use the most "love" ?
-Mike
On Wed, Sep 12, 2012 at 2:00 PM, Mike Reinstein <re...@gmail.com>wrote:
> I've signed up for the wiki, but it's listing the page as immutable. I'm
> assuming someone with write permissions would have to make the changes.
>
>
>
> On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks <mi...@michaelbrooks.ca>wrote:
>
>> >
>> > Do I need to sign up for a cordova wiki account, or will my jira
>> > credentials work?
>>
>>
>> You need to sign up. The account name convention has been a camel-case of
>> your first and last name. e.g. MichaelBrooks. However, you're free to do
>> whatever you want.
>>
>> I just got back from vacation and read through this discussion. Amazing
>> for
>> Mike, Michal, and Fil!
>>
>> Michael
>>
>> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein <reinstein.mike@gmail.com
>> >wrote:
>>
>> > Do I need to sign up for a cordova wiki account, or will my jira
>> > credentials work?
>> >
>> > -Mike
>> >
>> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pm...@gmail.com>
>> > wrote:
>> >
>> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
>> > reinstein.mike@gmail.com
>> > > >wrote:
>> > >
>> > > > I'd like to propose we replace the contents of this wiki page
>> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
>> simple
>> > > > note
>> > > > that points at the correct url "This documentation has merged into
>> > > >
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>> > > >
>> > >
>> > > I was just looking at the wiki page
>> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and thought -
>> > > "wow,
>> > > that's the same thing I was thinking about", then scrolled down and
>> > noticed
>> > > it was written by me. :-)
>> > >
>> > > Feel free to delete, this was a dump of some of my thoughts around the
>> > > command-line tooling. I haven't had time to even follow the current
>> CLI
>> > > work, but mean to catch up soon, so if nothing is relevant, pitch it.
>> > > Assuming I catch up with the ongoing work, I'm sure I'll have
>> comments
>> > :-)
>> > >
>> > > --
>> > > Patrick Mueller
>> > > http://muellerware.org
>> > >
>> >
>>
>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
I've signed up for the wiki, but it's listing the page as immutable. I'm
assuming someone with write permissions would have to make the changes.
On Wed, Sep 12, 2012 at 1:10 PM, Michael Brooks <mi...@michaelbrooks.ca>wrote:
> >
> > Do I need to sign up for a cordova wiki account, or will my jira
> > credentials work?
>
>
> You need to sign up. The account name convention has been a camel-case of
> your first and last name. e.g. MichaelBrooks. However, you're free to do
> whatever you want.
>
> I just got back from vacation and read through this discussion. Amazing for
> Mike, Michal, and Fil!
>
> Michael
>
> On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > Do I need to sign up for a cordova wiki account, or will my jira
> > credentials work?
> >
> > -Mike
> >
> > On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pm...@gmail.com>
> > wrote:
> >
> > > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> > reinstein.mike@gmail.com
> > > >wrote:
> > >
> > > > I'd like to propose we replace the contents of this wiki page
> > > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a
> simple
> > > > note
> > > > that points at the correct url "This documentation has merged into
> > > > https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> "
> > > >
> > >
> > > I was just looking at the wiki page
> > > http://wiki.apache.org/cordova/CommandLineToolingDesign and thought -
> > > "wow,
> > > that's the same thing I was thinking about", then scrolled down and
> > noticed
> > > it was written by me. :-)
> > >
> > > Feel free to delete, this was a dump of some of my thoughts around the
> > > command-line tooling. I haven't had time to even follow the current
> CLI
> > > work, but mean to catch up soon, so if nothing is relevant, pitch it.
> > > Assuming I catch up with the ongoing work, I'm sure I'll have comments
> > :-)
> > >
> > > --
> > > Patrick Mueller
> > > http://muellerware.org
> > >
> >
>
Re: plugin tooling/specification
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
>
> Do I need to sign up for a cordova wiki account, or will my jira
> credentials work?
You need to sign up. The account name convention has been a camel-case of
your first and last name. e.g. MichaelBrooks. However, you're free to do
whatever you want.
I just got back from vacation and read through this discussion. Amazing for
Mike, Michal, and Fil!
Michael
On Wed, Sep 12, 2012 at 9:52 AM, Mike Reinstein <re...@gmail.com>wrote:
> Do I need to sign up for a cordova wiki account, or will my jira
> credentials work?
>
> -Mike
>
> On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pm...@gmail.com>
> wrote:
>
> > On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <
> reinstein.mike@gmail.com
> > >wrote:
> >
> > > I'd like to propose we replace the contents of this wiki page
> > > http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
> > > note
> > > that points at the correct url "This documentation has merged into
> > > https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> > >
> >
> > I was just looking at the wiki page
> > http://wiki.apache.org/cordova/CommandLineToolingDesign and thought -
> > "wow,
> > that's the same thing I was thinking about", then scrolled down and
> noticed
> > it was written by me. :-)
> >
> > Feel free to delete, this was a dump of some of my thoughts around the
> > command-line tooling. I haven't had time to even follow the current CLI
> > work, but mean to catch up soon, so if nothing is relevant, pitch it.
> > Assuming I catch up with the ongoing work, I'm sure I'll have comments
> :-)
> >
> > --
> > Patrick Mueller
> > http://muellerware.org
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Do I need to sign up for a cordova wiki account, or will my jira
credentials work?
-Mike
On Wed, Sep 12, 2012 at 12:31 PM, Patrick Mueller <pm...@gmail.com> wrote:
> On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > I'd like to propose we replace the contents of this wiki page
> > http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
> > note
> > that points at the correct url "This documentation has merged into
> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
> >
>
> I was just looking at the wiki page
> http://wiki.apache.org/cordova/CommandLineToolingDesign and thought -
> "wow,
> that's the same thing I was thinking about", then scrolled down and noticed
> it was written by me. :-)
>
> Feel free to delete, this was a dump of some of my thoughts around the
> command-line tooling. I haven't had time to even follow the current CLI
> work, but mean to catch up soon, so if nothing is relevant, pitch it.
> Assuming I catch up with the ongoing work, I'm sure I'll have comments :-)
>
> --
> Patrick Mueller
> http://muellerware.org
>
Re: plugin tooling/specification
Posted by Patrick Mueller <pm...@gmail.com>.
On Tue, Sep 11, 2012 at 5:05 PM, Mike Reinstein <re...@gmail.com>wrote:
> I'd like to propose we replace the contents of this wiki page
> http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple
> note
> that points at the correct url "This documentation has merged into
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
>
I was just looking at the wiki page
http://wiki.apache.org/cordova/CommandLineToolingDesign and thought - "wow,
that's the same thing I was thinking about", then scrolled down and noticed
it was written by me. :-)
Feel free to delete, this was a dump of some of my thoughts around the
command-line tooling. I haven't had time to even follow the current CLI
work, but mean to catch up soon, so if nothing is relevant, pitch it.
Assuming I catch up with the ongoing work, I'm sure I'll have comments :-)
--
Patrick Mueller
http://muellerware.org
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
I'd like to propose we replace the contents of this wiki page
http://wiki.apache.org/cordova/CommandLineToolingDesign with a simple note
that points at the correct url "This documentation has merged into
https://github.com/apache/incubator-cordova-labs/tree/cordova-client"
Are there any other copies of this doc in other places? Other forks we can
eliminate to reduce confusion?
Has anyone heard from Andrew Lunny recently? I still have my change docs
that I submitted as a pull request but havent gotten any feedback, and it
seems like he hasn't been active on github in a few weeks. I'd prefer to
get the changes for pluginstall merged in so I can remove my copy.
-Mike
On Tue, Sep 11, 2012 at 10:52 AM, Mike Reinstein
<re...@gmail.com>wrote:
> > Subcommand argument formats still look off a bit
> Fixed
>
> > I think the $ is unneeded. All the other shell code
> > examples don't include the leading shell character.
>
> Actually, the opposite. Every example did have leading $ except for the
> first usage, which was inconsistent. But I agree $ is essentially just
> noise and have removed all instances from the doc. :)
>
> It would be nice to clean up the Random notes section. I think there may
> be some context associated with those chat discussion snippets that were
> copy/pasted in, so expanding on those points would be helpful for everyone
> else (including me.)
>
>
>
> On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mm...@chromium.org>wrote:
>
>> Subcommand argument formats still look off a bit, I think they should look
>> as follows:
>>
>> create <directory> [<id> [<name>]]
>> platform ls
>> platform add <platform>
>> platform remove <platform>
>> plugin ls
>> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
>> inconsistant with the other examples of add/remove)
>> plugin remove <plugin>
>> build
>> emulate
>>
>>
>>
>> Also, in the line "you can access the tool via $ cordova" I think the $
>> is
>> unneeded. All the other shell code examples don't include the leading
>> shell character. Alternatively we can add shell character to all the
>> other
>> shell command examples.
>>
>>
>> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
>> <re...@gmail.com>wrote:
>>
>> > I've updated my copy of the README.md, pulling changes from Filip,
>> Michal,
>> > and Brian:
>> >
>> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> >
>> > If I've missed anything please let me know.
>> >
>> > -Mike
>> >
>> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mm...@chromium.org>
>> > wrote:
>> >
>> > > I'm still unsure what a "baked in" plugin/platform would be, in that
>> > > context. Anyway, its not super important as the actual argument types
>> > may
>> > > change over time. The gist of it is just that you can reference a
>> > > plugin/platform using various typical methods and I think that point
>> gets
>> > > across well enough.
>> > >
>> > >
>> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
>> > >
>> > > > Considering the source I'd say 'baked' was intentional.
>> > > >
>> > > >
>> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
>> > > > <re...@gmail.com> wrote:
>> > > > >> assumed to be a 'backed in' platform/plugin
>> > > > >
>> > > > > This must be a typo, eh? 'baked' was intended?
>> > > > >
>> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
>> > > > >
>> > > > >> > * You will be able to access the client interface via: $
>> > > ./bin/cordova
>> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
>> > > > >>
>> > > > >> Agree...tho the npm install should be global (in /usr/local/bin)
>> > > > >> ....maybe we say as much?
>> > > > >>
>> > > > >>
>> > > > >> > * Subcommands section
>> > > > >> > * * Typical unix manpage style is to use [] to surround
>> optional
>> > > > >> arguments
>> > > > >> > <> to surround explanations and nothing for keywords. Examples
>> > that
>> > > > need
>> > > > >> > fixing include:
>> > > > >> > * * * create <directory> [<id>] [<name>]
>> > > > >> > * * * platform ls
>> > > > >> > * * * platform add <platform>
>> > > > >> > * * * etc
>> > > > >> > * * even if we aren't aiming for manpage style here, there
>> > > > >> > are inconsistencies
>> > > > >>
>> > > > >> Sure
>> > > > >>
>> > > > >>
>> > > > >> > * * File and Directory Structure ascii tree diagram
>> > > > >> > * * * suggest appending / after directory names
>> > > > >>
>> > > > >> +1
>> > > > >>
>> > > > >>
>> > > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
>> > Otherwise,
>> > > > it's
>> > > > >> > assumed to be a URL to a gzipped tar archive...
>> > > > >> > * * * Not sure what 'backed in' means here, nor how to identify
>> > > > something
>> > > > >> > as not being backed in so as to fallback to gzipped tar
>> > > > >> > * * * Also wording sounds more like "else .. else" instead of
>> > "else
>> > > > if ..
>> > > > >> > else" (if that makes sense) :P
>> > > > >>
>> > > > >> Ya not sure what this is about?
>> > > > >>
>> > > > >>
>> > > > >> > * * KewlApp directory structure ascii tree diagram
>> > > > >> > * * * based on my understanding of the text, the ios/android
>> > > platforms
>> > > > >> > should be subdirs of platforms/ and there should also be a
>> subdir
>> > > > listed
>> > > > >> in
>> > > > >> > plugins/
>> > > > >>
>> > > > >> Yes.
>> > > > >>
>> > > > >>
>> > > > >> > * * Running tests warning
>> > > > >> > * * * Perhaps explain how to bootstrap so as not to have
>> failing
>> > > tests
>> > > > >> > instead of assuming the reverse?
>> > > > >>
>> > > > >> Yes.
>> > > > >>
>> > > > >>
>> > > > >> > Also, I will look into bash completions in some spare cycles
>> and
>> > if
>> > > it
>> > > > >> > looks reasonable I may volunteer for the task. I've been
>> curious
>> > to
>> > > > >> learn
>> > > > >> > how those work :)
>> > > > >>
>> > > > >> That'd be awesome...but I'm thinking in a future iteration once
>> the
>> > > > >> actual CLI API is more solid. (But knock yourself out!)
>> > > > >>
>> > > >
>> > >
>> >
>>
>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
> Subcommand argument formats still look off a bit
Fixed
> I think the $ is unneeded. All the other shell code
> examples don't include the leading shell character.
Actually, the opposite. Every example did have leading $ except for the
first usage, which was inconsistent. But I agree $ is essentially just
noise and have removed all instances from the doc. :)
It would be nice to clean up the Random notes section. I think there may be
some context associated with those chat discussion snippets that were
copy/pasted in, so expanding on those points would be helpful for everyone
else (including me.)
On Tue, Sep 11, 2012 at 10:41 AM, Michal Mocny <mm...@chromium.org> wrote:
> Subcommand argument formats still look off a bit, I think they should look
> as follows:
>
> create <directory> [<id> [<name>]]
> platform ls
> platform add <platform>
> platform remove <platform>
> plugin ls
> plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
> inconsistant with the other examples of add/remove)
> plugin remove <plugin>
> build
> emulate
>
>
>
> Also, in the line "you can access the tool via $ cordova" I think the $ is
> unneeded. All the other shell code examples don't include the leading
> shell character. Alternatively we can add shell character to all the other
> shell command examples.
>
>
> On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
> <re...@gmail.com>wrote:
>
> > I've updated my copy of the README.md, pulling changes from Filip,
> Michal,
> > and Brian:
> > https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >
> > If I've missed anything please let me know.
> >
> > -Mike
> >
> > On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mm...@chromium.org>
> > wrote:
> >
> > > I'm still unsure what a "baked in" plugin/platform would be, in that
> > > context. Anyway, its not super important as the actual argument types
> > may
> > > change over time. The gist of it is just that you can reference a
> > > plugin/platform using various typical methods and I think that point
> gets
> > > across well enough.
> > >
> > >
> > > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > > > Considering the source I'd say 'baked' was intentional.
> > > >
> > > >
> > > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> > > > <re...@gmail.com> wrote:
> > > > >> assumed to be a 'backed in' platform/plugin
> > > > >
> > > > > This must be a typo, eh? 'baked' was intended?
> > > > >
> > > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
> > > > >
> > > > >> > * You will be able to access the client interface via: $
> > > ./bin/cordova
> > > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> > > > >>
> > > > >> Agree...tho the npm install should be global (in /usr/local/bin)
> > > > >> ....maybe we say as much?
> > > > >>
> > > > >>
> > > > >> > * Subcommands section
> > > > >> > * * Typical unix manpage style is to use [] to surround optional
> > > > >> arguments
> > > > >> > <> to surround explanations and nothing for keywords. Examples
> > that
> > > > need
> > > > >> > fixing include:
> > > > >> > * * * create <directory> [<id>] [<name>]
> > > > >> > * * * platform ls
> > > > >> > * * * platform add <platform>
> > > > >> > * * * etc
> > > > >> > * * even if we aren't aiming for manpage style here, there
> > > > >> > are inconsistencies
> > > > >>
> > > > >> Sure
> > > > >>
> > > > >>
> > > > >> > * * File and Directory Structure ascii tree diagram
> > > > >> > * * * suggest appending / after directory names
> > > > >>
> > > > >> +1
> > > > >>
> > > > >>
> > > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
> > Otherwise,
> > > > it's
> > > > >> > assumed to be a URL to a gzipped tar archive...
> > > > >> > * * * Not sure what 'backed in' means here, nor how to identify
> > > > something
> > > > >> > as not being backed in so as to fallback to gzipped tar
> > > > >> > * * * Also wording sounds more like "else .. else" instead of
> > "else
> > > > if ..
> > > > >> > else" (if that makes sense) :P
> > > > >>
> > > > >> Ya not sure what this is about?
> > > > >>
> > > > >>
> > > > >> > * * KewlApp directory structure ascii tree diagram
> > > > >> > * * * based on my understanding of the text, the ios/android
> > > platforms
> > > > >> > should be subdirs of platforms/ and there should also be a
> subdir
> > > > listed
> > > > >> in
> > > > >> > plugins/
> > > > >>
> > > > >> Yes.
> > > > >>
> > > > >>
> > > > >> > * * Running tests warning
> > > > >> > * * * Perhaps explain how to bootstrap so as not to have failing
> > > tests
> > > > >> > instead of assuming the reverse?
> > > > >>
> > > > >> Yes.
> > > > >>
> > > > >>
> > > > >> > Also, I will look into bash completions in some spare cycles and
> > if
> > > it
> > > > >> > looks reasonable I may volunteer for the task. I've been
> curious
> > to
> > > > >> learn
> > > > >> > how those work :)
> > > > >>
> > > > >> That'd be awesome...but I'm thinking in a future iteration once
> the
> > > > >> actual CLI API is more solid. (But knock yourself out!)
> > > > >>
> > > >
> > >
> >
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
Subcommand argument formats still look off a bit, I think they should look
as follows:
create <directory> [<id> [<name>]]
platform ls
platform add <platform>
platform remove <platform>
plugin ls
plugin add <path-to-plugin> (NOTE: why use "path-to-" here? Seems
inconsistant with the other examples of add/remove)
plugin remove <plugin>
build
emulate
Also, in the line "you can access the tool via $ cordova" I think the $ is
unneeded. All the other shell code examples don't include the leading
shell character. Alternatively we can add shell character to all the other
shell command examples.
On Tue, Sep 11, 2012 at 10:24 AM, Mike Reinstein
<re...@gmail.com>wrote:
> I've updated my copy of the README.md, pulling changes from Filip, Michal,
> and Brian:
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>
> If I've missed anything please let me know.
>
> -Mike
>
> On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mm...@chromium.org>
> wrote:
>
> > I'm still unsure what a "baked in" plugin/platform would be, in that
> > context. Anyway, its not super important as the actual argument types
> may
> > change over time. The gist of it is just that you can reference a
> > plugin/platform using various typical methods and I think that point gets
> > across well enough.
> >
> >
> > On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > Considering the source I'd say 'baked' was intentional.
> > >
> > >
> > > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> > > <re...@gmail.com> wrote:
> > > >> assumed to be a 'backed in' platform/plugin
> > > >
> > > > This must be a typo, eh? 'baked' was intended?
> > > >
> > > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
> > > >
> > > >> > * You will be able to access the client interface via: $
> > ./bin/cordova
> > > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> > > >>
> > > >> Agree...tho the npm install should be global (in /usr/local/bin)
> > > >> ....maybe we say as much?
> > > >>
> > > >>
> > > >> > * Subcommands section
> > > >> > * * Typical unix manpage style is to use [] to surround optional
> > > >> arguments
> > > >> > <> to surround explanations and nothing for keywords. Examples
> that
> > > need
> > > >> > fixing include:
> > > >> > * * * create <directory> [<id>] [<name>]
> > > >> > * * * platform ls
> > > >> > * * * platform add <platform>
> > > >> > * * * etc
> > > >> > * * even if we aren't aiming for manpage style here, there
> > > >> > are inconsistencies
> > > >>
> > > >> Sure
> > > >>
> > > >>
> > > >> > * * File and Directory Structure ascii tree diagram
> > > >> > * * * suggest appending / after directory names
> > > >>
> > > >> +1
> > > >>
> > > >>
> > > >> > * * ... it's assumed to be a 'backed in' platform/plugin.
> Otherwise,
> > > it's
> > > >> > assumed to be a URL to a gzipped tar archive...
> > > >> > * * * Not sure what 'backed in' means here, nor how to identify
> > > something
> > > >> > as not being backed in so as to fallback to gzipped tar
> > > >> > * * * Also wording sounds more like "else .. else" instead of
> "else
> > > if ..
> > > >> > else" (if that makes sense) :P
> > > >>
> > > >> Ya not sure what this is about?
> > > >>
> > > >>
> > > >> > * * KewlApp directory structure ascii tree diagram
> > > >> > * * * based on my understanding of the text, the ios/android
> > platforms
> > > >> > should be subdirs of platforms/ and there should also be a subdir
> > > listed
> > > >> in
> > > >> > plugins/
> > > >>
> > > >> Yes.
> > > >>
> > > >>
> > > >> > * * Running tests warning
> > > >> > * * * Perhaps explain how to bootstrap so as not to have failing
> > tests
> > > >> > instead of assuming the reverse?
> > > >>
> > > >> Yes.
> > > >>
> > > >>
> > > >> > Also, I will look into bash completions in some spare cycles and
> if
> > it
> > > >> > looks reasonable I may volunteer for the task. I've been curious
> to
> > > >> learn
> > > >> > how those work :)
> > > >>
> > > >> That'd be awesome...but I'm thinking in a future iteration once the
> > > >> actual CLI API is more solid. (But knock yourself out!)
> > > >>
> > >
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
I've updated my copy of the README.md, pulling changes from Filip, Michal,
and Brian:
https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
If I've missed anything please let me know.
-Mike
On Tue, Sep 11, 2012 at 10:22 AM, Michal Mocny <mm...@chromium.org> wrote:
> I'm still unsure what a "baked in" plugin/platform would be, in that
> context. Anyway, its not super important as the actual argument types may
> change over time. The gist of it is just that you can reference a
> plugin/platform using various typical methods and I think that point gets
> across well enough.
>
>
> On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > Considering the source I'd say 'baked' was intentional.
> >
> >
> > On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> > <re...@gmail.com> wrote:
> > >> assumed to be a 'backed in' platform/plugin
> > >
> > > This must be a typo, eh? 'baked' was intended?
> > >
> > > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > >> > * You will be able to access the client interface via: $
> ./bin/cordova
> > >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> > >>
> > >> Agree...tho the npm install should be global (in /usr/local/bin)
> > >> ....maybe we say as much?
> > >>
> > >>
> > >> > * Subcommands section
> > >> > * * Typical unix manpage style is to use [] to surround optional
> > >> arguments
> > >> > <> to surround explanations and nothing for keywords. Examples that
> > need
> > >> > fixing include:
> > >> > * * * create <directory> [<id>] [<name>]
> > >> > * * * platform ls
> > >> > * * * platform add <platform>
> > >> > * * * etc
> > >> > * * even if we aren't aiming for manpage style here, there
> > >> > are inconsistencies
> > >>
> > >> Sure
> > >>
> > >>
> > >> > * * File and Directory Structure ascii tree diagram
> > >> > * * * suggest appending / after directory names
> > >>
> > >> +1
> > >>
> > >>
> > >> > * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise,
> > it's
> > >> > assumed to be a URL to a gzipped tar archive...
> > >> > * * * Not sure what 'backed in' means here, nor how to identify
> > something
> > >> > as not being backed in so as to fallback to gzipped tar
> > >> > * * * Also wording sounds more like "else .. else" instead of "else
> > if ..
> > >> > else" (if that makes sense) :P
> > >>
> > >> Ya not sure what this is about?
> > >>
> > >>
> > >> > * * KewlApp directory structure ascii tree diagram
> > >> > * * * based on my understanding of the text, the ios/android
> platforms
> > >> > should be subdirs of platforms/ and there should also be a subdir
> > listed
> > >> in
> > >> > plugins/
> > >>
> > >> Yes.
> > >>
> > >>
> > >> > * * Running tests warning
> > >> > * * * Perhaps explain how to bootstrap so as not to have failing
> tests
> > >> > instead of assuming the reverse?
> > >>
> > >> Yes.
> > >>
> > >>
> > >> > Also, I will look into bash completions in some spare cycles and if
> it
> > >> > looks reasonable I may volunteer for the task. I've been curious to
> > >> learn
> > >> > how those work :)
> > >>
> > >> That'd be awesome...but I'm thinking in a future iteration once the
> > >> actual CLI API is more solid. (But knock yourself out!)
> > >>
> >
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
I'm still unsure what a "baked in" plugin/platform would be, in that
context. Anyway, its not super important as the actual argument types may
change over time. The gist of it is just that you can reference a
plugin/platform using various typical methods and I think that point gets
across well enough.
On Tue, Sep 11, 2012 at 8:38 AM, Brian LeRoux <b...@brian.io> wrote:
> Considering the source I'd say 'baked' was intentional.
>
>
> On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
> <re...@gmail.com> wrote:
> >> assumed to be a 'backed in' platform/plugin
> >
> > This must be a typo, eh? 'baked' was intended?
> >
> > On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> >> > * You will be able to access the client interface via: $ ./bin/cordova
> >> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> >>
> >> Agree...tho the npm install should be global (in /usr/local/bin)
> >> ....maybe we say as much?
> >>
> >>
> >> > * Subcommands section
> >> > * * Typical unix manpage style is to use [] to surround optional
> >> arguments
> >> > <> to surround explanations and nothing for keywords. Examples that
> need
> >> > fixing include:
> >> > * * * create <directory> [<id>] [<name>]
> >> > * * * platform ls
> >> > * * * platform add <platform>
> >> > * * * etc
> >> > * * even if we aren't aiming for manpage style here, there
> >> > are inconsistencies
> >>
> >> Sure
> >>
> >>
> >> > * * File and Directory Structure ascii tree diagram
> >> > * * * suggest appending / after directory names
> >>
> >> +1
> >>
> >>
> >> > * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise,
> it's
> >> > assumed to be a URL to a gzipped tar archive...
> >> > * * * Not sure what 'backed in' means here, nor how to identify
> something
> >> > as not being backed in so as to fallback to gzipped tar
> >> > * * * Also wording sounds more like "else .. else" instead of "else
> if ..
> >> > else" (if that makes sense) :P
> >>
> >> Ya not sure what this is about?
> >>
> >>
> >> > * * KewlApp directory structure ascii tree diagram
> >> > * * * based on my understanding of the text, the ios/android platforms
> >> > should be subdirs of platforms/ and there should also be a subdir
> listed
> >> in
> >> > plugins/
> >>
> >> Yes.
> >>
> >>
> >> > * * Running tests warning
> >> > * * * Perhaps explain how to bootstrap so as not to have failing tests
> >> > instead of assuming the reverse?
> >>
> >> Yes.
> >>
> >>
> >> > Also, I will look into bash completions in some spare cycles and if it
> >> > looks reasonable I may volunteer for the task. I've been curious to
> >> learn
> >> > how those work :)
> >>
> >> That'd be awesome...but I'm thinking in a future iteration once the
> >> actual CLI API is more solid. (But knock yourself out!)
> >>
>
Re: plugin tooling/specification
Posted by Brian LeRoux <b...@brian.io>.
Considering the source I'd say 'baked' was intentional.
On Tue, Sep 11, 2012 at 5:29 AM, Mike Reinstein
<re...@gmail.com> wrote:
>> assumed to be a 'backed in' platform/plugin
>
> This must be a typo, eh? 'baked' was intended?
>
> On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> > * You will be able to access the client interface via: $ ./bin/cordova
>> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
>>
>> Agree...tho the npm install should be global (in /usr/local/bin)
>> ....maybe we say as much?
>>
>>
>> > * Subcommands section
>> > * * Typical unix manpage style is to use [] to surround optional
>> arguments
>> > <> to surround explanations and nothing for keywords. Examples that need
>> > fixing include:
>> > * * * create <directory> [<id>] [<name>]
>> > * * * platform ls
>> > * * * platform add <platform>
>> > * * * etc
>> > * * even if we aren't aiming for manpage style here, there
>> > are inconsistencies
>>
>> Sure
>>
>>
>> > * * File and Directory Structure ascii tree diagram
>> > * * * suggest appending / after directory names
>>
>> +1
>>
>>
>> > * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
>> > assumed to be a URL to a gzipped tar archive...
>> > * * * Not sure what 'backed in' means here, nor how to identify something
>> > as not being backed in so as to fallback to gzipped tar
>> > * * * Also wording sounds more like "else .. else" instead of "else if ..
>> > else" (if that makes sense) :P
>>
>> Ya not sure what this is about?
>>
>>
>> > * * KewlApp directory structure ascii tree diagram
>> > * * * based on my understanding of the text, the ios/android platforms
>> > should be subdirs of platforms/ and there should also be a subdir listed
>> in
>> > plugins/
>>
>> Yes.
>>
>>
>> > * * Running tests warning
>> > * * * Perhaps explain how to bootstrap so as not to have failing tests
>> > instead of assuming the reverse?
>>
>> Yes.
>>
>>
>> > Also, I will look into bash completions in some spare cycles and if it
>> > looks reasonable I may volunteer for the task. I've been curious to
>> learn
>> > how those work :)
>>
>> That'd be awesome...but I'm thinking in a future iteration once the
>> actual CLI API is more solid. (But knock yourself out!)
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
> assumed to be a 'backed in' platform/plugin
This must be a typo, eh? 'baked' was intended?
On Tue, Sep 11, 2012 at 4:15 AM, Brian LeRoux <b...@brian.io> wrote:
> > * You will be able to access the client interface via: $ ./bin/cordova
> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
>
> Agree...tho the npm install should be global (in /usr/local/bin)
> ....maybe we say as much?
>
>
> > * Subcommands section
> > * * Typical unix manpage style is to use [] to surround optional
> arguments
> > <> to surround explanations and nothing for keywords. Examples that need
> > fixing include:
> > * * * create <directory> [<id>] [<name>]
> > * * * platform ls
> > * * * platform add <platform>
> > * * * etc
> > * * even if we aren't aiming for manpage style here, there
> > are inconsistencies
>
> Sure
>
>
> > * * File and Directory Structure ascii tree diagram
> > * * * suggest appending / after directory names
>
> +1
>
>
> > * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
> > assumed to be a URL to a gzipped tar archive...
> > * * * Not sure what 'backed in' means here, nor how to identify something
> > as not being backed in so as to fallback to gzipped tar
> > * * * Also wording sounds more like "else .. else" instead of "else if ..
> > else" (if that makes sense) :P
>
> Ya not sure what this is about?
>
>
> > * * KewlApp directory structure ascii tree diagram
> > * * * based on my understanding of the text, the ios/android platforms
> > should be subdirs of platforms/ and there should also be a subdir listed
> in
> > plugins/
>
> Yes.
>
>
> > * * Running tests warning
> > * * * Perhaps explain how to bootstrap so as not to have failing tests
> > instead of assuming the reverse?
>
> Yes.
>
>
> > Also, I will look into bash completions in some spare cycles and if it
> > looks reasonable I may volunteer for the task. I've been curious to
> learn
> > how those work :)
>
> That'd be awesome...but I'm thinking in a future iteration once the
> actual CLI API is more solid. (But knock yourself out!)
>
Re: plugin tooling/specification
Posted by Brian LeRoux <b...@brian.io>.
> * You will be able to access the client interface via: $ ./bin/cordova
> * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
Agree...tho the npm install should be global (in /usr/local/bin)
....maybe we say as much?
> * Subcommands section
> * * Typical unix manpage style is to use [] to surround optional arguments
> <> to surround explanations and nothing for keywords. Examples that need
> fixing include:
> * * * create <directory> [<id>] [<name>]
> * * * platform ls
> * * * platform add <platform>
> * * * etc
> * * even if we aren't aiming for manpage style here, there
> are inconsistencies
Sure
> * * File and Directory Structure ascii tree diagram
> * * * suggest appending / after directory names
+1
> * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
> assumed to be a URL to a gzipped tar archive...
> * * * Not sure what 'backed in' means here, nor how to identify something
> as not being backed in so as to fallback to gzipped tar
> * * * Also wording sounds more like "else .. else" instead of "else if ..
> else" (if that makes sense) :P
Ya not sure what this is about?
> * * KewlApp directory structure ascii tree diagram
> * * * based on my understanding of the text, the ios/android platforms
> should be subdirs of platforms/ and there should also be a subdir listed in
> plugins/
Yes.
> * * Running tests warning
> * * * Perhaps explain how to bootstrap so as not to have failing tests
> instead of assuming the reverse?
Yes.
> Also, I will look into bash completions in some spare cycles and if it
> looks reasonable I may volunteer for the task. I've been curious to learn
> how those work :)
That'd be awesome...but I'm thinking in a future iteration once the
actual CLI API is more solid. (But knock yourself out!)
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Thanks Michal, I agree with a lot of these.
On Mon, Sep 10, 2012 at 3:21 PM, Michal Mocny <mm...@chromium.org> wrote:
> My bullet point indentation is terribad ;) But you should be able to
> figure it out.
>
>
> On Mon, Sep 10, 2012 at 3:21 PM, Michal Mocny <mm...@chromium.org> wrote:
>
> > Alright, I'll post my comments here for now, but I'll have to ponder over
> > a more scalable approach in the future. (Im thinking that an online
> > document editor that sends all comments to ML and allows replies inline
> > would work really nice..).
> >
> > * You will be able to access the client interface via: $ ./bin/cordova
> > * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
> >
> > * Subcommands section
> > * * Typical unix manpage style is to use [] to surround optional
> arguments
> > <> to surround explanations and nothing for keywords. Examples that need
> > fixing include:
> > * * * create <directory> [<id>] [<name>]
> > * * * platform ls
> > * * * platform add <platform>
> > * * * etc
> > * * even if we aren't aiming for manpage style here, there
> > are inconsistencies
> >
> > * * File and Directory Structure ascii tree diagram
> > * * * suggest appending / after directory names
> >
> > * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
> > assumed to be a URL to a gzipped tar archive...
> > * * * Not sure what 'backed in' means here, nor how to identify something
> > as not being backed in so as to fallback to gzipped tar
> > * * * Also wording sounds more like "else .. else" instead of "else if ..
> > else" (if that makes sense) :P
> >
> > * * KewlApp directory structure ascii tree diagram
> > * * * based on my understanding of the text, the ios/android platforms
> > should be subdirs of platforms/ and there should also be a subdir listed
> in
> > plugins/
> >
> > * * Running tests warning
> > * * * Perhaps explain how to bootstrap so as not to have failing tests
> > instead of assuming the reverse?
> >
> > Also, I will look into bash completions in some spare cycles and if it
> > looks reasonable I may volunteer for the task. I've been curious to
> learn
> > how those work :)
> >
> > -Michal
> >
> >
> > On Mon, Sep 10, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Mailing list! We forked and committed for the simple stuff (deeper
> >> explanations and merging documentation), but if you have discussion +
> >> design points, ML is the place to do it.
> >>
> >> On 9/10/12 11:31 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >>
> >> >I'm just reading along and would like to make some comments here and
> >> >there.
> >> > However, it seems pretty inefficient to branch the project just to
> mark
> >> >my
> >> >comments and email may be confusing.
> >> >
> >> >Usually I've just used Google Docs to mark comments inline for stuff
> like
> >> >this but perhaps that suggestion won't fly well. Does github not have
> a
> >> >feature for this (commenting on a file, starting a wiki, etc?)
> >> >
> >> >Any suggestions/opinions?
> >> >
> >> >
> >> >On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein
> >> ><re...@gmail.com>wrote:
> >> >
> >> >> Looks good to me. What are the next steps? One thing I'd like to see
> >> >>happen
> >> >> is getting rid of some of those repos and documentation pages that
> are
> >> >> redundant.
> >> >>
> >> >> -Mike
> >> >>
> >> >> On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >> > Nice!
> >> >> >
> >> >> > I worked out some of your quotes/questions and put it up on my
> branch
> >> >>on
> >> >> > github: https://github.com/filmaj/cordova-client/tree/einstein
> >> >> >
> >> >> > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com>
> >> wrote:
> >> >> >
> >> >> > >Hey folks,
> >> >> > >
> >> >> > >Hope you all had a nice weekend. I have a preliminary draft ready
> >> >>that
> >> >> > >merges cordova-client and command line tooling design into 1
> >> >>document:
> >> >> > >
> >> >> > >
> >> >>
> >>
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> >> > >
> >> >> > >Any feedback would be greatly appreciated. Thanks!
> >> >> > >
> >> >> > >-Mike
> >> >> > >
> >> >> > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <anis.kadri@gmail.com
> >
> >> >> wrote:
> >> >> > >
> >> >> > >> Hi Mike,
> >> >> > >>
> >> >> > >> pluginstall-with-git support is just an experiment that I did a
> >> >>while
> >> >> > >>back
> >> >> > >> (it takes git URLs as well as local paths). I suggest you base
> >> your
> >> >> > >>work on
> >> >> > >> alunny's pluginstall until/if those changes get merged.
> >> >> > >>
> >> >> > >> Cheers
> >> >> > >>
> >> >> > >> Anis
> >> >> > >>
> >> >> > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
> >> >> > reinstein.mike@gmail.com
> >> >> > >> >wrote:
> >> >> > >>
> >> >> > >> > I see 2 repositories for pluginstall:
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> > >>
> >> >> > >>
> >> >> >
> >> >>
> >> >>
> >>
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
> >> >> > >>t-support
> >> >> > >> >
> >> >> > >> > and Andrew's:
> >> >> > >> > https://github.com/alunny/pluginstall
> >> >> > >> >
> >> >> > >> > When consolidating the pluginstall and plugin format docs I
> >> >>forked
> >> >> > >> Andrew's
> >> >> > >> > repo. Should I instead have used the
> >> pluginstall-with-git-support
> >> >> > >>repo as
> >> >> > >> > my base?
> >> >> > >> >
> >> >> > >> > -Mike
> >> >> > >> >
> >> >> > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
> >> >> > >><reinstein.mike@gmail.com
> >> >> > >> > >wrote:
> >> >> > >> >
> >> >> > >> > > My username is nekoflux.
> >> >> > >> > >
> >> >> > >> > >
> >> >> > >> > >
> >> >> > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com>
> >> >>wrote:
> >> >> > >> > >
> >> >> > >> > >> JIRA is separate, we can assign issues to you (if you so
> >> >>wish).
> >> >> > >> > >>
> >> >> > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> >> >> > >> > >>
> >> >> > >> > >> >Registration is open - let us know what your user account
> is
> >> >> once
> >> >> > >>you
> >> >> > >> > >> >do that, for assigning issues to yourself you need us to
> add
> >> >>you
> >> >> > >>to a
> >> >> > >> > >> >contributors group.
> >> >> > >> > >> >
> >> >> > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> >> >> > >> > reinstein.mike@gmail.com
> >> >> > >> > >> >
> >> >> > >> > >> >wrote:
> >> >> > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
> >> >> proceed
> >> >> > >> with
> >> >> > >> > >> >> merging the cordova-client and command line tooling spec
> >> >> next. I
> >> >> > >> > >> >>suppose it
> >> >> > >> > >> >> probably makes sense for me to start working out of JIRA
> >> so
> >> >> > >>these
> >> >> > >> > tasks
> >> >> > >> > >> >>can
> >> >> > >> > >> >> be tracked. Is registration open or do I need to get
> >> >> permission
> >> >> > >> from
> >> >> > >> > an
> >> >> > >> > >> >> admin for an account?
> >> >> > >> > >> >>
> >> >> > >> > >> >>
> >> >> > >> > >> >>
> >> >> > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <
> fil@adobe.com>
> >> >> > wrote:
> >> >> > >> > >> >>
> >> >> > >> > >> >>> Sorry for the late reply, this looks awesome!
> >> >> > >> > >> >>>
> >> >> > >> > >> >>> The one modification I would do is remove "www" as a
> >> >>platform
> >> >> > >>(you
> >> >> > >> > >> >>>have a
> >> >> > >> > >> >>> comment in there about that too).
> >> >> > >> > >> >>>
> >> >> > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
> >> >> reinstein.mike@gmail.com>
> >> >> > >> > wrote:
> >> >> > >> > >> >>>
> >> >> > >> > >> >>> >> eventually we will move pluginstall into apache
> >> >> > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went
> with
> >> >>the
> >> >> > >> > slightly
> >> >> > >> > >> >>>more
> >> >> > >> > >> >>> >conservative assumption, that pluginstall might live
> >> >> > >>separately
> >> >> > >> > from
> >> >> > >> > >> >>> >cordova-client. But I get the impression this is a
> >> >>left-over
> >> >> > >> notion
> >> >> > >> > >> >>>from
> >> >> > >> > >> >>> >when Andrew first built pluginstall and it wasn't
> clear
> >> >>then
> >> >> > >> > whether
> >> >> > >> > >> >>>or
> >> >> > >> > >> >>> >not
> >> >> > >> > >> >>> >it would take hold.
> >> >> > >> > >> >>> >
> >> >> > >> > >> >>> >I've got an initial version of the merged
> documentation
> >> >>for
> >> >> > >>the
> >> >> > >> > >> >>> >pluginstall
> >> >> > >> > >> >>> >command line tool, and the specification doc. It's
> here
> >> >> > >> > >> >>> >https://github.com/mreinstein/pluginstall
> >> >> > >> > >> >>> >
> >> >> > >> > >> >>> >I've also added some comments on possible changes.
> >> >>Overall
> >> >> the
> >> >> > >> doc
> >> >> > >> > is
> >> >> > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
> >> >> > >>appreciate
> >> >> > >> > >> >>> >constructive feedback on this. If it looks right I'll
> >> >>send a
> >> >> > >>pull
> >> >> > >> > >> >>>request
> >> >> > >> > >> >>> >to alunny, and then proceed with merging
> cordova-client
> >> >> design
> >> >> > >> doc
> >> >> > >> > >> >>>into
> >> >> > >> > >> >>> >the
> >> >> > >> > >> >>> >README on github.
> >> >> > >> > >> >>> >
> >> >> > >> > >> >>> >-Mike
> >> >> > >> > >> >>> >
> >> >> > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <
> >> fil@adobe.com>
> >> >> > >>wrote:
> >> >> > >> > >> >>> >
> >> >> > >> > >> >>> >> +1 !
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>> >> (I THINK) eventually we will move pluginstall into
> >> >>apache
> >> >> > >> > (assuming
> >> >> > >> > >> >>>the
> >> >> > >> > >> >>> >> authors are cool with that) so it will go 2 docs ->
> 1
> >> >>doc.
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io>
> wrote:
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>> >> >love it
> >> >> > >> > >> >>> >> >
> >> >> > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >> >> > >> > >> >>> >><re...@gmail.com>
> >> >> > >> > >> >>> >> >wrote:
> >> >> > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a
> >> >>chance
> >> >> to
> >> >> > >> > review
> >> >> > >> > >> >>>the
> >> >> > >> > >> >>> >> >>docs
> >> >> > >> > >> >>> >> >> more carefully. I'm really impressed with how
> well
> >> >> > >>written
> >> >> > >> > they
> >> >> > >> > >> >>>are.
> >> >> > >> > >> >>> >> >>What I
> >> >> > >> > >> >>> >> >> *think* makes the most sense is to consolidate
> into
> >> >> fewer
> >> >> > >> > >> >>>documents
> >> >> > >> > >> >>> >>so
> >> >> > >> > >> >>> >> >>that
> >> >> > >> > >> >>> >> >> it's not necessary to look at so many seperate
> >> >>places.
> >> >> > >> Here's
> >> >> > >> > >> >>>what I
> >> >> > >> > >> >>> >> >> propose:
> >> >> > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
> >> >> > >>alunny/pluginstall
> >> >> > >> > >> >>>README.md
> >> >> > >> > >> >>> >> >> * merge the command line tooling design doc into
> >> the
> >> >> > >> > >> >>>cordova-client
> >> >> > >> > >> >>> >> >> README.md
> >> >> > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page
> and
> >> >> merge
> >> >> > >> > parts
> >> >> > >> > >> >>>of it
> >> >> > >> > >> >>> >> >>into
> >> >> > >> > >> >>> >> >> the above 2 docs
> >> >> > >> > >> >>> >> >>
> >> >> > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5,
> >> >>and
> >> >> it
> >> >> > >> still
> >> >> > >> > >> >>> >>maintains
> >> >> > >> > >> >>> >> >> the nice loose coupling between alunny's
> >> pluginstall
> >> >> > >>utility
> >> >> > >> > and
> >> >> > >> > >> >>>the
> >> >> > >> > >> >>> >> >>larger
> >> >> > >> > >> >>> >> >> cordova-client. I'm assuming this separation was
> >> the
> >> >> > >> original
> >> >> > >> > >> >>>intent,
> >> >> > >> > >> >>> >> >> rather than having one monolithic tool.
> >> >> > >> > >> >>> >> >>
> >> >> > >> > >> >>> >> >> Would love feedback on this, I don't want to
> waste
> >> >>time
> >> >> > >> doing
> >> >> > >> > it
> >> >> > >> > >> >>>and
> >> >> > >> > >> >>> >> >>find
> >> >> > >> > >> >>> >> >> out this isn't appropriate. :)
> >> >> > >> > >> >>> >> >>
> >> >> > >> > >> >>> >> >>
> >> >> > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
> >> >> > >><fi...@adobe.com>
> >> >> > >> > >> wrote:
> >> >> > >> > >> >>> >> >>
> >> >> > >> > >> >>> >> >>> Cordova-client depends on pluginstall.
> Pluginstall
> >> >> does
> >> >> > >>the
> >> >> > >> > >> hard
> >> >> > >> > >> >>> >>work
> >> >> > >> > >> >>> >> >>>for
> >> >> > >> > >> >>> >> >>> programmatic plugin installation, which is just
> >> >>one of
> >> >> > >>the
> >> >> > >> > apis
> >> >> > >> > >> >>> >> >>>available
> >> >> > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells
> out"
> >> >>to
> >> >> > >> > >> >>>pluginstall.
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >> >>> The client also handles app creation, platform
> >> >> > >> > >> >>>removal/addition, and
> >> >> > >> > >> >>> >> >>> interpolating information from app's config.xml
> >> >>into
> >> >> the
> >> >> > >> > >> >>>necessary
> >> >> > >> > >> >>> >> >>>spots
> >> >> > >> > >> >>> >> >>> in each native project.
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> >> >> > >> > >> reinstein.mike@gmail.com>
> >> >> > >> > >> >>> >> wrote:
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >> >>> >Hey Filip,
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >One thing I"m curious about, whats the
> difference
> >> >> > >>between
> >> >> > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >>>
> >> >> > >> > >>
> >> >> > >>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >there seems to be some overlap there. Is
> >> >>pluginstall
> >> >> a
> >> >> > >> > subset
> >> >> > >> > >> >>>of
> >> >> > >> > >> >>> >> >>> >functionality just related to plugins that has
> >> >>moved
> >> >> > >>into
> >> >> > >> > >> >>> >> >>>cordova-client
> >> >> > >> > >> >>> >> >>> >or
> >> >> > >> > >> >>> >> >>> >is it different?
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
> >> >> > >>codebase
> >> >> > >> > that
> >> >> > >> > >> >>> >> >>>incorporates
> >> >> > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code
> I'm
> >> >> > >>finding
> >> >> > >> to
> >> >> > >> > >> >>>see if
> >> >> > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
> >> >> > >>differently,
> >> >> > >> is
> >> >> > >> > >> it
> >> >> > >> > >> >>> >>safe
> >> >> > >> > >> >>> >> >>>to
> >> >> > >> > >> >>> >> >>> >assume that just about all the worthwhile code
> is
> >> >>in
> >> >> > >> > >> >>> >>cordova-client?
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >-Mike
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
> >> >> > >><fil@adobe.com
> >> >> > >> >
> >> >> > >> > >> >>>wrote:
> >> >> > >> > >> >>> >> >>> >
> >> >> > >> > >> >>> >> >>> >> All looks good to me Mike.
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would
> >> >>be a
> >> >> > >>great
> >> >> > >> > >> >>>place to
> >> >> > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate
> >> you
> >> >> > >> tackling
> >> >> > >> > >> >>>this!
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> >> >> > >> > >> >>><re...@gmail.com>
> >> >> > >> > >> >>> >> >>>wrote:
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>> >> >Hey Filip, Brian:
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >I think where I'd like to start is on
> >> >> > >>documentation. I
> >> >> > >> > may
> >> >> > >> > >> >>>be
> >> >> > >> > >> >>> >>wrong
> >> >> > >> > >> >>> >> >>> >>about
> >> >> > >> > >> >>> >> >>> >> >this, but it seems like there are bits and
> >> >>pieces
> >> >> of
> >> >> > >> docs
> >> >> > >> > >> in
> >> >> > >> > >> >>> >> >>>various
> >> >> > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
> >> >> Maybe a
> >> >> > >> good
> >> >> > >> > >> >>>start
> >> >> > >> > >> >>> >>is
> >> >> > >> > >> >>> >> >>>for
> >> >> > >> > >> >>> >> >>> >>me
> >> >> > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
> >> >> > >>"master"
> >> >> > >> > >> >>>document,
> >> >> > >> > >> >>> >>and
> >> >> > >> > >> >>> >> >>> >>cull
> >> >> > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
> >> >> > >>rephrasing
> >> >> > >> > of
> >> >> > >> > >> >>>the
> >> >> > >> > >> >>> >> >>>various
> >> >> > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please
> take
> >> >>a
> >> >> > >>look
> >> >> > >> and
> >> >> > >> > >> >>>let me
> >> >> > >> > >> >>> >> >>>know
> >> >> > >> > >> >>> >> >>> >>if
> >> >> > >> > >> >>> >> >>> >> >I've characterised the content/purpose of
> >> these
> >> >> > >>various
> >> >> > >> > >> >>>links:
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is
> >> here:
> >> >> > >> > >> >>> >> >>> >> >
> https://github.com/alunny/cordova-plugin-spec
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >The implementation that manages plugin usage
> >> is
> >> >> > >>here:
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>>>
> >> >> > >> > >> >>>
> >> >> > >> >
> >> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >> > >> > >> >>> >> >>> >> >This project encompasses more than just
> >> plugins
> >> >> > >>because
> >> >> > >> > it
> >> >> > >> > >> >>>also
> >> >> > >> > >> >>> >> >>>handles
> >> >> > >> > >> >>> >> >>> >> >everything related to building, deploying,
> and
> >> >> > >>managing
> >> >> > >> > >> >>>cordova
> >> >> > >> > >> >>> >> >>> >> >applications
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >These plugins are most popular, and should
> >> >>ideally
> >> >> > >>work
> >> >> > >> > >> >>>with the
> >> >> > >> > >> >>> >> >>> >> >cordova-client implemenation:
> >> >> > >> > >> >>> >> >>> >> >
> http://github.com/phonegap/phonegap-plugins*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >This implementation by Drew was an initial
> >> >>proof
> >> >> of
> >> >> > >> > >> concept,
> >> >> > >> > >> >>> >>which
> >> >> > >> > >> >>> >> >>>only
> >> >> > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned
> in
> >> >> > >>favor of
> >> >> > >> > >> >>> >> >>>cordova-client,
> >> >> > >> > >> >>> >> >>> >> >with much of his ideas having made it into
> >> >> > >> > cordova-client:
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> https://github.com/deedubbu/cordova-blackberry-pluggable
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >This doc contains some info on the format of
> >> >>the
> >> >> > >> command
> >> >> > >> > >> >>>line
> >> >> > >> > >> >>> >> >>>interface
> >> >> > >> > >> >>> >> >>> >> >and
> >> >> > >> > >> >>> >> >>> >> >directory structure of cordova-client:
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >This doc contains some documentation on
> Drew's
> >> >>old
> >> >> > >> > >> >>> >>implementation,
> >> >> > >> > >> >>> >> >>>and
> >> >> > >> > >> >>> >> >>> >>is
> >> >> > >> > >> >>> >> >>> >> >out of date now:
> >> >> > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to
> >> >>get a
> >> >> > >> handle
> >> >> > >> > on
> >> >> > >> > >> >>>what
> >> >> > >> > >> >>> >> >>>docs
> >> >> > >> > >> >>> >> >>> >>are
> >> >> > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm
> not
> >> >> > >>judging
> >> >> > >> > >> >>>anyone's
> >> >> > >> > >> >>> >> >>>work or
> >> >> > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong
> >> >>idea
> >> >> > >>about
> >> >> > >> > >> what
> >> >> > >> > >> >>> >>these
> >> >> > >> > >> >>> >> >>> >>links
> >> >> > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >-Mike
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >*
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> >> >> > >> > fil@adobe.com>
> >> >> > >> > >> >>> >>wrote:
> >> >> > >> > >> >>> >> >>> >> >
> >> >> > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level
> >> >>project
> >> >> > >>goes
> >> >> > >> > >> >>> >> >>>hand-in-hand
> >> >> > >> > >> >>> >> >>> >>with
> >> >> > >> > >> >>> >> >>> >> >> this spec. Code here:
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>>
> >> >> > >> > >> >>>
> >> >> > >> > >>
> >> >> > >> >
> >> >> > >>
> >> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >> >> > >> > >> >>> >> >>>h
> >> >> > >> > >> >>> >> >>> >> >>or
> >> >> > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
> >> >> popular
> >> >> > >> > >> >>>plugins out
> >> >> > >> > >> >>> >> >>>in the
> >> >> > >> > >> >>> >> >>> >> >>wild
> >> >> > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins
> )
> >> >>work
> >> >> > >>with
> >> >> > >> > >> this
> >> >> > >> > >> >>> >>spec.
> >> >> > >> > >> >>> >> >>>Do
> >> >> > >> > >> >>> >> >>> we
> >> >> > >> > >> >>> >> >>> >> >>need
> >> >> > >> > >> >>> >> >>> >> >> to account for anything else?
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >> I think the one outstanding question is
> how
> >> >>to
> >> >> > >>handle
> >> >> > >> > >> >>> >> >>>installation /
> >> >> > >> > >> >>> >> >>> >> >> compatibility with different versions of
> >> >> cordova.
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the
> >> >>spec
> >> >> > >>(put
> >> >> > >> it
> >> >> > >> > on
> >> >> > >> > >> >>>the
> >> >> > >> > >> >>> >> >>>wiki,
> >> >> > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >> >> > >> > >> >>> >><re...@gmail.com>
> >> >> > >> > >> >>> >> >>> >>wrote:
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those
> projects.
> >> >>I'd
> >> >> > >>love
> >> >> > >> to
> >> >> > >> > >> >>>dig in
> >> >> > >> > >> >>> >> >>>and
> >> >> > >> > >> >>> >> >>> >>start
> >> >> > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help
> is
> >> >> > >>needed
> >> >> > >> at
> >> >> > >> > >> the
> >> >> > >> > >> >>> >> >>>moment?
> >> >> > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >-Mike
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip
> Maj
> >> >> > >> > >> >>><fi...@adobe.com>
> >> >> > >> > >> >>> >> >>>wrote:
> >> >> > >> > >> >>> >> >>> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto
> plugin
> >> >> > >>"spec"
> >> >> > >> we
> >> >> > >> > >> are
> >> >> > >> > >> >>> >> >>>working
> >> >> > >> > >> >>> >> >>> >> >>towards:
> >> >> > >> > >> >>> >> >>> >> >> >>
> >> >> https://github.com/alunny/cordova-plugin-spec
> >> >> > >> > >> >>> >> >>> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
> >> >> b@brian.io>
> >> >> > >> > wrote:
> >> >> > >> > >> >>> >> >>> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right
> place!
> >> >> > >> Currently
> >> >> > >> > >> the
> >> >> > >> > >> >>> >>plugin
> >> >> > >> > >> >>> >> >>> >> >>tooling
> >> >> > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil,
> >> >>Michael,
> >> >> > >>and
> >> >> > >> > >> >>>myself.
> >> >> > >> > >> >>> >> >>>(sorry
> >> >> > >> > >> >>> >> >>> >>for
> >> >> > >> > >> >>> >> >>> >> >>the
> >> >> > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
> >> >> summer
> >> >> > >> break
> >> >> > >> > >> >>>after
> >> >> > >> > >> >>> >> >>> >>shipping
> >> >> > >> > >> >>> >> >>> >> >> >> >2.0)
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this
> >> >>list,
> >> >> > >>git,
> >> >> > >> > and
> >> >> > >> > >> >>> >>these
> >> >> > >> > >> >>> >> >>>wiki
> >> >> > >> > >> >>> >> >>> >> >>pages:
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >-
> >> >> http://wiki.apache.org/cordova/PluginDesign
> >> >> > >> > >> >>> >> >>> >> >> >> >-
> >> >> > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
> >> >> branch
> >> >> > >> which
> >> >> > >> > >> >>>you
> >> >> > >> > >> >>> >>can
> >> >> > >> > >> >>> >> >>> >>preview
> >> >> > >> > >> >>> >> >>> >> >>on
> >> >> > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >>
> >> >> > >> > >>
> >> >> > >>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up
> on
> >> >>our
> >> >> > >> contrib
> >> >> > >> > >> >>> >>process
> >> >> > >> > >> >>> >> >>>in
> >> >> > >> > >> >>> >> >>> >>the
> >> >> > >> > >> >>> >> >>> >> >> >>wiki:
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> http://wiki.apache.org/cordova/ContributerWorkflow
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects
> >> >>everything
> >> >> > >>stays
> >> >> > >> > on
> >> >> > >> > >> >>>its
> >> >> > >> > >> >>> >>own
> >> >> > >> > >> >>> >> >>> >>branch
> >> >> > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its
> solid
> >> >>for
> >> >> > >>its
> >> >> > >> > own
> >> >> > >> > >> >>>repo.
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >* * *
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >
> >> >> > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
> >> >> > >>Reinstein
> >> >> > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >> >> > >> > >> >>> >> >>> >> >> >> >> Hey there,
> >> >> > >> > >> >>> >> >>> >> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to
> the
> >> >> plugin
> >> >> > >> > system
> >> >> > >> > >> >>> >>that is
> >> >> > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> >> >> > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up?
> >> >>Who
> >> >> are
> >> >> > >> the
> >> >> > >> > >> >>>right
> >> >> > >> > >> >>> >> >>>people
> >> >> > >> > >> >>> >> >>> >>to
> >> >> > >> > >> >>> >> >>> >> >>talk
> >> >> > >> > >> >>> >> >>> >> >> >> >>to?
> >> >> > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm
> >> an
> >> >> > >> > experienced
> >> >> > >> > >> >>> >> >>>developer,
> >> >> > >> > >> >>> >> >>> >> >>have
> >> >> > >> > >> >>> >> >>> >> >> >> >>worked
> >> >> > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects,
> and
> >> >> would
> >> >> > >> love
> >> >> > >> > to
> >> >> > >> > >> >>>give
> >> >> > >> > >> >>> >> >>>back
> >> >> > >> > >> >>> >> >>> >>to
> >> >> > >> > >> >>> >> >>> >> >>the
> >> >> > >> > >> >>> >> >>> >> >> >> >> community.
> >> >> > >> > >> >>> >> >>> >> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >> >> cheers,
> >> >> > >> > >> >>> >> >>> >> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >> >> -Mike
> >> >> > >> > >> >>> >> >>> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >> >>
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >> >>
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>> >>
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >> >>>
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>> >>
> >> >> > >> > >> >>>
> >> >> > >> > >> >>>
> >> >> > >> > >>
> >> >> > >> > >>
> >> >> > >> > >
> >> >> > >> >
> >> >> > >>
> >> >> >
> >> >> >
> >> >>
> >>
> >>
> >
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
My bullet point indentation is terribad ;) But you should be able to
figure it out.
On Mon, Sep 10, 2012 at 3:21 PM, Michal Mocny <mm...@chromium.org> wrote:
> Alright, I'll post my comments here for now, but I'll have to ponder over
> a more scalable approach in the future. (Im thinking that an online
> document editor that sends all comments to ML and allows replies inline
> would work really nice..).
>
> * You will be able to access the client interface via: $ ./bin/cordova
> * * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
>
> * Subcommands section
> * * Typical unix manpage style is to use [] to surround optional arguments
> <> to surround explanations and nothing for keywords. Examples that need
> fixing include:
> * * * create <directory> [<id>] [<name>]
> * * * platform ls
> * * * platform add <platform>
> * * * etc
> * * even if we aren't aiming for manpage style here, there
> are inconsistencies
>
> * * File and Directory Structure ascii tree diagram
> * * * suggest appending / after directory names
>
> * * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
> assumed to be a URL to a gzipped tar archive...
> * * * Not sure what 'backed in' means here, nor how to identify something
> as not being backed in so as to fallback to gzipped tar
> * * * Also wording sounds more like "else .. else" instead of "else if ..
> else" (if that makes sense) :P
>
> * * KewlApp directory structure ascii tree diagram
> * * * based on my understanding of the text, the ios/android platforms
> should be subdirs of platforms/ and there should also be a subdir listed in
> plugins/
>
> * * Running tests warning
> * * * Perhaps explain how to bootstrap so as not to have failing tests
> instead of assuming the reverse?
>
> Also, I will look into bash completions in some spare cycles and if it
> looks reasonable I may volunteer for the task. I've been curious to learn
> how those work :)
>
> -Michal
>
>
> On Mon, Sep 10, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Mailing list! We forked and committed for the simple stuff (deeper
>> explanations and merging documentation), but if you have discussion +
>> design points, ML is the place to do it.
>>
>> On 9/10/12 11:31 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>>
>> >I'm just reading along and would like to make some comments here and
>> >there.
>> > However, it seems pretty inefficient to branch the project just to mark
>> >my
>> >comments and email may be confusing.
>> >
>> >Usually I've just used Google Docs to mark comments inline for stuff like
>> >this but perhaps that suggestion won't fly well. Does github not have a
>> >feature for this (commenting on a file, starting a wiki, etc?)
>> >
>> >Any suggestions/opinions?
>> >
>> >
>> >On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein
>> ><re...@gmail.com>wrote:
>> >
>> >> Looks good to me. What are the next steps? One thing I'd like to see
>> >>happen
>> >> is getting rid of some of those repos and documentation pages that are
>> >> redundant.
>> >>
>> >> -Mike
>> >>
>> >> On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >> > Nice!
>> >> >
>> >> > I worked out some of your quotes/questions and put it up on my branch
>> >>on
>> >> > github: https://github.com/filmaj/cordova-client/tree/einstein
>> >> >
>> >> > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com>
>> wrote:
>> >> >
>> >> > >Hey folks,
>> >> > >
>> >> > >Hope you all had a nice weekend. I have a preliminary draft ready
>> >>that
>> >> > >merges cordova-client and command line tooling design into 1
>> >>document:
>> >> > >
>> >> > >
>> >>
>> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> >> > >
>> >> > >Any feedback would be greatly appreciated. Thanks!
>> >> > >
>> >> > >-Mike
>> >> > >
>> >> > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com>
>> >> wrote:
>> >> > >
>> >> > >> Hi Mike,
>> >> > >>
>> >> > >> pluginstall-with-git support is just an experiment that I did a
>> >>while
>> >> > >>back
>> >> > >> (it takes git URLs as well as local paths). I suggest you base
>> your
>> >> > >>work on
>> >> > >> alunny's pluginstall until/if those changes get merged.
>> >> > >>
>> >> > >> Cheers
>> >> > >>
>> >> > >> Anis
>> >> > >>
>> >> > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
>> >> > reinstein.mike@gmail.com
>> >> > >> >wrote:
>> >> > >>
>> >> > >> > I see 2 repositories for pluginstall:
>> >> > >> >
>> >> > >> >
>> >> > >> >
>> >> > >>
>> >> > >>
>> >> >
>> >>
>> >>
>> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
>> >> > >>t-support
>> >> > >> >
>> >> > >> > and Andrew's:
>> >> > >> > https://github.com/alunny/pluginstall
>> >> > >> >
>> >> > >> > When consolidating the pluginstall and plugin format docs I
>> >>forked
>> >> > >> Andrew's
>> >> > >> > repo. Should I instead have used the
>> pluginstall-with-git-support
>> >> > >>repo as
>> >> > >> > my base?
>> >> > >> >
>> >> > >> > -Mike
>> >> > >> >
>> >> > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
>> >> > >><reinstein.mike@gmail.com
>> >> > >> > >wrote:
>> >> > >> >
>> >> > >> > > My username is nekoflux.
>> >> > >> > >
>> >> > >> > >
>> >> > >> > >
>> >> > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com>
>> >>wrote:
>> >> > >> > >
>> >> > >> > >> JIRA is separate, we can assign issues to you (if you so
>> >>wish).
>> >> > >> > >>
>> >> > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>> >> > >> > >>
>> >> > >> > >> >Registration is open - let us know what your user account is
>> >> once
>> >> > >>you
>> >> > >> > >> >do that, for assigning issues to yourself you need us to add
>> >>you
>> >> > >>to a
>> >> > >> > >> >contributors group.
>> >> > >> > >> >
>> >> > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
>> >> > >> > reinstein.mike@gmail.com
>> >> > >> > >> >
>> >> > >> > >> >wrote:
>> >> > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
>> >> proceed
>> >> > >> with
>> >> > >> > >> >> merging the cordova-client and command line tooling spec
>> >> next. I
>> >> > >> > >> >>suppose it
>> >> > >> > >> >> probably makes sense for me to start working out of JIRA
>> so
>> >> > >>these
>> >> > >> > tasks
>> >> > >> > >> >>can
>> >> > >> > >> >> be tracked. Is registration open or do I need to get
>> >> permission
>> >> > >> from
>> >> > >> > an
>> >> > >> > >> >> admin for an account?
>> >> > >> > >> >>
>> >> > >> > >> >>
>> >> > >> > >> >>
>> >> > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
>> >> > wrote:
>> >> > >> > >> >>
>> >> > >> > >> >>> Sorry for the late reply, this looks awesome!
>> >> > >> > >> >>>
>> >> > >> > >> >>> The one modification I would do is remove "www" as a
>> >>platform
>> >> > >>(you
>> >> > >> > >> >>>have a
>> >> > >> > >> >>> comment in there about that too).
>> >> > >> > >> >>>
>> >> > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
>> >> reinstein.mike@gmail.com>
>> >> > >> > wrote:
>> >> > >> > >> >>>
>> >> > >> > >> >>> >> eventually we will move pluginstall into apache
>> >> > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with
>> >>the
>> >> > >> > slightly
>> >> > >> > >> >>>more
>> >> > >> > >> >>> >conservative assumption, that pluginstall might live
>> >> > >>separately
>> >> > >> > from
>> >> > >> > >> >>> >cordova-client. But I get the impression this is a
>> >>left-over
>> >> > >> notion
>> >> > >> > >> >>>from
>> >> > >> > >> >>> >when Andrew first built pluginstall and it wasn't clear
>> >>then
>> >> > >> > whether
>> >> > >> > >> >>>or
>> >> > >> > >> >>> >not
>> >> > >> > >> >>> >it would take hold.
>> >> > >> > >> >>> >
>> >> > >> > >> >>> >I've got an initial version of the merged documentation
>> >>for
>> >> > >>the
>> >> > >> > >> >>> >pluginstall
>> >> > >> > >> >>> >command line tool, and the specification doc. It's here
>> >> > >> > >> >>> >https://github.com/mreinstein/pluginstall
>> >> > >> > >> >>> >
>> >> > >> > >> >>> >I've also added some comments on possible changes.
>> >>Overall
>> >> the
>> >> > >> doc
>> >> > >> > is
>> >> > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
>> >> > >>appreciate
>> >> > >> > >> >>> >constructive feedback on this. If it looks right I'll
>> >>send a
>> >> > >>pull
>> >> > >> > >> >>>request
>> >> > >> > >> >>> >to alunny, and then proceed with merging cordova-client
>> >> design
>> >> > >> doc
>> >> > >> > >> >>>into
>> >> > >> > >> >>> >the
>> >> > >> > >> >>> >README on github.
>> >> > >> > >> >>> >
>> >> > >> > >> >>> >-Mike
>> >> > >> > >> >>> >
>> >> > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <
>> fil@adobe.com>
>> >> > >>wrote:
>> >> > >> > >> >>> >
>> >> > >> > >> >>> >> +1 !
>> >> > >> > >> >>> >>
>> >> > >> > >> >>> >> (I THINK) eventually we will move pluginstall into
>> >>apache
>> >> > >> > (assuming
>> >> > >> > >> >>>the
>> >> > >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1
>> >>doc.
>> >> > >> > >> >>> >>
>> >> > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >> > >> > >> >>> >>
>> >> > >> > >> >>> >> >love it
>> >> > >> > >> >>> >> >
>> >> > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>> >> > >> > >> >>> >><re...@gmail.com>
>> >> > >> > >> >>> >> >wrote:
>> >> > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a
>> >>chance
>> >> to
>> >> > >> > review
>> >> > >> > >> >>>the
>> >> > >> > >> >>> >> >>docs
>> >> > >> > >> >>> >> >> more carefully. I'm really impressed with how well
>> >> > >>written
>> >> > >> > they
>> >> > >> > >> >>>are.
>> >> > >> > >> >>> >> >>What I
>> >> > >> > >> >>> >> >> *think* makes the most sense is to consolidate into
>> >> fewer
>> >> > >> > >> >>>documents
>> >> > >> > >> >>> >>so
>> >> > >> > >> >>> >> >>that
>> >> > >> > >> >>> >> >> it's not necessary to look at so many seperate
>> >>places.
>> >> > >> Here's
>> >> > >> > >> >>>what I
>> >> > >> > >> >>> >> >> propose:
>> >> > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
>> >> > >>alunny/pluginstall
>> >> > >> > >> >>>README.md
>> >> > >> > >> >>> >> >> * merge the command line tooling design doc into
>> the
>> >> > >> > >> >>>cordova-client
>> >> > >> > >> >>> >> >> README.md
>> >> > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and
>> >> merge
>> >> > >> > parts
>> >> > >> > >> >>>of it
>> >> > >> > >> >>> >> >>into
>> >> > >> > >> >>> >> >> the above 2 docs
>> >> > >> > >> >>> >> >>
>> >> > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5,
>> >>and
>> >> it
>> >> > >> still
>> >> > >> > >> >>> >>maintains
>> >> > >> > >> >>> >> >> the nice loose coupling between alunny's
>> pluginstall
>> >> > >>utility
>> >> > >> > and
>> >> > >> > >> >>>the
>> >> > >> > >> >>> >> >>larger
>> >> > >> > >> >>> >> >> cordova-client. I'm assuming this separation was
>> the
>> >> > >> original
>> >> > >> > >> >>>intent,
>> >> > >> > >> >>> >> >> rather than having one monolithic tool.
>> >> > >> > >> >>> >> >>
>> >> > >> > >> >>> >> >> Would love feedback on this, I don't want to waste
>> >>time
>> >> > >> doing
>> >> > >> > it
>> >> > >> > >> >>>and
>> >> > >> > >> >>> >> >>find
>> >> > >> > >> >>> >> >> out this isn't appropriate. :)
>> >> > >> > >> >>> >> >>
>> >> > >> > >> >>> >> >>
>> >> > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
>> >> > >><fi...@adobe.com>
>> >> > >> > >> wrote:
>> >> > >> > >> >>> >> >>
>> >> > >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall
>> >> does
>> >> > >>the
>> >> > >> > >> hard
>> >> > >> > >> >>> >>work
>> >> > >> > >> >>> >> >>>for
>> >> > >> > >> >>> >> >>> programmatic plugin installation, which is just
>> >>one of
>> >> > >>the
>> >> > >> > apis
>> >> > >> > >> >>> >> >>>available
>> >> > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out"
>> >>to
>> >> > >> > >> >>>pluginstall.
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >> >>> The client also handles app creation, platform
>> >> > >> > >> >>>removal/addition, and
>> >> > >> > >> >>> >> >>> interpolating information from app's config.xml
>> >>into
>> >> the
>> >> > >> > >> >>>necessary
>> >> > >> > >> >>> >> >>>spots
>> >> > >> > >> >>> >> >>> in each native project.
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
>> >> > >> > >> reinstein.mike@gmail.com>
>> >> > >> > >> >>> >> wrote:
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >> >>> >Hey Filip,
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
>> >> > >>between
>> >> > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >>>
>> >> > >> > >>
>> >> > >>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >there seems to be some overlap there. Is
>> >>pluginstall
>> >> a
>> >> > >> > subset
>> >> > >> > >> >>>of
>> >> > >> > >> >>> >> >>> >functionality just related to plugins that has
>> >>moved
>> >> > >>into
>> >> > >> > >> >>> >> >>>cordova-client
>> >> > >> > >> >>> >> >>> >or
>> >> > >> > >> >>> >> >>> >is it different?
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
>> >> > >>codebase
>> >> > >> > that
>> >> > >> > >> >>> >> >>>incorporates
>> >> > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
>> >> > >>finding
>> >> > >> to
>> >> > >> > >> >>>see if
>> >> > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
>> >> > >>differently,
>> >> > >> is
>> >> > >> > >> it
>> >> > >> > >> >>> >>safe
>> >> > >> > >> >>> >> >>>to
>> >> > >> > >> >>> >> >>> >assume that just about all the worthwhile code is
>> >>in
>> >> > >> > >> >>> >>cordova-client?
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >-Mike
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
>> >> > >><fil@adobe.com
>> >> > >> >
>> >> > >> > >> >>>wrote:
>> >> > >> > >> >>> >> >>> >
>> >> > >> > >> >>> >> >>> >> All looks good to me Mike.
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would
>> >>be a
>> >> > >>great
>> >> > >> > >> >>>place to
>> >> > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate
>> you
>> >> > >> tackling
>> >> > >> > >> >>>this!
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
>> >> > >> > >> >>><re...@gmail.com>
>> >> > >> > >> >>> >> >>>wrote:
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>> >> >Hey Filip, Brian:
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >I think where I'd like to start is on
>> >> > >>documentation. I
>> >> > >> > may
>> >> > >> > >> >>>be
>> >> > >> > >> >>> >>wrong
>> >> > >> > >> >>> >> >>> >>about
>> >> > >> > >> >>> >> >>> >> >this, but it seems like there are bits and
>> >>pieces
>> >> of
>> >> > >> docs
>> >> > >> > >> in
>> >> > >> > >> >>> >> >>>various
>> >> > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
>> >> Maybe a
>> >> > >> good
>> >> > >> > >> >>>start
>> >> > >> > >> >>> >>is
>> >> > >> > >> >>> >> >>>for
>> >> > >> > >> >>> >> >>> >>me
>> >> > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
>> >> > >>"master"
>> >> > >> > >> >>>document,
>> >> > >> > >> >>> >>and
>> >> > >> > >> >>> >> >>> >>cull
>> >> > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
>> >> > >>rephrasing
>> >> > >> > of
>> >> > >> > >> >>>the
>> >> > >> > >> >>> >> >>>various
>> >> > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take
>> >>a
>> >> > >>look
>> >> > >> and
>> >> > >> > >> >>>let me
>> >> > >> > >> >>> >> >>>know
>> >> > >> > >> >>> >> >>> >>if
>> >> > >> > >> >>> >> >>> >> >I've characterised the content/purpose of
>> these
>> >> > >>various
>> >> > >> > >> >>>links:
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is
>> here:
>> >> > >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >The implementation that manages plugin usage
>> is
>> >> > >>here:
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>>>
>> >> > >> > >> >>>
>> >> > >> >
>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> > >> > >> >>> >> >>> >> >This project encompasses more than just
>> plugins
>> >> > >>because
>> >> > >> > it
>> >> > >> > >> >>>also
>> >> > >> > >> >>> >> >>>handles
>> >> > >> > >> >>> >> >>> >> >everything related to building, deploying, and
>> >> > >>managing
>> >> > >> > >> >>>cordova
>> >> > >> > >> >>> >> >>> >> >applications
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >These plugins are most popular, and should
>> >>ideally
>> >> > >>work
>> >> > >> > >> >>>with the
>> >> > >> > >> >>> >> >>> >> >cordova-client implemenation:
>> >> > >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >This implementation by Drew was an initial
>> >>proof
>> >> of
>> >> > >> > >> concept,
>> >> > >> > >> >>> >>which
>> >> > >> > >> >>> >> >>>only
>> >> > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
>> >> > >>favor of
>> >> > >> > >> >>> >> >>>cordova-client,
>> >> > >> > >> >>> >> >>> >> >with much of his ideas having made it into
>> >> > >> > cordova-client:
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> https://github.com/deedubbu/cordova-blackberry-pluggable
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >This doc contains some info on the format of
>> >>the
>> >> > >> command
>> >> > >> > >> >>>line
>> >> > >> > >> >>> >> >>>interface
>> >> > >> > >> >>> >> >>> >> >and
>> >> > >> > >> >>> >> >>> >> >directory structure of cordova-client:
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's
>> >>old
>> >> > >> > >> >>> >>implementation,
>> >> > >> > >> >>> >> >>>and
>> >> > >> > >> >>> >> >>> >>is
>> >> > >> > >> >>> >> >>> >> >out of date now:
>> >> > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to
>> >>get a
>> >> > >> handle
>> >> > >> > on
>> >> > >> > >> >>>what
>> >> > >> > >> >>> >> >>>docs
>> >> > >> > >> >>> >> >>> >>are
>> >> > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
>> >> > >>judging
>> >> > >> > >> >>>anyone's
>> >> > >> > >> >>> >> >>>work or
>> >> > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong
>> >>idea
>> >> > >>about
>> >> > >> > >> what
>> >> > >> > >> >>> >>these
>> >> > >> > >> >>> >> >>> >>links
>> >> > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >-Mike
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >*
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
>> >> > >> > fil@adobe.com>
>> >> > >> > >> >>> >>wrote:
>> >> > >> > >> >>> >> >>> >> >
>> >> > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level
>> >>project
>> >> > >>goes
>> >> > >> > >> >>> >> >>>hand-in-hand
>> >> > >> > >> >>> >> >>> >>with
>> >> > >> > >> >>> >> >>> >> >> this spec. Code here:
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >>
>> >> > >> > >> >>>
>> >> > >> > >> >>>
>> >> > >> > >>
>> >> > >> >
>> >> > >>
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> >> > >> > >> >>> >> >>>h
>> >> > >> > >> >>> >> >>> >> >>or
>> >> > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
>> >> popular
>> >> > >> > >> >>>plugins out
>> >> > >> > >> >>> >> >>>in the
>> >> > >> > >> >>> >> >>> >> >>wild
>> >> > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins)
>> >>work
>> >> > >>with
>> >> > >> > >> this
>> >> > >> > >> >>> >>spec.
>> >> > >> > >> >>> >> >>>Do
>> >> > >> > >> >>> >> >>> we
>> >> > >> > >> >>> >> >>> >> >>need
>> >> > >> > >> >>> >> >>> >> >> to account for anything else?
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >> I think the one outstanding question is how
>> >>to
>> >> > >>handle
>> >> > >> > >> >>> >> >>>installation /
>> >> > >> > >> >>> >> >>> >> >> compatibility with different versions of
>> >> cordova.
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the
>> >>spec
>> >> > >>(put
>> >> > >> it
>> >> > >> > on
>> >> > >> > >> >>>the
>> >> > >> > >> >>> >> >>>wiki,
>> >> > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>> >> > >> > >> >>> >><re...@gmail.com>
>> >> > >> > >> >>> >> >>> >>wrote:
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects.
>> >>I'd
>> >> > >>love
>> >> > >> to
>> >> > >> > >> >>>dig in
>> >> > >> > >> >>> >> >>>and
>> >> > >> > >> >>> >> >>> >>start
>> >> > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
>> >> > >>needed
>> >> > >> at
>> >> > >> > >> the
>> >> > >> > >> >>> >> >>>moment?
>> >> > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >-Mike
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
>> >> > >> > >> >>><fi...@adobe.com>
>> >> > >> > >> >>> >> >>>wrote:
>> >> > >> > >> >>> >> >>> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
>> >> > >>"spec"
>> >> > >> we
>> >> > >> > >> are
>> >> > >> > >> >>> >> >>>working
>> >> > >> > >> >>> >> >>> >> >>towards:
>> >> > >> > >> >>> >> >>> >> >> >>
>> >> https://github.com/alunny/cordova-plugin-spec
>> >> > >> > >> >>> >> >>> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
>> >> b@brian.io>
>> >> > >> > wrote:
>> >> > >> > >> >>> >> >>> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
>> >> > >> Currently
>> >> > >> > >> the
>> >> > >> > >> >>> >>plugin
>> >> > >> > >> >>> >> >>> >> >>tooling
>> >> > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil,
>> >>Michael,
>> >> > >>and
>> >> > >> > >> >>>myself.
>> >> > >> > >> >>> >> >>>(sorry
>> >> > >> > >> >>> >> >>> >>for
>> >> > >> > >> >>> >> >>> >> >>the
>> >> > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
>> >> summer
>> >> > >> break
>> >> > >> > >> >>>after
>> >> > >> > >> >>> >> >>> >>shipping
>> >> > >> > >> >>> >> >>> >> >> >> >2.0)
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this
>> >>list,
>> >> > >>git,
>> >> > >> > and
>> >> > >> > >> >>> >>these
>> >> > >> > >> >>> >> >>>wiki
>> >> > >> > >> >>> >> >>> >> >>pages:
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >-
>> >> http://wiki.apache.org/cordova/PluginDesign
>> >> > >> > >> >>> >> >>> >> >> >> >-
>> >> > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
>> >> branch
>> >> > >> which
>> >> > >> > >> >>>you
>> >> > >> > >> >>> >>can
>> >> > >> > >> >>> >> >>> >>preview
>> >> > >> > >> >>> >> >>> >> >>on
>> >> > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >>
>> >> > >> > >>
>> >> > >>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on
>> >>our
>> >> > >> contrib
>> >> > >> > >> >>> >>process
>> >> > >> > >> >>> >> >>>in
>> >> > >> > >> >>> >> >>> >>the
>> >> > >> > >> >>> >> >>> >> >> >>wiki:
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> http://wiki.apache.org/cordova/ContributerWorkflow
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects
>> >>everything
>> >> > >>stays
>> >> > >> > on
>> >> > >> > >> >>>its
>> >> > >> > >> >>> >>own
>> >> > >> > >> >>> >> >>> >>branch
>> >> > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid
>> >>for
>> >> > >>its
>> >> > >> > own
>> >> > >> > >> >>>repo.
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >* * *
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >
>> >> > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
>> >> > >>Reinstein
>> >> > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>> >> > >> > >> >>> >> >>> >> >> >> >> Hey there,
>> >> > >> > >> >>> >> >>> >> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the
>> >> plugin
>> >> > >> > system
>> >> > >> > >> >>> >>that is
>> >> > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
>> >> > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up?
>> >>Who
>> >> are
>> >> > >> the
>> >> > >> > >> >>>right
>> >> > >> > >> >>> >> >>>people
>> >> > >> > >> >>> >> >>> >>to
>> >> > >> > >> >>> >> >>> >> >>talk
>> >> > >> > >> >>> >> >>> >> >> >> >>to?
>> >> > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm
>> an
>> >> > >> > experienced
>> >> > >> > >> >>> >> >>>developer,
>> >> > >> > >> >>> >> >>> >> >>have
>> >> > >> > >> >>> >> >>> >> >> >> >>worked
>> >> > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and
>> >> would
>> >> > >> love
>> >> > >> > to
>> >> > >> > >> >>>give
>> >> > >> > >> >>> >> >>>back
>> >> > >> > >> >>> >> >>> >>to
>> >> > >> > >> >>> >> >>> >> >>the
>> >> > >> > >> >>> >> >>> >> >> >> >> community.
>> >> > >> > >> >>> >> >>> >> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >> >> cheers,
>> >> > >> > >> >>> >> >>> >> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >> >> -Mike
>> >> > >> > >> >>> >> >>> >> >> >>
>> >> > >> > >> >>> >> >>> >> >> >>
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >> >>
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>> >>
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >> >>>
>> >> > >> > >> >>> >>
>> >> > >> > >> >>> >>
>> >> > >> > >> >>>
>> >> > >> > >> >>>
>> >> > >> > >>
>> >> > >> > >>
>> >> > >> > >
>> >> > >> >
>> >> > >>
>> >> >
>> >> >
>> >>
>>
>>
>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
Alright, I'll post my comments here for now, but I'll have to ponder over a
more scalable approach in the future. (Im thinking that an online document
editor that sends all comments to ML and allows replies inline would work
really nice..).
* You will be able to access the client interface via: $ ./bin/cordova
* * suggest replacing ./ with $(CORDOVA_CLIENT_DIR)/
* Subcommands section
* * Typical unix manpage style is to use [] to surround optional arguments
<> to surround explanations and nothing for keywords. Examples that need
fixing include:
* * * create <directory> [<id>] [<name>]
* * * platform ls
* * * platform add <platform>
* * * etc
* * even if we aren't aiming for manpage style here, there
are inconsistencies
* * File and Directory Structure ascii tree diagram
* * * suggest appending / after directory names
* * ... it's assumed to be a 'backed in' platform/plugin. Otherwise, it's
assumed to be a URL to a gzipped tar archive...
* * * Not sure what 'backed in' means here, nor how to identify something
as not being backed in so as to fallback to gzipped tar
* * * Also wording sounds more like "else .. else" instead of "else if ..
else" (if that makes sense) :P
* * KewlApp directory structure ascii tree diagram
* * * based on my understanding of the text, the ios/android platforms
should be subdirs of platforms/ and there should also be a subdir listed in
plugins/
* * Running tests warning
* * * Perhaps explain how to bootstrap so as not to have failing tests
instead of assuming the reverse?
Also, I will look into bash completions in some spare cycles and if it
looks reasonable I may volunteer for the task. I've been curious to learn
how those work :)
-Michal
On Mon, Sep 10, 2012 at 2:52 PM, Filip Maj <fi...@adobe.com> wrote:
> Mailing list! We forked and committed for the simple stuff (deeper
> explanations and merging documentation), but if you have discussion +
> design points, ML is the place to do it.
>
> On 9/10/12 11:31 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
> >I'm just reading along and would like to make some comments here and
> >there.
> > However, it seems pretty inefficient to branch the project just to mark
> >my
> >comments and email may be confusing.
> >
> >Usually I've just used Google Docs to mark comments inline for stuff like
> >this but perhaps that suggestion won't fly well. Does github not have a
> >feature for this (commenting on a file, starting a wiki, etc?)
> >
> >Any suggestions/opinions?
> >
> >
> >On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein
> ><re...@gmail.com>wrote:
> >
> >> Looks good to me. What are the next steps? One thing I'd like to see
> >>happen
> >> is getting rid of some of those repos and documentation pages that are
> >> redundant.
> >>
> >> -Mike
> >>
> >> On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >> > Nice!
> >> >
> >> > I worked out some of your quotes/questions and put it up on my branch
> >>on
> >> > github: https://github.com/filmaj/cordova-client/tree/einstein
> >> >
> >> > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
> >> >
> >> > >Hey folks,
> >> > >
> >> > >Hope you all had a nice weekend. I have a preliminary draft ready
> >>that
> >> > >merges cordova-client and command line tooling design into 1
> >>document:
> >> > >
> >> > >
> >>
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >> > >
> >> > >Any feedback would be greatly appreciated. Thanks!
> >> > >
> >> > >-Mike
> >> > >
> >> > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com>
> >> wrote:
> >> > >
> >> > >> Hi Mike,
> >> > >>
> >> > >> pluginstall-with-git support is just an experiment that I did a
> >>while
> >> > >>back
> >> > >> (it takes git URLs as well as local paths). I suggest you base your
> >> > >>work on
> >> > >> alunny's pluginstall until/if those changes get merged.
> >> > >>
> >> > >> Cheers
> >> > >>
> >> > >> Anis
> >> > >>
> >> > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
> >> > reinstein.mike@gmail.com
> >> > >> >wrote:
> >> > >>
> >> > >> > I see 2 repositories for pluginstall:
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >>
> >> > >>
> >> >
> >>
> >>
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
> >> > >>t-support
> >> > >> >
> >> > >> > and Andrew's:
> >> > >> > https://github.com/alunny/pluginstall
> >> > >> >
> >> > >> > When consolidating the pluginstall and plugin format docs I
> >>forked
> >> > >> Andrew's
> >> > >> > repo. Should I instead have used the pluginstall-with-git-support
> >> > >>repo as
> >> > >> > my base?
> >> > >> >
> >> > >> > -Mike
> >> > >> >
> >> > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
> >> > >><reinstein.mike@gmail.com
> >> > >> > >wrote:
> >> > >> >
> >> > >> > > My username is nekoflux.
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com>
> >>wrote:
> >> > >> > >
> >> > >> > >> JIRA is separate, we can assign issues to you (if you so
> >>wish).
> >> > >> > >>
> >> > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> >> > >> > >>
> >> > >> > >> >Registration is open - let us know what your user account is
> >> once
> >> > >>you
> >> > >> > >> >do that, for assigning issues to yourself you need us to add
> >>you
> >> > >>to a
> >> > >> > >> >contributors group.
> >> > >> > >> >
> >> > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> >> > >> > reinstein.mike@gmail.com
> >> > >> > >> >
> >> > >> > >> >wrote:
> >> > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
> >> proceed
> >> > >> with
> >> > >> > >> >> merging the cordova-client and command line tooling spec
> >> next. I
> >> > >> > >> >>suppose it
> >> > >> > >> >> probably makes sense for me to start working out of JIRA so
> >> > >>these
> >> > >> > tasks
> >> > >> > >> >>can
> >> > >> > >> >> be tracked. Is registration open or do I need to get
> >> permission
> >> > >> from
> >> > >> > an
> >> > >> > >> >> admin for an account?
> >> > >> > >> >>
> >> > >> > >> >>
> >> > >> > >> >>
> >> > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
> >> > wrote:
> >> > >> > >> >>
> >> > >> > >> >>> Sorry for the late reply, this looks awesome!
> >> > >> > >> >>>
> >> > >> > >> >>> The one modification I would do is remove "www" as a
> >>platform
> >> > >>(you
> >> > >> > >> >>>have a
> >> > >> > >> >>> comment in there about that too).
> >> > >> > >> >>>
> >> > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
> >> reinstein.mike@gmail.com>
> >> > >> > wrote:
> >> > >> > >> >>>
> >> > >> > >> >>> >> eventually we will move pluginstall into apache
> >> > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with
> >>the
> >> > >> > slightly
> >> > >> > >> >>>more
> >> > >> > >> >>> >conservative assumption, that pluginstall might live
> >> > >>separately
> >> > >> > from
> >> > >> > >> >>> >cordova-client. But I get the impression this is a
> >>left-over
> >> > >> notion
> >> > >> > >> >>>from
> >> > >> > >> >>> >when Andrew first built pluginstall and it wasn't clear
> >>then
> >> > >> > whether
> >> > >> > >> >>>or
> >> > >> > >> >>> >not
> >> > >> > >> >>> >it would take hold.
> >> > >> > >> >>> >
> >> > >> > >> >>> >I've got an initial version of the merged documentation
> >>for
> >> > >>the
> >> > >> > >> >>> >pluginstall
> >> > >> > >> >>> >command line tool, and the specification doc. It's here
> >> > >> > >> >>> >https://github.com/mreinstein/pluginstall
> >> > >> > >> >>> >
> >> > >> > >> >>> >I've also added some comments on possible changes.
> >>Overall
> >> the
> >> > >> doc
> >> > >> > is
> >> > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
> >> > >>appreciate
> >> > >> > >> >>> >constructive feedback on this. If it looks right I'll
> >>send a
> >> > >>pull
> >> > >> > >> >>>request
> >> > >> > >> >>> >to alunny, and then proceed with merging cordova-client
> >> design
> >> > >> doc
> >> > >> > >> >>>into
> >> > >> > >> >>> >the
> >> > >> > >> >>> >README on github.
> >> > >> > >> >>> >
> >> > >> > >> >>> >-Mike
> >> > >> > >> >>> >
> >> > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fil@adobe.com
> >
> >> > >>wrote:
> >> > >> > >> >>> >
> >> > >> > >> >>> >> +1 !
> >> > >> > >> >>> >>
> >> > >> > >> >>> >> (I THINK) eventually we will move pluginstall into
> >>apache
> >> > >> > (assuming
> >> > >> > >> >>>the
> >> > >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1
> >>doc.
> >> > >> > >> >>> >>
> >> > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >> > >> > >> >>> >>
> >> > >> > >> >>> >> >love it
> >> > >> > >> >>> >> >
> >> > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >> > >> > >> >>> >><re...@gmail.com>
> >> > >> > >> >>> >> >wrote:
> >> > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a
> >>chance
> >> to
> >> > >> > review
> >> > >> > >> >>>the
> >> > >> > >> >>> >> >>docs
> >> > >> > >> >>> >> >> more carefully. I'm really impressed with how well
> >> > >>written
> >> > >> > they
> >> > >> > >> >>>are.
> >> > >> > >> >>> >> >>What I
> >> > >> > >> >>> >> >> *think* makes the most sense is to consolidate into
> >> fewer
> >> > >> > >> >>>documents
> >> > >> > >> >>> >>so
> >> > >> > >> >>> >> >>that
> >> > >> > >> >>> >> >> it's not necessary to look at so many seperate
> >>places.
> >> > >> Here's
> >> > >> > >> >>>what I
> >> > >> > >> >>> >> >> propose:
> >> > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
> >> > >>alunny/pluginstall
> >> > >> > >> >>>README.md
> >> > >> > >> >>> >> >> * merge the command line tooling design doc into the
> >> > >> > >> >>>cordova-client
> >> > >> > >> >>> >> >> README.md
> >> > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and
> >> merge
> >> > >> > parts
> >> > >> > >> >>>of it
> >> > >> > >> >>> >> >>into
> >> > >> > >> >>> >> >> the above 2 docs
> >> > >> > >> >>> >> >>
> >> > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5,
> >>and
> >> it
> >> > >> still
> >> > >> > >> >>> >>maintains
> >> > >> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
> >> > >>utility
> >> > >> > and
> >> > >> > >> >>>the
> >> > >> > >> >>> >> >>larger
> >> > >> > >> >>> >> >> cordova-client. I'm assuming this separation was the
> >> > >> original
> >> > >> > >> >>>intent,
> >> > >> > >> >>> >> >> rather than having one monolithic tool.
> >> > >> > >> >>> >> >>
> >> > >> > >> >>> >> >> Would love feedback on this, I don't want to waste
> >>time
> >> > >> doing
> >> > >> > it
> >> > >> > >> >>>and
> >> > >> > >> >>> >> >>find
> >> > >> > >> >>> >> >> out this isn't appropriate. :)
> >> > >> > >> >>> >> >>
> >> > >> > >> >>> >> >>
> >> > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
> >> > >><fi...@adobe.com>
> >> > >> > >> wrote:
> >> > >> > >> >>> >> >>
> >> > >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall
> >> does
> >> > >>the
> >> > >> > >> hard
> >> > >> > >> >>> >>work
> >> > >> > >> >>> >> >>>for
> >> > >> > >> >>> >> >>> programmatic plugin installation, which is just
> >>one of
> >> > >>the
> >> > >> > apis
> >> > >> > >> >>> >> >>>available
> >> > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out"
> >>to
> >> > >> > >> >>>pluginstall.
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >> >>> The client also handles app creation, platform
> >> > >> > >> >>>removal/addition, and
> >> > >> > >> >>> >> >>> interpolating information from app's config.xml
> >>into
> >> the
> >> > >> > >> >>>necessary
> >> > >> > >> >>> >> >>>spots
> >> > >> > >> >>> >> >>> in each native project.
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> >> > >> > >> reinstein.mike@gmail.com>
> >> > >> > >> >>> >> wrote:
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >> >>> >Hey Filip,
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
> >> > >>between
> >> > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >>>
> >> > >> > >>
> >> > >>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >there seems to be some overlap there. Is
> >>pluginstall
> >> a
> >> > >> > subset
> >> > >> > >> >>>of
> >> > >> > >> >>> >> >>> >functionality just related to plugins that has
> >>moved
> >> > >>into
> >> > >> > >> >>> >> >>>cordova-client
> >> > >> > >> >>> >> >>> >or
> >> > >> > >> >>> >> >>> >is it different?
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
> >> > >>codebase
> >> > >> > that
> >> > >> > >> >>> >> >>>incorporates
> >> > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
> >> > >>finding
> >> > >> to
> >> > >> > >> >>>see if
> >> > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
> >> > >>differently,
> >> > >> is
> >> > >> > >> it
> >> > >> > >> >>> >>safe
> >> > >> > >> >>> >> >>>to
> >> > >> > >> >>> >> >>> >assume that just about all the worthwhile code is
> >>in
> >> > >> > >> >>> >>cordova-client?
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >-Mike
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
> >> > >><fil@adobe.com
> >> > >> >
> >> > >> > >> >>>wrote:
> >> > >> > >> >>> >> >>> >
> >> > >> > >> >>> >> >>> >> All looks good to me Mike.
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would
> >>be a
> >> > >>great
> >> > >> > >> >>>place to
> >> > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
> >> > >> tackling
> >> > >> > >> >>>this!
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> >> > >> > >> >>><re...@gmail.com>
> >> > >> > >> >>> >> >>>wrote:
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>> >> >Hey Filip, Brian:
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >I think where I'd like to start is on
> >> > >>documentation. I
> >> > >> > may
> >> > >> > >> >>>be
> >> > >> > >> >>> >>wrong
> >> > >> > >> >>> >> >>> >>about
> >> > >> > >> >>> >> >>> >> >this, but it seems like there are bits and
> >>pieces
> >> of
> >> > >> docs
> >> > >> > >> in
> >> > >> > >> >>> >> >>>various
> >> > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
> >> Maybe a
> >> > >> good
> >> > >> > >> >>>start
> >> > >> > >> >>> >>is
> >> > >> > >> >>> >> >>>for
> >> > >> > >> >>> >> >>> >>me
> >> > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
> >> > >>"master"
> >> > >> > >> >>>document,
> >> > >> > >> >>> >>and
> >> > >> > >> >>> >> >>> >>cull
> >> > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
> >> > >>rephrasing
> >> > >> > of
> >> > >> > >> >>>the
> >> > >> > >> >>> >> >>>various
> >> > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take
> >>a
> >> > >>look
> >> > >> and
> >> > >> > >> >>>let me
> >> > >> > >> >>> >> >>>know
> >> > >> > >> >>> >> >>> >>if
> >> > >> > >> >>> >> >>> >> >I've characterised the content/purpose of these
> >> > >>various
> >> > >> > >> >>>links:
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> >> > >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >The implementation that manages plugin usage is
> >> > >>here:
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>>>
> >> > >> > >> >>>
> >> > >> >
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> > >> >>> >> >>> >> >This project encompasses more than just plugins
> >> > >>because
> >> > >> > it
> >> > >> > >> >>>also
> >> > >> > >> >>> >> >>>handles
> >> > >> > >> >>> >> >>> >> >everything related to building, deploying, and
> >> > >>managing
> >> > >> > >> >>>cordova
> >> > >> > >> >>> >> >>> >> >applications
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >These plugins are most popular, and should
> >>ideally
> >> > >>work
> >> > >> > >> >>>with the
> >> > >> > >> >>> >> >>> >> >cordova-client implemenation:
> >> > >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >This implementation by Drew was an initial
> >>proof
> >> of
> >> > >> > >> concept,
> >> > >> > >> >>> >>which
> >> > >> > >> >>> >> >>>only
> >> > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
> >> > >>favor of
> >> > >> > >> >>> >> >>>cordova-client,
> >> > >> > >> >>> >> >>> >> >with much of his ideas having made it into
> >> > >> > cordova-client:
> >> > >> > >> >>> >> >>> >> >
> >> > >> https://github.com/deedubbu/cordova-blackberry-pluggable
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >This doc contains some info on the format of
> >>the
> >> > >> command
> >> > >> > >> >>>line
> >> > >> > >> >>> >> >>>interface
> >> > >> > >> >>> >> >>> >> >and
> >> > >> > >> >>> >> >>> >> >directory structure of cordova-client:
> >> > >> > >> >>> >> >>> >> >
> >> > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's
> >>old
> >> > >> > >> >>> >>implementation,
> >> > >> > >> >>> >> >>>and
> >> > >> > >> >>> >> >>> >>is
> >> > >> > >> >>> >> >>> >> >out of date now:
> >> > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to
> >>get a
> >> > >> handle
> >> > >> > on
> >> > >> > >> >>>what
> >> > >> > >> >>> >> >>>docs
> >> > >> > >> >>> >> >>> >>are
> >> > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
> >> > >>judging
> >> > >> > >> >>>anyone's
> >> > >> > >> >>> >> >>>work or
> >> > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong
> >>idea
> >> > >>about
> >> > >> > >> what
> >> > >> > >> >>> >>these
> >> > >> > >> >>> >> >>> >>links
> >> > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >-Mike
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >*
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> >> > >> > fil@adobe.com>
> >> > >> > >> >>> >>wrote:
> >> > >> > >> >>> >> >>> >> >
> >> > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level
> >>project
> >> > >>goes
> >> > >> > >> >>> >> >>>hand-in-hand
> >> > >> > >> >>> >> >>> >>with
> >> > >> > >> >>> >> >>> >> >> this spec. Code here:
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >>
> >> > >> > >> >>>
> >> > >> > >> >>>
> >> > >> > >>
> >> > >> >
> >> > >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >> > >> > >> >>> >> >>>h
> >> > >> > >> >>> >> >>> >> >>or
> >> > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
> >> popular
> >> > >> > >> >>>plugins out
> >> > >> > >> >>> >> >>>in the
> >> > >> > >> >>> >> >>> >> >>wild
> >> > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins)
> >>work
> >> > >>with
> >> > >> > >> this
> >> > >> > >> >>> >>spec.
> >> > >> > >> >>> >> >>>Do
> >> > >> > >> >>> >> >>> we
> >> > >> > >> >>> >> >>> >> >>need
> >> > >> > >> >>> >> >>> >> >> to account for anything else?
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >> I think the one outstanding question is how
> >>to
> >> > >>handle
> >> > >> > >> >>> >> >>>installation /
> >> > >> > >> >>> >> >>> >> >> compatibility with different versions of
> >> cordova.
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the
> >>spec
> >> > >>(put
> >> > >> it
> >> > >> > on
> >> > >> > >> >>>the
> >> > >> > >> >>> >> >>>wiki,
> >> > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >> > >> > >> >>> >><re...@gmail.com>
> >> > >> > >> >>> >> >>> >>wrote:
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects.
> >>I'd
> >> > >>love
> >> > >> to
> >> > >> > >> >>>dig in
> >> > >> > >> >>> >> >>>and
> >> > >> > >> >>> >> >>> >>start
> >> > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
> >> > >>needed
> >> > >> at
> >> > >> > >> the
> >> > >> > >> >>> >> >>>moment?
> >> > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >-Mike
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> >> > >> > >> >>><fi...@adobe.com>
> >> > >> > >> >>> >> >>>wrote:
> >> > >> > >> >>> >> >>> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
> >> > >>"spec"
> >> > >> we
> >> > >> > >> are
> >> > >> > >> >>> >> >>>working
> >> > >> > >> >>> >> >>> >> >>towards:
> >> > >> > >> >>> >> >>> >> >> >>
> >> https://github.com/alunny/cordova-plugin-spec
> >> > >> > >> >>> >> >>> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
> >> b@brian.io>
> >> > >> > wrote:
> >> > >> > >> >>> >> >>> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
> >> > >> Currently
> >> > >> > >> the
> >> > >> > >> >>> >>plugin
> >> > >> > >> >>> >> >>> >> >>tooling
> >> > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil,
> >>Michael,
> >> > >>and
> >> > >> > >> >>>myself.
> >> > >> > >> >>> >> >>>(sorry
> >> > >> > >> >>> >> >>> >>for
> >> > >> > >> >>> >> >>> >> >>the
> >> > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
> >> summer
> >> > >> break
> >> > >> > >> >>>after
> >> > >> > >> >>> >> >>> >>shipping
> >> > >> > >> >>> >> >>> >> >> >> >2.0)
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this
> >>list,
> >> > >>git,
> >> > >> > and
> >> > >> > >> >>> >>these
> >> > >> > >> >>> >> >>>wiki
> >> > >> > >> >>> >> >>> >> >>pages:
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >-
> >> http://wiki.apache.org/cordova/PluginDesign
> >> > >> > >> >>> >> >>> >> >> >> >-
> >> > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
> >> branch
> >> > >> which
> >> > >> > >> >>>you
> >> > >> > >> >>> >>can
> >> > >> > >> >>> >> >>> >>preview
> >> > >> > >> >>> >> >>> >> >>on
> >> > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >>
> >> > >> > >>
> >> > >>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on
> >>our
> >> > >> contrib
> >> > >> > >> >>> >>process
> >> > >> > >> >>> >> >>>in
> >> > >> > >> >>> >> >>> >>the
> >> > >> > >> >>> >> >>> >> >> >>wiki:
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> http://wiki.apache.org/cordova/ContributerWorkflow
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects
> >>everything
> >> > >>stays
> >> > >> > on
> >> > >> > >> >>>its
> >> > >> > >> >>> >>own
> >> > >> > >> >>> >> >>> >>branch
> >> > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid
> >>for
> >> > >>its
> >> > >> > own
> >> > >> > >> >>>repo.
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >* * *
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >
> >> > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
> >> > >>Reinstein
> >> > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >> > >> > >> >>> >> >>> >> >> >> >> Hey there,
> >> > >> > >> >>> >> >>> >> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the
> >> plugin
> >> > >> > system
> >> > >> > >> >>> >>that is
> >> > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> >> > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up?
> >>Who
> >> are
> >> > >> the
> >> > >> > >> >>>right
> >> > >> > >> >>> >> >>>people
> >> > >> > >> >>> >> >>> >>to
> >> > >> > >> >>> >> >>> >> >>talk
> >> > >> > >> >>> >> >>> >> >> >> >>to?
> >> > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> >> > >> > experienced
> >> > >> > >> >>> >> >>>developer,
> >> > >> > >> >>> >> >>> >> >>have
> >> > >> > >> >>> >> >>> >> >> >> >>worked
> >> > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and
> >> would
> >> > >> love
> >> > >> > to
> >> > >> > >> >>>give
> >> > >> > >> >>> >> >>>back
> >> > >> > >> >>> >> >>> >>to
> >> > >> > >> >>> >> >>> >> >>the
> >> > >> > >> >>> >> >>> >> >> >> >> community.
> >> > >> > >> >>> >> >>> >> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >> >> cheers,
> >> > >> > >> >>> >> >>> >> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >> >> -Mike
> >> > >> > >> >>> >> >>> >> >> >>
> >> > >> > >> >>> >> >>> >> >> >>
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >> >>
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>> >>
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >> >>>
> >> > >> > >> >>> >>
> >> > >> > >> >>> >>
> >> > >> > >> >>>
> >> > >> > >> >>>
> >> > >> > >>
> >> > >> > >>
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >> >
> >>
>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Michael,
I strong agree. It's kind of silly that my solution for merging this
documentation into less pieces involves ...creating a new copy.... :) I'd
love to kill my forks, as well as any others that aren't really needed. One
of my biggest frustrations with cordova from a user's perspective is how
many disparate forks and branches of repos that are out there.
-Mike
On Mon, Sep 10, 2012 at 2:31 PM, Michal Mocny <mm...@chromium.org> wrote:
> I'm just reading along and would like to make some comments here and there.
> However, it seems pretty inefficient to branch the project just to mark my
> comments and email may be confusing.
>
> Usually I've just used Google Docs to mark comments inline for stuff like
> this but perhaps that suggestion won't fly well. Does github not have a
> feature for this (commenting on a file, starting a wiki, etc?)
>
> Any suggestions/opinions?
>
>
> On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > Looks good to me. What are the next steps? One thing I'd like to see
> happen
> > is getting rid of some of those repos and documentation pages that are
> > redundant.
> >
> > -Mike
> >
> > On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> > > Nice!
> > >
> > > I worked out some of your quotes/questions and put it up on my branch
> on
> > > github: https://github.com/filmaj/cordova-client/tree/einstein
> > >
> > > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
> > >
> > > >Hey folks,
> > > >
> > > >Hope you all had a nice weekend. I have a preliminary draft ready
> that
> > > >merges cordova-client and command line tooling design into 1 document:
> > > >
> > > >
> > https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> > > >
> > > >Any feedback would be greatly appreciated. Thanks!
> > > >
> > > >-Mike
> > > >
> > > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com>
> > wrote:
> > > >
> > > >> Hi Mike,
> > > >>
> > > >> pluginstall-with-git support is just an experiment that I did a
> while
> > > >>back
> > > >> (it takes git URLs as well as local paths). I suggest you base your
> > > >>work on
> > > >> alunny's pluginstall until/if those changes get merged.
> > > >>
> > > >> Cheers
> > > >>
> > > >> Anis
> > > >>
> > > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
> > > reinstein.mike@gmail.com
> > > >> >wrote:
> > > >>
> > > >> > I see 2 repositories for pluginstall:
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > >
> >
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
> > > >>t-support
> > > >> >
> > > >> > and Andrew's:
> > > >> > https://github.com/alunny/pluginstall
> > > >> >
> > > >> > When consolidating the pluginstall and plugin format docs I forked
> > > >> Andrew's
> > > >> > repo. Should I instead have used the pluginstall-with-git-support
> > > >>repo as
> > > >> > my base?
> > > >> >
> > > >> > -Mike
> > > >> >
> > > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
> > > >><reinstein.mike@gmail.com
> > > >> > >wrote:
> > > >> >
> > > >> > > My username is nekoflux.
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com>
> wrote:
> > > >> > >
> > > >> > >> JIRA is separate, we can assign issues to you (if you so wish).
> > > >> > >>
> > > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> > > >> > >>
> > > >> > >> >Registration is open - let us know what your user account is
> > once
> > > >>you
> > > >> > >> >do that, for assigning issues to yourself you need us to add
> you
> > > >>to a
> > > >> > >> >contributors group.
> > > >> > >> >
> > > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> > > >> > reinstein.mike@gmail.com
> > > >> > >> >
> > > >> > >> >wrote:
> > > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
> > proceed
> > > >> with
> > > >> > >> >> merging the cordova-client and command line tooling spec
> > next. I
> > > >> > >> >>suppose it
> > > >> > >> >> probably makes sense for me to start working out of JIRA so
> > > >>these
> > > >> > tasks
> > > >> > >> >>can
> > > >> > >> >> be tracked. Is registration open or do I need to get
> > permission
> > > >> from
> > > >> > an
> > > >> > >> >> admin for an account?
> > > >> > >> >>
> > > >> > >> >>
> > > >> > >> >>
> > > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
> > > wrote:
> > > >> > >> >>
> > > >> > >> >>> Sorry for the late reply, this looks awesome!
> > > >> > >> >>>
> > > >> > >> >>> The one modification I would do is remove "www" as a
> platform
> > > >>(you
> > > >> > >> >>>have a
> > > >> > >> >>> comment in there about that too).
> > > >> > >> >>>
> > > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
> > reinstein.mike@gmail.com>
> > > >> > wrote:
> > > >> > >> >>>
> > > >> > >> >>> >> eventually we will move pluginstall into apache
> > > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with
> the
> > > >> > slightly
> > > >> > >> >>>more
> > > >> > >> >>> >conservative assumption, that pluginstall might live
> > > >>separately
> > > >> > from
> > > >> > >> >>> >cordova-client. But I get the impression this is a
> left-over
> > > >> notion
> > > >> > >> >>>from
> > > >> > >> >>> >when Andrew first built pluginstall and it wasn't clear
> then
> > > >> > whether
> > > >> > >> >>>or
> > > >> > >> >>> >not
> > > >> > >> >>> >it would take hold.
> > > >> > >> >>> >
> > > >> > >> >>> >I've got an initial version of the merged documentation
> for
> > > >>the
> > > >> > >> >>> >pluginstall
> > > >> > >> >>> >command line tool, and the specification doc. It's here
> > > >> > >> >>> >https://github.com/mreinstein/pluginstall
> > > >> > >> >>> >
> > > >> > >> >>> >I've also added some comments on possible changes. Overall
> > the
> > > >> doc
> > > >> > is
> > > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
> > > >>appreciate
> > > >> > >> >>> >constructive feedback on this. If it looks right I'll
> send a
> > > >>pull
> > > >> > >> >>>request
> > > >> > >> >>> >to alunny, and then proceed with merging cordova-client
> > design
> > > >> doc
> > > >> > >> >>>into
> > > >> > >> >>> >the
> > > >> > >> >>> >README on github.
> > > >> > >> >>> >
> > > >> > >> >>> >-Mike
> > > >> > >> >>> >
> > > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com>
> > > >>wrote:
> > > >> > >> >>> >
> > > >> > >> >>> >> +1 !
> > > >> > >> >>> >>
> > > >> > >> >>> >> (I THINK) eventually we will move pluginstall into
> apache
> > > >> > (assuming
> > > >> > >> >>>the
> > > >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1
> doc.
> > > >> > >> >>> >>
> > > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> > > >> > >> >>> >>
> > > >> > >> >>> >> >love it
> > > >> > >> >>> >> >
> > > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> > > >> > >> >>> >><re...@gmail.com>
> > > >> > >> >>> >> >wrote:
> > > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a
> chance
> > to
> > > >> > review
> > > >> > >> >>>the
> > > >> > >> >>> >> >>docs
> > > >> > >> >>> >> >> more carefully. I'm really impressed with how well
> > > >>written
> > > >> > they
> > > >> > >> >>>are.
> > > >> > >> >>> >> >>What I
> > > >> > >> >>> >> >> *think* makes the most sense is to consolidate into
> > fewer
> > > >> > >> >>>documents
> > > >> > >> >>> >>so
> > > >> > >> >>> >> >>that
> > > >> > >> >>> >> >> it's not necessary to look at so many seperate
> places.
> > > >> Here's
> > > >> > >> >>>what I
> > > >> > >> >>> >> >> propose:
> > > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
> > > >>alunny/pluginstall
> > > >> > >> >>>README.md
> > > >> > >> >>> >> >> * merge the command line tooling design doc into the
> > > >> > >> >>>cordova-client
> > > >> > >> >>> >> >> README.md
> > > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and
> > merge
> > > >> > parts
> > > >> > >> >>>of it
> > > >> > >> >>> >> >>into
> > > >> > >> >>> >> >> the above 2 docs
> > > >> > >> >>> >> >>
> > > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5, and
> > it
> > > >> still
> > > >> > >> >>> >>maintains
> > > >> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
> > > >>utility
> > > >> > and
> > > >> > >> >>>the
> > > >> > >> >>> >> >>larger
> > > >> > >> >>> >> >> cordova-client. I'm assuming this separation was the
> > > >> original
> > > >> > >> >>>intent,
> > > >> > >> >>> >> >> rather than having one monolithic tool.
> > > >> > >> >>> >> >>
> > > >> > >> >>> >> >> Would love feedback on this, I don't want to waste
> time
> > > >> doing
> > > >> > it
> > > >> > >> >>>and
> > > >> > >> >>> >> >>find
> > > >> > >> >>> >> >> out this isn't appropriate. :)
> > > >> > >> >>> >> >>
> > > >> > >> >>> >> >>
> > > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
> > > >><fi...@adobe.com>
> > > >> > >> wrote:
> > > >> > >> >>> >> >>
> > > >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall
> > does
> > > >>the
> > > >> > >> hard
> > > >> > >> >>> >>work
> > > >> > >> >>> >> >>>for
> > > >> > >> >>> >> >>> programmatic plugin installation, which is just one
> of
> > > >>the
> > > >> > apis
> > > >> > >> >>> >> >>>available
> > > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out"
> to
> > > >> > >> >>>pluginstall.
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >> >>> The client also handles app creation, platform
> > > >> > >> >>>removal/addition, and
> > > >> > >> >>> >> >>> interpolating information from app's config.xml into
> > the
> > > >> > >> >>>necessary
> > > >> > >> >>> >> >>>spots
> > > >> > >> >>> >> >>> in each native project.
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> > > >> > >> reinstein.mike@gmail.com>
> > > >> > >> >>> >> wrote:
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >> >>> >Hey Filip,
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
> > > >>between
> > > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >>>
> > > >> > >>
> > > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >there seems to be some overlap there. Is
> pluginstall
> > a
> > > >> > subset
> > > >> > >> >>>of
> > > >> > >> >>> >> >>> >functionality just related to plugins that has
> moved
> > > >>into
> > > >> > >> >>> >> >>>cordova-client
> > > >> > >> >>> >> >>> >or
> > > >> > >> >>> >> >>> >is it different?
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
> > > >>codebase
> > > >> > that
> > > >> > >> >>> >> >>>incorporates
> > > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
> > > >>finding
> > > >> to
> > > >> > >> >>>see if
> > > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
> > > >>differently,
> > > >> is
> > > >> > >> it
> > > >> > >> >>> >>safe
> > > >> > >> >>> >> >>>to
> > > >> > >> >>> >> >>> >assume that just about all the worthwhile code is
> in
> > > >> > >> >>> >>cordova-client?
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >-Mike
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
> > > >><fil@adobe.com
> > > >> >
> > > >> > >> >>>wrote:
> > > >> > >> >>> >> >>> >
> > > >> > >> >>> >> >>> >> All looks good to me Mike.
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would be
> a
> > > >>great
> > > >> > >> >>>place to
> > > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
> > > >> tackling
> > > >> > >> >>>this!
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> > > >> > >> >>><re...@gmail.com>
> > > >> > >> >>> >> >>>wrote:
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>> >> >Hey Filip, Brian:
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >I think where I'd like to start is on
> > > >>documentation. I
> > > >> > may
> > > >> > >> >>>be
> > > >> > >> >>> >>wrong
> > > >> > >> >>> >> >>> >>about
> > > >> > >> >>> >> >>> >> >this, but it seems like there are bits and
> pieces
> > of
> > > >> docs
> > > >> > >> in
> > > >> > >> >>> >> >>>various
> > > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
> > Maybe a
> > > >> good
> > > >> > >> >>>start
> > > >> > >> >>> >>is
> > > >> > >> >>> >> >>>for
> > > >> > >> >>> >> >>> >>me
> > > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
> > > >>"master"
> > > >> > >> >>>document,
> > > >> > >> >>> >>and
> > > >> > >> >>> >> >>> >>cull
> > > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
> > > >>rephrasing
> > > >> > of
> > > >> > >> >>>the
> > > >> > >> >>> >> >>>various
> > > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take a
> > > >>look
> > > >> and
> > > >> > >> >>>let me
> > > >> > >> >>> >> >>>know
> > > >> > >> >>> >> >>> >>if
> > > >> > >> >>> >> >>> >> >I've characterised the content/purpose of these
> > > >>various
> > > >> > >> >>>links:
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> > > >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >The implementation that manages plugin usage is
> > > >>here:
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>>>
> > > >> > >> >>>
> > > >> >
> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > > >> > >> >>> >> >>> >> >This project encompasses more than just plugins
> > > >>because
> > > >> > it
> > > >> > >> >>>also
> > > >> > >> >>> >> >>>handles
> > > >> > >> >>> >> >>> >> >everything related to building, deploying, and
> > > >>managing
> > > >> > >> >>>cordova
> > > >> > >> >>> >> >>> >> >applications
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >These plugins are most popular, and should
> ideally
> > > >>work
> > > >> > >> >>>with the
> > > >> > >> >>> >> >>> >> >cordova-client implemenation:
> > > >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >This implementation by Drew was an initial proof
> > of
> > > >> > >> concept,
> > > >> > >> >>> >>which
> > > >> > >> >>> >> >>>only
> > > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
> > > >>favor of
> > > >> > >> >>> >> >>>cordova-client,
> > > >> > >> >>> >> >>> >> >with much of his ideas having made it into
> > > >> > cordova-client:
> > > >> > >> >>> >> >>> >> >
> > > >> https://github.com/deedubbu/cordova-blackberry-pluggable
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >This doc contains some info on the format of the
> > > >> command
> > > >> > >> >>>line
> > > >> > >> >>> >> >>>interface
> > > >> > >> >>> >> >>> >> >and
> > > >> > >> >>> >> >>> >> >directory structure of cordova-client:
> > > >> > >> >>> >> >>> >> >
> > > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's
> old
> > > >> > >> >>> >>implementation,
> > > >> > >> >>> >> >>>and
> > > >> > >> >>> >> >>> >>is
> > > >> > >> >>> >> >>> >> >out of date now:
> > > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to get
> a
> > > >> handle
> > > >> > on
> > > >> > >> >>>what
> > > >> > >> >>> >> >>>docs
> > > >> > >> >>> >> >>> >>are
> > > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
> > > >>judging
> > > >> > >> >>>anyone's
> > > >> > >> >>> >> >>>work or
> > > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong
> idea
> > > >>about
> > > >> > >> what
> > > >> > >> >>> >>these
> > > >> > >> >>> >> >>> >>links
> > > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >-Mike
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >*
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> > > >> > fil@adobe.com>
> > > >> > >> >>> >>wrote:
> > > >> > >> >>> >> >>> >> >
> > > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level
> project
> > > >>goes
> > > >> > >> >>> >> >>>hand-in-hand
> > > >> > >> >>> >> >>> >>with
> > > >> > >> >>> >> >>> >> >> this spec. Code here:
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >>
> > > >> > >> >>>
> > > >> > >> >>>
> > > >> > >>
> > > >> >
> > > >>
> > https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> > > >> > >> >>> >> >>>h
> > > >> > >> >>> >> >>> >> >>or
> > > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
> > popular
> > > >> > >> >>>plugins out
> > > >> > >> >>> >> >>>in the
> > > >> > >> >>> >> >>> >> >>wild
> > > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins)
> work
> > > >>with
> > > >> > >> this
> > > >> > >> >>> >>spec.
> > > >> > >> >>> >> >>>Do
> > > >> > >> >>> >> >>> we
> > > >> > >> >>> >> >>> >> >>need
> > > >> > >> >>> >> >>> >> >> to account for anything else?
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >> I think the one outstanding question is how to
> > > >>handle
> > > >> > >> >>> >> >>>installation /
> > > >> > >> >>> >> >>> >> >> compatibility with different versions of
> > cordova.
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the spec
> > > >>(put
> > > >> it
> > > >> > on
> > > >> > >> >>>the
> > > >> > >> >>> >> >>>wiki,
> > > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> > > >> > >> >>> >><re...@gmail.com>
> > > >> > >> >>> >> >>> >>wrote:
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects.
> I'd
> > > >>love
> > > >> to
> > > >> > >> >>>dig in
> > > >> > >> >>> >> >>>and
> > > >> > >> >>> >> >>> >>start
> > > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
> > > >>needed
> > > >> at
> > > >> > >> the
> > > >> > >> >>> >> >>>moment?
> > > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >-Mike
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> > > >> > >> >>><fi...@adobe.com>
> > > >> > >> >>> >> >>>wrote:
> > > >> > >> >>> >> >>> >> >> >
> > > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
> > > >>"spec"
> > > >> we
> > > >> > >> are
> > > >> > >> >>> >> >>>working
> > > >> > >> >>> >> >>> >> >>towards:
> > > >> > >> >>> >> >>> >> >> >>
> > https://github.com/alunny/cordova-plugin-spec
> > > >> > >> >>> >> >>> >> >> >>
> > > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
> > b@brian.io>
> > > >> > wrote:
> > > >> > >> >>> >> >>> >> >> >>
> > > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
> > > >> Currently
> > > >> > >> the
> > > >> > >> >>> >>plugin
> > > >> > >> >>> >> >>> >> >>tooling
> > > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil,
> Michael,
> > > >>and
> > > >> > >> >>>myself.
> > > >> > >> >>> >> >>>(sorry
> > > >> > >> >>> >> >>> >>for
> > > >> > >> >>> >> >>> >> >>the
> > > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
> > summer
> > > >> break
> > > >> > >> >>>after
> > > >> > >> >>> >> >>> >>shipping
> > > >> > >> >>> >> >>> >> >> >> >2.0)
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this
> list,
> > > >>git,
> > > >> > and
> > > >> > >> >>> >>these
> > > >> > >> >>> >> >>>wiki
> > > >> > >> >>> >> >>> >> >>pages:
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >-
> > http://wiki.apache.org/cordova/PluginDesign
> > > >> > >> >>> >> >>> >> >> >> >-
> > > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
> > branch
> > > >> which
> > > >> > >> >>>you
> > > >> > >> >>> >>can
> > > >> > >> >>> >> >>> >>preview
> > > >> > >> >>> >> >>> >> >>on
> > > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >>
> > > >> > >>
> > > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on
> our
> > > >> contrib
> > > >> > >> >>> >>process
> > > >> > >> >>> >> >>>in
> > > >> > >> >>> >> >>> >>the
> > > >> > >> >>> >> >>> >> >> >>wiki:
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> http://wiki.apache.org/cordova/ContributerWorkflow
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects
> everything
> > > >>stays
> > > >> > on
> > > >> > >> >>>its
> > > >> > >> >>> >>own
> > > >> > >> >>> >> >>> >>branch
> > > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid
> for
> > > >>its
> > > >> > own
> > > >> > >> >>>repo.
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >* * *
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >
> > > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
> > > >>Reinstein
> > > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> > > >> > >> >>> >> >>> >> >> >> >> Hey there,
> > > >> > >> >>> >> >>> >> >> >> >>
> > > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the
> > plugin
> > > >> > system
> > > >> > >> >>> >>that is
> > > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> > > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who
> > are
> > > >> the
> > > >> > >> >>>right
> > > >> > >> >>> >> >>>people
> > > >> > >> >>> >> >>> >>to
> > > >> > >> >>> >> >>> >> >>talk
> > > >> > >> >>> >> >>> >> >> >> >>to?
> > > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> > > >> > experienced
> > > >> > >> >>> >> >>>developer,
> > > >> > >> >>> >> >>> >> >>have
> > > >> > >> >>> >> >>> >> >> >> >>worked
> > > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and
> > would
> > > >> love
> > > >> > to
> > > >> > >> >>>give
> > > >> > >> >>> >> >>>back
> > > >> > >> >>> >> >>> >>to
> > > >> > >> >>> >> >>> >> >>the
> > > >> > >> >>> >> >>> >> >> >> >> community.
> > > >> > >> >>> >> >>> >> >> >> >>
> > > >> > >> >>> >> >>> >> >> >> >> cheers,
> > > >> > >> >>> >> >>> >> >> >> >>
> > > >> > >> >>> >> >>> >> >> >> >> -Mike
> > > >> > >> >>> >> >>> >> >> >>
> > > >> > >> >>> >> >>> >> >> >>
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >> >>
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>> >>
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >> >>>
> > > >> > >> >>> >>
> > > >> > >> >>> >>
> > > >> > >> >>>
> > > >> > >> >>>
> > > >> > >>
> > > >> > >>
> > > >> > >
> > > >> >
> > > >>
> > >
> > >
> >
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Mailing list! We forked and committed for the simple stuff (deeper
explanations and merging documentation), but if you have discussion +
design points, ML is the place to do it.
On 9/10/12 11:31 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>I'm just reading along and would like to make some comments here and
>there.
> However, it seems pretty inefficient to branch the project just to mark
>my
>comments and email may be confusing.
>
>Usually I've just used Google Docs to mark comments inline for stuff like
>this but perhaps that suggestion won't fly well. Does github not have a
>feature for this (commenting on a file, starting a wiki, etc?)
>
>Any suggestions/opinions?
>
>
>On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein
><re...@gmail.com>wrote:
>
>> Looks good to me. What are the next steps? One thing I'd like to see
>>happen
>> is getting rid of some of those repos and documentation pages that are
>> redundant.
>>
>> -Mike
>>
>> On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>> > Nice!
>> >
>> > I worked out some of your quotes/questions and put it up on my branch
>>on
>> > github: https://github.com/filmaj/cordova-client/tree/einstein
>> >
>> > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
>> >
>> > >Hey folks,
>> > >
>> > >Hope you all had a nice weekend. I have a preliminary draft ready
>>that
>> > >merges cordova-client and command line tooling design into 1
>>document:
>> > >
>> > >
>> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>> > >
>> > >Any feedback would be greatly appreciated. Thanks!
>> > >
>> > >-Mike
>> > >
>> > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com>
>> wrote:
>> > >
>> > >> Hi Mike,
>> > >>
>> > >> pluginstall-with-git support is just an experiment that I did a
>>while
>> > >>back
>> > >> (it takes git URLs as well as local paths). I suggest you base your
>> > >>work on
>> > >> alunny's pluginstall until/if those changes get merged.
>> > >>
>> > >> Cheers
>> > >>
>> > >> Anis
>> > >>
>> > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
>> > reinstein.mike@gmail.com
>> > >> >wrote:
>> > >>
>> > >> > I see 2 repositories for pluginstall:
>> > >> >
>> > >> >
>> > >> >
>> > >>
>> > >>
>> >
>>
>>https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
>> > >>t-support
>> > >> >
>> > >> > and Andrew's:
>> > >> > https://github.com/alunny/pluginstall
>> > >> >
>> > >> > When consolidating the pluginstall and plugin format docs I
>>forked
>> > >> Andrew's
>> > >> > repo. Should I instead have used the pluginstall-with-git-support
>> > >>repo as
>> > >> > my base?
>> > >> >
>> > >> > -Mike
>> > >> >
>> > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
>> > >><reinstein.mike@gmail.com
>> > >> > >wrote:
>> > >> >
>> > >> > > My username is nekoflux.
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com>
>>wrote:
>> > >> > >
>> > >> > >> JIRA is separate, we can assign issues to you (if you so
>>wish).
>> > >> > >>
>> > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>> > >> > >>
>> > >> > >> >Registration is open - let us know what your user account is
>> once
>> > >>you
>> > >> > >> >do that, for assigning issues to yourself you need us to add
>>you
>> > >>to a
>> > >> > >> >contributors group.
>> > >> > >> >
>> > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
>> > >> > reinstein.mike@gmail.com
>> > >> > >> >
>> > >> > >> >wrote:
>> > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
>> proceed
>> > >> with
>> > >> > >> >> merging the cordova-client and command line tooling spec
>> next. I
>> > >> > >> >>suppose it
>> > >> > >> >> probably makes sense for me to start working out of JIRA so
>> > >>these
>> > >> > tasks
>> > >> > >> >>can
>> > >> > >> >> be tracked. Is registration open or do I need to get
>> permission
>> > >> from
>> > >> > an
>> > >> > >> >> admin for an account?
>> > >> > >> >>
>> > >> > >> >>
>> > >> > >> >>
>> > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
>> > wrote:
>> > >> > >> >>
>> > >> > >> >>> Sorry for the late reply, this looks awesome!
>> > >> > >> >>>
>> > >> > >> >>> The one modification I would do is remove "www" as a
>>platform
>> > >>(you
>> > >> > >> >>>have a
>> > >> > >> >>> comment in there about that too).
>> > >> > >> >>>
>> > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
>> reinstein.mike@gmail.com>
>> > >> > wrote:
>> > >> > >> >>>
>> > >> > >> >>> >> eventually we will move pluginstall into apache
>> > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with
>>the
>> > >> > slightly
>> > >> > >> >>>more
>> > >> > >> >>> >conservative assumption, that pluginstall might live
>> > >>separately
>> > >> > from
>> > >> > >> >>> >cordova-client. But I get the impression this is a
>>left-over
>> > >> notion
>> > >> > >> >>>from
>> > >> > >> >>> >when Andrew first built pluginstall and it wasn't clear
>>then
>> > >> > whether
>> > >> > >> >>>or
>> > >> > >> >>> >not
>> > >> > >> >>> >it would take hold.
>> > >> > >> >>> >
>> > >> > >> >>> >I've got an initial version of the merged documentation
>>for
>> > >>the
>> > >> > >> >>> >pluginstall
>> > >> > >> >>> >command line tool, and the specification doc. It's here
>> > >> > >> >>> >https://github.com/mreinstein/pluginstall
>> > >> > >> >>> >
>> > >> > >> >>> >I've also added some comments on possible changes.
>>Overall
>> the
>> > >> doc
>> > >> > is
>> > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
>> > >>appreciate
>> > >> > >> >>> >constructive feedback on this. If it looks right I'll
>>send a
>> > >>pull
>> > >> > >> >>>request
>> > >> > >> >>> >to alunny, and then proceed with merging cordova-client
>> design
>> > >> doc
>> > >> > >> >>>into
>> > >> > >> >>> >the
>> > >> > >> >>> >README on github.
>> > >> > >> >>> >
>> > >> > >> >>> >-Mike
>> > >> > >> >>> >
>> > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com>
>> > >>wrote:
>> > >> > >> >>> >
>> > >> > >> >>> >> +1 !
>> > >> > >> >>> >>
>> > >> > >> >>> >> (I THINK) eventually we will move pluginstall into
>>apache
>> > >> > (assuming
>> > >> > >> >>>the
>> > >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1
>>doc.
>> > >> > >> >>> >>
>> > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> > >> > >> >>> >>
>> > >> > >> >>> >> >love it
>> > >> > >> >>> >> >
>> > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>> > >> > >> >>> >><re...@gmail.com>
>> > >> > >> >>> >> >wrote:
>> > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a
>>chance
>> to
>> > >> > review
>> > >> > >> >>>the
>> > >> > >> >>> >> >>docs
>> > >> > >> >>> >> >> more carefully. I'm really impressed with how well
>> > >>written
>> > >> > they
>> > >> > >> >>>are.
>> > >> > >> >>> >> >>What I
>> > >> > >> >>> >> >> *think* makes the most sense is to consolidate into
>> fewer
>> > >> > >> >>>documents
>> > >> > >> >>> >>so
>> > >> > >> >>> >> >>that
>> > >> > >> >>> >> >> it's not necessary to look at so many seperate
>>places.
>> > >> Here's
>> > >> > >> >>>what I
>> > >> > >> >>> >> >> propose:
>> > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
>> > >>alunny/pluginstall
>> > >> > >> >>>README.md
>> > >> > >> >>> >> >> * merge the command line tooling design doc into the
>> > >> > >> >>>cordova-client
>> > >> > >> >>> >> >> README.md
>> > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and
>> merge
>> > >> > parts
>> > >> > >> >>>of it
>> > >> > >> >>> >> >>into
>> > >> > >> >>> >> >> the above 2 docs
>> > >> > >> >>> >> >>
>> > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5,
>>and
>> it
>> > >> still
>> > >> > >> >>> >>maintains
>> > >> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
>> > >>utility
>> > >> > and
>> > >> > >> >>>the
>> > >> > >> >>> >> >>larger
>> > >> > >> >>> >> >> cordova-client. I'm assuming this separation was the
>> > >> original
>> > >> > >> >>>intent,
>> > >> > >> >>> >> >> rather than having one monolithic tool.
>> > >> > >> >>> >> >>
>> > >> > >> >>> >> >> Would love feedback on this, I don't want to waste
>>time
>> > >> doing
>> > >> > it
>> > >> > >> >>>and
>> > >> > >> >>> >> >>find
>> > >> > >> >>> >> >> out this isn't appropriate. :)
>> > >> > >> >>> >> >>
>> > >> > >> >>> >> >>
>> > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
>> > >><fi...@adobe.com>
>> > >> > >> wrote:
>> > >> > >> >>> >> >>
>> > >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall
>> does
>> > >>the
>> > >> > >> hard
>> > >> > >> >>> >>work
>> > >> > >> >>> >> >>>for
>> > >> > >> >>> >> >>> programmatic plugin installation, which is just
>>one of
>> > >>the
>> > >> > apis
>> > >> > >> >>> >> >>>available
>> > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out"
>>to
>> > >> > >> >>>pluginstall.
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >> >>> The client also handles app creation, platform
>> > >> > >> >>>removal/addition, and
>> > >> > >> >>> >> >>> interpolating information from app's config.xml
>>into
>> the
>> > >> > >> >>>necessary
>> > >> > >> >>> >> >>>spots
>> > >> > >> >>> >> >>> in each native project.
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
>> > >> > >> reinstein.mike@gmail.com>
>> > >> > >> >>> >> wrote:
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >> >>> >Hey Filip,
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
>> > >>between
>> > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >>>
>> > >> > >>
>> > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >there seems to be some overlap there. Is
>>pluginstall
>> a
>> > >> > subset
>> > >> > >> >>>of
>> > >> > >> >>> >> >>> >functionality just related to plugins that has
>>moved
>> > >>into
>> > >> > >> >>> >> >>>cordova-client
>> > >> > >> >>> >> >>> >or
>> > >> > >> >>> >> >>> >is it different?
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
>> > >>codebase
>> > >> > that
>> > >> > >> >>> >> >>>incorporates
>> > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
>> > >>finding
>> > >> to
>> > >> > >> >>>see if
>> > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
>> > >>differently,
>> > >> is
>> > >> > >> it
>> > >> > >> >>> >>safe
>> > >> > >> >>> >> >>>to
>> > >> > >> >>> >> >>> >assume that just about all the worthwhile code is
>>in
>> > >> > >> >>> >>cordova-client?
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >-Mike
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
>> > >><fil@adobe.com
>> > >> >
>> > >> > >> >>>wrote:
>> > >> > >> >>> >> >>> >
>> > >> > >> >>> >> >>> >> All looks good to me Mike.
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would
>>be a
>> > >>great
>> > >> > >> >>>place to
>> > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
>> > >> tackling
>> > >> > >> >>>this!
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
>> > >> > >> >>><re...@gmail.com>
>> > >> > >> >>> >> >>>wrote:
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>> >> >Hey Filip, Brian:
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >I think where I'd like to start is on
>> > >>documentation. I
>> > >> > may
>> > >> > >> >>>be
>> > >> > >> >>> >>wrong
>> > >> > >> >>> >> >>> >>about
>> > >> > >> >>> >> >>> >> >this, but it seems like there are bits and
>>pieces
>> of
>> > >> docs
>> > >> > >> in
>> > >> > >> >>> >> >>>various
>> > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
>> Maybe a
>> > >> good
>> > >> > >> >>>start
>> > >> > >> >>> >>is
>> > >> > >> >>> >> >>>for
>> > >> > >> >>> >> >>> >>me
>> > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
>> > >>"master"
>> > >> > >> >>>document,
>> > >> > >> >>> >>and
>> > >> > >> >>> >> >>> >>cull
>> > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
>> > >>rephrasing
>> > >> > of
>> > >> > >> >>>the
>> > >> > >> >>> >> >>>various
>> > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take
>>a
>> > >>look
>> > >> and
>> > >> > >> >>>let me
>> > >> > >> >>> >> >>>know
>> > >> > >> >>> >> >>> >>if
>> > >> > >> >>> >> >>> >> >I've characterised the content/purpose of these
>> > >>various
>> > >> > >> >>>links:
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
>> > >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >The implementation that manages plugin usage is
>> > >>here:
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>>>
>> > >> > >> >>>
>> > >> >
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> > >> >>> >> >>> >> >This project encompasses more than just plugins
>> > >>because
>> > >> > it
>> > >> > >> >>>also
>> > >> > >> >>> >> >>>handles
>> > >> > >> >>> >> >>> >> >everything related to building, deploying, and
>> > >>managing
>> > >> > >> >>>cordova
>> > >> > >> >>> >> >>> >> >applications
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >These plugins are most popular, and should
>>ideally
>> > >>work
>> > >> > >> >>>with the
>> > >> > >> >>> >> >>> >> >cordova-client implemenation:
>> > >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >This implementation by Drew was an initial
>>proof
>> of
>> > >> > >> concept,
>> > >> > >> >>> >>which
>> > >> > >> >>> >> >>>only
>> > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
>> > >>favor of
>> > >> > >> >>> >> >>>cordova-client,
>> > >> > >> >>> >> >>> >> >with much of his ideas having made it into
>> > >> > cordova-client:
>> > >> > >> >>> >> >>> >> >
>> > >> https://github.com/deedubbu/cordova-blackberry-pluggable
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >This doc contains some info on the format of
>>the
>> > >> command
>> > >> > >> >>>line
>> > >> > >> >>> >> >>>interface
>> > >> > >> >>> >> >>> >> >and
>> > >> > >> >>> >> >>> >> >directory structure of cordova-client:
>> > >> > >> >>> >> >>> >> >
>> > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's
>>old
>> > >> > >> >>> >>implementation,
>> > >> > >> >>> >> >>>and
>> > >> > >> >>> >> >>> >>is
>> > >> > >> >>> >> >>> >> >out of date now:
>> > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to
>>get a
>> > >> handle
>> > >> > on
>> > >> > >> >>>what
>> > >> > >> >>> >> >>>docs
>> > >> > >> >>> >> >>> >>are
>> > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
>> > >>judging
>> > >> > >> >>>anyone's
>> > >> > >> >>> >> >>>work or
>> > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong
>>idea
>> > >>about
>> > >> > >> what
>> > >> > >> >>> >>these
>> > >> > >> >>> >> >>> >>links
>> > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >-Mike
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >*
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
>> > >> > fil@adobe.com>
>> > >> > >> >>> >>wrote:
>> > >> > >> >>> >> >>> >> >
>> > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level
>>project
>> > >>goes
>> > >> > >> >>> >> >>>hand-in-hand
>> > >> > >> >>> >> >>> >>with
>> > >> > >> >>> >> >>> >> >> this spec. Code here:
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >>
>> > >> > >> >>>
>> > >> > >> >>>
>> > >> > >>
>> > >> >
>> > >>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> > >> > >> >>> >> >>>h
>> > >> > >> >>> >> >>> >> >>or
>> > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
>> popular
>> > >> > >> >>>plugins out
>> > >> > >> >>> >> >>>in the
>> > >> > >> >>> >> >>> >> >>wild
>> > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins)
>>work
>> > >>with
>> > >> > >> this
>> > >> > >> >>> >>spec.
>> > >> > >> >>> >> >>>Do
>> > >> > >> >>> >> >>> we
>> > >> > >> >>> >> >>> >> >>need
>> > >> > >> >>> >> >>> >> >> to account for anything else?
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >> I think the one outstanding question is how
>>to
>> > >>handle
>> > >> > >> >>> >> >>>installation /
>> > >> > >> >>> >> >>> >> >> compatibility with different versions of
>> cordova.
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the
>>spec
>> > >>(put
>> > >> it
>> > >> > on
>> > >> > >> >>>the
>> > >> > >> >>> >> >>>wiki,
>> > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>> > >> > >> >>> >><re...@gmail.com>
>> > >> > >> >>> >> >>> >>wrote:
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects.
>>I'd
>> > >>love
>> > >> to
>> > >> > >> >>>dig in
>> > >> > >> >>> >> >>>and
>> > >> > >> >>> >> >>> >>start
>> > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
>> > >>needed
>> > >> at
>> > >> > >> the
>> > >> > >> >>> >> >>>moment?
>> > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >-Mike
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
>> > >> > >> >>><fi...@adobe.com>
>> > >> > >> >>> >> >>>wrote:
>> > >> > >> >>> >> >>> >> >> >
>> > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
>> > >>"spec"
>> > >> we
>> > >> > >> are
>> > >> > >> >>> >> >>>working
>> > >> > >> >>> >> >>> >> >>towards:
>> > >> > >> >>> >> >>> >> >> >>
>> https://github.com/alunny/cordova-plugin-spec
>> > >> > >> >>> >> >>> >> >> >>
>> > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
>> b@brian.io>
>> > >> > wrote:
>> > >> > >> >>> >> >>> >> >> >>
>> > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
>> > >> Currently
>> > >> > >> the
>> > >> > >> >>> >>plugin
>> > >> > >> >>> >> >>> >> >>tooling
>> > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil,
>>Michael,
>> > >>and
>> > >> > >> >>>myself.
>> > >> > >> >>> >> >>>(sorry
>> > >> > >> >>> >> >>> >>for
>> > >> > >> >>> >> >>> >> >>the
>> > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
>> summer
>> > >> break
>> > >> > >> >>>after
>> > >> > >> >>> >> >>> >>shipping
>> > >> > >> >>> >> >>> >> >> >> >2.0)
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this
>>list,
>> > >>git,
>> > >> > and
>> > >> > >> >>> >>these
>> > >> > >> >>> >> >>>wiki
>> > >> > >> >>> >> >>> >> >>pages:
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >-
>> http://wiki.apache.org/cordova/PluginDesign
>> > >> > >> >>> >> >>> >> >> >> >-
>> > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
>> branch
>> > >> which
>> > >> > >> >>>you
>> > >> > >> >>> >>can
>> > >> > >> >>> >> >>> >>preview
>> > >> > >> >>> >> >>> >> >>on
>> > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >>
>> > >> > >>
>> > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on
>>our
>> > >> contrib
>> > >> > >> >>> >>process
>> > >> > >> >>> >> >>>in
>> > >> > >> >>> >> >>> >>the
>> > >> > >> >>> >> >>> >> >> >>wiki:
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> http://wiki.apache.org/cordova/ContributerWorkflow
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects
>>everything
>> > >>stays
>> > >> > on
>> > >> > >> >>>its
>> > >> > >> >>> >>own
>> > >> > >> >>> >> >>> >>branch
>> > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid
>>for
>> > >>its
>> > >> > own
>> > >> > >> >>>repo.
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >* * *
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >
>> > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
>> > >>Reinstein
>> > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>> > >> > >> >>> >> >>> >> >> >> >> Hey there,
>> > >> > >> >>> >> >>> >> >> >> >>
>> > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the
>> plugin
>> > >> > system
>> > >> > >> >>> >>that is
>> > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
>> > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up?
>>Who
>> are
>> > >> the
>> > >> > >> >>>right
>> > >> > >> >>> >> >>>people
>> > >> > >> >>> >> >>> >>to
>> > >> > >> >>> >> >>> >> >>talk
>> > >> > >> >>> >> >>> >> >> >> >>to?
>> > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
>> > >> > experienced
>> > >> > >> >>> >> >>>developer,
>> > >> > >> >>> >> >>> >> >>have
>> > >> > >> >>> >> >>> >> >> >> >>worked
>> > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and
>> would
>> > >> love
>> > >> > to
>> > >> > >> >>>give
>> > >> > >> >>> >> >>>back
>> > >> > >> >>> >> >>> >>to
>> > >> > >> >>> >> >>> >> >>the
>> > >> > >> >>> >> >>> >> >> >> >> community.
>> > >> > >> >>> >> >>> >> >> >> >>
>> > >> > >> >>> >> >>> >> >> >> >> cheers,
>> > >> > >> >>> >> >>> >> >> >> >>
>> > >> > >> >>> >> >>> >> >> >> >> -Mike
>> > >> > >> >>> >> >>> >> >> >>
>> > >> > >> >>> >> >>> >> >> >>
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >> >>
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>> >>
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >> >>>
>> > >> > >> >>> >>
>> > >> > >> >>> >>
>> > >> > >> >>>
>> > >> > >> >>>
>> > >> > >>
>> > >> > >>
>> > >> > >
>> > >> >
>> > >>
>> >
>> >
>>
Re: plugin tooling/specification
Posted by Michal Mocny <mm...@chromium.org>.
I'm just reading along and would like to make some comments here and there.
However, it seems pretty inefficient to branch the project just to mark my
comments and email may be confusing.
Usually I've just used Google Docs to mark comments inline for stuff like
this but perhaps that suggestion won't fly well. Does github not have a
feature for this (commenting on a file, starting a wiki, etc?)
Any suggestions/opinions?
On Mon, Sep 10, 2012 at 2:25 PM, Mike Reinstein <re...@gmail.com>wrote:
> Looks good to me. What are the next steps? One thing I'd like to see happen
> is getting rid of some of those repos and documentation pages that are
> redundant.
>
> -Mike
>
> On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
>
> > Nice!
> >
> > I worked out some of your quotes/questions and put it up on my branch on
> > github: https://github.com/filmaj/cordova-client/tree/einstein
> >
> > On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
> >
> > >Hey folks,
> > >
> > >Hope you all had a nice weekend. I have a preliminary draft ready that
> > >merges cordova-client and command line tooling design into 1 document:
> > >
> > >
> https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> > >
> > >Any feedback would be greatly appreciated. Thanks!
> > >
> > >-Mike
> > >
> > >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com>
> wrote:
> > >
> > >> Hi Mike,
> > >>
> > >> pluginstall-with-git support is just an experiment that I did a while
> > >>back
> > >> (it takes git URLs as well as local paths). I suggest you base your
> > >>work on
> > >> alunny's pluginstall until/if those changes get merged.
> > >>
> > >> Cheers
> > >>
> > >> Anis
> > >>
> > >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
> > reinstein.mike@gmail.com
> > >> >wrote:
> > >>
> > >> > I see 2 repositories for pluginstall:
> > >> >
> > >> >
> > >> >
> > >>
> > >>
> >
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
> > >>t-support
> > >> >
> > >> > and Andrew's:
> > >> > https://github.com/alunny/pluginstall
> > >> >
> > >> > When consolidating the pluginstall and plugin format docs I forked
> > >> Andrew's
> > >> > repo. Should I instead have used the pluginstall-with-git-support
> > >>repo as
> > >> > my base?
> > >> >
> > >> > -Mike
> > >> >
> > >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
> > >><reinstein.mike@gmail.com
> > >> > >wrote:
> > >> >
> > >> > > My username is nekoflux.
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
> > >> > >
> > >> > >> JIRA is separate, we can assign issues to you (if you so wish).
> > >> > >>
> > >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> > >> > >>
> > >> > >> >Registration is open - let us know what your user account is
> once
> > >>you
> > >> > >> >do that, for assigning issues to yourself you need us to add you
> > >>to a
> > >> > >> >contributors group.
> > >> > >> >
> > >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> > >> > reinstein.mike@gmail.com
> > >> > >> >
> > >> > >> >wrote:
> > >> > >> >> Okay, will do. Any feedback on the other comments? I'll
> proceed
> > >> with
> > >> > >> >> merging the cordova-client and command line tooling spec
> next. I
> > >> > >> >>suppose it
> > >> > >> >> probably makes sense for me to start working out of JIRA so
> > >>these
> > >> > tasks
> > >> > >> >>can
> > >> > >> >> be tracked. Is registration open or do I need to get
> permission
> > >> from
> > >> > an
> > >> > >> >> admin for an account?
> > >> > >> >>
> > >> > >> >>
> > >> > >> >>
> > >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
> > wrote:
> > >> > >> >>
> > >> > >> >>> Sorry for the late reply, this looks awesome!
> > >> > >> >>>
> > >> > >> >>> The one modification I would do is remove "www" as a platform
> > >>(you
> > >> > >> >>>have a
> > >> > >> >>> comment in there about that too).
> > >> > >> >>>
> > >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <
> reinstein.mike@gmail.com>
> > >> > wrote:
> > >> > >> >>>
> > >> > >> >>> >> eventually we will move pluginstall into apache
> > >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with the
> > >> > slightly
> > >> > >> >>>more
> > >> > >> >>> >conservative assumption, that pluginstall might live
> > >>separately
> > >> > from
> > >> > >> >>> >cordova-client. But I get the impression this is a left-over
> > >> notion
> > >> > >> >>>from
> > >> > >> >>> >when Andrew first built pluginstall and it wasn't clear then
> > >> > whether
> > >> > >> >>>or
> > >> > >> >>> >not
> > >> > >> >>> >it would take hold.
> > >> > >> >>> >
> > >> > >> >>> >I've got an initial version of the merged documentation for
> > >>the
> > >> > >> >>> >pluginstall
> > >> > >> >>> >command line tool, and the specification doc. It's here
> > >> > >> >>> >https://github.com/mreinstein/pluginstall
> > >> > >> >>> >
> > >> > >> >>> >I've also added some comments on possible changes. Overall
> the
> > >> doc
> > >> > is
> > >> > >> >>> >pretty tight, so it's largely unchanged. Would really
> > >>appreciate
> > >> > >> >>> >constructive feedback on this. If it looks right I'll send a
> > >>pull
> > >> > >> >>>request
> > >> > >> >>> >to alunny, and then proceed with merging cordova-client
> design
> > >> doc
> > >> > >> >>>into
> > >> > >> >>> >the
> > >> > >> >>> >README on github.
> > >> > >> >>> >
> > >> > >> >>> >-Mike
> > >> > >> >>> >
> > >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com>
> > >>wrote:
> > >> > >> >>> >
> > >> > >> >>> >> +1 !
> > >> > >> >>> >>
> > >> > >> >>> >> (I THINK) eventually we will move pluginstall into apache
> > >> > (assuming
> > >> > >> >>>the
> > >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> > >> > >> >>> >>
> > >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> > >> > >> >>> >>
> > >> > >> >>> >> >love it
> > >> > >> >>> >> >
> > >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> > >> > >> >>> >><re...@gmail.com>
> > >> > >> >>> >> >wrote:
> > >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a chance
> to
> > >> > review
> > >> > >> >>>the
> > >> > >> >>> >> >>docs
> > >> > >> >>> >> >> more carefully. I'm really impressed with how well
> > >>written
> > >> > they
> > >> > >> >>>are.
> > >> > >> >>> >> >>What I
> > >> > >> >>> >> >> *think* makes the most sense is to consolidate into
> fewer
> > >> > >> >>>documents
> > >> > >> >>> >>so
> > >> > >> >>> >> >>that
> > >> > >> >>> >> >> it's not necessary to look at so many seperate places.
> > >> Here's
> > >> > >> >>>what I
> > >> > >> >>> >> >> propose:
> > >> > >> >>> >> >> * merge the cordova-plugin-spec into the
> > >>alunny/pluginstall
> > >> > >> >>>README.md
> > >> > >> >>> >> >> * merge the command line tooling design doc into the
> > >> > >> >>>cordova-client
> > >> > >> >>> >> >> README.md
> > >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and
> merge
> > >> > parts
> > >> > >> >>>of it
> > >> > >> >>> >> >>into
> > >> > >> >>> >> >> the above 2 docs
> > >> > >> >>> >> >>
> > >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5, and
> it
> > >> still
> > >> > >> >>> >>maintains
> > >> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
> > >>utility
> > >> > and
> > >> > >> >>>the
> > >> > >> >>> >> >>larger
> > >> > >> >>> >> >> cordova-client. I'm assuming this separation was the
> > >> original
> > >> > >> >>>intent,
> > >> > >> >>> >> >> rather than having one monolithic tool.
> > >> > >> >>> >> >>
> > >> > >> >>> >> >> Would love feedback on this, I don't want to waste time
> > >> doing
> > >> > it
> > >> > >> >>>and
> > >> > >> >>> >> >>find
> > >> > >> >>> >> >> out this isn't appropriate. :)
> > >> > >> >>> >> >>
> > >> > >> >>> >> >>
> > >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
> > >><fi...@adobe.com>
> > >> > >> wrote:
> > >> > >> >>> >> >>
> > >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall
> does
> > >>the
> > >> > >> hard
> > >> > >> >>> >>work
> > >> > >> >>> >> >>>for
> > >> > >> >>> >> >>> programmatic plugin installation, which is just one of
> > >>the
> > >> > apis
> > >> > >> >>> >> >>>available
> > >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
> > >> > >> >>>pluginstall.
> > >> > >> >>> >> >>>
> > >> > >> >>> >> >>> The client also handles app creation, platform
> > >> > >> >>>removal/addition, and
> > >> > >> >>> >> >>> interpolating information from app's config.xml into
> the
> > >> > >> >>>necessary
> > >> > >> >>> >> >>>spots
> > >> > >> >>> >> >>> in each native project.
> > >> > >> >>> >> >>>
> > >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> > >> > >> reinstein.mike@gmail.com>
> > >> > >> >>> >> wrote:
> > >> > >> >>> >> >>>
> > >> > >> >>> >> >>> >Hey Filip,
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
> > >>between
> > >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> > >> > >> >>> >> >>>
> > >> > >> >>> >>>
> > >> > >>
> > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >there seems to be some overlap there. Is pluginstall
> a
> > >> > subset
> > >> > >> >>>of
> > >> > >> >>> >> >>> >functionality just related to plugins that has moved
> > >>into
> > >> > >> >>> >> >>>cordova-client
> > >> > >> >>> >> >>> >or
> > >> > >> >>> >> >>> >is it different?
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >It seems like cordova-client is the most mature
> > >>codebase
> > >> > that
> > >> > >> >>> >> >>>incorporates
> > >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
> > >>finding
> > >> to
> > >> > >> >>>see if
> > >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
> > >>differently,
> > >> is
> > >> > >> it
> > >> > >> >>> >>safe
> > >> > >> >>> >> >>>to
> > >> > >> >>> >> >>> >assume that just about all the worthwhile code is in
> > >> > >> >>> >>cordova-client?
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >-Mike
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
> > >><fil@adobe.com
> > >> >
> > >> > >> >>>wrote:
> > >> > >> >>> >> >>> >
> > >> > >> >>> >> >>> >> All looks good to me Mike.
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would be a
> > >>great
> > >> > >> >>>place to
> > >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
> > >> tackling
> > >> > >> >>>this!
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> > >> > >> >>><re...@gmail.com>
> > >> > >> >>> >> >>>wrote:
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>> >> >Hey Filip, Brian:
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >I think where I'd like to start is on
> > >>documentation. I
> > >> > may
> > >> > >> >>>be
> > >> > >> >>> >>wrong
> > >> > >> >>> >> >>> >>about
> > >> > >> >>> >> >>> >> >this, but it seems like there are bits and pieces
> of
> > >> docs
> > >> > >> in
> > >> > >> >>> >> >>>various
> > >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant.
> Maybe a
> > >> good
> > >> > >> >>>start
> > >> > >> >>> >>is
> > >> > >> >>> >> >>>for
> > >> > >> >>> >> >>> >>me
> > >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
> > >>"master"
> > >> > >> >>>document,
> > >> > >> >>> >>and
> > >> > >> >>> >> >>> >>cull
> > >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
> > >>rephrasing
> > >> > of
> > >> > >> >>>the
> > >> > >> >>> >> >>>various
> > >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take a
> > >>look
> > >> and
> > >> > >> >>>let me
> > >> > >> >>> >> >>>know
> > >> > >> >>> >> >>> >>if
> > >> > >> >>> >> >>> >> >I've characterised the content/purpose of these
> > >>various
> > >> > >> >>>links:
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> > >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >The implementation that manages plugin usage is
> > >>here:
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>>>
> > >> > >> >>>
> > >> >
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> > >> >>> >> >>> >> >This project encompasses more than just plugins
> > >>because
> > >> > it
> > >> > >> >>>also
> > >> > >> >>> >> >>>handles
> > >> > >> >>> >> >>> >> >everything related to building, deploying, and
> > >>managing
> > >> > >> >>>cordova
> > >> > >> >>> >> >>> >> >applications
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >These plugins are most popular, and should ideally
> > >>work
> > >> > >> >>>with the
> > >> > >> >>> >> >>> >> >cordova-client implemenation:
> > >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >This implementation by Drew was an initial proof
> of
> > >> > >> concept,
> > >> > >> >>> >>which
> > >> > >> >>> >> >>>only
> > >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
> > >>favor of
> > >> > >> >>> >> >>>cordova-client,
> > >> > >> >>> >> >>> >> >with much of his ideas having made it into
> > >> > cordova-client:
> > >> > >> >>> >> >>> >> >
> > >> https://github.com/deedubbu/cordova-blackberry-pluggable
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >This doc contains some info on the format of the
> > >> command
> > >> > >> >>>line
> > >> > >> >>> >> >>>interface
> > >> > >> >>> >> >>> >> >and
> > >> > >> >>> >> >>> >> >directory structure of cordova-client:
> > >> > >> >>> >> >>> >> >
> > >> http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's old
> > >> > >> >>> >>implementation,
> > >> > >> >>> >> >>>and
> > >> > >> >>> >> >>> >>is
> > >> > >> >>> >> >>> >> >out of date now:
> > >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to get a
> > >> handle
> > >> > on
> > >> > >> >>>what
> > >> > >> >>> >> >>>docs
> > >> > >> >>> >> >>> >>are
> > >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
> > >>judging
> > >> > >> >>>anyone's
> > >> > >> >>> >> >>>work or
> > >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong idea
> > >>about
> > >> > >> what
> > >> > >> >>> >>these
> > >> > >> >>> >> >>> >>links
> > >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >-Mike
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >*
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> > >> > fil@adobe.com>
> > >> > >> >>> >>wrote:
> > >> > >> >>> >> >>> >> >
> > >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level project
> > >>goes
> > >> > >> >>> >> >>>hand-in-hand
> > >> > >> >>> >> >>> >>with
> > >> > >> >>> >> >>> >> >> this spec. Code here:
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>>
> > >> > >> >>> >> >>>
> > >> > >> >>> >>
> > >> > >> >>>
> > >> > >> >>>
> > >> > >>
> > >> >
> > >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> > >> > >> >>> >> >>>h
> > >> > >> >>> >> >>> >> >>or
> > >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure
> popular
> > >> > >> >>>plugins out
> > >> > >> >>> >> >>>in the
> > >> > >> >>> >> >>> >> >>wild
> > >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work
> > >>with
> > >> > >> this
> > >> > >> >>> >>spec.
> > >> > >> >>> >> >>>Do
> > >> > >> >>> >> >>> we
> > >> > >> >>> >> >>> >> >>need
> > >> > >> >>> >> >>> >> >> to account for anything else?
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >> I think the one outstanding question is how to
> > >>handle
> > >> > >> >>> >> >>>installation /
> > >> > >> >>> >> >>> >> >> compatibility with different versions of
> cordova.
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >> Documentation for the tool as well as the spec
> > >>(put
> > >> it
> > >> > on
> > >> > >> >>>the
> > >> > >> >>> >> >>>wiki,
> > >> > >> >>> >> >>> >> >> perhaps) would be awesome!
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> > >> > >> >>> >><re...@gmail.com>
> > >> > >> >>> >> >>> >>wrote:
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd
> > >>love
> > >> to
> > >> > >> >>>dig in
> > >> > >> >>> >> >>>and
> > >> > >> >>> >> >>> >>start
> > >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
> > >>needed
> > >> at
> > >> > >> the
> > >> > >> >>> >> >>>moment?
> > >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >-Mike
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> > >> > >> >>><fi...@adobe.com>
> > >> > >> >>> >> >>>wrote:
> > >> > >> >>> >> >>> >> >> >
> > >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
> > >>"spec"
> > >> we
> > >> > >> are
> > >> > >> >>> >> >>>working
> > >> > >> >>> >> >>> >> >>towards:
> > >> > >> >>> >> >>> >> >> >>
> https://github.com/alunny/cordova-plugin-spec
> > >> > >> >>> >> >>> >> >> >>
> > >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <
> b@brian.io>
> > >> > wrote:
> > >> > >> >>> >> >>> >> >> >>
> > >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
> > >> Currently
> > >> > >> the
> > >> > >> >>> >>plugin
> > >> > >> >>> >> >>> >> >>tooling
> > >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael,
> > >>and
> > >> > >> >>>myself.
> > >> > >> >>> >> >>>(sorry
> > >> > >> >>> >> >>> >>for
> > >> > >> >>> >> >>> >> >>the
> > >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a
> summer
> > >> break
> > >> > >> >>>after
> > >> > >> >>> >> >>> >>shipping
> > >> > >> >>> >> >>> >> >> >> >2.0)
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this list,
> > >>git,
> > >> > and
> > >> > >> >>> >>these
> > >> > >> >>> >> >>>wiki
> > >> > >> >>> >> >>> >> >>pages:
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >-
> http://wiki.apache.org/cordova/PluginDesign
> > >> > >> >>> >> >>> >> >> >> >-
> > >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs
> branch
> > >> which
> > >> > >> >>>you
> > >> > >> >>> >>can
> > >> > >> >>> >> >>> >>preview
> > >> > >> >>> >> >>> >> >>on
> > >> > >> >>> >> >>> >> >> >> >the Github mirror here:
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >>
> > >> > >>
> > >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on our
> > >> contrib
> > >> > >> >>> >>process
> > >> > >> >>> >> >>>in
> > >> > >> >>> >> >>> >>the
> > >> > >> >>> >> >>> >> >> >>wiki:
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >
> > >> http://wiki.apache.org/cordova/ContributerWorkflow
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >And in the case of labs projects everything
> > >>stays
> > >> > on
> > >> > >> >>>its
> > >> > >> >>> >>own
> > >> > >> >>> >> >>> >>branch
> > >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid for
> > >>its
> > >> > own
> > >> > >> >>>repo.
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >* * *
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >Let me know any q's!
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >
> > >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
> > >>Reinstein
> > >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> > >> > >> >>> >> >>> >> >> >> >> Hey there,
> > >> > >> >>> >> >>> >> >> >> >>
> > >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the
> plugin
> > >> > system
> > >> > >> >>> >>that is
> > >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> > >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who
> are
> > >> the
> > >> > >> >>>right
> > >> > >> >>> >> >>>people
> > >> > >> >>> >> >>> >>to
> > >> > >> >>> >> >>> >> >>talk
> > >> > >> >>> >> >>> >> >> >> >>to?
> > >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> > >> > experienced
> > >> > >> >>> >> >>>developer,
> > >> > >> >>> >> >>> >> >>have
> > >> > >> >>> >> >>> >> >> >> >>worked
> > >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and
> would
> > >> love
> > >> > to
> > >> > >> >>>give
> > >> > >> >>> >> >>>back
> > >> > >> >>> >> >>> >>to
> > >> > >> >>> >> >>> >> >>the
> > >> > >> >>> >> >>> >> >> >> >> community.
> > >> > >> >>> >> >>> >> >> >> >>
> > >> > >> >>> >> >>> >> >> >> >> cheers,
> > >> > >> >>> >> >>> >> >> >> >>
> > >> > >> >>> >> >>> >> >> >> >> -Mike
> > >> > >> >>> >> >>> >> >> >>
> > >> > >> >>> >> >>> >> >> >>
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >> >>
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>> >>
> > >> > >> >>> >> >>>
> > >> > >> >>> >> >>>
> > >> > >> >>> >>
> > >> > >> >>> >>
> > >> > >> >>>
> > >> > >> >>>
> > >> > >>
> > >> > >>
> > >> > >
> > >> >
> > >>
> >
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Looks good to me. What are the next steps? One thing I'd like to see happen
is getting rid of some of those repos and documentation pages that are
redundant.
-Mike
On Mon, Sep 10, 2012 at 2:04 PM, Filip Maj <fi...@adobe.com> wrote:
> Nice!
>
> I worked out some of your quotes/questions and put it up on my branch on
> github: https://github.com/filmaj/cordova-client/tree/einstein
>
> On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >Hey folks,
> >
> >Hope you all had a nice weekend. I have a preliminary draft ready that
> >merges cordova-client and command line tooling design into 1 document:
> >
> >https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
> >
> >Any feedback would be greatly appreciated. Thanks!
> >
> >-Mike
> >
> >On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com> wrote:
> >
> >> Hi Mike,
> >>
> >> pluginstall-with-git support is just an experiment that I did a while
> >>back
> >> (it takes git URLs as well as local paths). I suggest you base your
> >>work on
> >> alunny's pluginstall until/if those changes get merged.
> >>
> >> Cheers
> >>
> >> Anis
> >>
> >> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <
> reinstein.mike@gmail.com
> >> >wrote:
> >>
> >> > I see 2 repositories for pluginstall:
> >> >
> >> >
> >> >
> >>
> >>
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
> >>t-support
> >> >
> >> > and Andrew's:
> >> > https://github.com/alunny/pluginstall
> >> >
> >> > When consolidating the pluginstall and plugin format docs I forked
> >> Andrew's
> >> > repo. Should I instead have used the pluginstall-with-git-support
> >>repo as
> >> > my base?
> >> >
> >> > -Mike
> >> >
> >> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
> >><reinstein.mike@gmail.com
> >> > >wrote:
> >> >
> >> > > My username is nekoflux.
> >> > >
> >> > >
> >> > >
> >> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
> >> > >
> >> > >> JIRA is separate, we can assign issues to you (if you so wish).
> >> > >>
> >> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> >> > >>
> >> > >> >Registration is open - let us know what your user account is once
> >>you
> >> > >> >do that, for assigning issues to yourself you need us to add you
> >>to a
> >> > >> >contributors group.
> >> > >> >
> >> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> >> > reinstein.mike@gmail.com
> >> > >> >
> >> > >> >wrote:
> >> > >> >> Okay, will do. Any feedback on the other comments? I'll proceed
> >> with
> >> > >> >> merging the cordova-client and command line tooling spec next. I
> >> > >> >>suppose it
> >> > >> >> probably makes sense for me to start working out of JIRA so
> >>these
> >> > tasks
> >> > >> >>can
> >> > >> >> be tracked. Is registration open or do I need to get permission
> >> from
> >> > an
> >> > >> >> admin for an account?
> >> > >> >>
> >> > >> >>
> >> > >> >>
> >> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com>
> wrote:
> >> > >> >>
> >> > >> >>> Sorry for the late reply, this looks awesome!
> >> > >> >>>
> >> > >> >>> The one modification I would do is remove "www" as a platform
> >>(you
> >> > >> >>>have a
> >> > >> >>> comment in there about that too).
> >> > >> >>>
> >> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com>
> >> > wrote:
> >> > >> >>>
> >> > >> >>> >> eventually we will move pluginstall into apache
> >> > >> >>> >Okay, I wasn't sure if that would happen, so I went with the
> >> > slightly
> >> > >> >>>more
> >> > >> >>> >conservative assumption, that pluginstall might live
> >>separately
> >> > from
> >> > >> >>> >cordova-client. But I get the impression this is a left-over
> >> notion
> >> > >> >>>from
> >> > >> >>> >when Andrew first built pluginstall and it wasn't clear then
> >> > whether
> >> > >> >>>or
> >> > >> >>> >not
> >> > >> >>> >it would take hold.
> >> > >> >>> >
> >> > >> >>> >I've got an initial version of the merged documentation for
> >>the
> >> > >> >>> >pluginstall
> >> > >> >>> >command line tool, and the specification doc. It's here
> >> > >> >>> >https://github.com/mreinstein/pluginstall
> >> > >> >>> >
> >> > >> >>> >I've also added some comments on possible changes. Overall the
> >> doc
> >> > is
> >> > >> >>> >pretty tight, so it's largely unchanged. Would really
> >>appreciate
> >> > >> >>> >constructive feedback on this. If it looks right I'll send a
> >>pull
> >> > >> >>>request
> >> > >> >>> >to alunny, and then proceed with merging cordova-client design
> >> doc
> >> > >> >>>into
> >> > >> >>> >the
> >> > >> >>> >README on github.
> >> > >> >>> >
> >> > >> >>> >-Mike
> >> > >> >>> >
> >> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com>
> >>wrote:
> >> > >> >>> >
> >> > >> >>> >> +1 !
> >> > >> >>> >>
> >> > >> >>> >> (I THINK) eventually we will move pluginstall into apache
> >> > (assuming
> >> > >> >>>the
> >> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> >> > >> >>> >>
> >> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >> > >> >>> >>
> >> > >> >>> >> >love it
> >> > >> >>> >> >
> >> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >> > >> >>> >><re...@gmail.com>
> >> > >> >>> >> >wrote:
> >> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to
> >> > review
> >> > >> >>>the
> >> > >> >>> >> >>docs
> >> > >> >>> >> >> more carefully. I'm really impressed with how well
> >>written
> >> > they
> >> > >> >>>are.
> >> > >> >>> >> >>What I
> >> > >> >>> >> >> *think* makes the most sense is to consolidate into fewer
> >> > >> >>>documents
> >> > >> >>> >>so
> >> > >> >>> >> >>that
> >> > >> >>> >> >> it's not necessary to look at so many seperate places.
> >> Here's
> >> > >> >>>what I
> >> > >> >>> >> >> propose:
> >> > >> >>> >> >> * merge the cordova-plugin-spec into the
> >>alunny/pluginstall
> >> > >> >>>README.md
> >> > >> >>> >> >> * merge the command line tooling design doc into the
> >> > >> >>>cordova-client
> >> > >> >>> >> >> README.md
> >> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge
> >> > parts
> >> > >> >>>of it
> >> > >> >>> >> >>into
> >> > >> >>> >> >> the above 2 docs
> >> > >> >>> >> >>
> >> > >> >>> >> >> I think what this gets us is 2 docs instead of 5, and it
> >> still
> >> > >> >>> >>maintains
> >> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
> >>utility
> >> > and
> >> > >> >>>the
> >> > >> >>> >> >>larger
> >> > >> >>> >> >> cordova-client. I'm assuming this separation was the
> >> original
> >> > >> >>>intent,
> >> > >> >>> >> >> rather than having one monolithic tool.
> >> > >> >>> >> >>
> >> > >> >>> >> >> Would love feedback on this, I don't want to waste time
> >> doing
> >> > it
> >> > >> >>>and
> >> > >> >>> >> >>find
> >> > >> >>> >> >> out this isn't appropriate. :)
> >> > >> >>> >> >>
> >> > >> >>> >> >>
> >> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
> >><fi...@adobe.com>
> >> > >> wrote:
> >> > >> >>> >> >>
> >> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does
> >>the
> >> > >> hard
> >> > >> >>> >>work
> >> > >> >>> >> >>>for
> >> > >> >>> >> >>> programmatic plugin installation, which is just one of
> >>the
> >> > apis
> >> > >> >>> >> >>>available
> >> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
> >> > >> >>>pluginstall.
> >> > >> >>> >> >>>
> >> > >> >>> >> >>> The client also handles app creation, platform
> >> > >> >>>removal/addition, and
> >> > >> >>> >> >>> interpolating information from app's config.xml into the
> >> > >> >>>necessary
> >> > >> >>> >> >>>spots
> >> > >> >>> >> >>> in each native project.
> >> > >> >>> >> >>>
> >> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> >> > >> reinstein.mike@gmail.com>
> >> > >> >>> >> wrote:
> >> > >> >>> >> >>>
> >> > >> >>> >> >>> >Hey Filip,
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >One thing I"m curious about, whats the difference
> >>between
> >> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> >> > >> >>> >> >>>
> >> > >> >>> >>>
> >> > >>
> >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >there seems to be some overlap there. Is pluginstall a
> >> > subset
> >> > >> >>>of
> >> > >> >>> >> >>> >functionality just related to plugins that has moved
> >>into
> >> > >> >>> >> >>>cordova-client
> >> > >> >>> >> >>> >or
> >> > >> >>> >> >>> >is it different?
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >It seems like cordova-client is the most mature
> >>codebase
> >> > that
> >> > >> >>> >> >>>incorporates
> >> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
> >>finding
> >> to
> >> > >> >>>see if
> >> > >> >>> >> >>> >everythign is in cordova-client or not. Said
> >>differently,
> >> is
> >> > >> it
> >> > >> >>> >>safe
> >> > >> >>> >> >>>to
> >> > >> >>> >> >>> >assume that just about all the worthwhile code is in
> >> > >> >>> >>cordova-client?
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >-Mike
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
> >><fil@adobe.com
> >> >
> >> > >> >>>wrote:
> >> > >> >>> >> >>> >
> >> > >> >>> >> >>> >> All looks good to me Mike.
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would be a
> >>great
> >> > >> >>>place to
> >> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
> >> tackling
> >> > >> >>>this!
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> >> > >> >>><re...@gmail.com>
> >> > >> >>> >> >>>wrote:
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>> >> >Hey Filip, Brian:
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >I think where I'd like to start is on
> >>documentation. I
> >> > may
> >> > >> >>>be
> >> > >> >>> >>wrong
> >> > >> >>> >> >>> >>about
> >> > >> >>> >> >>> >> >this, but it seems like there are bits and pieces of
> >> docs
> >> > >> in
> >> > >> >>> >> >>>various
> >> > >> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a
> >> good
> >> > >> >>>start
> >> > >> >>> >>is
> >> > >> >>> >> >>>for
> >> > >> >>> >> >>> >>me
> >> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
> >>"master"
> >> > >> >>>document,
> >> > >> >>> >>and
> >> > >> >>> >> >>> >>cull
> >> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
> >>rephrasing
> >> > of
> >> > >> >>>the
> >> > >> >>> >> >>>various
> >> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take a
> >>look
> >> and
> >> > >> >>>let me
> >> > >> >>> >> >>>know
> >> > >> >>> >> >>> >>if
> >> > >> >>> >> >>> >> >I've characterised the content/purpose of these
> >>various
> >> > >> >>>links:
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> >> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >The implementation that manages plugin usage is
> >>here:
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>>>
> >> > >> >>>
> >> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> >>> >> >>> >> >This project encompasses more than just plugins
> >>because
> >> > it
> >> > >> >>>also
> >> > >> >>> >> >>>handles
> >> > >> >>> >> >>> >> >everything related to building, deploying, and
> >>managing
> >> > >> >>>cordova
> >> > >> >>> >> >>> >> >applications
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >These plugins are most popular, and should ideally
> >>work
> >> > >> >>>with the
> >> > >> >>> >> >>> >> >cordova-client implemenation:
> >> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >This implementation by Drew was an initial proof of
> >> > >> concept,
> >> > >> >>> >>which
> >> > >> >>> >> >>>only
> >> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
> >>favor of
> >> > >> >>> >> >>>cordova-client,
> >> > >> >>> >> >>> >> >with much of his ideas having made it into
> >> > cordova-client:
> >> > >> >>> >> >>> >> >
> >> https://github.com/deedubbu/cordova-blackberry-pluggable
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >This doc contains some info on the format of the
> >> command
> >> > >> >>>line
> >> > >> >>> >> >>>interface
> >> > >> >>> >> >>> >> >and
> >> > >> >>> >> >>> >> >directory structure of cordova-client:
> >> > >> >>> >> >>> >> >
> >> http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >This doc contains some documentation on Drew's old
> >> > >> >>> >>implementation,
> >> > >> >>> >> >>>and
> >> > >> >>> >> >>> >>is
> >> > >> >>> >> >>> >> >out of date now:
> >> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to get a
> >> handle
> >> > on
> >> > >> >>>what
> >> > >> >>> >> >>>docs
> >> > >> >>> >> >>> >>are
> >> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
> >>judging
> >> > >> >>>anyone's
> >> > >> >>> >> >>>work or
> >> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong idea
> >>about
> >> > >> what
> >> > >> >>> >>these
> >> > >> >>> >> >>> >>links
> >> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >-Mike
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >*
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> >> > fil@adobe.com>
> >> > >> >>> >>wrote:
> >> > >> >>> >> >>> >> >
> >> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level project
> >>goes
> >> > >> >>> >> >>>hand-in-hand
> >> > >> >>> >> >>> >>with
> >> > >> >>> >> >>> >> >> this spec. Code here:
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>>
> >> > >> >>> >> >>>
> >> > >> >>> >>
> >> > >> >>>
> >> > >> >>>
> >> > >>
> >> >
> >>https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >> > >> >>> >> >>>h
> >> > >> >>> >> >>> >> >>or
> >> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
> >> > >> >>>plugins out
> >> > >> >>> >> >>>in the
> >> > >> >>> >> >>> >> >>wild
> >> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work
> >>with
> >> > >> this
> >> > >> >>> >>spec.
> >> > >> >>> >> >>>Do
> >> > >> >>> >> >>> we
> >> > >> >>> >> >>> >> >>need
> >> > >> >>> >> >>> >> >> to account for anything else?
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >> I think the one outstanding question is how to
> >>handle
> >> > >> >>> >> >>>installation /
> >> > >> >>> >> >>> >> >> compatibility with different versions of cordova.
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >> Documentation for the tool as well as the spec
> >>(put
> >> it
> >> > on
> >> > >> >>>the
> >> > >> >>> >> >>>wiki,
> >> > >> >>> >> >>> >> >> perhaps) would be awesome!
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >> > >> >>> >><re...@gmail.com>
> >> > >> >>> >> >>> >>wrote:
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd
> >>love
> >> to
> >> > >> >>>dig in
> >> > >> >>> >> >>>and
> >> > >> >>> >> >>> >>start
> >> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
> >>needed
> >> at
> >> > >> the
> >> > >> >>> >> >>>moment?
> >> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >-Mike
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> >> > >> >>><fi...@adobe.com>
> >> > >> >>> >> >>>wrote:
> >> > >> >>> >> >>> >> >> >
> >> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
> >>"spec"
> >> we
> >> > >> are
> >> > >> >>> >> >>>working
> >> > >> >>> >> >>> >> >>towards:
> >> > >> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >> > >> >>> >> >>> >> >> >>
> >> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io>
> >> > wrote:
> >> > >> >>> >> >>> >> >> >>
> >> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
> >> Currently
> >> > >> the
> >> > >> >>> >>plugin
> >> > >> >>> >> >>> >> >>tooling
> >> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael,
> >>and
> >> > >> >>>myself.
> >> > >> >>> >> >>>(sorry
> >> > >> >>> >> >>> >>for
> >> > >> >>> >> >>> >> >>the
> >> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a summer
> >> break
> >> > >> >>>after
> >> > >> >>> >> >>> >>shipping
> >> > >> >>> >> >>> >> >> >> >2.0)
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this list,
> >>git,
> >> > and
> >> > >> >>> >>these
> >> > >> >>> >> >>>wiki
> >> > >> >>> >> >>> >> >>pages:
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >> > >> >>> >> >>> >> >> >> >-
> >> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch
> >> which
> >> > >> >>>you
> >> > >> >>> >>can
> >> > >> >>> >> >>> >>preview
> >> > >> >>> >> >>> >> >>on
> >> > >> >>> >> >>> >> >> >> >the Github mirror here:
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >>
> >> > >> >>> >>
> >> > >>
> >>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >You will want to start by reading up on our
> >> contrib
> >> > >> >>> >>process
> >> > >> >>> >> >>>in
> >> > >> >>> >> >>> >>the
> >> > >> >>> >> >>> >> >> >>wiki:
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >
> >> http://wiki.apache.org/cordova/ContributerWorkflow
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >And in the case of labs projects everything
> >>stays
> >> > on
> >> > >> >>>its
> >> > >> >>> >>own
> >> > >> >>> >> >>> >>branch
> >> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid for
> >>its
> >> > own
> >> > >> >>>repo.
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >* * *
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >Let me know any q's!
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >
> >> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
> >>Reinstein
> >> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >> > >> >>> >> >>> >> >> >> >> Hey there,
> >> > >> >>> >> >>> >> >> >> >>
> >> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin
> >> > system
> >> > >> >>> >>that is
> >> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> >> > >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are
> >> the
> >> > >> >>>right
> >> > >> >>> >> >>>people
> >> > >> >>> >> >>> >>to
> >> > >> >>> >> >>> >> >>talk
> >> > >> >>> >> >>> >> >> >> >>to?
> >> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> >> > experienced
> >> > >> >>> >> >>>developer,
> >> > >> >>> >> >>> >> >>have
> >> > >> >>> >> >>> >> >> >> >>worked
> >> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would
> >> love
> >> > to
> >> > >> >>>give
> >> > >> >>> >> >>>back
> >> > >> >>> >> >>> >>to
> >> > >> >>> >> >>> >> >>the
> >> > >> >>> >> >>> >> >> >> >> community.
> >> > >> >>> >> >>> >> >> >> >>
> >> > >> >>> >> >>> >> >> >> >> cheers,
> >> > >> >>> >> >>> >> >> >> >>
> >> > >> >>> >> >>> >> >> >> >> -Mike
> >> > >> >>> >> >>> >> >> >>
> >> > >> >>> >> >>> >> >> >>
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >> >>
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>> >>
> >> > >> >>> >> >>>
> >> > >> >>> >> >>>
> >> > >> >>> >>
> >> > >> >>> >>
> >> > >> >>>
> >> > >> >>>
> >> > >>
> >> > >>
> >> > >
> >> >
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Nice!
I worked out some of your quotes/questions and put it up on my branch on
github: https://github.com/filmaj/cordova-client/tree/einstein
On 9/9/12 8:02 AM, "Mike Reinstein" <re...@gmail.com> wrote:
>Hey folks,
>
>Hope you all had a nice weekend. I have a preliminary draft ready that
>merges cordova-client and command line tooling design into 1 document:
>
>https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
>
>Any feedback would be greatly appreciated. Thanks!
>
>-Mike
>
>On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com> wrote:
>
>> Hi Mike,
>>
>> pluginstall-with-git support is just an experiment that I did a while
>>back
>> (it takes git URLs as well as local paths). I suggest you base your
>>work on
>> alunny's pluginstall until/if those changes get merged.
>>
>> Cheers
>>
>> Anis
>>
>> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <reinstein.mike@gmail.com
>> >wrote:
>>
>> > I see 2 repositories for pluginstall:
>> >
>> >
>> >
>>
>>https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-gi
>>t-support
>> >
>> > and Andrew's:
>> > https://github.com/alunny/pluginstall
>> >
>> > When consolidating the pluginstall and plugin format docs I forked
>> Andrew's
>> > repo. Should I instead have used the pluginstall-with-git-support
>>repo as
>> > my base?
>> >
>> > -Mike
>> >
>> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein
>><reinstein.mike@gmail.com
>> > >wrote:
>> >
>> > > My username is nekoflux.
>> > >
>> > >
>> > >
>> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
>> > >
>> > >> JIRA is separate, we can assign issues to you (if you so wish).
>> > >>
>> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>> > >>
>> > >> >Registration is open - let us know what your user account is once
>>you
>> > >> >do that, for assigning issues to yourself you need us to add you
>>to a
>> > >> >contributors group.
>> > >> >
>> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
>> > reinstein.mike@gmail.com
>> > >> >
>> > >> >wrote:
>> > >> >> Okay, will do. Any feedback on the other comments? I'll proceed
>> with
>> > >> >> merging the cordova-client and command line tooling spec next. I
>> > >> >>suppose it
>> > >> >> probably makes sense for me to start working out of JIRA so
>>these
>> > tasks
>> > >> >>can
>> > >> >> be tracked. Is registration open or do I need to get permission
>> from
>> > an
>> > >> >> admin for an account?
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
>> > >> >>
>> > >> >>> Sorry for the late reply, this looks awesome!
>> > >> >>>
>> > >> >>> The one modification I would do is remove "www" as a platform
>>(you
>> > >> >>>have a
>> > >> >>> comment in there about that too).
>> > >> >>>
>> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com>
>> > wrote:
>> > >> >>>
>> > >> >>> >> eventually we will move pluginstall into apache
>> > >> >>> >Okay, I wasn't sure if that would happen, so I went with the
>> > slightly
>> > >> >>>more
>> > >> >>> >conservative assumption, that pluginstall might live
>>separately
>> > from
>> > >> >>> >cordova-client. But I get the impression this is a left-over
>> notion
>> > >> >>>from
>> > >> >>> >when Andrew first built pluginstall and it wasn't clear then
>> > whether
>> > >> >>>or
>> > >> >>> >not
>> > >> >>> >it would take hold.
>> > >> >>> >
>> > >> >>> >I've got an initial version of the merged documentation for
>>the
>> > >> >>> >pluginstall
>> > >> >>> >command line tool, and the specification doc. It's here
>> > >> >>> >https://github.com/mreinstein/pluginstall
>> > >> >>> >
>> > >> >>> >I've also added some comments on possible changes. Overall the
>> doc
>> > is
>> > >> >>> >pretty tight, so it's largely unchanged. Would really
>>appreciate
>> > >> >>> >constructive feedback on this. If it looks right I'll send a
>>pull
>> > >> >>>request
>> > >> >>> >to alunny, and then proceed with merging cordova-client design
>> doc
>> > >> >>>into
>> > >> >>> >the
>> > >> >>> >README on github.
>> > >> >>> >
>> > >> >>> >-Mike
>> > >> >>> >
>> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com>
>>wrote:
>> > >> >>> >
>> > >> >>> >> +1 !
>> > >> >>> >>
>> > >> >>> >> (I THINK) eventually we will move pluginstall into apache
>> > (assuming
>> > >> >>>the
>> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
>> > >> >>> >>
>> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> > >> >>> >>
>> > >> >>> >> >love it
>> > >> >>> >> >
>> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>> > >> >>> >><re...@gmail.com>
>> > >> >>> >> >wrote:
>> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to
>> > review
>> > >> >>>the
>> > >> >>> >> >>docs
>> > >> >>> >> >> more carefully. I'm really impressed with how well
>>written
>> > they
>> > >> >>>are.
>> > >> >>> >> >>What I
>> > >> >>> >> >> *think* makes the most sense is to consolidate into fewer
>> > >> >>>documents
>> > >> >>> >>so
>> > >> >>> >> >>that
>> > >> >>> >> >> it's not necessary to look at so many seperate places.
>> Here's
>> > >> >>>what I
>> > >> >>> >> >> propose:
>> > >> >>> >> >> * merge the cordova-plugin-spec into the
>>alunny/pluginstall
>> > >> >>>README.md
>> > >> >>> >> >> * merge the command line tooling design doc into the
>> > >> >>>cordova-client
>> > >> >>> >> >> README.md
>> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge
>> > parts
>> > >> >>>of it
>> > >> >>> >> >>into
>> > >> >>> >> >> the above 2 docs
>> > >> >>> >> >>
>> > >> >>> >> >> I think what this gets us is 2 docs instead of 5, and it
>> still
>> > >> >>> >>maintains
>> > >> >>> >> >> the nice loose coupling between alunny's pluginstall
>>utility
>> > and
>> > >> >>>the
>> > >> >>> >> >>larger
>> > >> >>> >> >> cordova-client. I'm assuming this separation was the
>> original
>> > >> >>>intent,
>> > >> >>> >> >> rather than having one monolithic tool.
>> > >> >>> >> >>
>> > >> >>> >> >> Would love feedback on this, I don't want to waste time
>> doing
>> > it
>> > >> >>>and
>> > >> >>> >> >>find
>> > >> >>> >> >> out this isn't appropriate. :)
>> > >> >>> >> >>
>> > >> >>> >> >>
>> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj
>><fi...@adobe.com>
>> > >> wrote:
>> > >> >>> >> >>
>> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does
>>the
>> > >> hard
>> > >> >>> >>work
>> > >> >>> >> >>>for
>> > >> >>> >> >>> programmatic plugin installation, which is just one of
>>the
>> > apis
>> > >> >>> >> >>>available
>> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
>> > >> >>>pluginstall.
>> > >> >>> >> >>>
>> > >> >>> >> >>> The client also handles app creation, platform
>> > >> >>>removal/addition, and
>> > >> >>> >> >>> interpolating information from app's config.xml into the
>> > >> >>>necessary
>> > >> >>> >> >>>spots
>> > >> >>> >> >>> in each native project.
>> > >> >>> >> >>>
>> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
>> > >> reinstein.mike@gmail.com>
>> > >> >>> >> wrote:
>> > >> >>> >> >>>
>> > >> >>> >> >>> >Hey Filip,
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >One thing I"m curious about, whats the difference
>>between
>> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
>> > >> >>> >> >>>
>> > >> >>> >>>
>> > >>
>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >there seems to be some overlap there. Is pluginstall a
>> > subset
>> > >> >>>of
>> > >> >>> >> >>> >functionality just related to plugins that has moved
>>into
>> > >> >>> >> >>>cordova-client
>> > >> >>> >> >>> >or
>> > >> >>> >> >>> >is it different?
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >It seems like cordova-client is the most mature
>>codebase
>> > that
>> > >> >>> >> >>>incorporates
>> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm
>>finding
>> to
>> > >> >>>see if
>> > >> >>> >> >>> >everythign is in cordova-client or not. Said
>>differently,
>> is
>> > >> it
>> > >> >>> >>safe
>> > >> >>> >> >>>to
>> > >> >>> >> >>> >assume that just about all the worthwhile code is in
>> > >> >>> >>cordova-client?
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >-Mike
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj
>><fil@adobe.com
>> >
>> > >> >>>wrote:
>> > >> >>> >> >>> >
>> > >> >>> >> >>> >> All looks good to me Mike.
>> > >> >>> >> >>> >>
>> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would be a
>>great
>> > >> >>>place to
>> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
>> tackling
>> > >> >>>this!
>> > >> >>> >> >>> >>
>> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
>> > >> >>><re...@gmail.com>
>> > >> >>> >> >>>wrote:
>> > >> >>> >> >>> >>
>> > >> >>> >> >>> >> >Hey Filip, Brian:
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >I think where I'd like to start is on
>>documentation. I
>> > may
>> > >> >>>be
>> > >> >>> >>wrong
>> > >> >>> >> >>> >>about
>> > >> >>> >> >>> >> >this, but it seems like there are bits and pieces of
>> docs
>> > >> in
>> > >> >>> >> >>>various
>> > >> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a
>> good
>> > >> >>>start
>> > >> >>> >>is
>> > >> >>> >> >>>for
>> > >> >>> >> >>> >>me
>> > >> >>> >> >>> >> >to find all these pieces, consolidate into a
>>"master"
>> > >> >>>document,
>> > >> >>> >>and
>> > >> >>> >> >>> >>cull
>> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my
>>rephrasing
>> > of
>> > >> >>>the
>> > >> >>> >> >>>various
>> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take a
>>look
>> and
>> > >> >>>let me
>> > >> >>> >> >>>know
>> > >> >>> >> >>> >>if
>> > >> >>> >> >>> >> >I've characterised the content/purpose of these
>>various
>> > >> >>>links:
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
>> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >The implementation that manages plugin usage is
>>here:
>> > >> >>> >> >>> >>
>> > >> >>> >> >>>>
>> > >> >>>
>> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> >>> >> >>> >> >This project encompasses more than just plugins
>>because
>> > it
>> > >> >>>also
>> > >> >>> >> >>>handles
>> > >> >>> >> >>> >> >everything related to building, deploying, and
>>managing
>> > >> >>>cordova
>> > >> >>> >> >>> >> >applications
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >These plugins are most popular, and should ideally
>>work
>> > >> >>>with the
>> > >> >>> >> >>> >> >cordova-client implemenation:
>> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >This implementation by Drew was an initial proof of
>> > >> concept,
>> > >> >>> >>which
>> > >> >>> >> >>>only
>> > >> >>> >> >>> >> >works for blackberry and has been abandoned in
>>favor of
>> > >> >>> >> >>>cordova-client,
>> > >> >>> >> >>> >> >with much of his ideas having made it into
>> > cordova-client:
>> > >> >>> >> >>> >> >
>> https://github.com/deedubbu/cordova-blackberry-pluggable
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >This doc contains some info on the format of the
>> command
>> > >> >>>line
>> > >> >>> >> >>>interface
>> > >> >>> >> >>> >> >and
>> > >> >>> >> >>> >> >directory structure of cordova-client:
>> > >> >>> >> >>> >> >
>> http://wiki.apache.org/cordova/CommandLineToolingDesign
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >This doc contains some documentation on Drew's old
>> > >> >>> >>implementation,
>> > >> >>> >> >>>and
>> > >> >>> >> >>> >>is
>> > >> >>> >> >>> >> >out of date now:
>> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to get a
>> handle
>> > on
>> > >> >>>what
>> > >> >>> >> >>>docs
>> > >> >>> >> >>> >>are
>> > >> >>> >> >>> >> >relevant and which links contain what. I'm not
>>judging
>> > >> >>>anyone's
>> > >> >>> >> >>>work or
>> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong idea
>>about
>> > >> what
>> > >> >>> >>these
>> > >> >>> >> >>> >>links
>> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >-Mike
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >*
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
>> > fil@adobe.com>
>> > >> >>> >>wrote:
>> > >> >>> >> >>> >> >
>> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level project
>>goes
>> > >> >>> >> >>>hand-in-hand
>> > >> >>> >> >>> >>with
>> > >> >>> >> >>> >> >> this spec. Code here:
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >>
>> > >> >>> >> >>> >>
>> > >> >>> >> >>>
>> > >> >>> >> >>>
>> > >> >>> >>
>> > >> >>>
>> > >> >>>
>> > >>
>> >
>>https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> > >> >>> >> >>>h
>> > >> >>> >> >>> >> >>or
>> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
>> > >> >>>plugins out
>> > >> >>> >> >>>in the
>> > >> >>> >> >>> >> >>wild
>> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work
>>with
>> > >> this
>> > >> >>> >>spec.
>> > >> >>> >> >>>Do
>> > >> >>> >> >>> we
>> > >> >>> >> >>> >> >>need
>> > >> >>> >> >>> >> >> to account for anything else?
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >> I think the one outstanding question is how to
>>handle
>> > >> >>> >> >>>installation /
>> > >> >>> >> >>> >> >> compatibility with different versions of cordova.
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >> Documentation for the tool as well as the spec
>>(put
>> it
>> > on
>> > >> >>>the
>> > >> >>> >> >>>wiki,
>> > >> >>> >> >>> >> >> perhaps) would be awesome!
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>> > >> >>> >><re...@gmail.com>
>> > >> >>> >> >>> >>wrote:
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >> >Hi Brian, Filip,
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd
>>love
>> to
>> > >> >>>dig in
>> > >> >>> >> >>>and
>> > >> >>> >> >>> >>start
>> > >> >>> >> >>> >> >> >helping, where do you feel the most help is
>>needed
>> at
>> > >> the
>> > >> >>> >> >>>moment?
>> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >-Mike
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
>> > >> >>><fi...@adobe.com>
>> > >> >>> >> >>>wrote:
>> > >> >>> >> >>> >> >> >
>> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin
>>"spec"
>> we
>> > >> are
>> > >> >>> >> >>>working
>> > >> >>> >> >>> >> >>towards:
>> > >> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>> > >> >>> >> >>> >> >> >>
>> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io>
>> > wrote:
>> > >> >>> >> >>> >> >> >>
>> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
>> Currently
>> > >> the
>> > >> >>> >>plugin
>> > >> >>> >> >>> >> >>tooling
>> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael,
>>and
>> > >> >>>myself.
>> > >> >>> >> >>>(sorry
>> > >> >>> >> >>> >>for
>> > >> >>> >> >>> >> >>the
>> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a summer
>> break
>> > >> >>>after
>> > >> >>> >> >>> >>shipping
>> > >> >>> >> >>> >> >> >> >2.0)
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this list,
>>git,
>> > and
>> > >> >>> >>these
>> > >> >>> >> >>>wiki
>> > >> >>> >> >>> >> >>pages:
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>> > >> >>> >> >>> >> >> >> >-
>> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch
>> which
>> > >> >>>you
>> > >> >>> >>can
>> > >> >>> >> >>> >>preview
>> > >> >>> >> >>> >> >>on
>> > >> >>> >> >>> >> >> >> >the Github mirror here:
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >>
>> > >> >>> >>
>> > >>
>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >You will want to start by reading up on our
>> contrib
>> > >> >>> >>process
>> > >> >>> >> >>>in
>> > >> >>> >> >>> >>the
>> > >> >>> >> >>> >> >> >>wiki:
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >
>> http://wiki.apache.org/cordova/ContributerWorkflow
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >And in the case of labs projects everything
>>stays
>> > on
>> > >> >>>its
>> > >> >>> >>own
>> > >> >>> >> >>> >>branch
>> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid for
>>its
>> > own
>> > >> >>>repo.
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >* * *
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >Let me know any q's!
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >
>> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike
>>Reinstein
>> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>> > >> >>> >> >>> >> >> >> >> Hey there,
>> > >> >>> >> >>> >> >> >> >>
>> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin
>> > system
>> > >> >>> >>that is
>> > >> >>> >> >>> >> >> >> >>forthcoming. Is
>> > >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are
>> the
>> > >> >>>right
>> > >> >>> >> >>>people
>> > >> >>> >> >>> >>to
>> > >> >>> >> >>> >> >>talk
>> > >> >>> >> >>> >> >> >> >>to?
>> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
>> > experienced
>> > >> >>> >> >>>developer,
>> > >> >>> >> >>> >> >>have
>> > >> >>> >> >>> >> >> >> >>worked
>> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would
>> love
>> > to
>> > >> >>>give
>> > >> >>> >> >>>back
>> > >> >>> >> >>> >>to
>> > >> >>> >> >>> >> >>the
>> > >> >>> >> >>> >> >> >> >> community.
>> > >> >>> >> >>> >> >> >> >>
>> > >> >>> >> >>> >> >> >> >> cheers,
>> > >> >>> >> >>> >> >> >> >>
>> > >> >>> >> >>> >> >> >> >> -Mike
>> > >> >>> >> >>> >> >> >>
>> > >> >>> >> >>> >> >> >>
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >> >>
>> > >> >>> >> >>> >>
>> > >> >>> >> >>> >>
>> > >> >>> >> >>>
>> > >> >>> >> >>>
>> > >> >>> >>
>> > >> >>> >>
>> > >> >>>
>> > >> >>>
>> > >>
>> > >>
>> > >
>> >
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Hey folks,
Hope you all had a nice weekend. I have a preliminary draft ready that
merges cordova-client and command line tooling design into 1 document:
https://github.com/mreinstein/incubator-cordova-labs/tree/cordova-client
Any feedback would be greatly appreciated. Thanks!
-Mike
On Fri, Sep 7, 2012 at 10:01 PM, Anis KADRI <an...@gmail.com> wrote:
> Hi Mike,
>
> pluginstall-with-git support is just an experiment that I did a while back
> (it takes git URLs as well as local paths). I suggest you base your work on
> alunny's pluginstall until/if those changes get merged.
>
> Cheers
>
> Anis
>
> On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > I see 2 repositories for pluginstall:
> >
> >
> >
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-git-support
> >
> > and Andrew's:
> > https://github.com/alunny/pluginstall
> >
> > When consolidating the pluginstall and plugin format docs I forked
> Andrew's
> > repo. Should I instead have used the pluginstall-with-git-support repo as
> > my base?
> >
> > -Mike
> >
> > On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein <reinstein.mike@gmail.com
> > >wrote:
> >
> > > My username is nekoflux.
> > >
> > >
> > >
> > > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
> > >
> > >> JIRA is separate, we can assign issues to you (if you so wish).
> > >>
> > >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> > >>
> > >> >Registration is open - let us know what your user account is once you
> > >> >do that, for assigning issues to yourself you need us to add you to a
> > >> >contributors group.
> > >> >
> > >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> > reinstein.mike@gmail.com
> > >> >
> > >> >wrote:
> > >> >> Okay, will do. Any feedback on the other comments? I'll proceed
> with
> > >> >> merging the cordova-client and command line tooling spec next. I
> > >> >>suppose it
> > >> >> probably makes sense for me to start working out of JIRA so these
> > tasks
> > >> >>can
> > >> >> be tracked. Is registration open or do I need to get permission
> from
> > an
> > >> >> admin for an account?
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
> > >> >>
> > >> >>> Sorry for the late reply, this looks awesome!
> > >> >>>
> > >> >>> The one modification I would do is remove "www" as a platform (you
> > >> >>>have a
> > >> >>> comment in there about that too).
> > >> >>>
> > >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com>
> > wrote:
> > >> >>>
> > >> >>> >> eventually we will move pluginstall into apache
> > >> >>> >Okay, I wasn't sure if that would happen, so I went with the
> > slightly
> > >> >>>more
> > >> >>> >conservative assumption, that pluginstall might live separately
> > from
> > >> >>> >cordova-client. But I get the impression this is a left-over
> notion
> > >> >>>from
> > >> >>> >when Andrew first built pluginstall and it wasn't clear then
> > whether
> > >> >>>or
> > >> >>> >not
> > >> >>> >it would take hold.
> > >> >>> >
> > >> >>> >I've got an initial version of the merged documentation for the
> > >> >>> >pluginstall
> > >> >>> >command line tool, and the specification doc. It's here
> > >> >>> >https://github.com/mreinstein/pluginstall
> > >> >>> >
> > >> >>> >I've also added some comments on possible changes. Overall the
> doc
> > is
> > >> >>> >pretty tight, so it's largely unchanged. Would really appreciate
> > >> >>> >constructive feedback on this. If it looks right I'll send a pull
> > >> >>>request
> > >> >>> >to alunny, and then proceed with merging cordova-client design
> doc
> > >> >>>into
> > >> >>> >the
> > >> >>> >README on github.
> > >> >>> >
> > >> >>> >-Mike
> > >> >>> >
> > >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
> > >> >>> >
> > >> >>> >> +1 !
> > >> >>> >>
> > >> >>> >> (I THINK) eventually we will move pluginstall into apache
> > (assuming
> > >> >>>the
> > >> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> > >> >>> >>
> > >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> > >> >>> >>
> > >> >>> >> >love it
> > >> >>> >> >
> > >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> > >> >>> >><re...@gmail.com>
> > >> >>> >> >wrote:
> > >> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to
> > review
> > >> >>>the
> > >> >>> >> >>docs
> > >> >>> >> >> more carefully. I'm really impressed with how well written
> > they
> > >> >>>are.
> > >> >>> >> >>What I
> > >> >>> >> >> *think* makes the most sense is to consolidate into fewer
> > >> >>>documents
> > >> >>> >>so
> > >> >>> >> >>that
> > >> >>> >> >> it's not necessary to look at so many seperate places.
> Here's
> > >> >>>what I
> > >> >>> >> >> propose:
> > >> >>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall
> > >> >>>README.md
> > >> >>> >> >> * merge the command line tooling design doc into the
> > >> >>>cordova-client
> > >> >>> >> >> README.md
> > >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge
> > parts
> > >> >>>of it
> > >> >>> >> >>into
> > >> >>> >> >> the above 2 docs
> > >> >>> >> >>
> > >> >>> >> >> I think what this gets us is 2 docs instead of 5, and it
> still
> > >> >>> >>maintains
> > >> >>> >> >> the nice loose coupling between alunny's pluginstall utility
> > and
> > >> >>>the
> > >> >>> >> >>larger
> > >> >>> >> >> cordova-client. I'm assuming this separation was the
> original
> > >> >>>intent,
> > >> >>> >> >> rather than having one monolithic tool.
> > >> >>> >> >>
> > >> >>> >> >> Would love feedback on this, I don't want to waste time
> doing
> > it
> > >> >>>and
> > >> >>> >> >>find
> > >> >>> >> >> out this isn't appropriate. :)
> > >> >>> >> >>
> > >> >>> >> >>
> > >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com>
> > >> wrote:
> > >> >>> >> >>
> > >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the
> > >> hard
> > >> >>> >>work
> > >> >>> >> >>>for
> > >> >>> >> >>> programmatic plugin installation, which is just one of the
> > apis
> > >> >>> >> >>>available
> > >> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
> > >> >>>pluginstall.
> > >> >>> >> >>>
> > >> >>> >> >>> The client also handles app creation, platform
> > >> >>>removal/addition, and
> > >> >>> >> >>> interpolating information from app's config.xml into the
> > >> >>>necessary
> > >> >>> >> >>>spots
> > >> >>> >> >>> in each native project.
> > >> >>> >> >>>
> > >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> > >> reinstein.mike@gmail.com>
> > >> >>> >> wrote:
> > >> >>> >> >>>
> > >> >>> >> >>> >Hey Filip,
> > >> >>> >> >>> >
> > >> >>> >> >>> >One thing I"m curious about, whats the difference between
> > >> >>> >> >>> >https://github.com/alunny/pluginstall and
> > >> >>> >> >>>
> > >> >>> >>>
> > >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> >>> >> >>> >
> > >> >>> >> >>> >there seems to be some overlap there. Is pluginstall a
> > subset
> > >> >>>of
> > >> >>> >> >>> >functionality just related to plugins that has moved into
> > >> >>> >> >>>cordova-client
> > >> >>> >> >>> >or
> > >> >>> >> >>> >is it different?
> > >> >>> >> >>> >
> > >> >>> >> >>> >It seems like cordova-client is the most mature codebase
> > that
> > >> >>> >> >>>incorporates
> > >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding
> to
> > >> >>>see if
> > >> >>> >> >>> >everythign is in cordova-client or not. Said differently,
> is
> > >> it
> > >> >>> >>safe
> > >> >>> >> >>>to
> > >> >>> >> >>> >assume that just about all the worthwhile code is in
> > >> >>> >>cordova-client?
> > >> >>> >> >>> >
> > >> >>> >> >>> >-Mike
> > >> >>> >> >>> >
> > >> >>> >> >>> >
> > >> >>> >> >>> >
> > >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fil@adobe.com
> >
> > >> >>>wrote:
> > >> >>> >> >>> >
> > >> >>> >> >>> >> All looks good to me Mike.
> > >> >>> >> >>> >>
> > >> >>> >> >>> >> I think the "PluginDesign" wiki article would be a great
> > >> >>>place to
> > >> >>> >> >>> >> summarize / revamp all this info. Appreciate you
> tackling
> > >> >>>this!
> > >> >>> >> >>> >>
> > >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> > >> >>><re...@gmail.com>
> > >> >>> >> >>>wrote:
> > >> >>> >> >>> >>
> > >> >>> >> >>> >> >Hey Filip, Brian:
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >I think where I'd like to start is on documentation. I
> > may
> > >> >>>be
> > >> >>> >>wrong
> > >> >>> >> >>> >>about
> > >> >>> >> >>> >> >this, but it seems like there are bits and pieces of
> docs
> > >> in
> > >> >>> >> >>>various
> > >> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a
> good
> > >> >>>start
> > >> >>> >>is
> > >> >>> >> >>>for
> > >> >>> >> >>> >>me
> > >> >>> >> >>> >> >to find all these pieces, consolidate into a "master"
> > >> >>>document,
> > >> >>> >>and
> > >> >>> >> >>> >>cull
> > >> >>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing
> > of
> > >> >>>the
> > >> >>> >> >>>various
> > >> >>> >> >>> >> >links, etc that you've sent to me. Please take a look
> and
> > >> >>>let me
> > >> >>> >> >>>know
> > >> >>> >> >>> >>if
> > >> >>> >> >>> >> >I've characterised the content/purpose of these various
> > >> >>>links:
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> > >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >The implementation that manages plugin usage is here:
> > >> >>> >> >>> >>
> > >> >>> >> >>>>
> > >> >>>
> > https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> >>> >> >>> >> >This project encompasses more than just plugins because
> > it
> > >> >>>also
> > >> >>> >> >>>handles
> > >> >>> >> >>> >> >everything related to building, deploying, and managing
> > >> >>>cordova
> > >> >>> >> >>> >> >applications
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >These plugins are most popular, and should ideally work
> > >> >>>with the
> > >> >>> >> >>> >> >cordova-client implemenation:
> > >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >This implementation by Drew was an initial proof of
> > >> concept,
> > >> >>> >>which
> > >> >>> >> >>>only
> > >> >>> >> >>> >> >works for blackberry and has been abandoned in favor of
> > >> >>> >> >>>cordova-client,
> > >> >>> >> >>> >> >with much of his ideas having made it into
> > cordova-client:
> > >> >>> >> >>> >> >
> https://github.com/deedubbu/cordova-blackberry-pluggable
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >This doc contains some info on the format of the
> command
> > >> >>>line
> > >> >>> >> >>>interface
> > >> >>> >> >>> >> >and
> > >> >>> >> >>> >> >directory structure of cordova-client:
> > >> >>> >> >>> >> >
> http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >This doc contains some documentation on Drew's old
> > >> >>> >>implementation,
> > >> >>> >> >>>and
> > >> >>> >> >>> >>is
> > >> >>> >> >>> >> >out of date now:
> > >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >I want to emphasize that I'm just trying to get a
> handle
> > on
> > >> >>>what
> > >> >>> >> >>>docs
> > >> >>> >> >>> >>are
> > >> >>> >> >>> >> >relevant and which links contain what. I'm not judging
> > >> >>>anyone's
> > >> >>> >> >>>work or
> > >> >>> >> >>> >> >anything like that. :) If I've got the wrong idea about
> > >> what
> > >> >>> >>these
> > >> >>> >> >>> >>links
> > >> >>> >> >>> >> >represent or contain, _please_ let me know.
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >-Mike
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >*
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> > fil@adobe.com>
> > >> >>> >>wrote:
> > >> >>> >> >>> >> >
> > >> >>> >> >>> >> >> The cordova client CLI tooling top-level project goes
> > >> >>> >> >>>hand-in-hand
> > >> >>> >> >>> >>with
> > >> >>> >> >>> >> >> this spec. Code here:
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >>
> > >> >>> >> >>> >>
> > >> >>> >> >>>
> > >> >>> >> >>>
> > >> >>> >>
> > >> >>>
> > >> >>>
> > >>
> > https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> > >> >>> >> >>>h
> > >> >>> >> >>> >> >>or
> > >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
> > >> >>>plugins out
> > >> >>> >> >>>in the
> > >> >>> >> >>> >> >>wild
> > >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with
> > >> this
> > >> >>> >>spec.
> > >> >>> >> >>>Do
> > >> >>> >> >>> we
> > >> >>> >> >>> >> >>need
> > >> >>> >> >>> >> >> to account for anything else?
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >> I think the one outstanding question is how to handle
> > >> >>> >> >>>installation /
> > >> >>> >> >>> >> >> compatibility with different versions of cordova.
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >> Documentation for the tool as well as the spec (put
> it
> > on
> > >> >>>the
> > >> >>> >> >>>wiki,
> > >> >>> >> >>> >> >> perhaps) would be awesome!
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> > >> >>> >><re...@gmail.com>
> > >> >>> >> >>> >>wrote:
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >> >Hi Brian, Filip,
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love
> to
> > >> >>>dig in
> > >> >>> >> >>>and
> > >> >>> >> >>> >>start
> > >> >>> >> >>> >> >> >helping, where do you feel the most help is needed
> at
> > >> the
> > >> >>> >> >>>moment?
> > >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >-Mike
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> > >> >>><fi...@adobe.com>
> > >> >>> >> >>>wrote:
> > >> >>> >> >>> >> >> >
> > >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec"
> we
> > >> are
> > >> >>> >> >>>working
> > >> >>> >> >>> >> >>towards:
> > >> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> > >> >>> >> >>> >> >> >>
> > >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io>
> > wrote:
> > >> >>> >> >>> >> >> >>
> > >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place!
> Currently
> > >> the
> > >> >>> >>plugin
> > >> >>> >> >>> >> >>tooling
> > >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and
> > >> >>>myself.
> > >> >>> >> >>>(sorry
> > >> >>> >> >>> >>for
> > >> >>> >> >>> >> >>the
> > >> >>> >> >>> >> >> >> >delayed response / many of us are on a summer
> break
> > >> >>>after
> > >> >>> >> >>> >>shipping
> > >> >>> >> >>> >> >> >> >2.0)
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >We're loosely collaborating using this list, git,
> > and
> > >> >>> >>these
> > >> >>> >> >>>wiki
> > >> >>> >> >>> >> >>pages:
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> > >> >>> >> >>> >> >> >> >-
> > >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch
> which
> > >> >>>you
> > >> >>> >>can
> > >> >>> >> >>> >>preview
> > >> >>> >> >>> >> >>on
> > >> >>> >> >>> >> >> >> >the Github mirror here:
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >>
> > >> >>> >>
> > >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >You will want to start by reading up on our
> contrib
> > >> >>> >>process
> > >> >>> >> >>>in
> > >> >>> >> >>> >>the
> > >> >>> >> >>> >> >> >>wiki:
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >
> http://wiki.apache.org/cordova/ContributerWorkflow
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >And in the case of labs projects everything stays
> > on
> > >> >>>its
> > >> >>> >>own
> > >> >>> >> >>> >>branch
> > >> >>> >> >>> >> >> >> >until such a time that we feel its solid for its
> > own
> > >> >>>repo.
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >* * *
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >Let me know any q's!
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >
> > >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> > >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> > >> >>> >> >>> >> >> >> >> Hey there,
> > >> >>> >> >>> >> >> >> >>
> > >> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin
> > system
> > >> >>> >>that is
> > >> >>> >> >>> >> >> >> >>forthcoming. Is
> > >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are
> the
> > >> >>>right
> > >> >>> >> >>>people
> > >> >>> >> >>> >>to
> > >> >>> >> >>> >> >>talk
> > >> >>> >> >>> >> >> >> >>to?
> > >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> > experienced
> > >> >>> >> >>>developer,
> > >> >>> >> >>> >> >>have
> > >> >>> >> >>> >> >> >> >>worked
> > >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would
> love
> > to
> > >> >>>give
> > >> >>> >> >>>back
> > >> >>> >> >>> >>to
> > >> >>> >> >>> >> >>the
> > >> >>> >> >>> >> >> >> >> community.
> > >> >>> >> >>> >> >> >> >>
> > >> >>> >> >>> >> >> >> >> cheers,
> > >> >>> >> >>> >> >> >> >>
> > >> >>> >> >>> >> >> >> >> -Mike
> > >> >>> >> >>> >> >> >>
> > >> >>> >> >>> >> >> >>
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >> >>
> > >> >>> >> >>> >>
> > >> >>> >> >>> >>
> > >> >>> >> >>>
> > >> >>> >> >>>
> > >> >>> >>
> > >> >>> >>
> > >> >>>
> > >> >>>
> > >>
> > >>
> > >
> >
>
Re: plugin tooling/specification
Posted by Anis KADRI <an...@gmail.com>.
Hi Mike,
pluginstall-with-git support is just an experiment that I did a while back
(it takes git URLs as well as local paths). I suggest you base your work on
alunny's pluginstall until/if those changes get merged.
Cheers
Anis
On Fri, Sep 7, 2012 at 6:14 PM, Mike Reinstein <re...@gmail.com>wrote:
> I see 2 repositories for pluginstall:
>
>
> https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-git-support
>
> and Andrew's:
> https://github.com/alunny/pluginstall
>
> When consolidating the pluginstall and plugin format docs I forked Andrew's
> repo. Should I instead have used the pluginstall-with-git-support repo as
> my base?
>
> -Mike
>
> On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein <reinstein.mike@gmail.com
> >wrote:
>
> > My username is nekoflux.
> >
> >
> >
> > On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> JIRA is separate, we can assign issues to you (if you so wish).
> >>
> >> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
> >>
> >> >Registration is open - let us know what your user account is once you
> >> >do that, for assigning issues to yourself you need us to add you to a
> >> >contributors group.
> >> >
> >> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <
> reinstein.mike@gmail.com
> >> >
> >> >wrote:
> >> >> Okay, will do. Any feedback on the other comments? I'll proceed with
> >> >> merging the cordova-client and command line tooling spec next. I
> >> >>suppose it
> >> >> probably makes sense for me to start working out of JIRA so these
> tasks
> >> >>can
> >> >> be tracked. Is registration open or do I need to get permission from
> an
> >> >> admin for an account?
> >> >>
> >> >>
> >> >>
> >> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >>> Sorry for the late reply, this looks awesome!
> >> >>>
> >> >>> The one modification I would do is remove "www" as a platform (you
> >> >>>have a
> >> >>> comment in there about that too).
> >> >>>
> >> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com>
> wrote:
> >> >>>
> >> >>> >> eventually we will move pluginstall into apache
> >> >>> >Okay, I wasn't sure if that would happen, so I went with the
> slightly
> >> >>>more
> >> >>> >conservative assumption, that pluginstall might live separately
> from
> >> >>> >cordova-client. But I get the impression this is a left-over notion
> >> >>>from
> >> >>> >when Andrew first built pluginstall and it wasn't clear then
> whether
> >> >>>or
> >> >>> >not
> >> >>> >it would take hold.
> >> >>> >
> >> >>> >I've got an initial version of the merged documentation for the
> >> >>> >pluginstall
> >> >>> >command line tool, and the specification doc. It's here
> >> >>> >https://github.com/mreinstein/pluginstall
> >> >>> >
> >> >>> >I've also added some comments on possible changes. Overall the doc
> is
> >> >>> >pretty tight, so it's largely unchanged. Would really appreciate
> >> >>> >constructive feedback on this. If it looks right I'll send a pull
> >> >>>request
> >> >>> >to alunny, and then proceed with merging cordova-client design doc
> >> >>>into
> >> >>> >the
> >> >>> >README on github.
> >> >>> >
> >> >>> >-Mike
> >> >>> >
> >> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>> >
> >> >>> >> +1 !
> >> >>> >>
> >> >>> >> (I THINK) eventually we will move pluginstall into apache
> (assuming
> >> >>>the
> >> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> >> >>> >>
> >> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >> >>> >>
> >> >>> >> >love it
> >> >>> >> >
> >> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >> >>> >><re...@gmail.com>
> >> >>> >> >wrote:
> >> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to
> review
> >> >>>the
> >> >>> >> >>docs
> >> >>> >> >> more carefully. I'm really impressed with how well written
> they
> >> >>>are.
> >> >>> >> >>What I
> >> >>> >> >> *think* makes the most sense is to consolidate into fewer
> >> >>>documents
> >> >>> >>so
> >> >>> >> >>that
> >> >>> >> >> it's not necessary to look at so many seperate places. Here's
> >> >>>what I
> >> >>> >> >> propose:
> >> >>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall
> >> >>>README.md
> >> >>> >> >> * merge the command line tooling design doc into the
> >> >>>cordova-client
> >> >>> >> >> README.md
> >> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge
> parts
> >> >>>of it
> >> >>> >> >>into
> >> >>> >> >> the above 2 docs
> >> >>> >> >>
> >> >>> >> >> I think what this gets us is 2 docs instead of 5, and it still
> >> >>> >>maintains
> >> >>> >> >> the nice loose coupling between alunny's pluginstall utility
> and
> >> >>>the
> >> >>> >> >>larger
> >> >>> >> >> cordova-client. I'm assuming this separation was the original
> >> >>>intent,
> >> >>> >> >> rather than having one monolithic tool.
> >> >>> >> >>
> >> >>> >> >> Would love feedback on this, I don't want to waste time doing
> it
> >> >>>and
> >> >>> >> >>find
> >> >>> >> >> out this isn't appropriate. :)
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com>
> >> wrote:
> >> >>> >> >>
> >> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the
> >> hard
> >> >>> >>work
> >> >>> >> >>>for
> >> >>> >> >>> programmatic plugin installation, which is just one of the
> apis
> >> >>> >> >>>available
> >> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
> >> >>>pluginstall.
> >> >>> >> >>>
> >> >>> >> >>> The client also handles app creation, platform
> >> >>>removal/addition, and
> >> >>> >> >>> interpolating information from app's config.xml into the
> >> >>>necessary
> >> >>> >> >>>spots
> >> >>> >> >>> in each native project.
> >> >>> >> >>>
> >> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
> >> reinstein.mike@gmail.com>
> >> >>> >> wrote:
> >> >>> >> >>>
> >> >>> >> >>> >Hey Filip,
> >> >>> >> >>> >
> >> >>> >> >>> >One thing I"m curious about, whats the difference between
> >> >>> >> >>> >https://github.com/alunny/pluginstall and
> >> >>> >> >>>
> >> >>> >>>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >> >>> >
> >> >>> >> >>> >there seems to be some overlap there. Is pluginstall a
> subset
> >> >>>of
> >> >>> >> >>> >functionality just related to plugins that has moved into
> >> >>> >> >>>cordova-client
> >> >>> >> >>> >or
> >> >>> >> >>> >is it different?
> >> >>> >> >>> >
> >> >>> >> >>> >It seems like cordova-client is the most mature codebase
> that
> >> >>> >> >>>incorporates
> >> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to
> >> >>>see if
> >> >>> >> >>> >everythign is in cordova-client or not. Said differently, is
> >> it
> >> >>> >>safe
> >> >>> >> >>>to
> >> >>> >> >>> >assume that just about all the worthwhile code is in
> >> >>> >>cordova-client?
> >> >>> >> >>> >
> >> >>> >> >>> >-Mike
> >> >>> >> >>> >
> >> >>> >> >>> >
> >> >>> >> >>> >
> >> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com>
> >> >>>wrote:
> >> >>> >> >>> >
> >> >>> >> >>> >> All looks good to me Mike.
> >> >>> >> >>> >>
> >> >>> >> >>> >> I think the "PluginDesign" wiki article would be a great
> >> >>>place to
> >> >>> >> >>> >> summarize / revamp all this info. Appreciate you tackling
> >> >>>this!
> >> >>> >> >>> >>
> >> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> >> >>><re...@gmail.com>
> >> >>> >> >>>wrote:
> >> >>> >> >>> >>
> >> >>> >> >>> >> >Hey Filip, Brian:
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >I think where I'd like to start is on documentation. I
> may
> >> >>>be
> >> >>> >>wrong
> >> >>> >> >>> >>about
> >> >>> >> >>> >> >this, but it seems like there are bits and pieces of docs
> >> in
> >> >>> >> >>>various
> >> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good
> >> >>>start
> >> >>> >>is
> >> >>> >> >>>for
> >> >>> >> >>> >>me
> >> >>> >> >>> >> >to find all these pieces, consolidate into a "master"
> >> >>>document,
> >> >>> >>and
> >> >>> >> >>> >>cull
> >> >>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing
> of
> >> >>>the
> >> >>> >> >>>various
> >> >>> >> >>> >> >links, etc that you've sent to me. Please take a look and
> >> >>>let me
> >> >>> >> >>>know
> >> >>> >> >>> >>if
> >> >>> >> >>> >> >I've characterised the content/purpose of these various
> >> >>>links:
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >*The spec for how plugins are declared is here:
> >> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >The implementation that manages plugin usage is here:
> >> >>> >> >>> >>
> >> >>> >> >>>>
> >> >>>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >> >>> >> >This project encompasses more than just plugins because
> it
> >> >>>also
> >> >>> >> >>>handles
> >> >>> >> >>> >> >everything related to building, deploying, and managing
> >> >>>cordova
> >> >>> >> >>> >> >applications
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >These plugins are most popular, and should ideally work
> >> >>>with the
> >> >>> >> >>> >> >cordova-client implemenation:
> >> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >This implementation by Drew was an initial proof of
> >> concept,
> >> >>> >>which
> >> >>> >> >>>only
> >> >>> >> >>> >> >works for blackberry and has been abandoned in favor of
> >> >>> >> >>>cordova-client,
> >> >>> >> >>> >> >with much of his ideas having made it into
> cordova-client:
> >> >>> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >This doc contains some info on the format of the command
> >> >>>line
> >> >>> >> >>>interface
> >> >>> >> >>> >> >and
> >> >>> >> >>> >> >directory structure of cordova-client:
> >> >>> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >This doc contains some documentation on Drew's old
> >> >>> >>implementation,
> >> >>> >> >>>and
> >> >>> >> >>> >>is
> >> >>> >> >>> >> >out of date now:
> >> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >I want to emphasize that I'm just trying to get a handle
> on
> >> >>>what
> >> >>> >> >>>docs
> >> >>> >> >>> >>are
> >> >>> >> >>> >> >relevant and which links contain what. I'm not judging
> >> >>>anyone's
> >> >>> >> >>>work or
> >> >>> >> >>> >> >anything like that. :) If I've got the wrong idea about
> >> what
> >> >>> >>these
> >> >>> >> >>> >>links
> >> >>> >> >>> >> >represent or contain, _please_ let me know.
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >-Mike
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >*
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <
> fil@adobe.com>
> >> >>> >>wrote:
> >> >>> >> >>> >> >
> >> >>> >> >>> >> >> The cordova client CLI tooling top-level project goes
> >> >>> >> >>>hand-in-hand
> >> >>> >> >>> >>with
> >> >>> >> >>> >> >> this spec. Code here:
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >>
> >> >>> >> >>> >>
> >> >>> >> >>> >>
> >> >>> >> >>>
> >> >>> >> >>>
> >> >>> >>
> >> >>>
> >> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >> >>> >> >>>h
> >> >>> >> >>> >> >>or
> >> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
> >> >>>plugins out
> >> >>> >> >>>in the
> >> >>> >> >>> >> >>wild
> >> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with
> >> this
> >> >>> >>spec.
> >> >>> >> >>>Do
> >> >>> >> >>> we
> >> >>> >> >>> >> >>need
> >> >>> >> >>> >> >> to account for anything else?
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >> I think the one outstanding question is how to handle
> >> >>> >> >>>installation /
> >> >>> >> >>> >> >> compatibility with different versions of cordova.
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >> Documentation for the tool as well as the spec (put it
> on
> >> >>>the
> >> >>> >> >>>wiki,
> >> >>> >> >>> >> >> perhaps) would be awesome!
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >> >>> >><re...@gmail.com>
> >> >>> >> >>> >>wrote:
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >> >Hi Brian, Filip,
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to
> >> >>>dig in
> >> >>> >> >>>and
> >> >>> >> >>> >>start
> >> >>> >> >>> >> >> >helping, where do you feel the most help is needed at
> >> the
> >> >>> >> >>>moment?
> >> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >-Mike
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> >> >>><fi...@adobe.com>
> >> >>> >> >>>wrote:
> >> >>> >> >>> >> >> >
> >> >>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we
> >> are
> >> >>> >> >>>working
> >> >>> >> >>> >> >>towards:
> >> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >> >>> >> >>> >> >> >>
> >> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io>
> wrote:
> >> >>> >> >>> >> >> >>
> >> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently
> >> the
> >> >>> >>plugin
> >> >>> >> >>> >> >>tooling
> >> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and
> >> >>>myself.
> >> >>> >> >>>(sorry
> >> >>> >> >>> >>for
> >> >>> >> >>> >> >>the
> >> >>> >> >>> >> >> >> >delayed response / many of us are on a summer break
> >> >>>after
> >> >>> >> >>> >>shipping
> >> >>> >> >>> >> >> >> >2.0)
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >We're loosely collaborating using this list, git,
> and
> >> >>> >>these
> >> >>> >> >>>wiki
> >> >>> >> >>> >> >>pages:
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >> >>> >> >>> >> >> >> >-
> >> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which
> >> >>>you
> >> >>> >>can
> >> >>> >> >>> >>preview
> >> >>> >> >>> >> >>on
> >> >>> >> >>> >> >> >> >the Github mirror here:
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >>
> >> >>> >>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >You will want to start by reading up on our contrib
> >> >>> >>process
> >> >>> >> >>>in
> >> >>> >> >>> >>the
> >> >>> >> >>> >> >> >>wiki:
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >And in the case of labs projects everything stays
> on
> >> >>>its
> >> >>> >>own
> >> >>> >> >>> >>branch
> >> >>> >> >>> >> >> >> >until such a time that we feel its solid for its
> own
> >> >>>repo.
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >* * *
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >Let me know any q's!
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >
> >> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> >> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >> >>> >> >>> >> >> >> >> Hey there,
> >> >>> >> >>> >> >> >> >>
> >> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin
> system
> >> >>> >>that is
> >> >>> >> >>> >> >> >> >>forthcoming. Is
> >> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are the
> >> >>>right
> >> >>> >> >>>people
> >> >>> >> >>> >>to
> >> >>> >> >>> >> >>talk
> >> >>> >> >>> >> >> >> >>to?
> >> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an
> experienced
> >> >>> >> >>>developer,
> >> >>> >> >>> >> >>have
> >> >>> >> >>> >> >> >> >>worked
> >> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would love
> to
> >> >>>give
> >> >>> >> >>>back
> >> >>> >> >>> >>to
> >> >>> >> >>> >> >>the
> >> >>> >> >>> >> >> >> >> community.
> >> >>> >> >>> >> >> >> >>
> >> >>> >> >>> >> >> >> >> cheers,
> >> >>> >> >>> >> >> >> >>
> >> >>> >> >>> >> >> >> >> -Mike
> >> >>> >> >>> >> >> >>
> >> >>> >> >>> >> >> >>
> >> >>> >> >>> >> >>
> >> >>> >> >>> >> >>
> >> >>> >> >>> >>
> >> >>> >> >>> >>
> >> >>> >> >>>
> >> >>> >> >>>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >>
> >>
> >
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
I see 2 repositories for pluginstall:
https://github.com/apache/incubator-cordova-labs/tree/pluginstall-with-git-support
and Andrew's:
https://github.com/alunny/pluginstall
When consolidating the pluginstall and plugin format docs I forked Andrew's
repo. Should I instead have used the pluginstall-with-git-support repo as
my base?
-Mike
On Fri, Sep 7, 2012 at 8:01 PM, Mike Reinstein <re...@gmail.com>wrote:
> My username is nekoflux.
>
>
>
> On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> JIRA is separate, we can assign issues to you (if you so wish).
>>
>> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>>
>> >Registration is open - let us know what your user account is once you
>> >do that, for assigning issues to yourself you need us to add you to a
>> >contributors group.
>> >
>> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <reinstein.mike@gmail.com
>> >
>> >wrote:
>> >> Okay, will do. Any feedback on the other comments? I'll proceed with
>> >> merging the cordova-client and command line tooling spec next. I
>> >>suppose it
>> >> probably makes sense for me to start working out of JIRA so these tasks
>> >>can
>> >> be tracked. Is registration open or do I need to get permission from an
>> >> admin for an account?
>> >>
>> >>
>> >>
>> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >>> Sorry for the late reply, this looks awesome!
>> >>>
>> >>> The one modification I would do is remove "www" as a platform (you
>> >>>have a
>> >>> comment in there about that too).
>> >>>
>> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>> >>>
>> >>> >> eventually we will move pluginstall into apache
>> >>> >Okay, I wasn't sure if that would happen, so I went with the slightly
>> >>>more
>> >>> >conservative assumption, that pluginstall might live separately from
>> >>> >cordova-client. But I get the impression this is a left-over notion
>> >>>from
>> >>> >when Andrew first built pluginstall and it wasn't clear then whether
>> >>>or
>> >>> >not
>> >>> >it would take hold.
>> >>> >
>> >>> >I've got an initial version of the merged documentation for the
>> >>> >pluginstall
>> >>> >command line tool, and the specification doc. It's here
>> >>> >https://github.com/mreinstein/pluginstall
>> >>> >
>> >>> >I've also added some comments on possible changes. Overall the doc is
>> >>> >pretty tight, so it's largely unchanged. Would really appreciate
>> >>> >constructive feedback on this. If it looks right I'll send a pull
>> >>>request
>> >>> >to alunny, and then proceed with merging cordova-client design doc
>> >>>into
>> >>> >the
>> >>> >README on github.
>> >>> >
>> >>> >-Mike
>> >>> >
>> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>> >
>> >>> >> +1 !
>> >>> >>
>> >>> >> (I THINK) eventually we will move pluginstall into apache (assuming
>> >>>the
>> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
>> >>> >>
>> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>> >>
>> >>> >> >love it
>> >>> >> >
>> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>> >>> >><re...@gmail.com>
>> >>> >> >wrote:
>> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to review
>> >>>the
>> >>> >> >>docs
>> >>> >> >> more carefully. I'm really impressed with how well written they
>> >>>are.
>> >>> >> >>What I
>> >>> >> >> *think* makes the most sense is to consolidate into fewer
>> >>>documents
>> >>> >>so
>> >>> >> >>that
>> >>> >> >> it's not necessary to look at so many seperate places. Here's
>> >>>what I
>> >>> >> >> propose:
>> >>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall
>> >>>README.md
>> >>> >> >> * merge the command line tooling design doc into the
>> >>>cordova-client
>> >>> >> >> README.md
>> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge parts
>> >>>of it
>> >>> >> >>into
>> >>> >> >> the above 2 docs
>> >>> >> >>
>> >>> >> >> I think what this gets us is 2 docs instead of 5, and it still
>> >>> >>maintains
>> >>> >> >> the nice loose coupling between alunny's pluginstall utility and
>> >>>the
>> >>> >> >>larger
>> >>> >> >> cordova-client. I'm assuming this separation was the original
>> >>>intent,
>> >>> >> >> rather than having one monolithic tool.
>> >>> >> >>
>> >>> >> >> Would love feedback on this, I don't want to waste time doing it
>> >>>and
>> >>> >> >>find
>> >>> >> >> out this isn't appropriate. :)
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com>
>> wrote:
>> >>> >> >>
>> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the
>> hard
>> >>> >>work
>> >>> >> >>>for
>> >>> >> >>> programmatic plugin installation, which is just one of the apis
>> >>> >> >>>available
>> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
>> >>>pluginstall.
>> >>> >> >>>
>> >>> >> >>> The client also handles app creation, platform
>> >>>removal/addition, and
>> >>> >> >>> interpolating information from app's config.xml into the
>> >>>necessary
>> >>> >> >>>spots
>> >>> >> >>> in each native project.
>> >>> >> >>>
>> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <
>> reinstein.mike@gmail.com>
>> >>> >> wrote:
>> >>> >> >>>
>> >>> >> >>> >Hey Filip,
>> >>> >> >>> >
>> >>> >> >>> >One thing I"m curious about, whats the difference between
>> >>> >> >>> >https://github.com/alunny/pluginstall and
>> >>> >> >>>
>> >>> >>>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >> >>> >
>> >>> >> >>> >there seems to be some overlap there. Is pluginstall a subset
>> >>>of
>> >>> >> >>> >functionality just related to plugins that has moved into
>> >>> >> >>>cordova-client
>> >>> >> >>> >or
>> >>> >> >>> >is it different?
>> >>> >> >>> >
>> >>> >> >>> >It seems like cordova-client is the most mature codebase that
>> >>> >> >>>incorporates
>> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to
>> >>>see if
>> >>> >> >>> >everythign is in cordova-client or not. Said differently, is
>> it
>> >>> >>safe
>> >>> >> >>>to
>> >>> >> >>> >assume that just about all the worthwhile code is in
>> >>> >>cordova-client?
>> >>> >> >>> >
>> >>> >> >>> >-Mike
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >
>> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com>
>> >>>wrote:
>> >>> >> >>> >
>> >>> >> >>> >> All looks good to me Mike.
>> >>> >> >>> >>
>> >>> >> >>> >> I think the "PluginDesign" wiki article would be a great
>> >>>place to
>> >>> >> >>> >> summarize / revamp all this info. Appreciate you tackling
>> >>>this!
>> >>> >> >>> >>
>> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
>> >>><re...@gmail.com>
>> >>> >> >>>wrote:
>> >>> >> >>> >>
>> >>> >> >>> >> >Hey Filip, Brian:
>> >>> >> >>> >> >
>> >>> >> >>> >> >I think where I'd like to start is on documentation. I may
>> >>>be
>> >>> >>wrong
>> >>> >> >>> >>about
>> >>> >> >>> >> >this, but it seems like there are bits and pieces of docs
>> in
>> >>> >> >>>various
>> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good
>> >>>start
>> >>> >>is
>> >>> >> >>>for
>> >>> >> >>> >>me
>> >>> >> >>> >> >to find all these pieces, consolidate into a "master"
>> >>>document,
>> >>> >>and
>> >>> >> >>> >>cull
>> >>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing of
>> >>>the
>> >>> >> >>>various
>> >>> >> >>> >> >links, etc that you've sent to me. Please take a look and
>> >>>let me
>> >>> >> >>>know
>> >>> >> >>> >>if
>> >>> >> >>> >> >I've characterised the content/purpose of these various
>> >>>links:
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >*The spec for how plugins are declared is here:
>> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> >>> >> >>> >> >
>> >>> >> >>> >> >The implementation that manages plugin usage is here:
>> >>> >> >>> >>
>> >>> >> >>>>
>> >>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >> >>> >> >This project encompasses more than just plugins because it
>> >>>also
>> >>> >> >>>handles
>> >>> >> >>> >> >everything related to building, deploying, and managing
>> >>>cordova
>> >>> >> >>> >> >applications
>> >>> >> >>> >> >
>> >>> >> >>> >> >These plugins are most popular, and should ideally work
>> >>>with the
>> >>> >> >>> >> >cordova-client implemenation:
>> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >This implementation by Drew was an initial proof of
>> concept,
>> >>> >>which
>> >>> >> >>>only
>> >>> >> >>> >> >works for blackberry and has been abandoned in favor of
>> >>> >> >>>cordova-client,
>> >>> >> >>> >> >with much of his ideas having made it into cordova-client:
>> >>> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>> >>> >> >>> >> >
>> >>> >> >>> >> >This doc contains some info on the format of the command
>> >>>line
>> >>> >> >>>interface
>> >>> >> >>> >> >and
>> >>> >> >>> >> >directory structure of cordova-client:
>> >>> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>> >> >>> >> >
>> >>> >> >>> >> >This doc contains some documentation on Drew's old
>> >>> >>implementation,
>> >>> >> >>>and
>> >>> >> >>> >>is
>> >>> >> >>> >> >out of date now:
>> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >I want to emphasize that I'm just trying to get a handle on
>> >>>what
>> >>> >> >>>docs
>> >>> >> >>> >>are
>> >>> >> >>> >> >relevant and which links contain what. I'm not judging
>> >>>anyone's
>> >>> >> >>>work or
>> >>> >> >>> >> >anything like that. :) If I've got the wrong idea about
>> what
>> >>> >>these
>> >>> >> >>> >>links
>> >>> >> >>> >> >represent or contain, _please_ let me know.
>> >>> >> >>> >> >
>> >>> >> >>> >> >-Mike
>> >>> >> >>> >> >
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >*
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >
>> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
>> >>> >>wrote:
>> >>> >> >>> >> >
>> >>> >> >>> >> >> The cordova client CLI tooling top-level project goes
>> >>> >> >>>hand-in-hand
>> >>> >> >>> >>with
>> >>> >> >>> >> >> this spec. Code here:
>> >>> >> >>> >> >>
>> >>> >> >>> >> >>
>> >>> >> >>> >>
>> >>> >> >>> >>
>> >>> >> >>>
>> >>> >> >>>
>> >>> >>
>> >>>
>> >>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> >>> >> >>>h
>> >>> >> >>> >> >>or
>> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>> >>> >> >>> >> >>
>> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
>> >>>plugins out
>> >>> >> >>>in the
>> >>> >> >>> >> >>wild
>> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with
>> this
>> >>> >>spec.
>> >>> >> >>>Do
>> >>> >> >>> we
>> >>> >> >>> >> >>need
>> >>> >> >>> >> >> to account for anything else?
>> >>> >> >>> >> >>
>> >>> >> >>> >> >> I think the one outstanding question is how to handle
>> >>> >> >>>installation /
>> >>> >> >>> >> >> compatibility with different versions of cordova.
>> >>> >> >>> >> >>
>> >>> >> >>> >> >> Documentation for the tool as well as the spec (put it on
>> >>>the
>> >>> >> >>>wiki,
>> >>> >> >>> >> >> perhaps) would be awesome!
>> >>> >> >>> >> >>
>> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>> >>> >><re...@gmail.com>
>> >>> >> >>> >>wrote:
>> >>> >> >>> >> >>
>> >>> >> >>> >> >> >Hi Brian, Filip,
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to
>> >>>dig in
>> >>> >> >>>and
>> >>> >> >>> >>start
>> >>> >> >>> >> >> >helping, where do you feel the most help is needed at
>> the
>> >>> >> >>>moment?
>> >>> >> >>> >> >> >Documentation? Any specific code tasks?
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >-Mike
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
>> >>><fi...@adobe.com>
>> >>> >> >>>wrote:
>> >>> >> >>> >> >> >
>> >>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we
>> are
>> >>> >> >>>working
>> >>> >> >>> >> >>towards:
>> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>> >>> >> >>> >> >> >>
>> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>> >> >>> >> >> >>
>> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently
>> the
>> >>> >>plugin
>> >>> >> >>> >> >>tooling
>> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and
>> >>>myself.
>> >>> >> >>>(sorry
>> >>> >> >>> >>for
>> >>> >> >>> >> >>the
>> >>> >> >>> >> >> >> >delayed response / many of us are on a summer break
>> >>>after
>> >>> >> >>> >>shipping
>> >>> >> >>> >> >> >> >2.0)
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >We're loosely collaborating using this list, git, and
>> >>> >>these
>> >>> >> >>>wiki
>> >>> >> >>> >> >>pages:
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>> >>> >> >>> >> >> >> >-
>> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which
>> >>>you
>> >>> >>can
>> >>> >> >>> >>preview
>> >>> >> >>> >> >>on
>> >>> >> >>> >> >> >> >the Github mirror here:
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >>
>> >>> >>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >You will want to start by reading up on our contrib
>> >>> >>process
>> >>> >> >>>in
>> >>> >> >>> >>the
>> >>> >> >>> >> >> >>wiki:
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >And in the case of labs projects everything stays on
>> >>>its
>> >>> >>own
>> >>> >> >>> >>branch
>> >>> >> >>> >> >> >> >until such a time that we feel its solid for its own
>> >>>repo.
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >* * *
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >Let me know any q's!
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >
>> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>> >>> >> >>> >> >> >> >> Hey there,
>> >>> >> >>> >> >> >> >>
>> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin system
>> >>> >>that is
>> >>> >> >>> >> >> >> >>forthcoming. Is
>> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are the
>> >>>right
>> >>> >> >>>people
>> >>> >> >>> >>to
>> >>> >> >>> >> >>talk
>> >>> >> >>> >> >> >> >>to?
>> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an experienced
>> >>> >> >>>developer,
>> >>> >> >>> >> >>have
>> >>> >> >>> >> >> >> >>worked
>> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would love to
>> >>>give
>> >>> >> >>>back
>> >>> >> >>> >>to
>> >>> >> >>> >> >>the
>> >>> >> >>> >> >> >> >> community.
>> >>> >> >>> >> >> >> >>
>> >>> >> >>> >> >> >> >> cheers,
>> >>> >> >>> >> >> >> >>
>> >>> >> >>> >> >> >> >> -Mike
>> >>> >> >>> >> >> >>
>> >>> >> >>> >> >> >>
>> >>> >> >>> >> >>
>> >>> >> >>> >> >>
>> >>> >> >>> >>
>> >>> >> >>> >>
>> >>> >> >>>
>> >>> >> >>>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>>
>>
>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
My username is nekoflux.
On Fri, Sep 7, 2012 at 7:53 PM, Filip Maj <fi...@adobe.com> wrote:
> JIRA is separate, we can assign issues to you (if you so wish).
>
> On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>
> >Registration is open - let us know what your user account is once you
> >do that, for assigning issues to yourself you need us to add you to a
> >contributors group.
> >
> >On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <re...@gmail.com>
> >wrote:
> >> Okay, will do. Any feedback on the other comments? I'll proceed with
> >> merging the cordova-client and command line tooling spec next. I
> >>suppose it
> >> probably makes sense for me to start working out of JIRA so these tasks
> >>can
> >> be tracked. Is registration open or do I need to get permission from an
> >> admin for an account?
> >>
> >>
> >>
> >> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >>> Sorry for the late reply, this looks awesome!
> >>>
> >>> The one modification I would do is remove "www" as a platform (you
> >>>have a
> >>> comment in there about that too).
> >>>
> >>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
> >>>
> >>> >> eventually we will move pluginstall into apache
> >>> >Okay, I wasn't sure if that would happen, so I went with the slightly
> >>>more
> >>> >conservative assumption, that pluginstall might live separately from
> >>> >cordova-client. But I get the impression this is a left-over notion
> >>>from
> >>> >when Andrew first built pluginstall and it wasn't clear then whether
> >>>or
> >>> >not
> >>> >it would take hold.
> >>> >
> >>> >I've got an initial version of the merged documentation for the
> >>> >pluginstall
> >>> >command line tool, and the specification doc. It's here
> >>> >https://github.com/mreinstein/pluginstall
> >>> >
> >>> >I've also added some comments on possible changes. Overall the doc is
> >>> >pretty tight, so it's largely unchanged. Would really appreciate
> >>> >constructive feedback on this. If it looks right I'll send a pull
> >>>request
> >>> >to alunny, and then proceed with merging cordova-client design doc
> >>>into
> >>> >the
> >>> >README on github.
> >>> >
> >>> >-Mike
> >>> >
> >>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
> >>> >
> >>> >> +1 !
> >>> >>
> >>> >> (I THINK) eventually we will move pluginstall into apache (assuming
> >>>the
> >>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> >>> >>
> >>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >>> >>
> >>> >> >love it
> >>> >> >
> >>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >>> >><re...@gmail.com>
> >>> >> >wrote:
> >>> >> >> Ah ok, thanks for the clarification. I've had a chance to review
> >>>the
> >>> >> >>docs
> >>> >> >> more carefully. I'm really impressed with how well written they
> >>>are.
> >>> >> >>What I
> >>> >> >> *think* makes the most sense is to consolidate into fewer
> >>>documents
> >>> >>so
> >>> >> >>that
> >>> >> >> it's not necessary to look at so many seperate places. Here's
> >>>what I
> >>> >> >> propose:
> >>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall
> >>>README.md
> >>> >> >> * merge the command line tooling design doc into the
> >>>cordova-client
> >>> >> >> README.md
> >>> >> >> * pull apart the cordova/PluginDesign wiki page and merge parts
> >>>of it
> >>> >> >>into
> >>> >> >> the above 2 docs
> >>> >> >>
> >>> >> >> I think what this gets us is 2 docs instead of 5, and it still
> >>> >>maintains
> >>> >> >> the nice loose coupling between alunny's pluginstall utility and
> >>>the
> >>> >> >>larger
> >>> >> >> cordova-client. I'm assuming this separation was the original
> >>>intent,
> >>> >> >> rather than having one monolithic tool.
> >>> >> >>
> >>> >> >> Would love feedback on this, I don't want to waste time doing it
> >>>and
> >>> >> >>find
> >>> >> >> out this isn't appropriate. :)
> >>> >> >>
> >>> >> >>
> >>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com>
> wrote:
> >>> >> >>
> >>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the hard
> >>> >>work
> >>> >> >>>for
> >>> >> >>> programmatic plugin installation, which is just one of the apis
> >>> >> >>>available
> >>> >> >>> in cordova-client. So, cordova=client "shells out" to
> >>>pluginstall.
> >>> >> >>>
> >>> >> >>> The client also handles app creation, platform
> >>>removal/addition, and
> >>> >> >>> interpolating information from app's config.xml into the
> >>>necessary
> >>> >> >>>spots
> >>> >> >>> in each native project.
> >>> >> >>>
> >>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <reinstein.mike@gmail.com
> >
> >>> >> wrote:
> >>> >> >>>
> >>> >> >>> >Hey Filip,
> >>> >> >>> >
> >>> >> >>> >One thing I"m curious about, whats the difference between
> >>> >> >>> >https://github.com/alunny/pluginstall and
> >>> >> >>>
> >>> >>>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >> >>> >
> >>> >> >>> >there seems to be some overlap there. Is pluginstall a subset
> >>>of
> >>> >> >>> >functionality just related to plugins that has moved into
> >>> >> >>>cordova-client
> >>> >> >>> >or
> >>> >> >>> >is it different?
> >>> >> >>> >
> >>> >> >>> >It seems like cordova-client is the most mature codebase that
> >>> >> >>>incorporates
> >>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to
> >>>see if
> >>> >> >>> >everythign is in cordova-client or not. Said differently, is it
> >>> >>safe
> >>> >> >>>to
> >>> >> >>> >assume that just about all the worthwhile code is in
> >>> >>cordova-client?
> >>> >> >>> >
> >>> >> >>> >-Mike
> >>> >> >>> >
> >>> >> >>> >
> >>> >> >>> >
> >>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com>
> >>>wrote:
> >>> >> >>> >
> >>> >> >>> >> All looks good to me Mike.
> >>> >> >>> >>
> >>> >> >>> >> I think the "PluginDesign" wiki article would be a great
> >>>place to
> >>> >> >>> >> summarize / revamp all this info. Appreciate you tackling
> >>>this!
> >>> >> >>> >>
> >>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
> >>><re...@gmail.com>
> >>> >> >>>wrote:
> >>> >> >>> >>
> >>> >> >>> >> >Hey Filip, Brian:
> >>> >> >>> >> >
> >>> >> >>> >> >I think where I'd like to start is on documentation. I may
> >>>be
> >>> >>wrong
> >>> >> >>> >>about
> >>> >> >>> >> >this, but it seems like there are bits and pieces of docs in
> >>> >> >>>various
> >>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good
> >>>start
> >>> >>is
> >>> >> >>>for
> >>> >> >>> >>me
> >>> >> >>> >> >to find all these pieces, consolidate into a "master"
> >>>document,
> >>> >>and
> >>> >> >>> >>cull
> >>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing of
> >>>the
> >>> >> >>>various
> >>> >> >>> >> >links, etc that you've sent to me. Please take a look and
> >>>let me
> >>> >> >>>know
> >>> >> >>> >>if
> >>> >> >>> >> >I've characterised the content/purpose of these various
> >>>links:
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >*The spec for how plugins are declared is here:
> >>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >>> >> >>> >> >
> >>> >> >>> >> >The implementation that manages plugin usage is here:
> >>> >> >>> >>
> >>> >> >>>>
> >>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >> >>> >> >This project encompasses more than just plugins because it
> >>>also
> >>> >> >>>handles
> >>> >> >>> >> >everything related to building, deploying, and managing
> >>>cordova
> >>> >> >>> >> >applications
> >>> >> >>> >> >
> >>> >> >>> >> >These plugins are most popular, and should ideally work
> >>>with the
> >>> >> >>> >> >cordova-client implemenation:
> >>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >This implementation by Drew was an initial proof of concept,
> >>> >>which
> >>> >> >>>only
> >>> >> >>> >> >works for blackberry and has been abandoned in favor of
> >>> >> >>>cordova-client,
> >>> >> >>> >> >with much of his ideas having made it into cordova-client:
> >>> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
> >>> >> >>> >> >
> >>> >> >>> >> >This doc contains some info on the format of the command
> >>>line
> >>> >> >>>interface
> >>> >> >>> >> >and
> >>> >> >>> >> >directory structure of cordova-client:
> >>> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>> >> >>> >> >
> >>> >> >>> >> >This doc contains some documentation on Drew's old
> >>> >>implementation,
> >>> >> >>>and
> >>> >> >>> >>is
> >>> >> >>> >> >out of date now:
> >>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >I want to emphasize that I'm just trying to get a handle on
> >>>what
> >>> >> >>>docs
> >>> >> >>> >>are
> >>> >> >>> >> >relevant and which links contain what. I'm not judging
> >>>anyone's
> >>> >> >>>work or
> >>> >> >>> >> >anything like that. :) If I've got the wrong idea about what
> >>> >>these
> >>> >> >>> >>links
> >>> >> >>> >> >represent or contain, _please_ let me know.
> >>> >> >>> >> >
> >>> >> >>> >> >-Mike
> >>> >> >>> >> >
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >*
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >
> >>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
> >>> >>wrote:
> >>> >> >>> >> >
> >>> >> >>> >> >> The cordova client CLI tooling top-level project goes
> >>> >> >>>hand-in-hand
> >>> >> >>> >>with
> >>> >> >>> >> >> this spec. Code here:
> >>> >> >>> >> >>
> >>> >> >>> >> >>
> >>> >> >>> >>
> >>> >> >>> >>
> >>> >> >>>
> >>> >> >>>
> >>> >>
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >>> >> >>>h
> >>> >> >>> >> >>or
> >>> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >>> >> >>> >> >>
> >>> >> >>> >> >> Essentially: vet the spec out to make sure popular
> >>>plugins out
> >>> >> >>>in the
> >>> >> >>> >> >>wild
> >>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this
> >>> >>spec.
> >>> >> >>>Do
> >>> >> >>> we
> >>> >> >>> >> >>need
> >>> >> >>> >> >> to account for anything else?
> >>> >> >>> >> >>
> >>> >> >>> >> >> I think the one outstanding question is how to handle
> >>> >> >>>installation /
> >>> >> >>> >> >> compatibility with different versions of cordova.
> >>> >> >>> >> >>
> >>> >> >>> >> >> Documentation for the tool as well as the spec (put it on
> >>>the
> >>> >> >>>wiki,
> >>> >> >>> >> >> perhaps) would be awesome!
> >>> >> >>> >> >>
> >>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >>> >><re...@gmail.com>
> >>> >> >>> >>wrote:
> >>> >> >>> >> >>
> >>> >> >>> >> >> >Hi Brian, Filip,
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to
> >>>dig in
> >>> >> >>>and
> >>> >> >>> >>start
> >>> >> >>> >> >> >helping, where do you feel the most help is needed at the
> >>> >> >>>moment?
> >>> >> >>> >> >> >Documentation? Any specific code tasks?
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >-Mike
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
> >>><fi...@adobe.com>
> >>> >> >>>wrote:
> >>> >> >>> >> >> >
> >>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
> >>> >> >>>working
> >>> >> >>> >> >>towards:
> >>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >>> >> >>> >> >> >>
> >>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >>> >> >>> >> >> >>
> >>> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the
> >>> >>plugin
> >>> >> >>> >> >>tooling
> >>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and
> >>>myself.
> >>> >> >>>(sorry
> >>> >> >>> >>for
> >>> >> >>> >> >>the
> >>> >> >>> >> >> >> >delayed response / many of us are on a summer break
> >>>after
> >>> >> >>> >>shipping
> >>> >> >>> >> >> >> >2.0)
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >We're loosely collaborating using this list, git, and
> >>> >>these
> >>> >> >>>wiki
> >>> >> >>> >> >>pages:
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >>> >> >>> >> >> >> >-
> >>>http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which
> >>>you
> >>> >>can
> >>> >> >>> >>preview
> >>> >> >>> >> >>on
> >>> >> >>> >> >> >> >the Github mirror here:
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >
> >>> >> >>> >>
> >>> >>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >You will want to start by reading up on our contrib
> >>> >>process
> >>> >> >>>in
> >>> >> >>> >>the
> >>> >> >>> >> >> >>wiki:
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >And in the case of labs projects everything stays on
> >>>its
> >>> >>own
> >>> >> >>> >>branch
> >>> >> >>> >> >> >> >until such a time that we feel its solid for its own
> >>>repo.
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >* * *
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >Let me know any q's!
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >
> >>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> >>> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >>> >> >>> >> >> >> >> Hey there,
> >>> >> >>> >> >> >> >>
> >>> >> >>> >> >> >> >> I'm interested in contributing to the plugin system
> >>> >>that is
> >>> >> >>> >> >> >> >>forthcoming. Is
> >>> >> >>> >> >> >> >> this the right place to bring it up? Who are the
> >>>right
> >>> >> >>>people
> >>> >> >>> >>to
> >>> >> >>> >> >>talk
> >>> >> >>> >> >> >> >>to?
> >>> >> >>> >> >> >> >> Where do you need the most help? I'm an experienced
> >>> >> >>>developer,
> >>> >> >>> >> >>have
> >>> >> >>> >> >> >> >>worked
> >>> >> >>> >> >> >> >> on a few phonegap based projects, and would love to
> >>>give
> >>> >> >>>back
> >>> >> >>> >>to
> >>> >> >>> >> >>the
> >>> >> >>> >> >> >> >> community.
> >>> >> >>> >> >> >> >>
> >>> >> >>> >> >> >> >> cheers,
> >>> >> >>> >> >> >> >>
> >>> >> >>> >> >> >> >> -Mike
> >>> >> >>> >> >> >>
> >>> >> >>> >> >> >>
> >>> >> >>> >> >>
> >>> >> >>> >> >>
> >>> >> >>> >>
> >>> >> >>> >>
> >>> >> >>>
> >>> >> >>>
> >>> >>
> >>> >>
> >>>
> >>>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
JIRA is separate, we can assign issues to you (if you so wish).
On 9/7/12 4:51 PM, "Shazron" <sh...@gmail.com> wrote:
>Registration is open - let us know what your user account is once you
>do that, for assigning issues to yourself you need us to add you to a
>contributors group.
>
>On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <re...@gmail.com>
>wrote:
>> Okay, will do. Any feedback on the other comments? I'll proceed with
>> merging the cordova-client and command line tooling spec next. I
>>suppose it
>> probably makes sense for me to start working out of JIRA so these tasks
>>can
>> be tracked. Is registration open or do I need to get permission from an
>> admin for an account?
>>
>>
>>
>> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>>> Sorry for the late reply, this looks awesome!
>>>
>>> The one modification I would do is remove "www" as a platform (you
>>>have a
>>> comment in there about that too).
>>>
>>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>>
>>> >> eventually we will move pluginstall into apache
>>> >Okay, I wasn't sure if that would happen, so I went with the slightly
>>>more
>>> >conservative assumption, that pluginstall might live separately from
>>> >cordova-client. But I get the impression this is a left-over notion
>>>from
>>> >when Andrew first built pluginstall and it wasn't clear then whether
>>>or
>>> >not
>>> >it would take hold.
>>> >
>>> >I've got an initial version of the merged documentation for the
>>> >pluginstall
>>> >command line tool, and the specification doc. It's here
>>> >https://github.com/mreinstein/pluginstall
>>> >
>>> >I've also added some comments on possible changes. Overall the doc is
>>> >pretty tight, so it's largely unchanged. Would really appreciate
>>> >constructive feedback on this. If it looks right I'll send a pull
>>>request
>>> >to alunny, and then proceed with merging cordova-client design doc
>>>into
>>> >the
>>> >README on github.
>>> >
>>> >-Mike
>>> >
>>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >
>>> >> +1 !
>>> >>
>>> >> (I THINK) eventually we will move pluginstall into apache (assuming
>>>the
>>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
>>> >>
>>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>> >>
>>> >> >love it
>>> >> >
>>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>>> >><re...@gmail.com>
>>> >> >wrote:
>>> >> >> Ah ok, thanks for the clarification. I've had a chance to review
>>>the
>>> >> >>docs
>>> >> >> more carefully. I'm really impressed with how well written they
>>>are.
>>> >> >>What I
>>> >> >> *think* makes the most sense is to consolidate into fewer
>>>documents
>>> >>so
>>> >> >>that
>>> >> >> it's not necessary to look at so many seperate places. Here's
>>>what I
>>> >> >> propose:
>>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall
>>>README.md
>>> >> >> * merge the command line tooling design doc into the
>>>cordova-client
>>> >> >> README.md
>>> >> >> * pull apart the cordova/PluginDesign wiki page and merge parts
>>>of it
>>> >> >>into
>>> >> >> the above 2 docs
>>> >> >>
>>> >> >> I think what this gets us is 2 docs instead of 5, and it still
>>> >>maintains
>>> >> >> the nice loose coupling between alunny's pluginstall utility and
>>>the
>>> >> >>larger
>>> >> >> cordova-client. I'm assuming this separation was the original
>>>intent,
>>> >> >> rather than having one monolithic tool.
>>> >> >>
>>> >> >> Would love feedback on this, I don't want to waste time doing it
>>>and
>>> >> >>find
>>> >> >> out this isn't appropriate. :)
>>> >> >>
>>> >> >>
>>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >> >>
>>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the hard
>>> >>work
>>> >> >>>for
>>> >> >>> programmatic plugin installation, which is just one of the apis
>>> >> >>>available
>>> >> >>> in cordova-client. So, cordova=client "shells out" to
>>>pluginstall.
>>> >> >>>
>>> >> >>> The client also handles app creation, platform
>>>removal/addition, and
>>> >> >>> interpolating information from app's config.xml into the
>>>necessary
>>> >> >>>spots
>>> >> >>> in each native project.
>>> >> >>>
>>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com>
>>> >> wrote:
>>> >> >>>
>>> >> >>> >Hey Filip,
>>> >> >>> >
>>> >> >>> >One thing I"m curious about, whats the difference between
>>> >> >>> >https://github.com/alunny/pluginstall and
>>> >> >>>
>>> >>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >> >>> >
>>> >> >>> >there seems to be some overlap there. Is pluginstall a subset
>>>of
>>> >> >>> >functionality just related to plugins that has moved into
>>> >> >>>cordova-client
>>> >> >>> >or
>>> >> >>> >is it different?
>>> >> >>> >
>>> >> >>> >It seems like cordova-client is the most mature codebase that
>>> >> >>>incorporates
>>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to
>>>see if
>>> >> >>> >everythign is in cordova-client or not. Said differently, is it
>>> >>safe
>>> >> >>>to
>>> >> >>> >assume that just about all the worthwhile code is in
>>> >>cordova-client?
>>> >> >>> >
>>> >> >>> >-Mike
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >
>>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com>
>>>wrote:
>>> >> >>> >
>>> >> >>> >> All looks good to me Mike.
>>> >> >>> >>
>>> >> >>> >> I think the "PluginDesign" wiki article would be a great
>>>place to
>>> >> >>> >> summarize / revamp all this info. Appreciate you tackling
>>>this!
>>> >> >>> >>
>>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein"
>>><re...@gmail.com>
>>> >> >>>wrote:
>>> >> >>> >>
>>> >> >>> >> >Hey Filip, Brian:
>>> >> >>> >> >
>>> >> >>> >> >I think where I'd like to start is on documentation. I may
>>>be
>>> >>wrong
>>> >> >>> >>about
>>> >> >>> >> >this, but it seems like there are bits and pieces of docs in
>>> >> >>>various
>>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good
>>>start
>>> >>is
>>> >> >>>for
>>> >> >>> >>me
>>> >> >>> >> >to find all these pieces, consolidate into a "master"
>>>document,
>>> >>and
>>> >> >>> >>cull
>>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing of
>>>the
>>> >> >>>various
>>> >> >>> >> >links, etc that you've sent to me. Please take a look and
>>>let me
>>> >> >>>know
>>> >> >>> >>if
>>> >> >>> >> >I've characterised the content/purpose of these various
>>>links:
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >*The spec for how plugins are declared is here:
>>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>>> >> >>> >> >
>>> >> >>> >> >The implementation that manages plugin usage is here:
>>> >> >>> >>
>>> >> >>>>
>>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >> >>> >> >This project encompasses more than just plugins because it
>>>also
>>> >> >>>handles
>>> >> >>> >> >everything related to building, deploying, and managing
>>>cordova
>>> >> >>> >> >applications
>>> >> >>> >> >
>>> >> >>> >> >These plugins are most popular, and should ideally work
>>>with the
>>> >> >>> >> >cordova-client implemenation:
>>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >This implementation by Drew was an initial proof of concept,
>>> >>which
>>> >> >>>only
>>> >> >>> >> >works for blackberry and has been abandoned in favor of
>>> >> >>>cordova-client,
>>> >> >>> >> >with much of his ideas having made it into cordova-client:
>>> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>>> >> >>> >> >
>>> >> >>> >> >This doc contains some info on the format of the command
>>>line
>>> >> >>>interface
>>> >> >>> >> >and
>>> >> >>> >> >directory structure of cordova-client:
>>> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>>> >> >>> >> >
>>> >> >>> >> >This doc contains some documentation on Drew's old
>>> >>implementation,
>>> >> >>>and
>>> >> >>> >>is
>>> >> >>> >> >out of date now:
>>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >I want to emphasize that I'm just trying to get a handle on
>>>what
>>> >> >>>docs
>>> >> >>> >>are
>>> >> >>> >> >relevant and which links contain what. I'm not judging
>>>anyone's
>>> >> >>>work or
>>> >> >>> >> >anything like that. :) If I've got the wrong idea about what
>>> >>these
>>> >> >>> >>links
>>> >> >>> >> >represent or contain, _please_ let me know.
>>> >> >>> >> >
>>> >> >>> >> >-Mike
>>> >> >>> >> >
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >*
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >
>>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
>>> >>wrote:
>>> >> >>> >> >
>>> >> >>> >> >> The cordova client CLI tooling top-level project goes
>>> >> >>>hand-in-hand
>>> >> >>> >>with
>>> >> >>> >> >> this spec. Code here:
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>>
>>> >> >>>
>>> >>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>>> >> >>>h
>>> >> >>> >> >>or
>>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>>> >> >>> >> >>
>>> >> >>> >> >> Essentially: vet the spec out to make sure popular
>>>plugins out
>>> >> >>>in the
>>> >> >>> >> >>wild
>>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this
>>> >>spec.
>>> >> >>>Do
>>> >> >>> we
>>> >> >>> >> >>need
>>> >> >>> >> >> to account for anything else?
>>> >> >>> >> >>
>>> >> >>> >> >> I think the one outstanding question is how to handle
>>> >> >>>installation /
>>> >> >>> >> >> compatibility with different versions of cordova.
>>> >> >>> >> >>
>>> >> >>> >> >> Documentation for the tool as well as the spec (put it on
>>>the
>>> >> >>>wiki,
>>> >> >>> >> >> perhaps) would be awesome!
>>> >> >>> >> >>
>>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>>> >><re...@gmail.com>
>>> >> >>> >>wrote:
>>> >> >>> >> >>
>>> >> >>> >> >> >Hi Brian, Filip,
>>> >> >>> >> >> >
>>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to
>>>dig in
>>> >> >>>and
>>> >> >>> >>start
>>> >> >>> >> >> >helping, where do you feel the most help is needed at the
>>> >> >>>moment?
>>> >> >>> >> >> >Documentation? Any specific code tasks?
>>> >> >>> >> >> >
>>> >> >>> >> >> >-Mike
>>> >> >>> >> >> >
>>> >> >>> >> >> >
>>> >> >>> >> >> >
>>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj
>>><fi...@adobe.com>
>>> >> >>>wrote:
>>> >> >>> >> >> >
>>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
>>> >> >>>working
>>> >> >>> >> >>towards:
>>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>> >> >>> >> >> >>
>>> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the
>>> >>plugin
>>> >> >>> >> >>tooling
>>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and
>>>myself.
>>> >> >>>(sorry
>>> >> >>> >>for
>>> >> >>> >> >>the
>>> >> >>> >> >> >> >delayed response / many of us are on a summer break
>>>after
>>> >> >>> >>shipping
>>> >> >>> >> >> >> >2.0)
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >We're loosely collaborating using this list, git, and
>>> >>these
>>> >> >>>wiki
>>> >> >>> >> >>pages:
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>>> >> >>> >> >> >> >-
>>>http://wiki.apache.org/cordova/CommandLineToolingDesign
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which
>>>you
>>> >>can
>>> >> >>> >>preview
>>> >> >>> >> >>on
>>> >> >>> >> >> >> >the Github mirror here:
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >
>>> >> >>> >>
>>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >You will want to start by reading up on our contrib
>>> >>process
>>> >> >>>in
>>> >> >>> >>the
>>> >> >>> >> >> >>wiki:
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >And in the case of labs projects everything stays on
>>>its
>>> >>own
>>> >> >>> >>branch
>>> >> >>> >> >> >> >until such a time that we feel its solid for its own
>>>repo.
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >* * *
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >Let me know any q's!
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >
>>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>>> >> >>> >> >> >> >> Hey there,
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> I'm interested in contributing to the plugin system
>>> >>that is
>>> >> >>> >> >> >> >>forthcoming. Is
>>> >> >>> >> >> >> >> this the right place to bring it up? Who are the
>>>right
>>> >> >>>people
>>> >> >>> >>to
>>> >> >>> >> >>talk
>>> >> >>> >> >> >> >>to?
>>> >> >>> >> >> >> >> Where do you need the most help? I'm an experienced
>>> >> >>>developer,
>>> >> >>> >> >>have
>>> >> >>> >> >> >> >>worked
>>> >> >>> >> >> >> >> on a few phonegap based projects, and would love to
>>>give
>>> >> >>>back
>>> >> >>> >>to
>>> >> >>> >> >>the
>>> >> >>> >> >> >> >> community.
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> cheers,
>>> >> >>> >> >> >> >>
>>> >> >>> >> >> >> >> -Mike
>>> >> >>> >> >> >>
>>> >> >>> >> >> >>
>>> >> >>> >> >>
>>> >> >>> >> >>
>>> >> >>> >>
>>> >> >>> >>
>>> >> >>>
>>> >> >>>
>>> >>
>>> >>
>>>
>>>
Re: plugin tooling/specification
Posted by Shazron <sh...@gmail.com>.
Registration is open - let us know what your user account is once you
do that, for assigning issues to yourself you need us to add you to a
contributors group.
On Fri, Sep 7, 2012 at 4:44 PM, Mike Reinstein <re...@gmail.com> wrote:
> Okay, will do. Any feedback on the other comments? I'll proceed with
> merging the cordova-client and command line tooling spec next. I suppose it
> probably makes sense for me to start working out of JIRA so these tasks can
> be tracked. Is registration open or do I need to get permission from an
> admin for an account?
>
>
>
> On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Sorry for the late reply, this looks awesome!
>>
>> The one modification I would do is remove "www" as a platform (you have a
>> comment in there about that too).
>>
>> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>
>> >> eventually we will move pluginstall into apache
>> >Okay, I wasn't sure if that would happen, so I went with the slightly more
>> >conservative assumption, that pluginstall might live separately from
>> >cordova-client. But I get the impression this is a left-over notion from
>> >when Andrew first built pluginstall and it wasn't clear then whether or
>> >not
>> >it would take hold.
>> >
>> >I've got an initial version of the merged documentation for the
>> >pluginstall
>> >command line tool, and the specification doc. It's here
>> >https://github.com/mreinstein/pluginstall
>> >
>> >I've also added some comments on possible changes. Overall the doc is
>> >pretty tight, so it's largely unchanged. Would really appreciate
>> >constructive feedback on this. If it looks right I'll send a pull request
>> >to alunny, and then proceed with merging cordova-client design doc into
>> >the
>> >README on github.
>> >
>> >-Mike
>> >
>> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> +1 !
>> >>
>> >> (I THINK) eventually we will move pluginstall into apache (assuming the
>> >> authors are cool with that) so it will go 2 docs -> 1 doc.
>> >>
>> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>
>> >> >love it
>> >> >
>> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>> >><re...@gmail.com>
>> >> >wrote:
>> >> >> Ah ok, thanks for the clarification. I've had a chance to review the
>> >> >>docs
>> >> >> more carefully. I'm really impressed with how well written they are.
>> >> >>What I
>> >> >> *think* makes the most sense is to consolidate into fewer documents
>> >>so
>> >> >>that
>> >> >> it's not necessary to look at so many seperate places. Here's what I
>> >> >> propose:
>> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
>> >> >> * merge the command line tooling design doc into the cordova-client
>> >> >> README.md
>> >> >> * pull apart the cordova/PluginDesign wiki page and merge parts of it
>> >> >>into
>> >> >> the above 2 docs
>> >> >>
>> >> >> I think what this gets us is 2 docs instead of 5, and it still
>> >>maintains
>> >> >> the nice loose coupling between alunny's pluginstall utility and the
>> >> >>larger
>> >> >> cordova-client. I'm assuming this separation was the original intent,
>> >> >> rather than having one monolithic tool.
>> >> >>
>> >> >> Would love feedback on this, I don't want to waste time doing it and
>> >> >>find
>> >> >> out this isn't appropriate. :)
>> >> >>
>> >> >>
>> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >>
>> >> >>> Cordova-client depends on pluginstall. Pluginstall does the hard
>> >>work
>> >> >>>for
>> >> >>> programmatic plugin installation, which is just one of the apis
>> >> >>>available
>> >> >>> in cordova-client. So, cordova=client "shells out" to pluginstall.
>> >> >>>
>> >> >>> The client also handles app creation, platform removal/addition, and
>> >> >>> interpolating information from app's config.xml into the necessary
>> >> >>>spots
>> >> >>> in each native project.
>> >> >>>
>> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com>
>> >> wrote:
>> >> >>>
>> >> >>> >Hey Filip,
>> >> >>> >
>> >> >>> >One thing I"m curious about, whats the difference between
>> >> >>> >https://github.com/alunny/pluginstall and
>> >> >>>
>> >>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> >>> >
>> >> >>> >there seems to be some overlap there. Is pluginstall a subset of
>> >> >>> >functionality just related to plugins that has moved into
>> >> >>>cordova-client
>> >> >>> >or
>> >> >>> >is it different?
>> >> >>> >
>> >> >>> >It seems like cordova-client is the most mature codebase that
>> >> >>>incorporates
>> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
>> >> >>> >everythign is in cordova-client or not. Said differently, is it
>> >>safe
>> >> >>>to
>> >> >>> >assume that just about all the worthwhile code is in
>> >>cordova-client?
>> >> >>> >
>> >> >>> >-Mike
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >>> >
>> >> >>> >> All looks good to me Mike.
>> >> >>> >>
>> >> >>> >> I think the "PluginDesign" wiki article would be a great place to
>> >> >>> >> summarize / revamp all this info. Appreciate you tackling this!
>> >> >>> >>
>> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com>
>> >> >>>wrote:
>> >> >>> >>
>> >> >>> >> >Hey Filip, Brian:
>> >> >>> >> >
>> >> >>> >> >I think where I'd like to start is on documentation. I may be
>> >>wrong
>> >> >>> >>about
>> >> >>> >> >this, but it seems like there are bits and pieces of docs in
>> >> >>>various
>> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good start
>> >>is
>> >> >>>for
>> >> >>> >>me
>> >> >>> >> >to find all these pieces, consolidate into a "master" document,
>> >>and
>> >> >>> >>cull
>> >> >>> >> >out the outdated bits? As a start, here's my rephrasing of the
>> >> >>>various
>> >> >>> >> >links, etc that you've sent to me. Please take a look and let me
>> >> >>>know
>> >> >>> >>if
>> >> >>> >> >I've characterised the content/purpose of these various links:
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >*The spec for how plugins are declared is here:
>> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> >> >>> >> >
>> >> >>> >> >The implementation that manages plugin usage is here:
>> >> >>> >>
>> >> >>>>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> >>> >> >This project encompasses more than just plugins because it also
>> >> >>>handles
>> >> >>> >> >everything related to building, deploying, and managing cordova
>> >> >>> >> >applications
>> >> >>> >> >
>> >> >>> >> >These plugins are most popular, and should ideally work with the
>> >> >>> >> >cordova-client implemenation:
>> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >This implementation by Drew was an initial proof of concept,
>> >>which
>> >> >>>only
>> >> >>> >> >works for blackberry and has been abandoned in favor of
>> >> >>>cordova-client,
>> >> >>> >> >with much of his ideas having made it into cordova-client:
>> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>> >> >>> >> >
>> >> >>> >> >This doc contains some info on the format of the command line
>> >> >>>interface
>> >> >>> >> >and
>> >> >>> >> >directory structure of cordova-client:
>> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> >>> >> >
>> >> >>> >> >This doc contains some documentation on Drew's old
>> >>implementation,
>> >> >>>and
>> >> >>> >>is
>> >> >>> >> >out of date now:
>> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >I want to emphasize that I'm just trying to get a handle on what
>> >> >>>docs
>> >> >>> >>are
>> >> >>> >> >relevant and which links contain what. I'm not judging anyone's
>> >> >>>work or
>> >> >>> >> >anything like that. :) If I've got the wrong idea about what
>> >>these
>> >> >>> >>links
>> >> >>> >> >represent or contain, _please_ let me know.
>> >> >>> >> >
>> >> >>> >> >-Mike
>> >> >>> >> >
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >*
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >
>> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
>> >>wrote:
>> >> >>> >> >
>> >> >>> >> >> The cordova client CLI tooling top-level project goes
>> >> >>>hand-in-hand
>> >> >>> >>with
>> >> >>> >> >> this spec. Code here:
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>>
>> >> >>>
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> >> >>>h
>> >> >>> >> >>or
>> >> >>> >> >> tlog;h=refs/heads/cordova-client
>> >> >>> >> >>
>> >> >>> >> >> Essentially: vet the spec out to make sure popular plugins out
>> >> >>>in the
>> >> >>> >> >>wild
>> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this
>> >>spec.
>> >> >>>Do
>> >> >>> we
>> >> >>> >> >>need
>> >> >>> >> >> to account for anything else?
>> >> >>> >> >>
>> >> >>> >> >> I think the one outstanding question is how to handle
>> >> >>>installation /
>> >> >>> >> >> compatibility with different versions of cordova.
>> >> >>> >> >>
>> >> >>> >> >> Documentation for the tool as well as the spec (put it on the
>> >> >>>wiki,
>> >> >>> >> >> perhaps) would be awesome!
>> >> >>> >> >>
>> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>> >><re...@gmail.com>
>> >> >>> >>wrote:
>> >> >>> >> >>
>> >> >>> >> >> >Hi Brian, Filip,
>> >> >>> >> >> >
>> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to dig in
>> >> >>>and
>> >> >>> >>start
>> >> >>> >> >> >helping, where do you feel the most help is needed at the
>> >> >>>moment?
>> >> >>> >> >> >Documentation? Any specific code tasks?
>> >> >>> >> >> >
>> >> >>> >> >> >-Mike
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> >
>> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com>
>> >> >>>wrote:
>> >> >>> >> >> >
>> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
>> >> >>>working
>> >> >>> >> >>towards:
>> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>> >> >>> >> >> >>
>> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >> >>> >> >> >>
>> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the
>> >>plugin
>> >> >>> >> >>tooling
>> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself.
>> >> >>>(sorry
>> >> >>> >>for
>> >> >>> >> >>the
>> >> >>> >> >> >> >delayed response / many of us are on a summer break after
>> >> >>> >>shipping
>> >> >>> >> >> >> >2.0)
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >We're loosely collaborating using this list, git, and
>> >>these
>> >> >>>wiki
>> >> >>> >> >>pages:
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>> >> >>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which you
>> >>can
>> >> >>> >>preview
>> >> >>> >> >>on
>> >> >>> >> >> >> >the Github mirror here:
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >
>> >> >>> >>
>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >You will want to start by reading up on our contrib
>> >>process
>> >> >>>in
>> >> >>> >>the
>> >> >>> >> >> >>wiki:
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >And in the case of labs projects everything stays on its
>> >>own
>> >> >>> >>branch
>> >> >>> >> >> >> >until such a time that we feel its solid for its own repo.
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >* * *
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >Let me know any q's!
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >
>> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>> >> >>> >> >> >> ><re...@gmail.com> wrote:
>> >> >>> >> >> >> >> Hey there,
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> I'm interested in contributing to the plugin system
>> >>that is
>> >> >>> >> >> >> >>forthcoming. Is
>> >> >>> >> >> >> >> this the right place to bring it up? Who are the right
>> >> >>>people
>> >> >>> >>to
>> >> >>> >> >>talk
>> >> >>> >> >> >> >>to?
>> >> >>> >> >> >> >> Where do you need the most help? I'm an experienced
>> >> >>>developer,
>> >> >>> >> >>have
>> >> >>> >> >> >> >>worked
>> >> >>> >> >> >> >> on a few phonegap based projects, and would love to give
>> >> >>>back
>> >> >>> >>to
>> >> >>> >> >>the
>> >> >>> >> >> >> >> community.
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> cheers,
>> >> >>> >> >> >> >>
>> >> >>> >> >> >> >> -Mike
>> >> >>> >> >> >>
>> >> >>> >> >> >>
>> >> >>> >> >>
>> >> >>> >> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>>
>> >> >>>
>> >>
>> >>
>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
Okay, will do. Any feedback on the other comments? I'll proceed with
merging the cordova-client and command line tooling spec next. I suppose it
probably makes sense for me to start working out of JIRA so these tasks can
be tracked. Is registration open or do I need to get permission from an
admin for an account?
On Fri, Sep 7, 2012 at 2:37 PM, Filip Maj <fi...@adobe.com> wrote:
> Sorry for the late reply, this looks awesome!
>
> The one modification I would do is remove "www" as a platform (you have a
> comment in there about that too).
>
> On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >> eventually we will move pluginstall into apache
> >Okay, I wasn't sure if that would happen, so I went with the slightly more
> >conservative assumption, that pluginstall might live separately from
> >cordova-client. But I get the impression this is a left-over notion from
> >when Andrew first built pluginstall and it wasn't clear then whether or
> >not
> >it would take hold.
> >
> >I've got an initial version of the merged documentation for the
> >pluginstall
> >command line tool, and the specification doc. It's here
> >https://github.com/mreinstein/pluginstall
> >
> >I've also added some comments on possible changes. Overall the doc is
> >pretty tight, so it's largely unchanged. Would really appreciate
> >constructive feedback on this. If it looks right I'll send a pull request
> >to alunny, and then proceed with merging cordova-client design doc into
> >the
> >README on github.
> >
> >-Mike
> >
> >On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> +1 !
> >>
> >> (I THINK) eventually we will move pluginstall into apache (assuming the
> >> authors are cool with that) so it will go 2 docs -> 1 doc.
> >>
> >> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >>
> >> >love it
> >> >
> >> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
> >><re...@gmail.com>
> >> >wrote:
> >> >> Ah ok, thanks for the clarification. I've had a chance to review the
> >> >>docs
> >> >> more carefully. I'm really impressed with how well written they are.
> >> >>What I
> >> >> *think* makes the most sense is to consolidate into fewer documents
> >>so
> >> >>that
> >> >> it's not necessary to look at so many seperate places. Here's what I
> >> >> propose:
> >> >> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
> >> >> * merge the command line tooling design doc into the cordova-client
> >> >> README.md
> >> >> * pull apart the cordova/PluginDesign wiki page and merge parts of it
> >> >>into
> >> >> the above 2 docs
> >> >>
> >> >> I think what this gets us is 2 docs instead of 5, and it still
> >>maintains
> >> >> the nice loose coupling between alunny's pluginstall utility and the
> >> >>larger
> >> >> cordova-client. I'm assuming this separation was the original intent,
> >> >> rather than having one monolithic tool.
> >> >>
> >> >> Would love feedback on this, I don't want to waste time doing it and
> >> >>find
> >> >> out this isn't appropriate. :)
> >> >>
> >> >>
> >> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>
> >> >>> Cordova-client depends on pluginstall. Pluginstall does the hard
> >>work
> >> >>>for
> >> >>> programmatic plugin installation, which is just one of the apis
> >> >>>available
> >> >>> in cordova-client. So, cordova=client "shells out" to pluginstall.
> >> >>>
> >> >>> The client also handles app creation, platform removal/addition, and
> >> >>> interpolating information from app's config.xml into the necessary
> >> >>>spots
> >> >>> in each native project.
> >> >>>
> >> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com>
> >> wrote:
> >> >>>
> >> >>> >Hey Filip,
> >> >>> >
> >> >>> >One thing I"m curious about, whats the difference between
> >> >>> >https://github.com/alunny/pluginstall and
> >> >>>
> >>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >
> >> >>> >there seems to be some overlap there. Is pluginstall a subset of
> >> >>> >functionality just related to plugins that has moved into
> >> >>>cordova-client
> >> >>> >or
> >> >>> >is it different?
> >> >>> >
> >> >>> >It seems like cordova-client is the most mature codebase that
> >> >>>incorporates
> >> >>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
> >> >>> >everythign is in cordova-client or not. Said differently, is it
> >>safe
> >> >>>to
> >> >>> >assume that just about all the worthwhile code is in
> >>cordova-client?
> >> >>> >
> >> >>> >-Mike
> >> >>> >
> >> >>> >
> >> >>> >
> >> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >>> >
> >> >>> >> All looks good to me Mike.
> >> >>> >>
> >> >>> >> I think the "PluginDesign" wiki article would be a great place to
> >> >>> >> summarize / revamp all this info. Appreciate you tackling this!
> >> >>> >>
> >> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com>
> >> >>>wrote:
> >> >>> >>
> >> >>> >> >Hey Filip, Brian:
> >> >>> >> >
> >> >>> >> >I think where I'd like to start is on documentation. I may be
> >>wrong
> >> >>> >>about
> >> >>> >> >this, but it seems like there are bits and pieces of docs in
> >> >>>various
> >> >>> >> >places, and some may be stale or irrelevant. Maybe a good start
> >>is
> >> >>>for
> >> >>> >>me
> >> >>> >> >to find all these pieces, consolidate into a "master" document,
> >>and
> >> >>> >>cull
> >> >>> >> >out the outdated bits? As a start, here's my rephrasing of the
> >> >>>various
> >> >>> >> >links, etc that you've sent to me. Please take a look and let me
> >> >>>know
> >> >>> >>if
> >> >>> >> >I've characterised the content/purpose of these various links:
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >*The spec for how plugins are declared is here:
> >> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >> >>> >> >
> >> >>> >> >The implementation that manages plugin usage is here:
> >> >>> >>
> >> >>>>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >> >This project encompasses more than just plugins because it also
> >> >>>handles
> >> >>> >> >everything related to building, deploying, and managing cordova
> >> >>> >> >applications
> >> >>> >> >
> >> >>> >> >These plugins are most popular, and should ideally work with the
> >> >>> >> >cordova-client implemenation:
> >> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >This implementation by Drew was an initial proof of concept,
> >>which
> >> >>>only
> >> >>> >> >works for blackberry and has been abandoned in favor of
> >> >>>cordova-client,
> >> >>> >> >with much of his ideas having made it into cordova-client:
> >> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
> >> >>> >> >
> >> >>> >> >This doc contains some info on the format of the command line
> >> >>>interface
> >> >>> >> >and
> >> >>> >> >directory structure of cordova-client:
> >> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>> >> >
> >> >>> >> >This doc contains some documentation on Drew's old
> >>implementation,
> >> >>>and
> >> >>> >>is
> >> >>> >> >out of date now:
> >> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >I want to emphasize that I'm just trying to get a handle on what
> >> >>>docs
> >> >>> >>are
> >> >>> >> >relevant and which links contain what. I'm not judging anyone's
> >> >>>work or
> >> >>> >> >anything like that. :) If I've got the wrong idea about what
> >>these
> >> >>> >>links
> >> >>> >> >represent or contain, _please_ let me know.
> >> >>> >> >
> >> >>> >> >-Mike
> >> >>> >> >
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >*
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >
> >> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
> >>wrote:
> >> >>> >> >
> >> >>> >> >> The cordova client CLI tooling top-level project goes
> >> >>>hand-in-hand
> >> >>> >>with
> >> >>> >> >> this spec. Code here:
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >> >>>h
> >> >>> >> >>or
> >> >>> >> >> tlog;h=refs/heads/cordova-client
> >> >>> >> >>
> >> >>> >> >> Essentially: vet the spec out to make sure popular plugins out
> >> >>>in the
> >> >>> >> >>wild
> >> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this
> >>spec.
> >> >>>Do
> >> >>> we
> >> >>> >> >>need
> >> >>> >> >> to account for anything else?
> >> >>> >> >>
> >> >>> >> >> I think the one outstanding question is how to handle
> >> >>>installation /
> >> >>> >> >> compatibility with different versions of cordova.
> >> >>> >> >>
> >> >>> >> >> Documentation for the tool as well as the spec (put it on the
> >> >>>wiki,
> >> >>> >> >> perhaps) would be awesome!
> >> >>> >> >>
> >> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
> >><re...@gmail.com>
> >> >>> >>wrote:
> >> >>> >> >>
> >> >>> >> >> >Hi Brian, Filip,
> >> >>> >> >> >
> >> >>> >> >> >Thanks for the pointers to those projects. I'd love to dig in
> >> >>>and
> >> >>> >>start
> >> >>> >> >> >helping, where do you feel the most help is needed at the
> >> >>>moment?
> >> >>> >> >> >Documentation? Any specific code tasks?
> >> >>> >> >> >
> >> >>> >> >> >-Mike
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >
> >> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com>
> >> >>>wrote:
> >> >>> >> >> >
> >> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
> >> >>>working
> >> >>> >> >>towards:
> >> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >> >>> >> >> >>
> >> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >> >>> >> >> >>
> >> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the
> >>plugin
> >> >>> >> >>tooling
> >> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself.
> >> >>>(sorry
> >> >>> >>for
> >> >>> >> >>the
> >> >>> >> >> >> >delayed response / many of us are on a summer break after
> >> >>> >>shipping
> >> >>> >> >> >> >2.0)
> >> >>> >> >> >> >
> >> >>> >> >> >> >We're loosely collaborating using this list, git, and
> >>these
> >> >>>wiki
> >> >>> >> >>pages:
> >> >>> >> >> >> >
> >> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >> >>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
> >> >>> >> >> >> >
> >> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which you
> >>can
> >> >>> >>preview
> >> >>> >> >>on
> >> >>> >> >> >> >the Github mirror here:
> >> >>> >> >> >> >
> >> >>> >> >> >> >
> >> >>> >>
> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >> >>> >> >> >> >
> >> >>> >> >> >> >You will want to start by reading up on our contrib
> >>process
> >> >>>in
> >> >>> >>the
> >> >>> >> >> >>wiki:
> >> >>> >> >> >> >
> >> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
> >> >>> >> >> >> >
> >> >>> >> >> >> >And in the case of labs projects everything stays on its
> >>own
> >> >>> >>branch
> >> >>> >> >> >> >until such a time that we feel its solid for its own repo.
> >> >>> >> >> >> >
> >> >>> >> >> >> >* * *
> >> >>> >> >> >> >
> >> >>> >> >> >> >Let me know any q's!
> >> >>> >> >> >> >
> >> >>> >> >> >> >
> >> >>> >> >> >> >
> >> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> >> >>> >> >> >> ><re...@gmail.com> wrote:
> >> >>> >> >> >> >> Hey there,
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> I'm interested in contributing to the plugin system
> >>that is
> >> >>> >> >> >> >>forthcoming. Is
> >> >>> >> >> >> >> this the right place to bring it up? Who are the right
> >> >>>people
> >> >>> >>to
> >> >>> >> >>talk
> >> >>> >> >> >> >>to?
> >> >>> >> >> >> >> Where do you need the most help? I'm an experienced
> >> >>>developer,
> >> >>> >> >>have
> >> >>> >> >> >> >>worked
> >> >>> >> >> >> >> on a few phonegap based projects, and would love to give
> >> >>>back
> >> >>> >>to
> >> >>> >> >>the
> >> >>> >> >> >> >> community.
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> cheers,
> >> >>> >> >> >> >>
> >> >>> >> >> >> >> -Mike
> >> >>> >> >> >>
> >> >>> >> >> >>
> >> >>> >> >>
> >> >>> >> >>
> >> >>> >>
> >> >>> >>
> >> >>>
> >> >>>
> >>
> >>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
Sorry for the late reply, this looks awesome!
The one modification I would do is remove "www" as a platform (you have a
comment in there about that too).
On 9/5/12 7:12 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>> eventually we will move pluginstall into apache
>Okay, I wasn't sure if that would happen, so I went with the slightly more
>conservative assumption, that pluginstall might live separately from
>cordova-client. But I get the impression this is a left-over notion from
>when Andrew first built pluginstall and it wasn't clear then whether or
>not
>it would take hold.
>
>I've got an initial version of the merged documentation for the
>pluginstall
>command line tool, and the specification doc. It's here
>https://github.com/mreinstein/pluginstall
>
>I've also added some comments on possible changes. Overall the doc is
>pretty tight, so it's largely unchanged. Would really appreciate
>constructive feedback on this. If it looks right I'll send a pull request
>to alunny, and then proceed with merging cordova-client design doc into
>the
>README on github.
>
>-Mike
>
>On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> +1 !
>>
>> (I THINK) eventually we will move pluginstall into apache (assuming the
>> authors are cool with that) so it will go 2 docs -> 1 doc.
>>
>> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>
>> >love it
>> >
>> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein
>><re...@gmail.com>
>> >wrote:
>> >> Ah ok, thanks for the clarification. I've had a chance to review the
>> >>docs
>> >> more carefully. I'm really impressed with how well written they are.
>> >>What I
>> >> *think* makes the most sense is to consolidate into fewer documents
>>so
>> >>that
>> >> it's not necessary to look at so many seperate places. Here's what I
>> >> propose:
>> >> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
>> >> * merge the command line tooling design doc into the cordova-client
>> >> README.md
>> >> * pull apart the cordova/PluginDesign wiki page and merge parts of it
>> >>into
>> >> the above 2 docs
>> >>
>> >> I think what this gets us is 2 docs instead of 5, and it still
>>maintains
>> >> the nice loose coupling between alunny's pluginstall utility and the
>> >>larger
>> >> cordova-client. I'm assuming this separation was the original intent,
>> >> rather than having one monolithic tool.
>> >>
>> >> Would love feedback on this, I don't want to waste time doing it and
>> >>find
>> >> out this isn't appropriate. :)
>> >>
>> >>
>> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >>> Cordova-client depends on pluginstall. Pluginstall does the hard
>>work
>> >>>for
>> >>> programmatic plugin installation, which is just one of the apis
>> >>>available
>> >>> in cordova-client. So, cordova=client "shells out" to pluginstall.
>> >>>
>> >>> The client also handles app creation, platform removal/addition, and
>> >>> interpolating information from app's config.xml into the necessary
>> >>>spots
>> >>> in each native project.
>> >>>
>> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com>
>> wrote:
>> >>>
>> >>> >Hey Filip,
>> >>> >
>> >>> >One thing I"m curious about, whats the difference between
>> >>> >https://github.com/alunny/pluginstall and
>> >>>
>>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >
>> >>> >there seems to be some overlap there. Is pluginstall a subset of
>> >>> >functionality just related to plugins that has moved into
>> >>>cordova-client
>> >>> >or
>> >>> >is it different?
>> >>> >
>> >>> >It seems like cordova-client is the most mature codebase that
>> >>>incorporates
>> >>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
>> >>> >everythign is in cordova-client or not. Said differently, is it
>>safe
>> >>>to
>> >>> >assume that just about all the worthwhile code is in
>>cordova-client?
>> >>> >
>> >>> >-Mike
>> >>> >
>> >>> >
>> >>> >
>> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
>> >>> >
>> >>> >> All looks good to me Mike.
>> >>> >>
>> >>> >> I think the "PluginDesign" wiki article would be a great place to
>> >>> >> summarize / revamp all this info. Appreciate you tackling this!
>> >>> >>
>> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com>
>> >>>wrote:
>> >>> >>
>> >>> >> >Hey Filip, Brian:
>> >>> >> >
>> >>> >> >I think where I'd like to start is on documentation. I may be
>>wrong
>> >>> >>about
>> >>> >> >this, but it seems like there are bits and pieces of docs in
>> >>>various
>> >>> >> >places, and some may be stale or irrelevant. Maybe a good start
>>is
>> >>>for
>> >>> >>me
>> >>> >> >to find all these pieces, consolidate into a "master" document,
>>and
>> >>> >>cull
>> >>> >> >out the outdated bits? As a start, here's my rephrasing of the
>> >>>various
>> >>> >> >links, etc that you've sent to me. Please take a look and let me
>> >>>know
>> >>> >>if
>> >>> >> >I've characterised the content/purpose of these various links:
>> >>> >> >
>> >>> >> >
>> >>> >> >*The spec for how plugins are declared is here:
>> >>> >> >https://github.com/alunny/cordova-plugin-spec
>> >>> >> >
>> >>> >> >The implementation that manages plugin usage is here:
>> >>> >>
>> >>>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >> >This project encompasses more than just plugins because it also
>> >>>handles
>> >>> >> >everything related to building, deploying, and managing cordova
>> >>> >> >applications
>> >>> >> >
>> >>> >> >These plugins are most popular, and should ideally work with the
>> >>> >> >cordova-client implemenation:
>> >>> >> >http://github.com/phonegap/phonegap-plugins*
>> >>> >> >*
>> >>> >> >*
>> >>> >> >This implementation by Drew was an initial proof of concept,
>>which
>> >>>only
>> >>> >> >works for blackberry and has been abandoned in favor of
>> >>>cordova-client,
>> >>> >> >with much of his ideas having made it into cordova-client:
>> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>> >>> >> >
>> >>> >> >This doc contains some info on the format of the command line
>> >>>interface
>> >>> >> >and
>> >>> >> >directory structure of cordova-client:
>> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>> >> >
>> >>> >> >This doc contains some documentation on Drew's old
>>implementation,
>> >>>and
>> >>> >>is
>> >>> >> >out of date now:
>> >>> >> >http://wiki.apache.org/cordova/PluginDesign
>> >>> >> >
>> >>> >> >
>> >>> >> >I want to emphasize that I'm just trying to get a handle on what
>> >>>docs
>> >>> >>are
>> >>> >> >relevant and which links contain what. I'm not judging anyone's
>> >>>work or
>> >>> >> >anything like that. :) If I've got the wrong idea about what
>>these
>> >>> >>links
>> >>> >> >represent or contain, _please_ let me know.
>> >>> >> >
>> >>> >> >-Mike
>> >>> >> >
>> >>> >> >*
>> >>> >> >*
>> >>> >> >*
>> >>> >> >*
>> >>> >> >*
>> >>> >> >*
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com>
>>wrote:
>> >>> >> >
>> >>> >> >> The cordova client CLI tooling top-level project goes
>> >>>hand-in-hand
>> >>> >>with
>> >>> >> >> this spec. Code here:
>> >>> >> >>
>> >>> >> >>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>> >>>h
>> >>> >> >>or
>> >>> >> >> tlog;h=refs/heads/cordova-client
>> >>> >> >>
>> >>> >> >> Essentially: vet the spec out to make sure popular plugins out
>> >>>in the
>> >>> >> >>wild
>> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this
>>spec.
>> >>>Do
>> >>> we
>> >>> >> >>need
>> >>> >> >> to account for anything else?
>> >>> >> >>
>> >>> >> >> I think the one outstanding question is how to handle
>> >>>installation /
>> >>> >> >> compatibility with different versions of cordova.
>> >>> >> >>
>> >>> >> >> Documentation for the tool as well as the spec (put it on the
>> >>>wiki,
>> >>> >> >> perhaps) would be awesome!
>> >>> >> >>
>> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein"
>><re...@gmail.com>
>> >>> >>wrote:
>> >>> >> >>
>> >>> >> >> >Hi Brian, Filip,
>> >>> >> >> >
>> >>> >> >> >Thanks for the pointers to those projects. I'd love to dig in
>> >>>and
>> >>> >>start
>> >>> >> >> >helping, where do you feel the most help is needed at the
>> >>>moment?
>> >>> >> >> >Documentation? Any specific code tasks?
>> >>> >> >> >
>> >>> >> >> >-Mike
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >
>> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com>
>> >>>wrote:
>> >>> >> >> >
>> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
>> >>>working
>> >>> >> >>towards:
>> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>> >>> >> >> >>
>> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >>> >> >> >>
>> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the
>>plugin
>> >>> >> >>tooling
>> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself.
>> >>>(sorry
>> >>> >>for
>> >>> >> >>the
>> >>> >> >> >> >delayed response / many of us are on a summer break after
>> >>> >>shipping
>> >>> >> >> >> >2.0)
>> >>> >> >> >> >
>> >>> >> >> >> >We're loosely collaborating using this list, git, and
>>these
>> >>>wiki
>> >>> >> >>pages:
>> >>> >> >> >> >
>> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>> >>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >>> >> >> >> >
>> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which you
>>can
>> >>> >>preview
>> >>> >> >>on
>> >>> >> >> >> >the Github mirror here:
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >>
>> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >>> >> >> >> >
>> >>> >> >> >> >You will want to start by reading up on our contrib
>>process
>> >>>in
>> >>> >>the
>> >>> >> >> >>wiki:
>> >>> >> >> >> >
>> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>> >>> >> >> >> >
>> >>> >> >> >> >And in the case of labs projects everything stays on its
>>own
>> >>> >>branch
>> >>> >> >> >> >until such a time that we feel its solid for its own repo.
>> >>> >> >> >> >
>> >>> >> >> >> >* * *
>> >>> >> >> >> >
>> >>> >> >> >> >Let me know any q's!
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >> >> >> >
>> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>> >>> >> >> >> ><re...@gmail.com> wrote:
>> >>> >> >> >> >> Hey there,
>> >>> >> >> >> >>
>> >>> >> >> >> >> I'm interested in contributing to the plugin system
>>that is
>> >>> >> >> >> >>forthcoming. Is
>> >>> >> >> >> >> this the right place to bring it up? Who are the right
>> >>>people
>> >>> >>to
>> >>> >> >>talk
>> >>> >> >> >> >>to?
>> >>> >> >> >> >> Where do you need the most help? I'm an experienced
>> >>>developer,
>> >>> >> >>have
>> >>> >> >> >> >>worked
>> >>> >> >> >> >> on a few phonegap based projects, and would love to give
>> >>>back
>> >>> >>to
>> >>> >> >>the
>> >>> >> >> >> >> community.
>> >>> >> >> >> >>
>> >>> >> >> >> >> cheers,
>> >>> >> >> >> >>
>> >>> >> >> >> >> -Mike
>> >>> >> >> >>
>> >>> >> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >>
>> >>> >>
>> >>>
>> >>>
>>
>>
Re: plugin tooling/specification
Posted by Mike Reinstein <re...@gmail.com>.
> eventually we will move pluginstall into apache
Okay, I wasn't sure if that would happen, so I went with the slightly more
conservative assumption, that pluginstall might live separately from
cordova-client. But I get the impression this is a left-over notion from
when Andrew first built pluginstall and it wasn't clear then whether or not
it would take hold.
I've got an initial version of the merged documentation for the pluginstall
command line tool, and the specification doc. It's here
https://github.com/mreinstein/pluginstall
I've also added some comments on possible changes. Overall the doc is
pretty tight, so it's largely unchanged. Would really appreciate
constructive feedback on this. If it looks right I'll send a pull request
to alunny, and then proceed with merging cordova-client design doc into the
README on github.
-Mike
On Tue, Sep 4, 2012 at 1:47 PM, Filip Maj <fi...@adobe.com> wrote:
> +1 !
>
> (I THINK) eventually we will move pluginstall into apache (assuming the
> authors are cool with that) so it will go 2 docs -> 1 doc.
>
> On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>
> >love it
> >
> >On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein <re...@gmail.com>
> >wrote:
> >> Ah ok, thanks for the clarification. I've had a chance to review the
> >>docs
> >> more carefully. I'm really impressed with how well written they are.
> >>What I
> >> *think* makes the most sense is to consolidate into fewer documents so
> >>that
> >> it's not necessary to look at so many seperate places. Here's what I
> >> propose:
> >> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
> >> * merge the command line tooling design doc into the cordova-client
> >> README.md
> >> * pull apart the cordova/PluginDesign wiki page and merge parts of it
> >>into
> >> the above 2 docs
> >>
> >> I think what this gets us is 2 docs instead of 5, and it still maintains
> >> the nice loose coupling between alunny's pluginstall utility and the
> >>larger
> >> cordova-client. I'm assuming this separation was the original intent,
> >> rather than having one monolithic tool.
> >>
> >> Would love feedback on this, I don't want to waste time doing it and
> >>find
> >> out this isn't appropriate. :)
> >>
> >>
> >> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
> >>
> >>> Cordova-client depends on pluginstall. Pluginstall does the hard work
> >>>for
> >>> programmatic plugin installation, which is just one of the apis
> >>>available
> >>> in cordova-client. So, cordova=client "shells out" to pluginstall.
> >>>
> >>> The client also handles app creation, platform removal/addition, and
> >>> interpolating information from app's config.xml into the necessary
> >>>spots
> >>> in each native project.
> >>>
> >>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com>
> wrote:
> >>>
> >>> >Hey Filip,
> >>> >
> >>> >One thing I"m curious about, whats the difference between
> >>> >https://github.com/alunny/pluginstall and
> >>> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >
> >>> >there seems to be some overlap there. Is pluginstall a subset of
> >>> >functionality just related to plugins that has moved into
> >>>cordova-client
> >>> >or
> >>> >is it different?
> >>> >
> >>> >It seems like cordova-client is the most mature codebase that
> >>>incorporates
> >>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
> >>> >everythign is in cordova-client or not. Said differently, is it safe
> >>>to
> >>> >assume that just about all the worthwhile code is in cordova-client?
> >>> >
> >>> >-Mike
> >>> >
> >>> >
> >>> >
> >>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
> >>> >
> >>> >> All looks good to me Mike.
> >>> >>
> >>> >> I think the "PluginDesign" wiki article would be a great place to
> >>> >> summarize / revamp all this info. Appreciate you tackling this!
> >>> >>
> >>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com>
> >>>wrote:
> >>> >>
> >>> >> >Hey Filip, Brian:
> >>> >> >
> >>> >> >I think where I'd like to start is on documentation. I may be wrong
> >>> >>about
> >>> >> >this, but it seems like there are bits and pieces of docs in
> >>>various
> >>> >> >places, and some may be stale or irrelevant. Maybe a good start is
> >>>for
> >>> >>me
> >>> >> >to find all these pieces, consolidate into a "master" document, and
> >>> >>cull
> >>> >> >out the outdated bits? As a start, here's my rephrasing of the
> >>>various
> >>> >> >links, etc that you've sent to me. Please take a look and let me
> >>>know
> >>> >>if
> >>> >> >I've characterised the content/purpose of these various links:
> >>> >> >
> >>> >> >
> >>> >> >*The spec for how plugins are declared is here:
> >>> >> >https://github.com/alunny/cordova-plugin-spec
> >>> >> >
> >>> >> >The implementation that manages plugin usage is here:
> >>> >>
> >>>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >> >This project encompasses more than just plugins because it also
> >>>handles
> >>> >> >everything related to building, deploying, and managing cordova
> >>> >> >applications
> >>> >> >
> >>> >> >These plugins are most popular, and should ideally work with the
> >>> >> >cordova-client implemenation:
> >>> >> >http://github.com/phonegap/phonegap-plugins*
> >>> >> >*
> >>> >> >*
> >>> >> >This implementation by Drew was an initial proof of concept, which
> >>>only
> >>> >> >works for blackberry and has been abandoned in favor of
> >>>cordova-client,
> >>> >> >with much of his ideas having made it into cordova-client:
> >>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
> >>> >> >
> >>> >> >This doc contains some info on the format of the command line
> >>>interface
> >>> >> >and
> >>> >> >directory structure of cordova-client:
> >>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>> >> >
> >>> >> >This doc contains some documentation on Drew's old implementation,
> >>>and
> >>> >>is
> >>> >> >out of date now:
> >>> >> >http://wiki.apache.org/cordova/PluginDesign
> >>> >> >
> >>> >> >
> >>> >> >I want to emphasize that I'm just trying to get a handle on what
> >>>docs
> >>> >>are
> >>> >> >relevant and which links contain what. I'm not judging anyone's
> >>>work or
> >>> >> >anything like that. :) If I've got the wrong idea about what these
> >>> >>links
> >>> >> >represent or contain, _please_ let me know.
> >>> >> >
> >>> >> >-Mike
> >>> >> >
> >>> >> >*
> >>> >> >*
> >>> >> >*
> >>> >> >*
> >>> >> >*
> >>> >> >*
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >
> >>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com> wrote:
> >>> >> >
> >>> >> >> The cordova client CLI tooling top-level project goes
> >>>hand-in-hand
> >>> >>with
> >>> >> >> this spec. Code here:
> >>> >> >>
> >>> >> >>
> >>> >>
> >>> >>
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
> >>>h
> >>> >> >>or
> >>> >> >> tlog;h=refs/heads/cordova-client
> >>> >> >>
> >>> >> >> Essentially: vet the spec out to make sure popular plugins out
> >>>in the
> >>> >> >>wild
> >>> >> >> (see github.com/phonegap/phonegap-plugins) work with this spec.
> >>>Do
> >>> we
> >>> >> >>need
> >>> >> >> to account for anything else?
> >>> >> >>
> >>> >> >> I think the one outstanding question is how to handle
> >>>installation /
> >>> >> >> compatibility with different versions of cordova.
> >>> >> >>
> >>> >> >> Documentation for the tool as well as the spec (put it on the
> >>>wiki,
> >>> >> >> perhaps) would be awesome!
> >>> >> >>
> >>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein" <re...@gmail.com>
> >>> >>wrote:
> >>> >> >>
> >>> >> >> >Hi Brian, Filip,
> >>> >> >> >
> >>> >> >> >Thanks for the pointers to those projects. I'd love to dig in
> >>>and
> >>> >>start
> >>> >> >> >helping, where do you feel the most help is needed at the
> >>>moment?
> >>> >> >> >Documentation? Any specific code tasks?
> >>> >> >> >
> >>> >> >> >-Mike
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >
> >>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com>
> >>>wrote:
> >>> >> >> >
> >>> >> >> >> Also, this is the current de-facto plugin "spec" we are
> >>>working
> >>> >> >>towards:
> >>> >> >> >> https://github.com/alunny/cordova-plugin-spec
> >>> >> >> >>
> >>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
> >>> >> >> >>
> >>> >> >> >> >Hi Mike, you've come to the right place! Currently the plugin
> >>> >> >>tooling
> >>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself.
> >>>(sorry
> >>> >>for
> >>> >> >>the
> >>> >> >> >> >delayed response / many of us are on a summer break after
> >>> >>shipping
> >>> >> >> >> >2.0)
> >>> >> >> >> >
> >>> >> >> >> >We're loosely collaborating using this list, git, and these
> >>>wiki
> >>> >> >>pages:
> >>> >> >> >> >
> >>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
> >>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
> >>> >> >> >> >
> >>> >> >> >> >The dev is taking place a Cordova/Labs branch which you can
> >>> >>preview
> >>> >> >>on
> >>> >> >> >> >the Github mirror here:
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >>
> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
> >>> >> >> >> >
> >>> >> >> >> >You will want to start by reading up on our contrib process
> >>>in
> >>> >>the
> >>> >> >> >>wiki:
> >>> >> >> >> >
> >>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
> >>> >> >> >> >
> >>> >> >> >> >And in the case of labs projects everything stays on its own
> >>> >>branch
> >>> >> >> >> >until such a time that we feel its solid for its own repo.
> >>> >> >> >> >
> >>> >> >> >> >* * *
> >>> >> >> >> >
> >>> >> >> >> >Let me know any q's!
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> >
> >>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
> >>> >> >> >> ><re...@gmail.com> wrote:
> >>> >> >> >> >> Hey there,
> >>> >> >> >> >>
> >>> >> >> >> >> I'm interested in contributing to the plugin system that is
> >>> >> >> >> >>forthcoming. Is
> >>> >> >> >> >> this the right place to bring it up? Who are the right
> >>>people
> >>> >>to
> >>> >> >>talk
> >>> >> >> >> >>to?
> >>> >> >> >> >> Where do you need the most help? I'm an experienced
> >>>developer,
> >>> >> >>have
> >>> >> >> >> >>worked
> >>> >> >> >> >> on a few phonegap based projects, and would love to give
> >>>back
> >>> >>to
> >>> >> >>the
> >>> >> >> >> >> community.
> >>> >> >> >> >>
> >>> >> >> >> >> cheers,
> >>> >> >> >> >>
> >>> >> >> >> >> -Mike
> >>> >> >> >>
> >>> >> >> >>
> >>> >> >>
> >>> >> >>
> >>> >>
> >>> >>
> >>>
> >>>
>
>
Re: plugin tooling/specification
Posted by Filip Maj <fi...@adobe.com>.
+1 !
(I THINK) eventually we will move pluginstall into apache (assuming the
authors are cool with that) so it will go 2 docs -> 1 doc.
On 9/3/12 1:49 PM, "Brian LeRoux" <b...@brian.io> wrote:
>love it
>
>On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein <re...@gmail.com>
>wrote:
>> Ah ok, thanks for the clarification. I've had a chance to review the
>>docs
>> more carefully. I'm really impressed with how well written they are.
>>What I
>> *think* makes the most sense is to consolidate into fewer documents so
>>that
>> it's not necessary to look at so many seperate places. Here's what I
>> propose:
>> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
>> * merge the command line tooling design doc into the cordova-client
>> README.md
>> * pull apart the cordova/PluginDesign wiki page and merge parts of it
>>into
>> the above 2 docs
>>
>> I think what this gets us is 2 docs instead of 5, and it still maintains
>> the nice loose coupling between alunny's pluginstall utility and the
>>larger
>> cordova-client. I'm assuming this separation was the original intent,
>> rather than having one monolithic tool.
>>
>> Would love feedback on this, I don't want to waste time doing it and
>>find
>> out this isn't appropriate. :)
>>
>>
>> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>>> Cordova-client depends on pluginstall. Pluginstall does the hard work
>>>for
>>> programmatic plugin installation, which is just one of the apis
>>>available
>>> in cordova-client. So, cordova=client "shells out" to pluginstall.
>>>
>>> The client also handles app creation, platform removal/addition, and
>>> interpolating information from app's config.xml into the necessary
>>>spots
>>> in each native project.
>>>
>>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>>
>>> >Hey Filip,
>>> >
>>> >One thing I"m curious about, whats the difference between
>>> >https://github.com/alunny/pluginstall and
>>> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >
>>> >there seems to be some overlap there. Is pluginstall a subset of
>>> >functionality just related to plugins that has moved into
>>>cordova-client
>>> >or
>>> >is it different?
>>> >
>>> >It seems like cordova-client is the most mature codebase that
>>>incorporates
>>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
>>> >everythign is in cordova-client or not. Said differently, is it safe
>>>to
>>> >assume that just about all the worthwhile code is in cordova-client?
>>> >
>>> >-Mike
>>> >
>>> >
>>> >
>>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >
>>> >> All looks good to me Mike.
>>> >>
>>> >> I think the "PluginDesign" wiki article would be a great place to
>>> >> summarize / revamp all this info. Appreciate you tackling this!
>>> >>
>>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com>
>>>wrote:
>>> >>
>>> >> >Hey Filip, Brian:
>>> >> >
>>> >> >I think where I'd like to start is on documentation. I may be wrong
>>> >>about
>>> >> >this, but it seems like there are bits and pieces of docs in
>>>various
>>> >> >places, and some may be stale or irrelevant. Maybe a good start is
>>>for
>>> >>me
>>> >> >to find all these pieces, consolidate into a "master" document, and
>>> >>cull
>>> >> >out the outdated bits? As a start, here's my rephrasing of the
>>>various
>>> >> >links, etc that you've sent to me. Please take a look and let me
>>>know
>>> >>if
>>> >> >I've characterised the content/purpose of these various links:
>>> >> >
>>> >> >
>>> >> >*The spec for how plugins are declared is here:
>>> >> >https://github.com/alunny/cordova-plugin-spec
>>> >> >
>>> >> >The implementation that manages plugin usage is here:
>>> >>
>>>>https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >> >This project encompasses more than just plugins because it also
>>>handles
>>> >> >everything related to building, deploying, and managing cordova
>>> >> >applications
>>> >> >
>>> >> >These plugins are most popular, and should ideally work with the
>>> >> >cordova-client implemenation:
>>> >> >http://github.com/phonegap/phonegap-plugins*
>>> >> >*
>>> >> >*
>>> >> >This implementation by Drew was an initial proof of concept, which
>>>only
>>> >> >works for blackberry and has been abandoned in favor of
>>>cordova-client,
>>> >> >with much of his ideas having made it into cordova-client:
>>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>>> >> >
>>> >> >This doc contains some info on the format of the command line
>>>interface
>>> >> >and
>>> >> >directory structure of cordova-client:
>>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>>> >> >
>>> >> >This doc contains some documentation on Drew's old implementation,
>>>and
>>> >>is
>>> >> >out of date now:
>>> >> >http://wiki.apache.org/cordova/PluginDesign
>>> >> >
>>> >> >
>>> >> >I want to emphasize that I'm just trying to get a handle on what
>>>docs
>>> >>are
>>> >> >relevant and which links contain what. I'm not judging anyone's
>>>work or
>>> >> >anything like that. :) If I've got the wrong idea about what these
>>> >>links
>>> >> >represent or contain, _please_ let me know.
>>> >> >
>>> >> >-Mike
>>> >> >
>>> >> >*
>>> >> >*
>>> >> >*
>>> >> >*
>>> >> >*
>>> >> >*
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com> wrote:
>>> >> >
>>> >> >> The cordova client CLI tooling top-level project goes
>>>hand-in-hand
>>> >>with
>>> >> >> this spec. Code here:
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=s
>>>h
>>> >> >>or
>>> >> >> tlog;h=refs/heads/cordova-client
>>> >> >>
>>> >> >> Essentially: vet the spec out to make sure popular plugins out
>>>in the
>>> >> >>wild
>>> >> >> (see github.com/phonegap/phonegap-plugins) work with this spec.
>>>Do
>>> we
>>> >> >>need
>>> >> >> to account for anything else?
>>> >> >>
>>> >> >> I think the one outstanding question is how to handle
>>>installation /
>>> >> >> compatibility with different versions of cordova.
>>> >> >>
>>> >> >> Documentation for the tool as well as the spec (put it on the
>>>wiki,
>>> >> >> perhaps) would be awesome!
>>> >> >>
>>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein" <re...@gmail.com>
>>> >>wrote:
>>> >> >>
>>> >> >> >Hi Brian, Filip,
>>> >> >> >
>>> >> >> >Thanks for the pointers to those projects. I'd love to dig in
>>>and
>>> >>start
>>> >> >> >helping, where do you feel the most help is needed at the
>>>moment?
>>> >> >> >Documentation? Any specific code tasks?
>>> >> >> >
>>> >> >> >-Mike
>>> >> >> >
>>> >> >> >
>>> >> >> >
>>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com>
>>>wrote:
>>> >> >> >
>>> >> >> >> Also, this is the current de-facto plugin "spec" we are
>>>working
>>> >> >>towards:
>>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>>> >> >> >>
>>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>> >> >> >>
>>> >> >> >> >Hi Mike, you've come to the right place! Currently the plugin
>>> >> >>tooling
>>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself.
>>>(sorry
>>> >>for
>>> >> >>the
>>> >> >> >> >delayed response / many of us are on a summer break after
>>> >>shipping
>>> >> >> >> >2.0)
>>> >> >> >> >
>>> >> >> >> >We're loosely collaborating using this list, git, and these
>>>wiki
>>> >> >>pages:
>>> >> >> >> >
>>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
>>> >> >> >> >
>>> >> >> >> >The dev is taking place a Cordova/Labs branch which you can
>>> >>preview
>>> >> >>on
>>> >> >> >> >the Github mirror here:
>>> >> >> >> >
>>> >> >> >> >
>>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>>> >> >> >> >
>>> >> >> >> >You will want to start by reading up on our contrib process
>>>in
>>> >>the
>>> >> >> >>wiki:
>>> >> >> >> >
>>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>>> >> >> >> >
>>> >> >> >> >And in the case of labs projects everything stays on its own
>>> >>branch
>>> >> >> >> >until such a time that we feel its solid for its own repo.
>>> >> >> >> >
>>> >> >> >> >* * *
>>> >> >> >> >
>>> >> >> >> >Let me know any q's!
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >
>>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>>> >> >> >> ><re...@gmail.com> wrote:
>>> >> >> >> >> Hey there,
>>> >> >> >> >>
>>> >> >> >> >> I'm interested in contributing to the plugin system that is
>>> >> >> >> >>forthcoming. Is
>>> >> >> >> >> this the right place to bring it up? Who are the right
>>>people
>>> >>to
>>> >> >>talk
>>> >> >> >> >>to?
>>> >> >> >> >> Where do you need the most help? I'm an experienced
>>>developer,
>>> >> >>have
>>> >> >> >> >>worked
>>> >> >> >> >> on a few phonegap based projects, and would love to give
>>>back
>>> >>to
>>> >> >>the
>>> >> >> >> >> community.
>>> >> >> >> >>
>>> >> >> >> >> cheers,
>>> >> >> >> >>
>>> >> >> >> >> -Mike
>>> >> >> >>
>>> >> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>
Re: plugin tooling/specification
Posted by Brian LeRoux <b...@brian.io>.
love it
On Sat, Sep 1, 2012 at 7:13 AM, Mike Reinstein <re...@gmail.com> wrote:
> Ah ok, thanks for the clarification. I've had a chance to review the docs
> more carefully. I'm really impressed with how well written they are. What I
> *think* makes the most sense is to consolidate into fewer documents so that
> it's not necessary to look at so many seperate places. Here's what I
> propose:
> * merge the cordova-plugin-spec into the alunny/pluginstall README.md
> * merge the command line tooling design doc into the cordova-client
> README.md
> * pull apart the cordova/PluginDesign wiki page and merge parts of it into
> the above 2 docs
>
> I think what this gets us is 2 docs instead of 5, and it still maintains
> the nice loose coupling between alunny's pluginstall utility and the larger
> cordova-client. I'm assuming this separation was the original intent,
> rather than having one monolithic tool.
>
> Would love feedback on this, I don't want to waste time doing it and find
> out this isn't appropriate. :)
>
>
> On Fri, Aug 31, 2012 at 3:35 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Cordova-client depends on pluginstall. Pluginstall does the hard work for
>> programmatic plugin installation, which is just one of the apis available
>> in cordova-client. So, cordova=client "shells out" to pluginstall.
>>
>> The client also handles app creation, platform removal/addition, and
>> interpolating information from app's config.xml into the necessary spots
>> in each native project.
>>
>> On 8/31/12 12:32 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>
>> >Hey Filip,
>> >
>> >One thing I"m curious about, whats the difference between
>> >https://github.com/alunny/pluginstall and
>> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >
>> >there seems to be some overlap there. Is pluginstall a subset of
>> >functionality just related to plugins that has moved into cordova-client
>> >or
>> >is it different?
>> >
>> >It seems like cordova-client is the most mature codebase that incorporates
>> >a lot of ideas, so I'm just chasing down code I'm finding to see if
>> >everythign is in cordova-client or not. Said differently, is it safe to
>> >assume that just about all the worthwhile code is in cordova-client?
>> >
>> >-Mike
>> >
>> >
>> >
>> >On Fri, Aug 31, 2012 at 3:01 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> All looks good to me Mike.
>> >>
>> >> I think the "PluginDesign" wiki article would be a great place to
>> >> summarize / revamp all this info. Appreciate you tackling this!
>> >>
>> >> On 8/31/12 11:59 AM, "Mike Reinstein" <re...@gmail.com> wrote:
>> >>
>> >> >Hey Filip, Brian:
>> >> >
>> >> >I think where I'd like to start is on documentation. I may be wrong
>> >>about
>> >> >this, but it seems like there are bits and pieces of docs in various
>> >> >places, and some may be stale or irrelevant. Maybe a good start is for
>> >>me
>> >> >to find all these pieces, consolidate into a "master" document, and
>> >>cull
>> >> >out the outdated bits? As a start, here's my rephrasing of the various
>> >> >links, etc that you've sent to me. Please take a look and let me know
>> >>if
>> >> >I've characterised the content/purpose of these various links:
>> >> >
>> >> >
>> >> >*The spec for how plugins are declared is here:
>> >> >https://github.com/alunny/cordova-plugin-spec
>> >> >
>> >> >The implementation that manages plugin usage is here:
>> >> >https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> >This project encompasses more than just plugins because it also handles
>> >> >everything related to building, deploying, and managing cordova
>> >> >applications
>> >> >
>> >> >These plugins are most popular, and should ideally work with the
>> >> >cordova-client implemenation:
>> >> >http://github.com/phonegap/phonegap-plugins*
>> >> >*
>> >> >*
>> >> >This implementation by Drew was an initial proof of concept, which only
>> >> >works for blackberry and has been abandoned in favor of cordova-client,
>> >> >with much of his ideas having made it into cordova-client:
>> >> >https://github.com/deedubbu/cordova-blackberry-pluggable
>> >> >
>> >> >This doc contains some info on the format of the command line interface
>> >> >and
>> >> >directory structure of cordova-client:
>> >> >http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> >
>> >> >This doc contains some documentation on Drew's old implementation, and
>> >>is
>> >> >out of date now:
>> >> >http://wiki.apache.org/cordova/PluginDesign
>> >> >
>> >> >
>> >> >I want to emphasize that I'm just trying to get a handle on what docs
>> >>are
>> >> >relevant and which links contain what. I'm not judging anyone's work or
>> >> >anything like that. :) If I've got the wrong idea about what these
>> >>links
>> >> >represent or contain, _please_ let me know.
>> >> >
>> >> >-Mike
>> >> >
>> >> >*
>> >> >*
>> >> >*
>> >> >*
>> >> >*
>> >> >*
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >On Sat, Aug 25, 2012 at 7:12 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >
>> >> >> The cordova client CLI tooling top-level project goes hand-in-hand
>> >>with
>> >> >> this spec. Code here:
>> >> >>
>> >> >>
>> >>
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-labs.git;a=sh
>> >> >>or
>> >> >> tlog;h=refs/heads/cordova-client
>> >> >>
>> >> >> Essentially: vet the spec out to make sure popular plugins out in the
>> >> >>wild
>> >> >> (see github.com/phonegap/phonegap-plugins) work with this spec. Do
>> we
>> >> >>need
>> >> >> to account for anything else?
>> >> >>
>> >> >> I think the one outstanding question is how to handle installation /
>> >> >> compatibility with different versions of cordova.
>> >> >>
>> >> >> Documentation for the tool as well as the spec (put it on the wiki,
>> >> >> perhaps) would be awesome!
>> >> >>
>> >> >> On 8/25/12 10:23 AM, "Mike Reinstein" <re...@gmail.com>
>> >>wrote:
>> >> >>
>> >> >> >Hi Brian, Filip,
>> >> >> >
>> >> >> >Thanks for the pointers to those projects. I'd love to dig in and
>> >>start
>> >> >> >helping, where do you feel the most help is needed at the moment?
>> >> >> >Documentation? Any specific code tasks?
>> >> >> >
>> >> >> >-Mike
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >On Sat, Aug 25, 2012 at 12:51 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >> >
>> >> >> >> Also, this is the current de-facto plugin "spec" we are working
>> >> >>towards:
>> >> >> >> https://github.com/alunny/cordova-plugin-spec
>> >> >> >>
>> >> >> >> On 8/6/12 8:20 PM, "Brian LeRoux" <b...@brian.io> wrote:
>> >> >> >>
>> >> >> >> >Hi Mike, you've come to the right place! Currently the plugin
>> >> >>tooling
>> >> >> >> >is being implemented by Anis, Fil, Michael, and myself. (sorry
>> >>for
>> >> >>the
>> >> >> >> >delayed response / many of us are on a summer break after
>> >>shipping
>> >> >> >> >2.0)
>> >> >> >> >
>> >> >> >> >We're loosely collaborating using this list, git, and these wiki
>> >> >>pages:
>> >> >> >> >
>> >> >> >> >- http://wiki.apache.org/cordova/PluginDesign
>> >> >> >> >- http://wiki.apache.org/cordova/CommandLineToolingDesign
>> >> >> >> >
>> >> >> >> >The dev is taking place a Cordova/Labs branch which you can
>> >>preview
>> >> >>on
>> >> >> >> >the Github mirror here:
>> >> >> >> >
>> >> >> >> >
>> >> https://github.com/apache/incubator-cordova-labs/tree/cordova-client
>> >> >> >> >
>> >> >> >> >You will want to start by reading up on our contrib process in
>> >>the
>> >> >> >>wiki:
>> >> >> >> >
>> >> >> >> >http://wiki.apache.org/cordova/ContributerWorkflow
>> >> >> >> >
>> >> >> >> >And in the case of labs projects everything stays on its own
>> >>branch
>> >> >> >> >until such a time that we feel its solid for its own repo.
>> >> >> >> >
>> >> >> >> >* * *
>> >> >> >> >
>> >> >> >> >Let me know any q's!
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >On Mon, Jul 30, 2012 at 4:18 PM, Mike Reinstein
>> >> >> >> ><re...@gmail.com> wrote:
>> >> >> >> >> Hey there,
>> >> >> >> >>
>> >> >> >> >> I'm interested in contributing to the plugin system that is
>> >> >> >> >>forthcoming. Is
>> >> >> >> >> this the right place to bring it up? Who are the right people
>> >>to
>> >> >>talk
>> >> >> >> >>to?
>> >> >> >> >> Where do you need the most help? I'm an experienced developer,
>> >> >>have
>> >> >> >> >>worked
>> >> >> >> >> on a few phonegap based projects, and would love to give back
>> >>to
>> >> >>the
>> >> >> >> >> community.
>> >> >> >> >>
>> >> >> >> >> cheers,
>> >> >> >> >>
>> >> >> >> >> -Mike
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>