In the dynamic text area it would be nice if there was an advanced option to create our own variable.
In the dynamic text area it would be nice if there was an advanced option to create our own variable. That way even though there is no unread facebook variable we could add our own.
And probably a list of variables would be handy on long tap cause I dont know what im doing. 🙂
]]>
< ![CDATA[
Adding a facebook variable means that you know how to connect to facebook 😉
At the moment I plan to add a generic Tasker variable (depending on technical constraints) which would cover more use cases, though it relies on an external component
]]>
< ![CDATA[
for those that don’t use tasker (I don’t) I will add a few other sources such as battery and similar, but no facebook or twitter, etc. This is too big. Each library to do that is bigger than LL itself
]]>
< ![CDATA[
If its something that would require adding large libraries then its pobably not wort it.
I was thinking of apps like NiLS that can just figure out notification s from any android app. So that you Pierre Hébert wouldent have to add them in for us and the community could figure them out.
And we could type something like
Com.facebook.dash.activitys.dashactivty – “mesages-00”
]]>
< ![CDATA[
Generic notification support is on the TODO list but this does not mean it can be used to extract data. This need to be studied on a per application basis and is somewhat fragile. Some app may change their text upon each update, some app will display “one message” instead of “1 message”, position varies according to language, etc. So this can only a do it yourself solution.
]]>
< ![CDATA[
That sounds like what im talking about. 🙂
]]>