Hi Nuwan,
On Thu, Jun 20, 2013 at 10:02 PM, Nuwan Bandara <[email protected]> wrote: > Hi Harshana, > > > On Fri, Jun 21, 2013 at 1:21 AM, Harshana Martin <[email protected]>wrote: > >> Hi Rajeeva, >> >> Good progress! >> >> If we can get the Jaggery parser to identify atleast basic constructs in >> Jaggery, we could ship it with upcoming release as a experimental feature. >> >> @Nuwan, >> >> WDYT? >> > > I think the current state is good enough to ship. We can later add jaggery > apis, but right now javascript is working well. What I really need is to > delegate the js parsing to vjet, in the next milestone. > > Can we ship this with the current state, for DevS next release. > I'm +1 with shipping it as it is in the next DevS release if we are calling it a Developer Preview/Experimental feature. Otherwise people will assume that it is the final version of this editor. Thanks and Regards, Harshana > > Regards, > /Nuwan > > >> >> Thanks and Regards, >> Harshana >> >> >> On Wed, Jun 19, 2013 at 3:10 AM, Rajeeva Uthayasangar >> <[email protected]>wrote: >> >>> Hi, >>> I have figured out how the PHP code segment is identified through the >>> PHP start,end tags ("<?php","?>") and tested with the php code itself with >>> the jaggery start and end tags("<%","%>). It worked as expected. >>> >>> Initially I have started to work from scratch and wrote a simple parser >>> and tokenizer to identify the jaggery segment but identifying the related >>> java file for the document partitioned seemed difficult. >>> >>> So I have forked the php code started to working on that and edited the >>> existing php parser and tokenizer to identify the jaggery code segment and >>> passed the jaggery code portion to html parser. HTML parser handles the >>> jaggery code as it handles the JavaScript code segment. >>> >>> Now Jaggery, Javascript and HTML codes are corrected identified with >>> syntax coloring and code assist. I have attached the snapshot of the >>> jaggery source file. >>> >>> Thanks, >>> Rajeeva >>> >>> >>> >>> >>> On Sat, May 4, 2013 at 8:18 AM, Nuwan Bandara <[email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Sat, May 4, 2013 at 12:13 AM, Harshana Martin <[email protected]>wrote: >>>> >>>>> Hi Nuwan, >>>>> >>>>> >>>>> On Fri, May 3, 2013 at 5:29 PM, Nuwan Bandara <[email protected]> wrote: >>>>> >>>>>> Hi Harshana, >>>>>> >>>>>> IDE work is going back and forth, and we have now evaluated JSP/PHP >>>>>> and VJET without a success, >>>>>> >>>>> >>>>> I still believe PHP is the way to go. However the PHP editor was >>>>> developed using DLTK, a framework new to most of us. So there will be a >>>>> learning curve to most of us including Rajeeva, >>>>> >>>>> >>>>>> We need to find where the content getting slitted and identified as >>>>>> different regions. >>>>>> >>>>> >>>>> Yes. Finding the Document Partitioner is the current challenge. Once >>>>> we identify that, we just need to override that document partitioner with >>>>> Jaggery Document Partitioner. >>>>> >>>>> However the PHP Editor Tokenizer and Parsers are generated using Java >>>>> Cup and JFlex, standard software to generate Tokenziners and Parsers. So >>>>> understanding those 2 is also a requirement right now. >>>>> >>>>> Can someone in DevS team guide Rajeeva on this, IFAIK she has hit a >>>>>> dead end and needing some experienced help. >>>>>> >>>>> >>>>> Yes. Currently she is working with Viraj. >>>>> >>>>> However it would be better to have a weekly status update mail/meeting >>>>> which allows us to understand when to provide more help and guidance. I >>>>> will make sure we keep close eye on the progress more often at least from >>>>> now on. >>>>> >>>>> Let's meet Monday or Tuesday to discuss this further. >>>>> >>>> >>>> Great. Thanks Harshana >>>> >>>> >>>>> >>>>> Thanks and Regards, >>>>> Harshana >>>>> >>>>>> >>>>>> Regards, >>>>>> /Nuwan >>>>>> >>>>>> >>>>>> On Thu, May 2, 2013 at 2:42 PM, Viraj Rajaguru <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Apr 30, 2013 at 5:22 PM, Rajeeva Uthayasangar < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> I were asked to write a Jaggery IDE plugin for eclipse with the >>>>>>>> following features: >>>>>>>> >>>>>>>> 1.Editor syntax coloring >>>>>>>> 2. HTML and JavaScript support for Jaggery Editor >>>>>>>> 2. Code Assistance feature. >>>>>>>> 3. Code Auto Completion. >>>>>>>> >>>>>>>> Tasks completed:: >>>>>>>> https://wso2.org/jira/browse/TOOLS-1595 >>>>>>>> >>>>>>>> Initially I have started to write the jaggery editor based on VJET >>>>>>>> (JavaScript Plugin) and finished the syntax coloring part. But HTML >>>>>>>> syntax >>>>>>>> coloring is not supported. >>>>>>>> >>>>>>>> So I switched from VJET and followed the PHP Development Tools(PDT) >>>>>>>> source code which has the multi-language(JavaScript and HTML) support >>>>>>>> as >>>>>>>> we expects from Jaggery Editor. >>>>>>>> >>>>>>>> In VJET, predefined eclipse APIs can be used to identify the code >>>>>>>> partitions. But in PDT, they have defined their own class for all >>>>>>>> document >>>>>>>> partitioning. Since there is no documentation, it takes time to debug >>>>>>>> and >>>>>>>> go through the full source code to identify the necessary part. >>>>>>>> >>>>>>> >>>>>>> PHP Development Tools(PDT) is based on Eclipse 'Dynamic Language >>>>>>> ToolKit' (DLTK) which has a great support to generate editors for domain >>>>>>> specific languages. DLTK should be provided the grammar for the specific >>>>>>> language. For this thing PDT is using 'Java Cup' for generating the >>>>>>> parser >>>>>>> and they are using JFlex for generating the scanner. So when you going >>>>>>> to >>>>>>> debug the PDT code, the knowledge about above technologies (DLTK, Java >>>>>>> Cup, >>>>>>> JFlex etc.) needed and will acquire some time to get familiar with these >>>>>>> technologies. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Thanks, >>>>>>> Viraj. >>>>>>> >>>>>>> -- >>>>>>> Viraj Rajaguru >>>>>>> Software Engineer >>>>>>> WSO2 Inc. : http://wso2.com >>>>>>> >>>>>>> Mobile: +94 77 3683068 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Thanks & Regards, >>>>>> >>>>>> Nuwan Bandara >>>>>> Associate Technical Lead & Member, MC, Development Technologies >>>>>> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >>>>>> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 >>>>>> 763 9629 >>>>>> * >>>>>> <http://www.nuwanbando.com/> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Harshana Martin >>>>> Senior Software Engineer >>>>> Member, Management Committee - Development Technologies >>>>> WSO2 Inc. : http://wso2.com >>>>> >>>>> Mobile: +94 775 998 115 >>>>> Profile: https://www.google.com/profiles/harshana05 >>>>> Blog: http://harshana05.blogspot.com >>>>> Twitter: http://twitter.com/harshana05 >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Thanks & Regards, >>>> >>>> Nuwan Bandara >>>> Associate Technical Lead & Member, MC, Development Technologies >>>> WSO2 Inc. - lean . enterprise . middleware | http://wso2.com >>>> blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 >>>> 9629 >>>> * >>>> <http://www.nuwanbando.com/> >>>> >>> >>> >>> >>> -- >>> *Rajeeva Uthayasangar* >>> Software Engineer >>> WSO2, Inc.:http://wso2.com* >>> * >>> >>> >>> Mobile: +94777298873 >>> >>> >> >> >> -- >> >> Harshana Martin >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 775 998 115 >> Profile: https://www.google.com/profiles/harshana05 >> Blog: http://harshana05.blogspot.com >> Twitter: http://twitter.com/harshana05 >> >> > > > -- > * > Thanks & Regards, > > Nuwan Bandara > Technical Lead; **WSO2 Inc. * > *lean . enterprise . middleware | http://wso2.com * > *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > -- Harshana Martin Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 775 998 115 Profile: https://www.google.com/profiles/harshana05 Blog: http://harshana05.blogspot.com Twitter: http://twitter.com/harshana05
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
