09-04-2010 10:00 AM
i didnt use UiAction or contextobject.
I just get call in my entity and from there assuming that user had selected this entity. I start doing what i want to.
09-04-2010 12:42 PM
I have published many entities say 50 using appcontentmanager.
The method getUiActions is available in every entity. So whenever user select a result, getUiActions corresponding to that entity is invoked. And from there you can take over, do what you want to do, as you know which entity is invoked. Take care that you should do stuff in a seaparate thread.
09-04-2010 01:49 PM
You use none of those. Since the getUiAction is in the SearchableEntity, you should have the selected item with it. Then you launch your app with alternate entry point with an argument or pass it through runtime store or something.
My guess is that your inserted contents are fine as long as the uss don't need to interact with your Searchable. But once it does (and who knows when and why it does) and doesn't get that SearchableEntity back, then it will wipe your stuff out.
Yea.... i am hoping for an update too. Of all the new things I saw from OS6, the USS is what impressed me the most (which is why I am implementing it even though not much ppl can use it... Torch isn't even out in its home country :-P). I know it's a catch-up feature much like other part of OS6 but it actually managed to out do the integrated search in other platform (iPhone doesn't allow 3rd party content I don't think... android is pretty much the same but it doesn't have the keyboard. The slide-out-and-just-type search edged out android just a bit.) This is almost like those type-ahead-search in Firefox and Vim. It's unfortunate that the API is a bit botched.
09-04-2010 10:10 PM
thanks again for pointing out that USS could wipe off data in some unknown cases. didn't thought in that way.
glad that you got to know how to get it work for you.
also have a look at below thread, another discussion about some problems with USS (Unified Search Service)