Get your own customer support community
 

activity precedence rules

Greetings! I am in love with Slife so far.

However, Slife could be far more useful if I had the ability to (a) define precedence among rules for classifying activities, or even (b) if more specific rules took precedence over less specific rules. For example, I'd like to classify certain sites as "work" documents, eg: localhost, jquery.com, djangoproject, etc. Other sites are classified under "lifehacks", or "checking mail". But I'd like all unclassified sites visited in Firefox to be put under my "procrastination" activity.

So using the (a) approach, each rule would have a precedence rating, which could be confusing but would offer absolute control. Using (b), since an "Application" like Firefox is less specific than a "Web and Documents", the activity analyzer would first try to find a specific match to a "Web and Documents" definition. If it couldn't find one, only then would it continue searching through "Applications".

As a workaround, we can use a separate browser for work and non-work activities, but Slife shouldn't force you to work differently to make best use of it. Personally, I rely too much on Firefox extensions to be willing to split up my browsing like that, but I mention it in case other users find the classification more important than the convenience of using one browser.

Thanks for such a great product :-)
 
indifferent I’m hoping against hopes
Inappropriate?
2 people have this question

  • onceuponapriori
    Inappropriate?
    Hmm, taking the specificity further, it could apply among documents too. Eg, usually, any url that I visit at localhost will be for work, so I should be able to tell my "Work" activity that sites at "localhost" belongs to it. This is, of course, already possible. BUT, if I am working on a side project, eg, writing a web app in scheme, I want to be able to specify that "localhost:8483" is "personal". Then, if I point my browser to localhost:8483, the activity analyzer would scan through my defined urls, perhaps finding "localhost" first, and mark it as the best match. But instead of building up a list of matches, it could just keep scanning for more specific rules and storing the best match. At the end, it applies the best match.

    Unfortunately, this further refinement prevents Slife from classifying a document into more than one Activity. This is why it'd probably be good to have a precedence value (which defaults to, say, medium. rules with equal precedence are ALL matched; else, the highest precedence rule matches. So if the beginner or uninterested user never touched the precedence settings, Slife would function exactly as it does today [unless you supplied B above, which is pretty straightforward...] and only users interested in messing with it would have to worry about it).

    Sorry if that was too much rambling.

    Best!
     
    silly I’m excited
User_default_medium