Ok, then we had similar suggestions :-)

Somehow extend the default information about intent filters with
additional information provided by the developer (either in the
Manifest, or through separate intents).

Whether any of these is more effective than writing good documentation
remains to be seen :-)
At least it could help in those cases where applications need to
extract this information programmatically.

Peli

On Feb 2, 4:05 pm, dar <dher...@gmail.com> wrote:
> It does not exist, it is meant to be an example of how it could be
> done.
>
> On Feb 2, 9:11 am, Peli <peli0...@googlemail.com> wrote:
>
> > > In Android, to make it easier to let developers communicate how to use
> > > intents you could add a url to document how to use the Intent to the
> > > intent-filter.
> > >       <usage-url android:name="http://mydomain.com/android-api/appname/
>
> > Is this something that exists, or did you just make this up as an
> > example, how it *could* be done?
> > I could not find it in the documentation.
>
> > The only place to put custom values would be 
> > meta-data:http://code.google.com/android/devel/bblocks-manifest.htmlhttp://code......
>
> > Peli
--~--~---------~--~----~------------~-------~--~----~
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 unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to