blob: bef71966b10411508366271457749f2f3967d66d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
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.
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
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
|
