I did not get the use case of this feature.
Do u mean to say that instead of usingItemLabelAnchor ila = ....
I can useILA ila = ...
If so this does NOT make good reading/maintenance as well
My understanding is that import aliasing exists to allow otherwise identical class names to be disambiguated without having to provide a full class name and the chance to reduce particularly long class names to something more memorable.
import java.util.Labelimport com.company.acme.Label as AcmeLabelimport org.jfree.chart.labels.StandardCategoryItemLabelGenerator as LabelGenerator
swaroop, what Daniel writes above is my understanding too. Plus, it's easier to write "BF" than "BorderFactory". But, I didn't invent this, so don't blame me if you don't like it. That's Groovy. Look up Groovy and write to those guys if you have problems with this. In terms of reading/maintenance, the screenshot above shows you quite clearly how the IDE can help you by providing syntax coloring so that at one glance you can see your import aliases.
Could I ask which plugin this is ? Is this the Coyote plugin you mentioned in some previous post or is this some other dedicated Groovy/Grails plugin ?
Monday, October 22
9:00 - 9:45: Moscone West - Room 2014
Delivering Mobile Apps to the Field with Oracle JET (DEV6242)
Over the last
few days, I introduced and held an Oracle JET workshop in Oslo,
earlier in the same week in Amsterdam, the week before that...
Together with my colleague JB Brock I've spent the past week in
South Africa. Last year, with Andrejus Baranovskis from Oracle