author | hash <hash> | 2002-10-24 08:38:23 (UTC) |
---|---|---|
committer | hash <hash> | 2002-10-24 08:38:23 (UTC) |
commit | bb381ba95d321259295ff7fc02534281d21ded87 (patch) (side-by-side diff) | |
tree | 55b7ff20d90db06cb92d7dbd1a1a770a9e87dc24 /noncore/apps/opie-console | |
parent | 915d9778a69f5ea549ab81d9f153cfa7dd458d89 (diff) | |
download | opie-bb381ba95d321259295ff7fc02534281d21ded87.zip opie-bb381ba95d321259295ff7fc02534281d21ded87.tar.gz opie-bb381ba95d321259295ff7fc02534281d21ded87.tar.bz2 |
lets make a general config dialog
-rw-r--r-- | noncore/apps/opie-console/PLANS | 6 |
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 @@ -7,12 +7,14 @@ 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 +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 |