summaryrefslogtreecommitdiff
path: root/noncore/apps/opie-console/PLANS
Side-by-side diff
Diffstat (limited to 'noncore/apps/opie-console/PLANS') (more/less context) (show whitespace changes)
-rw-r--r--noncore/apps/opie-console/PLANS3
1 files changed, 1 insertions, 2 deletions
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS
index a7c7578..bef7196 100644
--- a/noncore/apps/opie-console/PLANS
+++ b/noncore/apps/opie-console/PLANS
@@ -7,49 +7,48 @@ Besides this requirement we would like to be able to execute 'scripts'
in a session.
A script would just write to the TEmulation and then be sent via
an IOlayer.
We want a modular architecture which might support plugins in
the future
should we have a general opie-console setting dialog where you configure
general things like where the tabs are, the profiles, and the default
keyboard?
(Almost) DONE:
Framework
Serial IOLayer
Saving and Restoring Profiles
ConfigDialog Framework
IOLayer
Profile->Session and MainWidget
FilesendingLayer ( Z/Y Modem tested X does not work at all )
Fullscreen
Modem - Josef
Keys - hash
Scripting - wazlaf
-
-TASKS in progress:
Keys - hash
+TASKS in progress:
Session->Profile - hash => why is this needed? you can not change any settings
after you start the session, so all you would do is
create a duplicate of the profile used to open the
current session. maybe needed later when you can change
settings while the session is running (colors, fonts...)
zecke => think of that. You try to hook up with a New Device
neither know anything.... speed flow and such stuff
you start to experiment and it starts to work
now you want to save the session
hash => got it.
OPEN tasks:
Receiving ( copy &n paste from filetransfer.cpp )
POSTPONED UNTIL LATER:
Irda ConfigWidget
BT ConfigWidget
IRDA-Layer
Bluetooth-Layer