Hello Dianne,

ah ok, I will try the GET_CONTENT with audio/*. But can I also use it
for artists and albums?
And yes ok, I can copy the code of your activities (I will try this
out now). But I would really appreciate to eat Google's dogfood here
and don't want to invent the wheel again by myself. I also think this
is not what the users expect from the Android platform, because maybe
my activity will be somehow different from Googles (maybe in future
versions) and the users will not understand why...

For me the intent stuff really makes up some of Android's modularity
and openness. Yes it is right that desktop Linux does not have this
feature. That's why I like Android much more than desktop Linux :-).
But I really don't want to start a flamewar on this topic. I simply do
not understand why these activities are not available anymore to 3rd
party developers. Maybe it is because of task stacks, but I don't
know.

Best regards,
Daniel

On 26 Feb., 22:10, Dianne Hackborn <[email protected]> wrote:
> Oh also, the media app still does support the proper way to have it pick a
> music track for you, through GET_CONTENT if audio/*.
>
> On Sat, Feb 26, 2011 at 1:09 PM, Dianne Hackborn <[email protected]>wrote:
>
>
>
>
>
>
>
>
>
> > The music app is an implementation detail; I don't do the app, but I assume
> > this was done because people shouldn't be relying on the implementation
> > detail of it being implemented as separate activities.
>
> > The media provider is still in the SDK, and is the same thing the media
> > application uses for this UI.
>
> > You can just copy the code you want and use it in your own activity.
>
> > This didn't "lose its openness" for third party developers in any way,
> > shape, or form.  If you want to define openness that way, well then Linux
> > desktops aren't open because they don't allow apps to launch pieces of other
> > apps at all.
>
> > On Sat, Feb 26, 2011 at 12:30 PM, Daniel 
> > <[email protected]>wrote:
>
> >> Btw, the problem is not that something was changed (yes I know it was
> >> not documented). But the platform lost some of its openness for 3rd
> >> party developers.
>
> >> On 26 Feb., 21:26, Daniel <[email protected]> wrote:
> >> > Well I don't think so. It was really cool to build apps like a mesh up
> >> > of activities others implemented.
> >> > I know a lot of developers who used exactly this intents and this
> >> > change really killed all of them. Only Google apps like "Search" are
> >> > still able to use these intents. This is not what I expect from an
> >> > open platform where 3rd party developers should be able to write apps
> >> > with the same quality as Google.
> >> > But ok if your argumentation goes that way, what shall I say, well
> >> > done my app is dead. I'm pretty sure others too.
>
> >> > On 25 Feb., 20:03, TreKing <[email protected]> wrote:
>
> >> > > On Fri, Feb 25, 2011 at 7:45 AM, Daniel <
> >> [email protected]>wrote:
>
> >> > > > The activities ArtistAlbumBrowserActivity, AlbumBrowserActivity
> >> > > > and TrackBrowserActivity cannot be started anymore by an Intent
> >> (e.g. using
> >> > > > action.PICK and "vnd.android.cursor.dir/album") since the attribute
> >> > > > android:exported is set to "false" for those activities since
> >> Android 2.3
>
> >> > > Is (or was) it documented somewhere that this is the proper way to do
> >> this?
>
> >> > > That is really annoying because the Intent stuff was once one of
> >> Android's
>
> >> > > > strength's and now you are not allowed to use this stuff any more.
> >> That's a
> >> > > > shame...
>
> >> > > Intent stuff is still one of Android's strengths - when used
> >> correctly. It
> >> > > looks like you were exploiting private implementation details to get
> >> this to
> >> > > work. You should not be surprised that it has changed.
>
> >> ---------------------------------------------------------------------------
> >> ----------------------
> >> > > TreKing <http://sites.google.com/site/rezmobileapps/treking> -
> >> Chicago
> >> > > transit tracking app for Android-powered devices
>
> >> --
> >> You received this message because you are subscribed to the Google
> >> Groups "Android Developers" group.
> >> To post to this group, send email to [email protected]
> >> To unsubscribe from this group, send email to
> >> [email protected]
> >> For more options, visit this group at
> >>http://groups.google.com/group/android-developers?hl=en
>
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [email protected]
>
> > Note: please don't send private questions to me, as I don't have time to
> > provide private support, and so won't reply to such e-mails.  All such
> > questions should be posted on public forums, where I and others can see and
> > answer them.
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to