-rw-r--r-- | noncore/apps/opie-console/PLANS | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS index e3ddc7a..11fb2fc 100644 --- a/noncore/apps/opie-console/PLANS +++ b/noncore/apps/opie-console/PLANS | |||
@@ -1,51 +1,51 @@ | |||
1 | 1 | ||
2 | From a UNIX point of view we want to do something like minicom | 2 | From a UNIX point of view we want to do something like minicom |
3 | with a better GUI. | 3 | with a better GUI. |
4 | It should feature some terminal emulation vt100/102, ansi, | 4 | It should feature some terminal emulation vt100/102, ansi, |
5 | filetransfer via {x,y,z}modem, and some sort of session management. | 5 | filetransfer via {x,y,z}modem, and some sort of session management. |
6 | Besides this requirement we would like to be able to execute 'scripts' | 6 | Besides this requirement we would like to be able to execute 'scripts' |
7 | in a session. | 7 | in a session. |
8 | A script would just write to the TEmulation and then be sent via | 8 | A script would just write to the TEmulation and then be sent via |
9 | an IOlayer. | 9 | an IOlayer. |
10 | Then we would like to send keys? Do we want that? | 10 | Then we would like to send keys? Do we want that? |
11 | > what kind of keys would we send? | 11 | > what kind of keys would we send? |
12 | 12 | ||
13 | We want a modular architecture which might support plugins in | 13 | We want a modular architecture which might support plugins in |
14 | the future | 14 | the future |
15 | 15 | ||
16 | |||
16 | (Almost) DONE: | 17 | (Almost) DONE: |
17 | Framework | 18 | Framework |
18 | Serial IOLayer | 19 | Serial IOLayer |
19 | Saving and Restoring Profiles | 20 | Saving and Restoring Profiles |
20 | ConfigDialog Framework | 21 | ConfigDialog Framework |
21 | IOLayer | 22 | IOLayer |
22 | Profile->Session and MainWidget | 23 | Profile->Session and MainWidget |
23 | FilesendingLayer ( Z/Y Modem tested X does not work at all ) | 24 | FilesendingLayer ( Z/Y Modem tested X does not work at all ) |
25 | Fullscreen | ||
24 | 26 | ||
25 | TASKS in progress: | 27 | TASKS in progress: |
26 | Irda ConfigWidget - Harlekin | 28 | Irda ConfigWidget - Harlekin |
27 | BT ConfigWidget - Harlekin | 29 | BT ConfigWidget - Harlekin |
28 | IRDA-Layer - Harlekin | 30 | IRDA-Layer - Harlekin |
29 | Bluetooth-Layer - Harlekin | 31 | Bluetooth-Layer - Harlekin |
30 | Modem - Harlekin | 32 | Modem - Josef |
31 | Keys - hash | 33 | Keys - hash |
32 | TE - ibotty | 34 | TE - ibotty |
33 | Scripting - wazlaf | 35 | Scripting - wazlaf |
34 | 36 | ||
35 | Session->Profile - hash => why is this needed? you can not change any settings | 37 | Session->Profile - hash => why is this needed? you can not change any settings |
36 | after you start the session, so all you would do is | 38 | after you start the session, so all you would do is |
37 | create a duplicate of the profile used to open the | 39 | create a duplicate of the profile used to open the |
38 | current session. maybe needed later when you can change | 40 | current session. maybe needed later when you can change |
39 | settings while the session is running (colors, fonts...) | 41 | settings while the session is running (colors, fonts...) |
40 | zecke => think of that. You try to hook up with a New Device | 42 | zecke => think of that. You try to hook up with a New Device |
41 | neither know anything.... speed flow and such stuff | 43 | neither know anything.... speed flow and such stuff |
42 | you start to experiment and it starts to work | 44 | you start to experiment and it starts to work |
43 | now you want to save the session | 45 | now you want to save the session |
44 | 46 | ||
45 | hash => got it. | 47 | hash => got it. |
46 | 48 | ||
47 | OPEN tasks: | 49 | OPEN tasks: |
48 | Modem | ||
49 | Fullscreen mode ( maybe spy at vnc viewer or read NeoTrons HOWTO) | ||
50 | Receiving ( copy &n paste from filetransfer.cpp ) | 50 | Receiving ( copy &n paste from filetransfer.cpp ) |
51 | 51 | ||