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