Hi, basically my question is which of the below methods is better in terms of app design and UI:
M1: Loding dialog show on first activity and then moving on to next activity and then displaying data. M2: Moving to next Activity, then showing loding dialog and then displaying data On Fri, Feb 17, 2012 at 3:15 PM, moktarul anam <[email protected]> wrote: > > HI Giles > if your web service data he heavy then i will suggest you to > store in database or local files. otherwise memory will be allocated > through out ur application( if u store in static variable/ stack > memory). > > if your web service data is xml file use saxParser. ( android sax > parser) > > Moktarul anam > > > > On Feb 17, 12:09 pm, giles ian <[email protected]> wrote: > > Hi, > > > > I have 2 activities A & B. Both display data fetched from 2 different web > > service lets say ws1 and ws2 > > > > When i click on a button on Activity A i call ws2 in that avtivity itself > > and show loading dialog there itself and then move to Activity B and > > display data.(In this case i have to save lot of data in static variables > > so that they can be shared across activities as im getting data on > Activity > > A and need to display on Activity B) > > > > Is this rite approach. > > > > The other option that i have is i call ws2 from Activity B instead of A > > > > Which is a better way. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
