Hi Diannel
Thank you for the reply, I know How painful is it to impl. generic
back.. in j2me. I am glad that Intents could help here.
However, Intents way does open up certain other issues of code clarity
as said in my message.. Specially the compile check and passing
different parameters to
On Sat, Jan 31, 2009 at 8:12 PM, Raja Nagendra Kumar
nagendra.r...@gmail.com wrote:
In the contex of one each activity approach, we the following
advantages
- Go with just one activity for the enitre
application, hence no need to think of managing many activities life
cycle
Hi Firedger,
Thank you bringin clarity by way of internal and external.
The one I am refering here is for internal usage. The application I am
refering here has
Main menu list, which has Settings and About and Help as menu items.
On user choosing Settings it would show submenu
Login
Register
I remember reading about Activities as functional units, which are
reusuable across the applications and would take life based Intents
raised by other applications.. If this understanding of mine true.. I
have the following questions..
1. In an application.. e.g I display list of folders
There are two things that might clarify the use of intents.
1. There are internal and external intents. Internal intents start an
Activity of the same application (by giving the class name). This is
recommended to ensure the lifecycle.
2. Intents can have extra values used as input to the next
Could any one from Android team, pl. provide your comments..
--~--~-~--~~~---~--~~
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
Is it advisable to uses Intent approach from switching from one view
of the other, which are part of the same application
Yes, it is advisable.
Peli
www.openintents.org
On Jan 24, 8:22 am, Raja Nagendra Kumar nagendra.r...@gmail.com
wrote:
Is it advisable to uses Intent approach from
7 matches
Mail list logo
