For what it's worth, the biggest problem I've had in upgrading is with
'phonegap plugin add <plugin>'. The native code gets copied but
cordova_plugins.js doesn't get updated and the plugin JS isn't wrapped
in a call to cordova.define. In a couple of Stack Overflow posts,
running 'phonegap build <platform>' after adding a plugin is suggested
but I don't see that documented in the Phonegap docs. Plus, that
overwrites the www directory so it has to be copied beforehand which is
troublesome if there are platform-specific customizations. (Is that the
only time the outer www is used?) In addition, I didn't find
documentation for the contents of cordova_plugins.js or the linkage
between it and the plugin JS so I wasn't sure what was required and had
to piece that together on my own. In the end, I manually updated
cordova_plugin.js and the plugin JS files which is way more hairs than I
think was intended.
Overall, I still think Cordova is great framework but that improved
documentation would go a long way towards making that more apparent.
-Terence
On 4/28/2014 2:15 PM, Michal Mocny wrote:
s/mailing list/distribution list/
On Mon, Apr 28, 2014 at 3:14 PM, Michal Mocny <mmo...@chromium.org> wrote:
I think this particular users' frustration is not addressable (and his
feedback in places is just annoying: "you work for X and I demand that you
should have the money to do everything for me").
He hasn't maintained his project for 2 years, hasn't read our docs, hasn't
written tests to guard against platform assumptions, and expects to update
everything in a few hours.
There are a few issues he got hit with (plugin authoring with the CLI is a
pain in the butt, 3.4 release plugin docs issue), but generally its
probably not worth putting to much weight into it.
More broadly, though, perhaps we should acknowledge that we will never
catch all issues with releases and try to find ways to incentivize the
community to help test out RC's for us? Perhaps a dedicated mailing list
for known developers who stay bleeding edge that we email as part of
starting the release vote process / at the end of [DISCUSS] thread?
-Michal
On Mon, Apr 28, 2014 at 2:54 PM, Shazron <shaz...@gmail.com> wrote:
We come with a (framework) developer's perspective, thus an echo chamber.
The comments may or may not be fair but the users do encounter pain, and I
think it does help in identifying issues we missed (reading from the list
overall). Canary in the coal mine, etc.
Filing issues etc ideal, but some, for whatever reason, do not like that
type of forum, but still choose the Google Groups.
On Mon, Apr 28, 2014 at 11:44 AM, Brian LeRoux <b...@brian.io> wrote:
I feel the comments there are not really constructive or fair. Cordova
changes too much? Sorry, static code means bitrot aka abandonware.
We work on Cordova because we are improving it for the many thousands of
our users whom appreciate that. I don't need to tell you guys that but
1.8
was a mess compared to 3.x and if you are only updating YOUR userland
source once every 2 years and you don't expect it to be come with
problems?! The bugs found usually are not introduced by us but with
Xcode,
iOS, or Android and we are FIXING those things with updates.
Docs are a problem but as they say patches welcome. This is the sort of
entitled complaint that lead me off that list.
On Mon, Apr 28, 2014 at 11:30 AM, Shazron <shaz...@gmail.com> wrote:
See:
https://groups.google.com/d/msg/phonegap/II0qo-dSFWs/Fj8jkemGSbUJ
