| 1 | Stuff planned for future releases... (in no particular order) |
|---|
| 2 | |
|---|
| 3 | Feel free to help out with any of this stuff! :) |
|---|
| 4 | |
|---|
| 5 | |
|---|
| 6 | ---------------------------------------- |
|---|
| 7 | Client driver |
|---|
| 8 | |
|---|
| 9 | An LCDproc client can connect, request the "client" driver, then get |
|---|
| 10 | all screen information sent to it! This allows things such as logging |
|---|
| 11 | in remotely and starting up a curses display of LCDproc. It also |
|---|
| 12 | gives another method for writing drivers. In a sense, it could even |
|---|
| 13 | let you write and link in new drivers without having to recompile and |
|---|
| 14 | restart LCDproc... |
|---|
| 15 | |
|---|
| 16 | Another bonus is that LCDproc will come with a client which can, for |
|---|
| 17 | example, start up a "client" driver to send "keypresses" from the |
|---|
| 18 | command line. Or, |
|---|
| 19 | |
|---|
| 20 | lcdtool -key A |
|---|
| 21 | |
|---|
| 22 | would have the same result as pressing a key on the keypad. |
|---|
| 23 | |
|---|
| 24 | |
|---|
| 25 | ---------------------------------------- |
|---|
| 26 | Menus / Client menus |
|---|
| 27 | |
|---|
| 28 | LCDproc will have a "menu" mode, where various options can be |
|---|
| 29 | configured. You can rearrange the screenlist, change the contrast, |
|---|
| 30 | add/remove drivers, change screen priorities, kick off clients, etc... |
|---|
| 31 | |
|---|
| 32 | You can also access client menus to configure options in each client. |
|---|
| 33 | |
|---|
| 34 | ---------------------------------------- |
|---|
| 35 | Config Files... |
|---|
| 36 | |
|---|
| 37 | LCDproc will use a config file for its parameters, like other |
|---|
| 38 | programs; instead of relying upon long command lines. Keypresses, |
|---|
| 39 | drivers, and other things will be configurable here. Also, LCDproc |
|---|
| 40 | will have the ability to load/modify/save config files via its menu |
|---|
| 41 | interface, so you don't have to edit it by hand. |
|---|
| 42 | |
|---|
| 43 | Info about particular clients/screens will also be stored in the |
|---|
| 44 | LCDproc config file, so you can (for example) save your preferences |
|---|
| 45 | about screen priorities, etc... |
|---|
| 46 | |
|---|
| 47 | Code will be made generic, so that other programs can use it for their |
|---|
| 48 | own config files. Clients may want to use this.. |
|---|
| 49 | |
|---|
| 50 | ---------------------------------------- |
|---|
| 51 | Scheduling modes |
|---|
| 52 | |
|---|
| 53 | Instead of the simplistic "round robin" circular screen-scheduling in |
|---|
| 54 | the current release, later versions will offer several different |
|---|
| 55 | algorithms for screen-ordering. |
|---|
| 56 | |
|---|
| 57 | One example: High-priority screens will be shown more often than |
|---|
| 58 | low-priority screens, simply by showing up more often. |
|---|
| 59 | |
|---|
| 60 | ---------------------------------------- |
|---|
| 61 | Shell Commands |
|---|
| 62 | |
|---|
| 63 | The server will also be able to run arbitrary shell commands from the |
|---|
| 64 | config file. This will allow you to, for example, shut down the |
|---|
| 65 | machine, get online, or other system tasks. |
|---|
| 66 | |
|---|
| 67 | ---------------------------------------- |
|---|
| 68 | Improved display driver API |
|---|
| 69 | |
|---|
| 70 | The desirable aspects of what a driver should do has changed somewhat |
|---|
| 71 | since I first read the LCD manual. The driver spec is based largely |
|---|
| 72 | on the functions MtxOrb's LCDs provide easily, but it is not |
|---|
| 73 | well-suited to other types of display. |
|---|
| 74 | |
|---|
| 75 | So, I'll be working on a new driver spec which is more flexible and |
|---|
| 76 | more powerful. In addition, I'm looking for ways to better handle |
|---|
| 77 | multiple driver devices. |
|---|
| 78 | |
|---|
| 79 | ---------------------------------------- |
|---|
| 80 | Anonymous CVS |
|---|
| 81 | |
|---|
| 82 | I want to *really* open up LCDproc development, by giving everyone |
|---|
| 83 | access to the CVS repository. But, alas, I've got to figure out how |
|---|
| 84 | to set up a CVS server first... (or convince Gareth to do it.. :) |
|---|
| 85 | |
|---|
| 86 | ---------------------------------------- |
|---|
