[android-developers] Re: My experience with LVL and the precedence it sets

2010-07-31 Thread Krischik Martin
Hi, > As for importing java.lang.String, those 2 files have been created > automatically by aidl (see the files in aidl/) and the tool doesn't > care about unneeded imports and automatically put import statements > for all the used classes. Heretic question: Import is optional so why import at al

[android-developers] Re: My experience with LVL and the precedence it sets

2010-07-30 Thread andrew android
I just started using the LVL also. I had problems adding a reference to the LVL project (I kept getting manifest errors immediately upon adding the reference) so I just added it directly. Then, I tried to buile the sample code into my project but I find it all very "clunky". I think it is absurd

[android-developers] Re: My experience with LVL and the precedence it sets

2010-07-29 Thread Mark Carter
I believe I'm using the default eclipse compiler warning settings and I got a bunch of "unused import/instance variable" warnings in my workspace when adding the LVL project. Furthermore, all the warnings were doubled up - once for the library project at the top level and once for the library proje

[android-developers] Re: My experience with LVL and the precedence it sets

2010-07-28 Thread Zsolt Vasvari
Thanks for your answer, Xavier. > $NON-NLS is something specific to Eclipse that we do not use in Android. > Our convention for the android source code do not enforce the use of > this qualifier. > > As for importing java.lang.String, those 2 files have been created > automatically by aidl (see th