Lpsmagic

(Feature Requests for v2)
(Feature Requests for v2)
Line 3: Line 3:
=== Feature Requests for v2 ===
=== Feature Requests for v2 ===
-
----
+
 
-
wolke
+
-wolke-
-
1) user-editable rc file that gets read on lpsm startup
+
 
 +
1) user-editable rc file that gets read on lpsm startup[BR]
sample ~/.lpsmrc
sample ~/.lpsmrc
   date.format=dd/MM/YYYY HH:mm:ss
   date.format=dd/MM/YYYY HH:mm:ss
Line 21: Line 22:
4) plugin support {for, e.g.: unread text count. thats the one id write, anyway}
4) plugin support {for, e.g.: unread text count. thats the one id write, anyway}
{i would make all the built-in ones just be plugins as well; would give folks a jumping off place and makes good design sense}
{i would make all the built-in ones just be plugins as well; would give folks a jumping off place and makes good design sense}
-
----
+
 
 +
--
=== Planned Features for v2 ===
=== Planned Features for v2 ===
  * C++ rewrite
  * C++ rewrite
  * plugin system
  * plugin system

Revision as of 17:36, 31 January 2012

You can find more info on first post of tmo thread. Info

Feature Requests for v2

-wolke-

1) user-editable rc file that gets read on lpsm startup[BR] sample ~/.lpsmrc

  date.format=dd/MM/YYYY HH:mm:ss
  interval=60

or have a template file:

   %img:calendar% %date:MM/dd/YY%   %img:clock% %uptime%
   %img:cpu%  %cpu% %%  %img:load% %load:1% %load:5% %load:15%
   %img:power% %battery:percent% %battery:capacity% mAh   %img:mem% %mem% %%

2) easy way to restart/reread rc file {via command line}

3) on-demand image generation {for testing mostly}

4) plugin support {for, e.g.: unread text count. thats the one id write, anyway} {i would make all the built-in ones just be plugins as well; would give folks a jumping off place and makes good design sense}

--

Planned Features for v2

* C++ rewrite
* plugin system