Related to the specific naming and namespaces: http://wiki.apache.org/cordova/Core%20Plugin%20Name%20Proposal
I don't care on the namespace label. However, I would rather not have to change it more than over the next few releases. Every time the namespace of a plugin changes, it requires a longer upgrade guide (As Joe pointed out). Let's figure out the namespaces in this thread and stick to it (for all applicable platforms). On 3/15/13 2:48 PM, "Joe Bowser" <[email protected]> wrote: >On Fri, Mar 15, 2013 at 2:41 PM, Anis KADRI <[email protected]> wrote: >> What is it that needs to change in the config.xml as far as plugins are >> concerned ? I am hoping they will keep the same name and namespace when >> they get updated, right ? > >That's if they get updated. When they get installed, the entry has to >be added to the config.xml. Or is that still a manual process? > >> The only things that should change when plugins >> get updated is the native/javascript code and maybe dependencies (but >> that's another topic). >> >> As far as naming everything core, I say why not. I wonder if it's not >> preferable to have one directory per plugin instead to make the >>separation >> even more obvious: >> >> org.apache.cordova.acceleration.Acceleration >> org.apache.cordova.capture.Capture >> org.apache.cordova.file.File >> org.apache.cordova.file.FileTransfer >> org.apache.cordova.file.FileProgressResult >> > >I think that actually might be better, but that should probably happen >once we actually get repositories for them all. I'm just proposing >this as a first step.
