By the way what I wrote in this one is actually common-sense, nothing smart or special. Question is at which point does it go from “hiding the innards” to “rewriting the entire thing”?

* I should add that it is not so much about abstraction rather than “guaranteed behaviour” that I am after. I know its a blurred line, but an important one nonetheless. Also I dont want layers. I just like little components that I can retrofit as I need them…

The Java AppEngine impl makes code reuse much easier (e.g. using JPA) which is a very much a Java way of doing things. However, its a slipper slope and next think you know you’ve truckloads of XML & boilerplate. Of course the alternative solution is to hide it all away and do things automagicly, but people dont like magic either.

Is there a middle ground?

By the way, what great things are you doing with android?

But can you PLEASE turn off the SnapShot service? I mean, 1) It gets in the way, and 2) it’s 1/32nd the original screen size, so there’s no way you can read anything on it, right?

I’d much rather see the target page title on mouseover, than an unreadable thumbnail of a page.

Thanks for reading (or not.) I’m on a campaign to rid the world of mouseover web page previews. =)

But can you PLEASE turn off the SnapShot service? I mean, 1) It gets in the way, and 2) it’s 1/32nd the original screen size, so there’s no way you can read anything on it, right?

I’d much rather see the target page title on mouseover, than an unreadable thumbnail of a page.

Thanks for reading (or not.) I’m on a campaign to rid the world of mouseover web page previews. =)

Mate did this one workout ok for you?

Cheers
sri

Sorry for the late one mate. Just checked both your comments. I thought Il check out the latest SDK and try it out again. So is it working fine for you now?

cheers
Sri

I am trying to implement the Parcelable interface using Eclipse and the 1.0 r2 SDK, and I am getting this error message:

MyClass.java is in the way of MyClass.aidl

I tried the project structure you described in your original post but the problem remains.

Do you have any idea why?
Thanks.

Thanks heaps for that mate. I had written that on a very early version of the SDK (M5 I think), earlier this year. I hadnt checked it for the later SDKs, which may explain the slight differences (or am I wrong in this??)

Glad you got it working and thanks for posting the fixes/updates for this. Appreciate it mate.

What are you working on anyway?

Cheers
Sri

my AIDL is simply this:

package com.foo;

import com.foo.MyParcelable;

// one-way interface so the server does not block waiting for the client.

oneway interface IMyInterface {
// Called when a parcel of information has been received
void localInput(in MyParcelable p);
}

——- NOW, the secret is that my Parcelable implementation was fielding complaints from Eclipse for its untemplated CREATOR member. It had to be changed to the following form from the examples provided in the docs (note addition of in the constructor and definition of CREATOR):

within MyParcelable.java:

public static final Parcelable.Creator CREATOR
= new Parcelable.Creator() {
public MyParcelable createFromParcel(Parcel in) {
return new MyParcelable(in);
}

public MyParcelable[] newArray(int size) {
return new MyParcelable[size];
}
};

Hope this helps.

rather than call these files file1.java, etc, why not

MyParcelableClass.aidl

IMyFirstInterface.aidl

etc

Where are the .java files that are generated expected to appear? Under src/ or under aidl/ ? One (only) of my interface.java files is being generated under aidl/ and the other is not kicking off, presumably because it is using my parcelable class.

Confused here…

Tom Humes

Mate glad someone found it useful My first real contribution to the world I guess!!

Cheers
Sri

wow quick response. thanks for that. was doing this post at midnight . i will update it asap… (how do you spell posterior by the way?)

an seconly you dont need an ant file. That was preceisely what I had wanted to avoid. It was going to be a bit of work to do all that manually. the reason is that having the entry in you .classpath takes care of that and ensures all folders of the type “src” are included in auto-build as I had discovered.

you are right, i had thought that eclipse would have tried to compile all aidl files into .java files regardless of them parcelable or not. But this turned out not to be true. As it happened with my project, the aidl files corresponding to existing parcelable objects did not get compiled as (i think) eclipse was able to find .java files for this.

There is another explanation, but I am not fully convinced about it, which goes as follows:

aidl.exe has a “-b” switch that forces the aidl compiler to NOT compile parcelable aidl files. Now this rule I believe is sort of being enforced by eclipse but if the .java and .aidl files are in the same folder, eclipse complains.

Cheers
Sri

But I don’t see how. What’s the difference between class1.aidl and class2.aidl, sitting beside each other in aidl/package2/, which cause one to be compiled buy AIDL and other to not be?

I assumed I’d need to create a little ant file and “manually” launch it to get the contents of my aidl/ subdirectory correctly compiled.

Thanks