-rw-r--r-- | noncore/apps/opie-console/PLANS | 15 |
1 files changed, 8 insertions, 7 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,6 +1,2 @@ -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 @@ -13,4 +9,5 @@ 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 @@ -22,5 +19,4 @@ Serial IOLayer Saving and Restoring Profiles ConfigDialog Framework -FilesendingLayer - hash TASKS in progress: @@ -28,11 +24,16 @@ Profile->Session and MainWidget --- Harlekin IOLayer - wazlaf TE - ibotty -Session->Profile - hash 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 + Keys - hash IRDA-Layer - open Bluetooth-Layer - open |