author | hash <hash> | 2002-10-07 07:17:04 (UTC) |
---|---|---|
committer | hash <hash> | 2002-10-07 07:17:04 (UTC) |
commit | 82c55f5dbe4d621019b9b9f153e85af0ce52799e (patch) (unidiff) | |
tree | cffd155aa35cf9e0b83c0da5f9db71445109ed40 | |
parent | 099bf9c07cc08d50c9637e55a1dd89d9e4b5e9b8 (diff) | |
download | opie-82c55f5dbe4d621019b9b9f153e85af0ce52799e.zip opie-82c55f5dbe4d621019b9b9f153e85af0ce52799e.tar.gz opie-82c55f5dbe4d621019b9b9f153e85af0ce52799e.tar.bz2 |
i'll do the UI for filetransfers too
-rw-r--r-- | noncore/apps/opie-console/PLANS | 11 |
1 files changed, 1 insertions, 10 deletions
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS index 9952efb..636bed4 100644 --- a/noncore/apps/opie-console/PLANS +++ b/noncore/apps/opie-console/PLANS | |||
@@ -1,40 +1,31 @@ | |||
1 | Shall we write what the plans are here? | ||
2 | Ok I'll do | ||
3 | |||
4 | I think we sould take the TE* stuff from embeddedconsole and use them for the | ||
5 | TE here. TE isn't going to be easy starting from scratch. If nobody is doing | ||
6 | TE yet, i'll try to port that stuff over here. -hash | ||
7 | ibotty is doing it. | ||
8 | |||
9 | From a UNIX point of view we want to do something like minicom | 1 | From a UNIX point of view we want to do something like minicom |
10 | with a better GUI. | 2 | with a better GUI. |
11 | It should feature some terminal emulation vt100/102, ansi, | 3 | It should feature some terminal emulation vt100/102, ansi, |
12 | filetransfer via {x,y,z}modem, and some sort of session management. | 4 | filetransfer via {x,y,z}modem, and some sort of session management. |
13 | Besides this requirement we would like to be able to execute 'scripts' | 5 | Besides this requirement we would like to be able to execute 'scripts' |
14 | in a session. | 6 | in a session. |
15 | A script would just write to the TEmulation and then be sent via | 7 | A script would just write to the TEmulation and then be sent via |
16 | an IOlayer. | 8 | an IOlayer. |
17 | Then we would like to send keys? Do we want that? | 9 | Then we would like to send keys? Do we want that? |
18 | 10 | ||
19 | We want a modular architecture which might support plugins in | 11 | We want a modular architecture which might support plugins in |
20 | the future | 12 | the future |
21 | 13 | ||
22 | (Almost) DONE: | 14 | (Almost) DONE: |
23 | Framework | 15 | Framework |
24 | Serial IOLayer | 16 | Serial IOLayer |
25 | Saving and Restoring Profiles | 17 | Saving and Restoring Profiles |
26 | 18 | ||
27 | TASKS in progress: | 19 | TASKS in progress: |
28 | Profile->Session and MainWidget --- Harlekin | 20 | Profile->Session and MainWidget --- Harlekin |
29 | FilesendingLayer - hash | 21 | FilesendingLayer & UI - hash |
30 | IOLayer - wazlaf | 22 | IOLayer - wazlaf |
31 | Configuration - josef | 23 | Configuration - josef |
32 | TE - ibotty | 24 | TE - ibotty |
33 | 25 | ||
34 | OPEN tasks: | 26 | OPEN tasks: |
35 | Session->Profile - open | 27 | Session->Profile - open |
36 | Scripting - wazlaf | 28 | Scripting - wazlaf |
37 | Keys - open | 29 | Keys - open |
38 | IRDA-Layer - open | 30 | IRDA-Layer - open |
39 | Bluetooth-Layer - open | 31 | Bluetooth-Layer - open |
40 | FilesendingUI - open | ||