On 15 mai, 03:06, Alyxandor <[email protected]> wrote:
> Are you getting a "wrong package error"? Because if you aren't, you
> should!
Actually, I'd rather say you shouldn't add your "super" to the
projects build path (no need to compile the classes to Java .class,
with the risk of having them used in place of the Java runtime's ones;
only the source is needed, and only for the GWT Compiler, so what's
needed is that the "super" is in the classpath, not the build path!)
(however, adding it to the build path in Eclipse brings you better
editing, with better code completion, etc.)
Finally, it's more a matter of taste than a "rule" or even "best
practice"; but you have to understand what it means when you add the
"super" to the build path or not.
> Also, you've got to make your java.io hack-pack-age another level
> deeper...
Not necessarily. GWT's Emul package uses <super-source/>, and so do I
in GWT-in-the-AIR (cf.
http://code.google.com/p/gwt-in-the-air/source/browse/trunk/super/net/ltgt/gwt/air/emul/
)
> You don't need to make two different source folders, that's
> just to minimize IDE confusions....
My personal taste is the opposite (same as what's done in GWT's own
code)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
