No significant changes applied.
* function syntax has been changed to another one, any function may be called
by using the following construction:
$aw_function_name<some args here if any>{{function body if any}}
* rewrite travis.yml
* Initial syntax is the following:
* $template{{ some JS code here }} - simple template based on JS
code inside. It works the same as lambda functions, but calculates
only once.
* aw_count(regex) - keys count found for given regex
* aw_keys(regex, [separator]) - keys found for given regex and
joined by using given separator
* aw_names(regex, [separator]) - key names found for given regex and
joined by using given separator (the same as previous but w\o $)
The template and function syntax may be changed before release.
* replace `foreach` to `for (auto foo : bar)` and update CONTRIBUTING.md
accordingly
I suppose the better way is to move weather adaptor to another open
weather engine despite the fact that OWM has provided me a special FOSS
permissions. I've changed weather provider to Yahoo! Weather because
there is no good way to provide my own API key to end-users except for
being compiled to the source code.
In other hand this solution leads to the fact that humidity and
atmosphere pressure is not available for forecast more. And moreover
pressure units has been changed for current weather.
+ fix possible memory leak in dataengine aggregator
+ add "special thanks" group to acknoledgment tab
This fact caused by the qt signal-slot implementation. Even if slots
code is going into parallel they will be called in the main app thread.
And also it is used inside KF5 dataengine implementation, so I'm affraid
that it could not be optimized w\o backend rewriting
* create QTimer object in AWDataEngineAggregator class, emit signal to
this timer because timers could not be started in the separate thread
* increase limit x2 with leaving the thread pool size as was
