summaryrefslogtreecommitdiff
path: root/noncore
authorhash <hash>2002-10-11 10:54:55 (UTC)
committer hash <hash>2002-10-11 10:54:55 (UTC)
commit68de1deb2aac466f6bc5cbde9b90c01823b3e7db (patch) (side-by-side diff)
treefe700f4a9572cb13932a86aec495ad37c30381c6 /noncore
parent40e16e5d1c9d586d51da9e4d51b43a051f63ce06 (diff)
downloadopie-68de1deb2aac466f6bc5cbde9b90c01823b3e7db.zip
opie-68de1deb2aac466f6bc5cbde9b90c01823b3e7db.tar.gz
opie-68de1deb2aac466f6bc5cbde9b90c01823b3e7db.tar.bz2
why session->profile?
Diffstat (limited to 'noncore') (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,7 +1,3 @@
-can we please get a working serial connection for now? if that works
-i can test file transfers and stuff. -hash
-sure. I finished the ConfigDialog and now doing the Profile->Session
-stuff. Then you just need to click Open -zecke
From a UNIX point of view we want to do something like minicom
with a better GUI.
@@ -12,28 +8,33 @@ in a session.
A script would just write to the TEmulation and then be sent via
an IOlayer.
Then we would like to send keys? Do we want that?
+> what kind of keys would we send?
We want a modular architecture which might support plugins in
the future
(Almost) DONE:
-Framework
-Serial IOLayer
-Saving and Restoring Profiles
-ConfigDialog Framework
-FilesendingLayer - hash
+ Framework
+ Serial IOLayer
+ Saving and Restoring Profiles
+ ConfigDialog Framework
TASKS in progress:
-Profile->Session and MainWidget --- Harlekin
-IOLayer - wazlaf
-TE - ibotty
-Session->Profile - hash
-Scripting - wazlaf
+ Profile->Session and MainWidget --- Harlekin
+ IOLayer - wazlaf
+ TE - ibotty
+ Scripting - wazlaf
+ FilesendingLayer
+ 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...)
OPEN tasks:
-Irda ConfigWidget - Harlekin
-BT ConfigWidget
-Keys - open
-IRDA-Layer - open
-Bluetooth-Layer - open
-Fullscreen mode ( maybe spy at vnc viewer ) \ No newline at end of file
+ Irda ConfigWidget - Harlekin
+ BT ConfigWidget
+ Keys - hash
+ IRDA-Layer - open
+ Bluetooth-Layer - open
+ Fullscreen mode ( maybe spy at vnc viewer )