summaryrefslogtreecommitdiff
path: root/noncore/apps/opie-console/PLANS
Unidiff
Diffstat (limited to 'noncore/apps/opie-console/PLANS') (more/less context) (ignore whitespace changes)
-rw-r--r--noncore/apps/opie-console/PLANS41
1 files changed, 21 insertions, 20 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 @@
1can we please get a working serial connection for now? if that works
2i can test file transfers and stuff. -hash
3sure. I finished the ConfigDialog and now doing the Profile->Session
4stuff. Then you just need to click Open -zecke
5 1
6From a UNIX point of view we want to do something like minicom 2From a UNIX point of view we want to do something like minicom
7with a better GUI. 3with a better GUI.
8It should feature some terminal emulation vt100/102, ansi, 4It should feature some terminal emulation vt100/102, ansi,
9filetransfer via {x,y,z}modem, and some sort of session management. 5filetransfer via {x,y,z}modem, and some sort of session management.
10Besides this requirement we would like to be able to execute 'scripts' 6Besides this requirement we would like to be able to execute 'scripts'
11in a session. 7in a session.
12A script would just write to the TEmulation and then be sent via 8A script would just write to the TEmulation and then be sent via
13an IOlayer. 9an IOlayer.
14Then we would like to send keys? Do we want that? 10Then we would like to send keys? Do we want that?
11> what kind of keys would we send?
15 12
16We want a modular architecture which might support plugins in 13We want a modular architecture which might support plugins in
17the future 14the future
18 15
19(Almost) DONE: 16(Almost) DONE:
20Framework 17 Framework
21Serial IOLayer 18 Serial IOLayer
22Saving and Restoring Profiles 19 Saving and Restoring Profiles
23ConfigDialog Framework 20 ConfigDialog Framework
24FilesendingLayer - hash
25 21
26TASKS in progress: 22TASKS in progress:
27Profile->Session and MainWidget --- Harlekin 23 Profile->Session and MainWidget --- Harlekin
28IOLayer - wazlaf 24 IOLayer - wazlaf
29TE - ibotty 25 TE - ibotty
30Session->Profile - hash 26 Scripting - wazlaf
31Scripting - 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
33OPEN tasks: 34OPEN tasks:
34Irda ConfigWidget - Harlekin 35 Irda ConfigWidget - Harlekin
35BT ConfigWidget 36 BT ConfigWidget
36Keys - open 37 Keys - hash
37IRDA-Layer - open 38 IRDA-Layer - open
38Bluetooth-Layer - open 39 Bluetooth-Layer - open
39Fullscreen mode ( maybe spy at vnc viewer ) \ No newline at end of file 40 Fullscreen mode ( maybe spy at vnc viewer )