Single step specification

This section describes the code fragment that can be used as single steps by the AppDesigner application.

Event-Based-Components

As by the previous project (see: https://ebcappbuilder.codeplex.com/) event based components can be used. The following code fragment shows the basic structure of these components:

public class EBC_Class
{
  public void Method_Pin(dataType1 arg1, dataType2 arg2, …, datatTypeN, argN) 
  {
    // Do something …
	
    Event_Pin(…)
  }

  public event Action<dataType3, dataType4, …, dataTypeM> Event_Pin;
}

Note:
More than one input method or output event can be used. There are any datatypes supported and random number of arguments are allowed (even no arguments).

Functions

You can use functions hosted by static or instancable classes:

public [static] class Functional_Class
{
  public [static] returnDataType Function_Pin(dataType1 arg1, dataType2 arg2, …, dataTypeN argN)
  {
    // Do something

    return (…);
  }
}

Note:
Functions only support a single return data type. If you need more than one use the Tuple<S,T> datatype.
It’a also allowed to mix event based component classes and functional classes. This means that a function class could also contain other methods and events.

Continuation Methods

These types of methods contains an action argument in the method header:

public [static] class Continuation_Class
{
  public [static] void Method_Pin(dataType1 arg1, dataType2 arg2, …,. dataTypeN argN, Action<continueType1> continue_Pin1, Action<continueType2> continue_Pin2, …)
  {
    // Do something

    Continue_Pin1(…);

    Continue_pin2(…);
  }
}

Last edited May 20, 2014 at 1:14 PM by InneHo, version 11