Re: @DontCompileToJavaScript method annotation
+1 to the "@JavaOnly" annotation On Jun 22, 4:57 pm, Tom Sorgie wrote: > I've been thinking the same thing, but taking it from a reverse > perspective. In fact i just posted a question about being able to use > the @GWTCompatible annotation to get reuse out of server code. I > didn't really connect that to the other side - which is writing code > in your client that you only want available from the server - till i > just read your post. I guess in that circumstance you would be > marking code (class, method, or var) written in the client package as > @GWTIncompatible. That would automatically remove it from the source > tree before gwt-compilation. > > Good to see that someone else is hitting the same issue. > > tom. > > On Jun 22, 4:46 pm, Dave Ford wrote: > > > > > Are there any plans for gwt to provide a method annotation that > > instructs the GWT compiler to *not* include that particular method in > > the generated JavaScript. Here is my justification for this feature. > > > One of the appeals of GWT (for me) is that I have been able to achieve > > a decent amount of client/server code reuse. Specifically, i have a > > number of classes that I can use on both the server (in a jvm) and in > > the browser (in my gwt app). This is a huge benefit of GWT over, say, > > Flex or native JavaScript frameworks. > > > I can't be the only one who appreciates this benefit. Here is an > > entire product to address this same concern (only > > inverted):http://www.aptana.com/jaxer > > > The problem is, creating java classes that run in the server and in > > client (gwt app) can lead to jumping thru lots of whoops and some > > major code refactoring. There are many times where it would be just so > > easy (if such a thing existed) to add an annotation to a method (or a > > class). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: @DontCompileToJavaScript method annotation
I've been thinking the same thing, but taking it from a reverse perspective. In fact i just posted a question about being able to use the @GWTCompatible annotation to get reuse out of server code. I didn't really connect that to the other side - which is writing code in your client that you only want available from the server - till i just read your post. I guess in that circumstance you would be marking code (class, method, or var) written in the client package as @GWTIncompatible. That would automatically remove it from the source tree before gwt-compilation. Good to see that someone else is hitting the same issue. tom. On Jun 22, 4:46 pm, Dave Ford wrote: > Are there any plans for gwt to provide a method annotation that > instructs the GWT compiler to *not* include that particular method in > the generated JavaScript. Here is my justification for this feature. > > One of the appeals of GWT (for me) is that I have been able to achieve > a decent amount of client/server code reuse. Specifically, i have a > number of classes that I can use on both the server (in a jvm) and in > the browser (in my gwt app). This is a huge benefit of GWT over, say, > Flex or native JavaScript frameworks. > > I can't be the only one who appreciates this benefit. Here is an > entire product to address this same concern (only > inverted):http://www.aptana.com/jaxer > > The problem is, creating java classes that run in the server and in > client (gwt app) can lead to jumping thru lots of whoops and some > major code refactoring. There are many times where it would be just so > easy (if such a thing existed) to add an annotation to a method (or a > class). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
@DontCompileToJavaScript method annotation
Are there any plans for gwt to provide a method annotation that instructs the GWT compiler to *not* include that particular method in the generated JavaScript. Here is my justification for this feature. One of the appeals of GWT (for me) is that I have been able to achieve a decent amount of client/server code reuse. Specifically, i have a number of classes that I can use on both the server (in a jvm) and in the browser (in my gwt app). This is a huge benefit of GWT over, say, Flex or native JavaScript frameworks. I can't be the only one who appreciates this benefit. Here is an entire product to address this same concern (only inverted): http://www.aptana.com/jaxer The problem is, creating java classes that run in the server and in client (gwt app) can lead to jumping thru lots of whoops and some major code refactoring. There are many times where it would be just so easy (if such a thing existed) to add an annotation to a method (or a class). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
