[Mono-bugs] [Bug 632611] Application name is that of the activity class, not specified name

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Aug 20 14:34:09 EDT 2010



--- Comment #13 from Jonathan Pryor <jpryor at novell.com> 2010-08-20 18:34:08 UTC ---
Frankly, this keeps getting scarier and scarier to me.

Let's look at the <activity/> docs, shall we?

<activity/> [0] itself has 21 attributes, and can contain <intent-filter/> [1]
(3 attributes) and <meta-data/> [2] (3 attributes) elements, and
<intent-filter/> can in turn contain <category/> (1 attribute) and <data/> (7

All of these elements and attributes have various semantics and constraints on
their values.  And since it's XML, I don't see anything preventing you from
having multiple different sibling <intent-activity/> elements.  I don't know
what the semantics would be, nor do I particularly want to find out.

The prospect of defining attributes to support generating these 6 elements and
35 attributes is...daunting.  And if we only support some subset, either the
tooling is ignored or we have the prospect of merging things together (probably

Is there some (E) that doesn't involve writing tons of code to generate XML? 
Perhaps a "simple" merge process where the single most important thing that
monodroid does -- ensure that //activity/@android:name matches the type name
that monodroid generates -- is properly set?

For example, we could have monodroid look for //activity/@android:name values
and if they exactly match either the Name of an activity ("HelloActivity") or
the FullName of a an activity ("Mono.Samples.HelloActivity"), monodroid will
replace that attribute value with the name of the generated Java proxy, and
everything else would be unchanged.

This "simple" amount of merging should be simple enough to support, would keep
complicated XML generated outside of monodroid (and in the hands of developers
via AndroidManifest.xml), and won't drive me to drink.


[0] http://developer.android.com/guide/topics/manifest/activity-element.html
[2] http://developer.android.com/guide/topics/manifest/meta-data-element.html

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list