What about this suggestion?
What about this suggestion?
In the app drawer two new events:
‘App installed’ triggered when an app is installed
‘App uninstalled’ triggered when an app is uninstalled
Those events are designed to run scripts. If possible also add the label of the installed/uninstalled app that triggered the action as a defined variable or to the LL.getEvent().getData()
This will allow to change the style of that new app instead of change all at load, place the app in a folder automatically, keep a log of recently uninstalled apps…
]]>
D5 Creation
< ![CDATA[
You can trigger all app installed, uninstalled and updated by tasker. You can’t pass the name ATM.
]]>
< ![CDATA[
I bet if we could pull this off there would be no need for the refresh button anymore. Except I don’t think this one would be scripted but rather built in. No script no menu no hair pulling out no skin wrinkles. Just 100% pure automatic update.
]]>
< ![CDATA[
That would open some interesting use case indeed. There are two technical issues at the moment. The first is exactly what Curtis Sylvester Jr. said: it should work but it don’t. On some devices install/updates are not always received and I don’t know why. The second issue is that the launcher may not be running at time of install, and its situation only a subset of the launcher is activated (parse and update data file to add an item mainly). The consequence is that most other parts are unavailable at this time (everything linked with the views). I don’t know yet how it would prevent scripts to run properly.
]]>
< ![CDATA[
If I’m not mistaken didn’t you already try to make this possible? If was a fail last time
]]>
< ![CDATA[
It was probably something else
]]>
< ![CDATA[
I don’t remember much about it. It was awhile back
]]>
< ![CDATA[
Pierre Hébert: and can you keep a log of the status updates of the apps and launch the script once for each change when the app drawer loads?
I mean: every time an app get installed/uninstalled/updated a new entry in a reserved list is created with the name of the app and the reason of the change.
Then in the load event run the script once for each entry passing that entry data (or perhaps just one passing all the list) and after that delete that list.
If the launcher is not loaded, it won’t happen anything. And if you need to refresh to see changes it will work after refreshing.
Just ideas.
Another possible solution will be a function to get the launcher’s list of updated apps in that app drawer (with uninstalled if possible), and from script keep track of the previous last one and do things accordingly.
]]>
< ![CDATA[
That’s an interesting idea. I will see what I can do with this.
]]>