Generator, get method body

[Manuel Carrasco Moñino]

Hi all

Is there a way to get the body of a method in a generator? I've seen JMethodBody is used in compile time, but I dont figure out how to get it in generators.

Thanks

[Roberto Lublinerman]

Can you share what you are attempting to do? Generators only get to see structure (class hierarchy and method definitions) as far as I know.

[Manuel Carrasco Moñino]

Hi Roberto, sorry by the delay.

What I'm doing is a generator for presentations. Given a java class with my example methods, create a set of html slides. 

The generator reads the javadoc and the body of the method, and put them in a hash table into the generated class. Then in client side I can use this info to insert the code and wording in my slides using gwtquery.

You can see my generator in github [1], focus on parseJava() in line #73.

Right now I'm using japa.parser.JavaParser [2], but I'm wondering if there is a way to use gwt parsers so as I dont have to import a 3party library.

[1] https://github.com/manolo/gwt-slides/blob/master/src/main/java/org/gquery/slides/bind/SlidesGenerator.java#L73

[2] https://code.google.com/p/javaparser/

Thanks

- Manolo

--
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[John A. Tamplin]

On Thu, May 23, 2013 at 5:28 PM, Manuel Carrasco Moñino <man...@apache.org> wrote:

What I'm doing is a generator for presentations. Given a java class with my example methods, create a set of html slides. 

The generator reads the javadoc and the body of the method, and put them in a hash table into the generated class. Then in client side I can use this info to insert the code and wording in my slides using gwtquery.

That sounds a lot like what Showcase does -- maybe this will help:

https://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/showcase/src/com/google/gwt/sample/showcase/generator/ShowcaseGenerator.java 

--
John A. Tamplin

[Manuel Carrasco Moñino]

Thank John for the link.

The ShowcaseGenerator, is actually reading the content of the source files and generating .html files, but I want to extract method bodies and their javadoc so what I need an AST. So my question is more about how to use the gwt ast from a generator. 

 

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.

[John A. Tamplin]

On Thu, May 23, 2013 at 7:56 PM, Manuel Carrasco Moñino <man...@apache.org> wrote:

The ShowcaseGenerator, is actually reading the content of the source files and generating .html files, but I want to extract method bodies and their javadoc so what I need an AST. So my question is more about how to use the gwt ast from a generator.  

The GWT AST is not available to generators, so you will have to build your own -- you can use JDT as that is included with GWT.

--
John A. Tamplin

[Roberto Lublinerman]

Even if it were accessible to the generators the GWT AST does not contain javadocs nor comments. 

Roberto Lublinerman | Software Engineer | rlu...@google.com | 408-500-9148

--

[Manuel Carrasco Moñino]

It seems that the eclipse-jdt-core included in GWT doesnt have certain classes like ASTParser. I would give a  try including the eclipse dependency in my pom.xml.

--

[Manuel Carrasco Moñino]

Good to know. thanks.

[Roberto Lublinerman]

ASTParser should be in eclipse-jdt-core, although there seems to be different AST representation, GWT uses the one in org.eclipse.jdt.internal.compiler.ast whereas the ASTParser works in org.eclipse.jdt.core.dom. JDT has a very thick api to support the eclipse editor and some simple tasks might become overly complex. I wonder if the approach you have taken using a much smaller and simpler parser is not actually better.

[John A. Tamplin]

On Fri, May 24, 2013 at 6:33 AM, Roberto Lublinerman <rlu...@google.com> wrote:

ASTParser should be in eclipse-jdt-core, although there seems to be different AST representation, GWT uses the one in org.eclipse.jdt.internal.compiler.ast whereas the ASTParser works in org.eclipse.jdt.core.dom. JDT has a very thick api to support the eclipse editor and some simple tasks might become overly complex. I wonder if the approach you have taken using a much smaller and simpler parser is not actually better.

When I needed to parse the source to get parameter names from interface methods (which aren't included in the bytecode), I used CodeSnippetParsingUtil in JDT and it seemed straightforward enough.

--
John A. Tamplin

[Manuel Carrasco Moñino]

Agreed, I've tried to use the eclipse stuff in gwt-dev and my code get much more complex, so finally I keep using javaparser.

Thank guys

- Manolo

On Fri, May 24, 2013 at 12:33 PM, Roberto Lublinerman <rlu...@google.com> wrote:

ASTParser should be in eclipse-jdt-core, although there seems to be different AST representation, GWT uses the one in org.eclipse.jdt.internal.compiler.ast whereas the ASTParser works in org.eclipse.jdt.core.dom. JDT has a very thick api to support the eclipse editor and some simple tasks might become overly complex. I wonder if the approach you have taken using a much smaller and simpler parser is not actually better.

--