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