Hi Lasantha, On Sat, Aug 3, 2013 at 6:23 PM, Lasantha Fernando <[email protected]> wrote:
> Hi, > > Yes, will do the diagrams as Mohan suggests. > > Regarding the idea of one real life usecase for docs, +1 for that. > Actually, the same idea came up during an internal CEP meeting as well, and > Mohan is maintaining a doc regarding all the ideas that have come up so far > the usecase.. :-) > > Regarding the FAQ, I don't have much of an idea right now regarding what > to write for the FAQ (maybe based on SO questions we've got so far), but > will work on that as well after finishing the main content. > Yes, As you mentioned we can get some content from SO as well but not all since it is a rewrite... We can also get some content from support queries and QSPs as well.. I can also work on finding the content for FAQ.. Regards, Mohan > > Thanks all for your feedback. > > Thanks, > Lasantha > > On 2 August 2013 23:17, Mohanadarshan Vivekanandalingam <[email protected]>wrote: > >> >> >> On Fri, Aug 2, 2013 at 10:47 PM, Lasantha Fernando <[email protected]>wrote: >> >>> +1 for the brief tutorial + full specification approach. That will give >>> the best of both... >>> >>> @Mohan, can you elaborate on how we should provide graphical content? Do >>> you mean like a query tree/flow diagram like thing to explain the query? >>> >>> Yes, As Suho mentioned diagrams gives more detailed idea and also nice >> graphical pictures for usecases also, if we can find.. :) >> >> Regards, >> Mohan >> >>> Yes, I guess we can introduce something like that to some of the >>> examples...maybe to make it easier for a first time reader to understand >>> some concepts like sequences/partitions etc.? >>> >>> Thanks, >>> Lasantha >>> >>> On 2 August 2013 22:32, Mohanadarshan Vivekanandalingam >>> <[email protected]>wrote: >>> >>>> >>>> Hi, >>>> >>>> On Fri, Aug 2, 2013 at 6:06 PM, Sriskandarajah Suhothayan < >>>> [email protected]> wrote: >>>> >>>>> It good to have a tutorial like structure, but covering all the query >>>>> specification in that will make it not user-friendly. >>>>> >>>> >>>> +1. Yes, That's right... It is better to add some graphical content >>>> without only going with words... Clearly mention the example >>>> and provide clear description also needed.. We can gradually improve >>>> that.. >>>> >>>> Regards, >>>> Mohan >>>> >>>> >>>> >>>>> >>>>> I think having a proper specification, and brief tutorial guide will >>>>> be the best case. >>>>> At the same time using samples we can demonstrate different real life >>>>> use-cases >>>>> >>>>> WDUT? >>>>> >>>>> >>>> Suho >>>>> >>>>> >>>>> On Fri, Aug 2, 2013 at 2:31 PM, Lasantha Fernando >>>>> <[email protected]>wrote: >>>>> >>>>>> Missed the link... :-) >>>>>> >>>>>> [1] >>>>>> http://docs.wso2.org/wiki/display/CEP210/Siddhi+Language+Specification >>>>>> >>>>>> >>>>>> On 2 August 2013 17:58, Lasantha Fernando <[email protected]> wrote: >>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> We are writing the Siddhi QL spec for new Siddhi 2.0.0 which will >>>>>>> ship with CEP-3.0.0 and there will be a lot of changes with Siddhi 2.0.0 >>>>>>> (Changes in syntax structure, Partitioning, Event Tables, Output Rate >>>>>>> Limiting, External Time Windows etc.). We feel that the current doc >>>>>>> structure can be improved to make it more easier for a user to learn >>>>>>> Siddhi. Should we make it similar to a strict language specification >>>>>>> (Ordered, categorized by similarity), or maybe follow a more tutorial >>>>>>> like >>>>>>> approach? >>>>>>> >>>>>>> The current Siddhi docs are available at [1]. Please send your >>>>>>> suggestions, feedback. >>>>>>> >>>>>>> Thanks, >>>>>>> Lasantha >>>>>>> >>>>>>> -- >>>>>>> *Lasantha Fernando* >>>>>>> Software Engineer - Data Technologies Team >>>>>>> WSO2 Inc. http://wso2.com >>>>>>> >>>>>>> email: [email protected] >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Lasantha Fernando* >>>>>> Software Engineer - Data Technologies Team >>>>>> WSO2 Inc. http://wso2.com >>>>>> >>>>>> email: [email protected] >>>>>> mobile: (+94) 71 5247551 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *S. Suhothayan >>>>> * >>>>> Associate Technical Lead, >>>>> *WSO2 Inc. *http://wso2.com * >>>>> <http://wso2.com/>* >>>>> lean . enterprise . middleware >>>>> >>>>> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >>>>> twitter: http://twitter.com/suhothayan | linked-in: >>>>> http://lk.linkedin.com/in/suhothayan* >>>>> * >>>>> * >>>>> >>>> >>>> >>>> >>>> -- >>>> *V. Mohanadarshan* >>>> *Software Engineer,* >>>> *Data Technologies Team,* >>>> *WSO2, Inc. http://wso2.com * >>>> *lean.enterprise.middleware.* >>>> * >>>> * >>>> email: [email protected] >>>> phone:(+94) 771117673 >>>> >>> >>> >>> >>> -- >>> *Lasantha Fernando* >>> Software Engineer - Data Technologies Team >>> WSO2 Inc. http://wso2.com >>> >>> email: [email protected] >>> mobile: (+94) 71 5247551 >>> >> >> >> >> -- >> *V. Mohanadarshan* >> *Software Engineer,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com * >> *lean.enterprise.middleware.* >> * >> * >> email: [email protected] >> phone:(+94) 771117673 >> > > > > -- > *Lasantha Fernando* > Software Engineer - Data Technologies Team > WSO2 Inc. http://wso2.com > > email: [email protected] > mobile: (+94) 71 5247551 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *V. Mohanadarshan* *Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com * *lean.enterprise.middleware.* * * email: [email protected] phone:(+94) 771117673
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
