When I wrote "I'm sure you are starting to see that what you thought
of doing was made intentionally difficult" I was referring the fact
that when you create an instance of LinearLayout, or any other class
in the View hierarchy, you have to specify a Context (an abstract
class) in the constructor o
@Zigurd: Using Intents is fine and I'm using that as well.
But my question was more about creating a LinearLayout and adding child
views to it outside an Activity (like in a regular Java class) and then
spawning an Android Activity based on certain parameters (say some
parameters derived from a ser
I'm sure you are starting to see that what you thought of doing was
made intentionally difficult.
The reason is that, if you do it right, taking the code for an
activity and moving it to another application is easy. It's part of
Android's modularity. The data you pass using an Intent object, and
"
If I were to have one class(java non Android but within the same
Application) create a LinearLayout dynamically consisting of 'n' views
And then let us say we want to spawn a new Activity with this
LinearLayout in it then how would we do this.
Is there a good approach for this?
I do realize th
Thanks a lot.
I just wanted to know if such things are possible and shud it be done.
I was havin a discussion on Intents and someone raised this question. After
thinking about it for a while and trying it out (obviously it didn't work),
I thought I'd ask for help on the forum.
What we were trying
Can you clarify what you are trying to do? It's hard to see why you
want to do what you are asking about.
If you are trying to display the same information, from the same data
model, in two identical-looking views in two different activities, you
should create a class that extends AdapterView if y
6 matches
Mail list logo
