summaryrefslogtreecommitdiff
authorhash <hash>2002-10-24 08:38:23 (UTC)
committer hash <hash>2002-10-24 08:38:23 (UTC)
commitbb381ba95d321259295ff7fc02534281d21ded87 (patch) (unidiff)
tree55b7ff20d90db06cb92d7dbd1a1a770a9e87dc24
parent915d9778a69f5ea549ab81d9f153cfa7dd458d89 (diff)
downloadopie-bb381ba95d321259295ff7fc02534281d21ded87.zip
opie-bb381ba95d321259295ff7fc02534281d21ded87.tar.gz
opie-bb381ba95d321259295ff7fc02534281d21ded87.tar.bz2
lets make a general config dialog
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--noncore/apps/opie-console/PLANS6
1 files changed, 4 insertions, 2 deletions
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS
index ea1b5fd..8e0bee4 100644
--- a/noncore/apps/opie-console/PLANS
+++ b/noncore/apps/opie-console/PLANS
@@ -1,53 +1,55 @@
1 1
2From 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
3with a better GUI. 3with a better GUI.
4It should feature some terminal emulation vt100/102, ansi, 4It should feature some terminal emulation vt100/102, ansi,
5filetransfer via {x,y,z}modem, and some sort of session management. 5filetransfer via {x,y,z}modem, and some sort of session management.
6Besides this requirement we would like to be able to execute 'scripts' 6Besides this requirement we would like to be able to execute 'scripts'
7in a session. 7in a session.
8A 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
9an IOlayer. 9an IOlayer.
10Then we would like to send keys? Do we want that?
11> what kind of keys would we send?
12 10
13We want a modular architecture which might support plugins in 11We want a modular architecture which might support plugins in
14the future 12the future
15 13
14should we have a general opie-console setting dialog where you configure
15general things like where the tabs are, the profiles, and the default
16keyboard?
17
16 18
17(Almost) DONE: 19(Almost) DONE:
18 Framework 20 Framework
19 Serial IOLayer 21 Serial IOLayer
20 Saving and Restoring Profiles 22 Saving and Restoring Profiles
21 ConfigDialog Framework 23 ConfigDialog Framework
22 IOLayer 24 IOLayer
23 Profile->Session and MainWidget 25 Profile->Session and MainWidget
24 FilesendingLayer ( Z/Y Modem tested X does not work at all ) 26 FilesendingLayer ( Z/Y Modem tested X does not work at all )
25 Fullscreen 27 Fullscreen
26 Modem - Josef 28 Modem - Josef
27 Keys - hash 29 Keys - hash
28 30
29TASKS in progress: 31TASKS in progress:
30 Keys - hash 32 Keys - hash
31 Scripting - wazlaf 33 Scripting - wazlaf
32 34
33 Session->Profile - hash => why is this needed? you can not change any settings 35 Session->Profile - hash => why is this needed? you can not change any settings
34 after you start the session, so all you would do is 36 after you start the session, so all you would do is
35 create a duplicate of the profile used to open the 37 create a duplicate of the profile used to open the
36 current session. maybe needed later when you can change 38 current session. maybe needed later when you can change
37 settings while the session is running (colors, fonts...) 39 settings while the session is running (colors, fonts...)
38 zecke => think of that. You try to hook up with a New Device 40 zecke => think of that. You try to hook up with a New Device
39 neither know anything.... speed flow and such stuff 41 neither know anything.... speed flow and such stuff
40 you start to experiment and it starts to work 42 you start to experiment and it starts to work
41 now you want to save the session 43 now you want to save the session
42 44
43 hash => got it. 45 hash => got it.
44 46
45OPEN tasks: 47OPEN tasks:
46 Receiving ( copy &n paste from filetransfer.cpp ) 48 Receiving ( copy &n paste from filetransfer.cpp )
47 49
48POSTPONED UNTIL LATER: 50POSTPONED UNTIL LATER:
49 Irda ConfigWidget 51 Irda ConfigWidget
50 BT ConfigWidget 52 BT ConfigWidget
51 IRDA-Layer 53 IRDA-Layer
52 Bluetooth-Layer 54 Bluetooth-Layer
53 55