some more bugs/todo

2 files changed, 26 insertions, 7 deletions

diff --git a/noncore/apps/opie-console/BUGS b/noncore/apps/opie-console/BUGS
index 2956b31..23a1026 100644
--- a/noncore/apps/opie-console/BUGS
+++ b/noncore/apps/opie-console/BUGS
@@ -1,7 +1,24 @@
 Ok we all know we write perfect code
 but sometimes the compiler produces bad code
 and we need to work around some compiler bugs!! -zecke
 
 
 Send/receive: lrzsz behaves strange when trying to use
 --overwrite or --rename.
+
+- console should autoconnect by default
+
+- keys and buttonbar merge
+
+- keys really working
+
+- scripting with "direct subpopup"
+
+- kill more compiler warnings.
+
+- more colorshemes ( "orange is ugly" )
+
+- irda and bluetooth out ( can be done with normal serial as long as the
+connection is allready up, and extended stuff is a lot of work; maybe later
+in again ).
+
diff --git a/noncore/apps/opie-console/PLANS b/noncore/apps/opie-console/PLANS
index 11fb2fc..ea1b5fd 100644
--- a/noncore/apps/opie-console/PLANS
+++ b/noncore/apps/opie-console/PLANS
@@ -2,50 +2,52 @@
 From a UNIX point of view we want to do something like minicom
 with a better GUI.
 It should feature some terminal emulation vt100/102, ansi,
 filetransfer via {x,y,z}modem, and some sort of session management.
 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.
 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
   IOLayer
   Profile->Session and MainWidget
   FilesendingLayer ( Z/Y Modem tested X does not work at all )
   Fullscreen
+  Modem - Josef
+  Keys - hash 
 
 TASKS in progress:
-  Irda  ConfigWidget - Harlekin
-  BT ConfigWidget - Harlekin
-  IRDA-Layer - Harlekin
-  Bluetooth-Layer - Harlekin
-  Modem - Josef
   Keys - hash
-  TE - ibotty
   Scripting - wazlaf 
    
   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 
+