Google Ads SDK needs updating

Solar2D Monetization (in-app purchases, ads, etc.)
#21

Think of it. The whole purpose of Open Source is to harness the expertise in a community of developers. Without trust, Open Source projects like Linux and others would’ve been dead a long time ago.

Of course CoronaLabs can’t automatically incorporate every Pull request they get. It has to be managed by them. However in my experience looking over code to see if it meets requirements is a lot quicker than trying to debug/find solutions to problems.

We’re also talking about version control software that shows you exactly what the Pull request is trying to do. And like I said above, we’re talking about a plugin interface to a SDK which is not rocket-science in any way.

Luckily I’m an Enterprise user and can code my own plugins if ever I have an issue.

#22

Hey, Ingemar, I’m not using Enterprise version, so I’d be at a mercy of whatever gets added to the build process.  

That said, I do trust your judgement, and if you absolutely believe Open Sourcing all plugin would work perfectly fine, perhaps it does.

Naomi

#23

Unfortunately when I think more about it, even if they did Open Source the plugins, I worry that nobody would care.

Look at what happened to Widgets 2.0. It’s Open Sourced, and nobody is contributing. Also it’s a two-way street. Both the Community and the Source-owner must be willing to make things happen. I tried contributing to Widgets in the beginning, but got more or less ignored.

#24

Not updating to the new SDK is a mistake imho. A new SDK introdces bug fixes and features that we are missing out on. I too saw the warning message posted by the OP but decided not to alert Corona as I simply did not expect them to respond promptly. They are clearly overworked and under resourced.

I take your point about Open Source and the Linux example. However, the Corona community simply does not have that kind of traction. I, respectfully, do not “trust” the community to devote time to such an effort - as evidenced by Widgets 2.0.

On a wider note, the demise of Corona support starting with Chartboost and PlayHaven and now Gremlin leads me to believe that the future for Corona is not bright. I hope I am wrong. For sure I will not pay the full asking price for a Pro license when my discounted Pro rate expires. Still no Windows phone, a buggy framework and now a 3rd party plugin marketplace that isn’t viable. 

Rant over! :smiley:

#25

i think open-sourcing widgets was a good idea, for those who can fix their own bugs, but as a case-study of community support i’d agree that it falls a bit short.

my impression is that the “o-s community” expects a certain minimum “structure” before they’ll take it upon themselves to improve/upgrade.  so, while widgets has some basic organization in place, it also has lots of weird “gotchas” that (probably?) prevent wider adoption for development.

things like scrollview having “special-case” logic built into the base class for use with date picker, instead of sub-classing it for just the functionality dp requires.  that’s the sort of design that screams “please give me unintended consequences and obscure regression bugs”.  (fe, you fix your scrollview, but therein break your datepicker)

or docs like “all widgets are groups… except scrollview, tableview”, without bothering to say why.  (would have rather seen “MOST widgets are groups, notable exceptions are … because …”)  that sort of half-doc’d stuff litters the code.

it’s “just complicated enough” that newbies probably wouldn’t touch it at all, medium-level devs might get something half-fixed and possibly suffer the above “consequences”; advanced devs might just pass it by as unmaintainable and just roll their own from scratch.

that’s my impression, $0.02, fwiw.  but i still think it’s a great that the source is available.