Allow custom formatters

[arcan1s]

No description provided.

[arcan1s]

RFC:

1. Tag configuration: file $AWHOME/formatters/formatters.ini, section Formatters. Key - related widget key, value is formatter name.
2. Each formatter should be stored inside $AWHOME/formatters as .desktop file, section is Desktop Entry. Configuration incudes default fields:
   • Name - see above
   • Comment - comment, optional
   • Type - formatter type (see descriptions below)
3. Formatters
   • NoFormat formatter - just put text as is. No special configuration required.
   • Float formatter - format any numeric value
     • FillChar - char, character which will be put to fill width, default is space
     • Format - char, qt specific number format, http://doc.qt.io/qt-5/qstring.html#argument-formats, default is f
     • Multiplier, Summand - doubles which will be used for calculation in the following formula: Multiplier * value + Summand
     • Precision - int, amount of numbers after comma, default is -1
     • Width - int, amount of number for value, default is 0
   • DateTime formatter - format qdatetime objects (like $ctime tag)
     • Format - string, qt specific datetime format line, http://doc.qt.io/qt-5/qdatetime.html#toString
   • Script formatter - custom JS code. Value will be inserted as value variable
     • AppendCode - boolean. If true your code will be inserted between (function(value) { and })
     • HasReturn - boolean, if false your code will be appended ; return output;, e.g. it means that your code just calculates output variable. Works only if AppendCode=true.
     • Code - string, your JS code.

[arcan1s]

at the moment these keys works normally with BUILD_FUTURE=ON, but requires configuration inside $AWHOME/general.ini, section Formatters for applied formatters list. And one section which named as Name value per formatter

[arcan1s]

For consistent with other extensions (and actually according to freedesktop standard) X-AWprefixes have been added to keys.

Another change is the following: formatter.ini will be read from global configuration first and then will be overrided by local configuration (if there will be conflicting key names)