Diffstat (limited to 'noncore/apps/opie-console/PLANS') (more/less context) (show whitespace changes)
-rw-r--r-- | noncore/apps/opie-console/PLANS | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS index 18ac08c..e0b9130 100644 --- a/noncore/apps/opie-console/PLANS +++ b/noncore/apps/opie-console/PLANS | |||
@@ -1,39 +1,40 @@ | |||
1 | can we please get a working serial connection for now? if that works | ||
2 | i can test file transfers and stuff. -hash | ||
3 | sure. I finished the ConfigDialog and now doing the Profile->Session | ||
4 | stuff. Then you just need to click Open -zecke | ||
5 | 1 | ||
6 | 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 |
7 | with a better GUI. | 3 | with a better GUI. |
8 | It should feature some terminal emulation vt100/102, ansi, | 4 | It should feature some terminal emulation vt100/102, ansi, |
9 | 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. |
10 | 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' |
11 | in a session. | 7 | in a session. |
12 | 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 |
13 | an IOlayer. | 9 | an IOlayer. |
14 | 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? | ||
15 | 12 | ||
16 | We want a modular architecture which might support plugins in | 13 | We want a modular architecture which might support plugins in |
17 | the future | 14 | the future |
18 | 15 | ||
19 | (Almost) DONE: | 16 | (Almost) DONE: |
20 | Framework | 17 | Framework |
21 | Serial IOLayer | 18 | Serial IOLayer |
22 | Saving and Restoring Profiles | 19 | Saving and Restoring Profiles |
23 | ConfigDialog Framework | 20 | ConfigDialog Framework |
24 | FilesendingLayer - hash | ||
25 | 21 | ||
26 | TASKS in progress: | 22 | TASKS in progress: |
27 | Profile->Session and MainWidget --- Harlekin | 23 | Profile->Session and MainWidget --- Harlekin |
28 | IOLayer - wazlaf | 24 | IOLayer - wazlaf |
29 | TE - ibotty | 25 | TE - ibotty |
30 | Session->Profile - hash | ||
31 | Scripting - wazlaf | 26 | Scripting - wazlaf |
27 | FilesendingLayer | ||
28 | Session->Profile - hash => why is this needed? you can not change any settings | ||
29 | after you start the session, so all you would do is | ||
30 | create a duplicate of the profile used to open the | ||
31 | current session. maybe needed later when you can change | ||
32 | settings while the session is running (colors, fonts...) | ||
32 | 33 | ||
33 | OPEN tasks: | 34 | OPEN tasks: |
34 | Irda ConfigWidget - Harlekin | 35 | Irda ConfigWidget - Harlekin |
35 | BT ConfigWidget | 36 | BT ConfigWidget |
36 | Keys - open | 37 | Keys - hash |
37 | IRDA-Layer - open | 38 | IRDA-Layer - open |
38 | Bluetooth-Layer - open | 39 | Bluetooth-Layer - open |
39 | Fullscreen mode ( maybe spy at vnc viewer ) \ No newline at end of file | 40 | Fullscreen mode ( maybe spy at vnc viewer ) \ No newline at end of file |