Philippe Cloutier

Solving this would obviously require major efforts, so it's unlikely to happen shortly. Meanwhile, Workrave offers good usage statistics. These cover breaks:  ...as well as activity:  I realize...

Thank you very much for this ticket @mwoz123 I agree with the request, but having used Workrave for years, I must say I disabled the daily limit after a couple...

Thank you for this request. I suggest avoiding the "FR" acronym. It is highly ambiguous and I have never seen it in use before. Workrave is one Stretchly equivalent which...

[The README file's _Known issues_ section](https://github.com/hovancik/stretchly/blob/trunk/README.md#known-issues) already takes the first approach, but unfortunately fails to mention several important issues.

> Well, _Known issues_ mention only technical issues (that I am not able to fix) not the _usage issues_: If you want to keep a specific list of issues which...

Is there a reason why this ticket is closed?

@hovancik I see that you may be Stretchly's main contributor, but this does not prevent others from contributing to Stretchly. In fact, someone else may become its main contributor soon....

> FWIW, I just did some comparison, and I appreciate the value of this, but indeed _maintaining_ comparisons with projects all being moving targets is really cumbersome. Good point. So...

I agree - it would be better to have a mechanism for specifying dependencies than ordering mechanisms.

@daminichopra are you trying to reproduce on demo.ckan.org, or on another CKAN instance?