Plugin System

NeuroKernel has a very flexible plugin system. Every application can be used as a plugin inside another application if the application itself allows it. There is no need to install any plugin to your server, locale or remote. Plugin system is one of the most striking features of NeuroKernel operating system.

A plugin branch is a plugin reques tmade by an already running plugin application. Plugin applications running as a branch wont have any visuals, they can interact with their parent in terms of data input and output. NeuroKernel task processor wont allow recursive calling of plugin branches. Plugin branches are a good choice for connecting other servers for information needed. It may be used as distributed data searches, pattern recognition and more. Plugin branches are forced to run in a worker by kernel.

Plugin component, or NPlugin, is the UI control that embeds a plugin application for its parent. It can request a plugin component from various sources including peer-to-peer networks. IPluginSystem interface object is created for both the plugin component and the plugin application to make the development consistent. The messaging is made via events between parent and plugin.

import com.neurokernel.client.*;
import com.neurokernel.client.adapter.IActionListener;
 
public class PluginExample extends NApplication {
      private IPluginSystem pluginSystem;
 
      @Override
      public void main(int argc, String[] argv) {
          NFrame mainFrame=getMainFrame();
          NButton button=new NButton(mainFrame,"Hello");
 
          button.addListener((ActionListener) (e) -> pluginSystem.sendEvent(500, "Hello"));
 
          NPlugin pluginApp=new NPlugin(mainFrame, "HelloPlugin");
          pluginSystem = pluginApp.getEmbeddedSystem();
          pluginSystem.addListener(e -> NMessageDialog.showInfo(mainFrame, e.getString()), 500);
 
          setVisible("Plugin Example");
      }
 
}

An application can define itself as a device by using Device annotation. The advance of defining a device is to give a standardized plugin interface to the applications so that same device type can be loaded from different sources implemented differently.

import com.neurokernel.system.ICallback;
import com.neurokernel.system.device.*;
import com.neurokernel.client.NApplication;
import com.neurokernel.system.io.IConsole;
import com.neurokernel.system.constants.DataType;
import com.neurokernel.system.annotation.Device;
import com.neurokernel.system.annotation.Method;
import java.util.Date;
 
@Device(
        value="NDayTime", 
        type="DayTimeDevice", 
        methods={
            @Method(value="getTime",returnType=DataType.LONG),
            @Method(value="getDate",returnType=DataType.DATE)
        }
)
public class NDayTimeDevice extends NApplication {
    Date currentDate=new Date();
    NMethod getTime;
 
    @Override
    public void main(int argc, String[] argv) {
         NDevice deviceInfo=getSystem().getDevice();
 
         if(deviceInfo!=null) {
             getTime=deviceInfo.getDeviceMethod("getTime").
                     setCallProcessor((IAsyncResponse response, Object... args) -> currentDate.getTime());
 
             deviceInfo.getDeviceMethod("getDate").
                     setCallProcessor((IAsyncResponse response, Object... args) -> currentDate);
         }
    }
}

    import com.neurokernel.system.constants.DataType;
    import com.neurokernel.system.annotation.*
    import com.neurokernel.client.*;
    import com.neurokernel.system.ISystem;
    import com.neurokernel.system.device.*;
    import java.util.Date;
 
    @Device(
        value="NDayTime", 
        type="DayTimeDevice", 
        methods={
            @Method(value="getTime",returnType=DataType.LONG),
            @Method(value="getDate",returnType=DataType.DATE)
        }
    )
    public class NMyDevice extends NDeviceDriver {
        IConsole console;
 
        public NMyDevice(ISystem system) {
            super("DayTimeDevice",system);
            console=system.getConsole();
        }
 
       @Override
        protected void onDeviceSuccess(NDevice device) {
             device.getDeviceMethod("getTime").
               setResponseProcessor((NMethod method, Long result) -> {
                   console.print(new Date(result));
             }).call();
 
             device.getDeviceMethod("getDate").
               setResponseProcessor((NMethod method, Date result) -> {
                   console.print(result);
             }).call();
        } 
 
        @Override
        protected void onDeviceFailure() {
 
        }
    }

Parent application can associate a canvas with the plugin application by giving reference information to it. This gives opportunity to the plugin to draw a parent canvas on protocol level. This association can also be done with direct canvas access if the offline canvas feature is supported by the browser used, or the plugin application is from the same domain as the parent application.

   import com.neurokernel.client.*;
   import com.neurokernel.system.IPluginSystem;
 
   public class MyApplication extends NApplication {
      @Override
      public void main(int argc, String[] argv) {
          NFrame mainFrame=getMainFrame();
 
          NCanvas canvas=new NCanvas(mainFrame);
          NPlugin plugin=new NPlugin(mainFrame, "teapot", null);
          IPluginSystem pluginSystem=plugin.getPluginSystem();
          pluginSystem.associateCanvas("MyCanvas", canvas.getGraphics());
 
          mainFrame.setTitle("Plugin Application");
          mainFrame.setBounds(20,20,200,200);
          mainFrame.setVisible(true);
       }
    }