Hi Nayantara , With this GUI can we create queries on demand or should be predefined?
On Wed, Jun 8, 2016 at 11:01 AM, Nayantara Jeyaraj <[email protected]> wrote: > I am currently working on the Design and Implementation of the Siddhi > Visual Editor for WSO2's CEP. The tasks completed and on-going have been > listed out below. Your input will be appreciated. > > The interface will consist of a Toolbox/palette, a canvas and a Properties > panel that appears upon clicking the toolbar icon of each element. > > *Tasks completed:* > > - > > Functionality that enables dragging an object from the palette and > dropping it onto the canvas. > - > > Permitting the Creation of multiple connections between anchors from > varied sources and storing data in an array regarding the connections for > further utilization. > - > > Deleting Connections along with the parent element. > > *Currently working on:* > > - > > Changing the property attributes such as stream name and stream > definition of dropped elements (Stream name will be displayed on the > respective icon when saved). > > *Eg:* > > from TempStream > > select roomNo, temp > > insert into RoomTempStream; > > > *The toolbar will hold:* > > 1. A stream icon > > 2. A query icon > > Once a stream has been dragged on to the canvas, the > type(import/export/temporary) can be selected in the properties panel and > thereafter it will be validated against the available schema and > dropped(The validation part has not been done yet). Then a query can > consume one or more event streams and generate a new event stream from > them. > > *A Tempstream will be created with the following attributes:* > > define stream TempStream(deviceID long, roomNo int, temp double); > > So when the event stream icon is dropped onto the canvas, the properties > panel for that event stream appears permitting the set up of the event > stream. > > *Requested Stream Property Data in the properties panel:* > > Event stream type: import/ export/ temporary > > Event stream Name: <user_input> > > Event stream definition: <user_input> Derived from an existing stream > > Following this, a query can consume this stream. The query will not be > decomposed into its minuscule details but will be merely considered as one > unit. > > From the above example, the query filters out only the temperature of the > respective room from the TempStream and generates a new RoomTempStream. > > > The Visual Representation of the above ( Relevant icons will be used): > > tempStream -----> query -----> RoomTempStream > > > Th following query types can be chosen when dealing with the query object > > 1. Pass-through (Prioritized at present) > > 2. Filters > > 3. Window > > 4. Joins > > > Fig1: BasicUI developed to date > > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Technical Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
