Hi Nayanathara, when you say allowing the user to define the query as a set of constructs, > do you propose having individual icons for these minuscule parts? > Yes.
IMO, it's okay to expect users to have a basic understanding on Siddhi queries when he's writing a query. But we have to put some effort to do the validations. We can guide users through proper error messages when he/she does something wrong. In the suggested approach there are 2 drawbacks I see - Does not scale for complex queries and different types of queries - Doesn't really give the user the experience of constructing a query. However, this approach may be good as a starting point to implement the framework required for a visual editor. Thanks *,Sajith Ravindra* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 2273550 blog: http://sajithr.blogspot.com/ <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> On Wed, Jun 8, 2016 at 1:52 PM, Nayantara Jeyaraj <[email protected]> wrote: > Hi Sajith, > when you say allowing the user to define the query as a set of constructs, > do you propose having individual icons for these minuscule parts? If > so,there maybe issues of an amateur user trying invalid connections such as > connecting a stream to a sub construct of the query, instead of piping it > to the entire query. But, on the whole, it would actually provide a visual > enhancement to the UI, not considering this issue. > > On Wed, Jun 8, 2016 at 1:00 PM, Sajith Ravindra <[email protected]> wrote: > >> Hi Nayanthara, >> >> AFAIU the query is more of a template in the scope of this project where >> you get the parameters and convert it into a passthrough, join or another >> type of a query. So, is the plan is to add support to different types of >> queries as we go forward? IMO, it might not be a scalable solution. Can't >> we let the user define the query as a set of constructs(i.e select, insert, >> join, etc..). To start with we can support few basic ones like select, >> insert. >> That wlll actually give the user the experience of visully constructing >> the query. WDYT? >> >> >> >> Thanks >> *,Sajith Ravindra* >> Senior Software Engineer >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: +94 77 2273550 >> blog: http://sajithr.blogspot.com/ >> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> >> >> On Wed, Jun 8, 2016 at 12:40 PM, Lasantha Fernando <[email protected]> >> wrote: >> >>> Hi Nayantara, >>> >>> Can you provide a bit more information on how you are generating the >>> query based on the icons that are dropped to editor? >>> >>> I assume we are working on the top level design currently and maybe not >>> finalized how the query generation happens. But is there a rough idea on >>> how the query generation would happen? i.e. Are we mapping the query from >>> the configurations of the query/stream directly at front end? Or will we >>> have another intermediate layer that will map the visual configuration to >>> the query? >>> >>> As the editor evolves, I believe features such as refactoring queries >>> will be useful. For providing such features, it might help to keep some >>> sort of object model that maps the icons to queries. Such an object model >>> might help in developing the validation scheme as well. WDYT? >>> >>> Thanks, >>> Lasantha >>> >>> On 8 June 2016 at 12:12, Nayantara Jeyaraj <[email protected]> wrote: >>> >>>> Hi Malaka, >>>> The user will be given the privilege to type in his/her own query. The >>>> conceptualization so far is that, when a query icon is dropped, a >>>> properties panel pops up (just as it did for the stream) and the user can >>>> type in his entire query in a text field. >>>> >>>> On Wed, Jun 8, 2016 at 11:39 AM, Malaka Silva <[email protected]> wrote: >>>> >>>>> 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 >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Lasantha Fernando* >>> Senior Software Engineer - Data Technologies Team >>> WSO2 Inc. http://wso2.com >>> >>> email: [email protected] >>> mobile: (+94) 71 5247551 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
