I am interested in this approach too. Do you mean having a sort of
toBundle() method and a constructor that accept a Bundle, or is there
something more slick?
Thanks,
Federico
On 26 Nov, 10:31, pedr0 <pulsarpie...@gmail.com> wrote:
> Hi TreKing, could you explain the 3rd way, I have to send to another
> application an ArrayList<CustomObject>, how to do it?
>
> On 25 Nov, 23:53, TreKing <treking...@gmail.com> wrote:
>
> > On Thu, Nov 25, 2010 at 9:55 AM, pedr0 <pulsarpie...@gmail.com> wrote:
> > > I read some tutorial about the object of this topic (Passing object via
> > > intent) there tutorial said that there are two way:
>
> > > 1) My object must implement Parcelable Interface
>
> > > 2) I have to move my object static, for share data between activities.
>
> > A 3rd way that I prefer: make your object "bundleable", where it can put
> > it's relevant data into a Bundle and re-construct itself from a Bundle,
> > which you put in the intent. This eliminates the complexity and
> > class-loading issues of Parcelable and the common issues with statics.
>
> > ---------------------------------------------------------------------------
> > ----------------------
> > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago
> > transit tracking app for Android-powered devices
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
