Thanks guys for the encouragements ! Anybody could give feedback ? Anybody already tried to do this already ?
On 17 juin, 01:33, Sky <[email protected]> wrote: > Man, that just sounds kickass! Infinitely better than writing your > parser code twice in two different languages and any time you fix a > bug or add functionality needing to do it twice. Man, if that works > that smoothly you guys will be sooo happy! > > Isn't that just exciting! woot :) > > On Jun 16, 2:06 pm, Sripathi Krishnan <[email protected]> > wrote: > > > > > Hi Laurent, > > > You actually have an interesting idea, something I have been thinking about > > for a different context for sometime. > > > I haven't used ANTLR before, I prefer JAVACC. When I analysed javacc > > generated code, most of it was plain java that GWT could easily convert to > > Javascript. The only classes that needed modifications were the ones that > > read from the File/InputSteam. In the case of javacc, they were just 2 java > > classes that are standard across all javacc projects. So, it should be > > possible to replace those classes with a client specific class that reads > > from textarea. > > > I suspect when you analyse the antlr generated code, it will follow the same > > pattern. So, it should be possible to parse your "language" on the client > > side without having to make network calls. If latency/user-responsiveness is > > an issue, its definitely a good thing to do. > > > --Sri > > > On 16 June 2010 21:54, Stefan Bachert <[email protected]> wrote: > > > > Hi Laurent, > > > > I did not use antlr, yet. However, antlr generates java code and as > > > far it generates ALL, the GWT compiler probably translates generated > > > javacode to javascript. > > > I would just give them a try. > > > > Stefan Bachert > > >http://gwtworld.de > > > > On Jun 16, 3:02 pm, Laurent PETIT <[email protected]> wrote: > > > > Hello, > > > > > I must create a rich editor. We have a custom language, and our > > > > customers will be able to edit "sentences" of this language in their > > > > browser. > > > > Now, on the server side, we already have antlr stuff to parse the > > > language. > > > > > I'm contemplating whether I should try to reuse to the maximum the > > > > existing stuff, at the (probable) cost of more client/server > > > > communications to benefit from the parser's functionality (hopefully > > > > the client side editor will be "structured") ; > > > > or whether I should rewrite a parser (by hand or with the help of a > > > > third party library which could run on GWT client code) for my client > > > > side ... > > > > > Any comments / suggestions ? > > > > > Thanks in advance, > > > > > -- > > > > Laurent > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Google Web Toolkit" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<google-web-toolkit%2Bunsubs > > > [email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
