> But, this shouldn't be a problem much longer since I should be aquiring a
> Tungsten (and access to this part of the API) to specifically bring
> plucker code up to par. Hopefully soon enough the problem you describe
> will be fixed.
Er, ah, uhm... if Palm doesn't hand it out, and you gain access to
it through them, and it ends up in Plucker... aren't we putting ourselves in
potential jeapordy there by making it publically available in the source?
d.
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
