Difference between revisions of "Ads"
Line 3: | Line 3: | ||
'''Available since:''' Gideros 2011.6<br/> | '''Available since:''' Gideros 2011.6<br/> | ||
=== Description === | === Description === | ||
− | The idea is to provide common Ads interface for most of available ad frameworks, so that user's would not have to create a plugin for each of them separately, but rather it would be possible to wrap ad framework in single Java or Objective-C class (depending on the platform) and add it to the project, without even recompiling existing Ads Interface plugin. | + | <translate>The idea is to provide common Ads interface for most of available ad frameworks, so that user's would not have to create a plugin for each of them separately, but rather it would be possible to wrap ad framework in single Java or Objective-C class (depending on the platform) and add it to the project, without even recompiling existing Ads Interface plugin. |
Additionally it would be able to support multiple ad frameworks simultaneously so users could switch and fall back between ad frameworks on runtime. | Additionally it would be able to support multiple ad frameworks simultaneously so users could switch and fall back between ad frameworks on runtime. | ||
− | More information available in [http://docs.giderosmobile.com/interface/ads](Ads interface guide). | + | More information available in [http://docs.giderosmobile.com/interface/ads](Ads interface guide).</translate> |
=== Examples === | === Examples === | ||
'''Creating fallbacks with Ads frameworks'''<br/> | '''Creating fallbacks with Ads frameworks'''<br/> |
Revision as of 13:32, 23 August 2018
Supported platforms:
Available since: Gideros 2011.6
Description
The idea is to provide common Ads interface for most of available ad frameworks, so that user's would not have to create a plugin for each of them separately, but rather it would be possible to wrap ad framework in single Java or Objective-C class (depending on the platform) and add it to the project, without even recompiling existing Ads Interface plugin.
Additionally it would be able to support multiple ad frameworks simultaneously so users could switch and fall back between ad frameworks on runtime.
More information available in [1](Ads interface guide).
Examples
Creating fallbacks with Ads frameworks
--require plugin
require "ads"
--initialize amazon
amazon = Ads.new("amazon")
amazon:setKey("amazon-key")
--initialize admob
admob = Ads.new("admob")
admob:setKey("admob-key")
--if amazon fails
--show admob
amazon:addEventListener(Event.AD_FAILED, function(e)
print("amazon AD_FAILED", e.error)
admob:showAd("auto")
end)
--if admob fails
--show amazon
admob:addEventListener(Event.AD_FAILED, function(e)
print("admob AD_FAILED", e.error)
amazon:showAd("auto")
end)
--start displaying amazon ads
amazon:showAd("auto");
MethodsAds.new - initializes new ad framework |
EventsEvent.AD_ACTION_BEGIN Constants |