Thanks, hackbod, for your comments.
I see how this API is satisfactory for the stated purpose of notifying
other view elements when they need to re-sync with the
ContentProvider. Of course, that is not the only kind of application
that cares about changes to content, and I personally wish you guy
On Mar 26, 9:30 pm, severian <[EMAIL PROTECTED]> wrote:
> I really hope they fix this API to indicate what has changed, because
> ContentObserver is a nice idea - it allows different frontend and
> backend applications to share a common data pool.
It's a very intentional design. In fact original
I totally agree.To detect even a single change, I will surely have
to rescan everythingThats a lot of work of course
Dexter.
On Mar 27, 9:30 am, severian <[EMAIL PROTECTED]> wrote:
> The problem is that ContentObserver.onChange() doesn't tell you what
> changed. So how do you figure
The problem is that ContentObserver.onChange() doesn't tell you what
changed. So how do you figure it out? Well, as far as I can tell you
have to keep your own copy of everything you might care about in the
database, and then when you get onChange() you read everything from
the ContentProvider and
Great that you liked the idea.
In fact, this would be useful for more than one application, so one
small background service could actually keep track of changes for
several applications. In this general sense, it would eventually be
interesting for our project as well (OpenIntents -
http://code.
Ok...this seems to be the only option to me now..I LL DO
THAT.:-)
On Mar 27, 5:20 am, Peli <[EMAIL PROTECTED]> wrote:
> > You could use a content observer, but this would require your app
> > always running to monitor for changes.
>
> So one could probably write a lightweight background s
What do you mean by sync???
On Mar 27, 12:12 am, jtaylor <[EMAIL PROTECTED]> wrote:
> Possibly using sync as well.
>
> - Juan
>
> On Mar 26, 1:42 pm, Peli <[EMAIL PROTECTED]> wrote:
>
> > Could a ContentObserver be registered for cases like
> > these?http://code.google.com/android/reference/andr
> You could use a content observer, but this would require your app
> always running to monitor for changes.
So one could probably write a lightweight background service that uses
a content observer to constantly monitor for changes, and notifies the
starting app only of those fields that have ch
You could use a content observer, but this would require your app
always running to monitor for changes.
I'm not sure of a solution off-hand besides updating your list when
your application starts. We deliberately decided to not support
having apps launched to be notified when data in a content
Possibly using sync as well.
- Juan
On Mar 26, 1:42 pm, Peli <[EMAIL PROTECTED]> wrote:
> Could a ContentObserver be registered for cases like
> these?http://code.google.com/android/reference/android/database/ContentObse...http://code.google.com/android/reference/android/content/ContentResol..
Could a ContentObserver be registered for cases like these?
http://code.google.com/android/reference/android/database/ContentObserver.html
http://code.google.com/android/reference/android/content/ContentResolver.html#notifyChange(android.net.Uri,%20android.database.ContentObserver)
Peli
On Mar 2
ok...Let me tell you what i wanted to doI have a local file that
has information about all the contacts on the phone. And my
application uses this local file and not the phone book data
directly
So I wanted that, whenever a new contact is added or an old one is
deleted, I should run a pro
No, it has nothing to do with writing a contacts provider. The
provider is the back-end data; an activity is the user interface. You
just write a new activity that operates on the existing content
provider.
On Mar 26, 3:24 am, Diego Torres Milano <[EMAIL PROTECTED]> wrote:
> If you want to writ
If you want to write your own activity implementing those actions, how
would you do that ?
Implementing a new whole ContactsProvider ?
If you only want to replace, say INSERT ?
How your new ContactsProvider can coexist with the standard one if you
want to extend its functionality ?
On Mar 26, 7:3
Ya, thanks Hackbod.I dont think I can do what i want... :-)
On Mar 26, 11:35 am, hackbod <[EMAIL PROTECTED]> wrote:
> The android.intent.action.INSERT and android.intent.action.VIEW
> actions are not broadcasts, they are actions for starting activities
> to show a UI to insert a new entry, or
The android.intent.action.INSERT and android.intent.action.VIEW
actions are not broadcasts, they are actions for starting activities
to show a UI to insert a new entry, or view an existing entry,
respectively. Thus you don't register for them with a , you
launch them with startActivity(). (You c
Thanks Megha...But, will it be provided in the subsequent releases???
Can you think of a situation where we would need this???
Dexter.
On Mar 26, 3:15 am, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I don't think that the intents for contacts added and contacts deleted
> intents are broa
Hi,
I don't think that the intents for contacts added and contacts deleted
intents are broadcasted.
So you cannot receive these intents.
Thanks,
Megha
On Mon, Mar 24, 2008 at 9:49 AM, Dexter's Brain <[EMAIL PROTECTED]>
wrote:
>
> Hello All,
>
> I have an Intent Receiver which I will be trigger
18 matches
Mail list logo
