must be declared in the manifest. That is WHY it is named 'manifest':
it is like the manifest that a shipper fills out, listing all the
goods in the shipment.
But I am curious what programming problem Snap believed was best
solved by making the dynamic code an Activity. I don't believe such a
step really is necessary, Snap's choice of this step is probably based
on a misunderstanding of the nature of an Android Activity; but until
Snap tells us more about the programming problem, I can't be sure.
On Jun 29, 1:33 pm, DonFrench <dcfre...@gmail.com> wrote:
> So declare it!
> On Jun 25, 7:00 pm, Snap <snap4...@gmail.com> wrote:> I'm trying to write some dynamic code that I load a new class that's
> > supposed to be an Activity and I want to start it, but using the
> > regular startActivity(Intent) wants the Activity to be "Declared" in
> > the AndroidManifest.xml file.
> > Any clue?
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to email@example.com
To unsubscribe from this group, send email to
For more options, visit this group at