We would like to integrate our extensions with Ant Media Server using plugins.
How can we do that and build plugins on top of Ant Media Server?
Also what are the resource requirement for that?
Ant Media Server supports plugins to integrate them into the video/audio processing in it. You can have a plugin that captures video/audio packets (encoded) or frames (decoded) data from Ant Media Server. Then your plugin can consume the data or process them and feed back to the Ant Media Server.
You can check this blogpost to understand the plugin architecture and check this to learn how you can create a plugin.
Also I recommend you to check the Ant Media's Plugins repository. There are open source plugins developed by the team.
Related
The latest GCM update includes steps on developer.google.com to create a configuration file and use a gradle plugin. I have an existing app that already configured to use GCM. Is switching to the plugin recommended? Will this cause any problems. Looks like Google is moving to using this plugin & google-services.json as the configuration for all Google apis. Thoughts?
Using the plugin will not cause any issue with your current projects. The google-services plugin assists in the creation and use of projects from the Google Developer Console in your Android application. It provides constants that map to values from your console projects eg: gcm_defaultSenderId for GCM. The values could still enter manually, so you have the option of not using the plugin.
I worked through the ApacheCordovaPlugin example. Its nice to see that creating a new plugin is possible, and I successfully replicated the HelloWorldPlugin in a WL project of my own just to make sure I could get all the plumbing to work. It is tricky, you have to make entries in the right XML files, name your Java and .js files appropriately, know how to include them and call the functions, etc. If you make a mistake there is very little information visible that you can use to debug it. The entire process is very fragile.
Now I would like to have access to the large library of existing Cordova plugins. My primary development target is Android. I downloaded a plugin zip file from a git repository and extracted it. Looking at the files and the directory layout it is not at all clear how to integrate this into a WL project. Cordova has a 'plugin.xml' file that appears to supply all the glue, but there is no such thing in WL. I was not able to determine where to put files and what edits to make in the Worklight project that would cause the Cordova plugin to be recognized and accessed from my application JavaScript.
Surely this process is possible and is documented somewhere? Ideally there would be a utility that we use to import Cordova plugins, but next-best would be a step-by-step procedure description. I saw one somebody did for getting plugins into the iOS application environment, but not Android.
Most probably you've downloaded a plugin for cordova 3.0+. Since latest WL contains Cordova 2.6 you need to download plugin for this (or similar) version. E.g. if you're talking about barcode scanner plugin the most suitable version would be 2.2 (https://github.com/phonegap/phonegap-plugins/tree/master/Android/BarcodeScanner)
IBM has this big 200+ Mb Eclipse plugin where I'm given access to everything and all functionality of Eclipse.
Is there a smaller more lightweight Eclipse plugin available that just gives access to the information a developer needs. Basically just a list of the workitems assigned to me or my team.
Yes, I can configure the big existing IBM plugin to just display that info, but then I'd still have this massive behemoth installed in my Eclipse.
I am aware of Tasktop Dev that allows me to import the workitems into my mylyn tasklist, but I'm looking for something cheaper.
No, because that plugin would have to manage work items and change sets (the list of versioned files), that is the planning and the source control part.
Plus you would need the EMF - GMF dependencies, part of the 200+ MB bundle, as described in "Tip: Installing the Rational Team Concert client into Eclipse 3.5.x".
Which is basically 75% of what the RTC plugin is (the rest being a link to the JBE: Jazz Build Engine).
currently I am having following version of clear case on my local machine.
I downloded plugin "com.rational.clearcase.win32-20081031A" from url: "http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/clearcase/ccplugin/com.rational.clearcase.win32-20081031A.zip" which include following files in feature and plugin folders.
3.then I installed this plugin from eclipse Help->Software update-> search and install->given here local path of plugin folder which looks like following screen shot 4. It got installed on eclipse;but when I am trying tu connect through it it's giveing me following error.
can you please suggest whats going wrong in it?
That plugin won't work with CCRC (ClearCase Remote Client), only with a full base ClearCase installation.
CCRC comes with its own Eclipse interface, in which you will find all the necessary ClearCase commands.
If you want a CCRC plugin (which is different from the SCM Adaptor you have downloaded), you need to download it from your CCRC server, as I detail in your last question.
I have some basic questions in eclipse plugin development, can anyone give clarification of the following questions,
When should we have to add features in our plugin development ?
What is the difference between feature and plugin.xml ?
Regards
Mathan
As mentioned in this thread:
A plugin is the eclipse "unit of work". An OSGi bundle that supplies a classpath and can contribute to eclipse through extensions.
A fragment points to a host plugin, and anything it provides (classpath, extensions, etc) are "sucked" into the host plugin. A fragment is also a more specialized OSGi bundle.
A feature represents a versioned collection of plugins, and is used for configuration management in eclipse. They can be deployed manually or through the update manager. If you want to deploy through the update manager, then you need to use features to represent your plugins.
So if you want to manage your plugin or plugins through the update manager, a feature is in order.
You can find more in the Eclipse Help:
Feature
Features do not contain any code.
They merely describe a set of plug-ins that provide the function for the feature and information about how to update it.
Features are packaged in a feature archive file and described using a feature manifest file, feature.xml.
Plugin
While features are organized for the purposes of distributing and updating products, plug-ins are organized to facilitate the development of the product function among the product team. The development team determines when to carve up program function into a separate plug-in.
Plug-ins are packaged in a plug-in archive file and described using a plug-in manifest file, plugin.xml.