File: NOTES

package info (click to toggle)
tkmasqdialer 1.12-1
  • links: PTS
  • area: main
  • in suites: potato
  • size: 120 kB
  • sloc: sh: 1,076; makefile: 40
file content (50 lines) | stat: -rw-r--r-- 2,497 bytes parent folder | download
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
    
    NOTES ON THE NEW TKMASQDIALER -

    As of version 1.1 tkmasqdialer is currently in the grips of a major
    rewrite . Things have changed , code has changed and the doc's 
    havent been keeping up to date ( I got a life to try and lead at the
    same time ) .
    
    Currently the tkmasqdialer has a few problems with telnet zombies
    that must be addressed . I could hack away at it for several hours
    to try and work around it , but what the heck , its going to get a 
    complete re-write from the ground up .
    
    NEW INTERFACE - 
    
    The new interface will have only the bare essentials for doing the
    actual dialing to an outside connection . Facilities must be allowed
    for to include the newer features of mserver where mserver will not 
    disconnect until all masqdialer clients have disconnected . However
    the main panel will only have eight buttons . 
    
	DIAL - The main purpose of the tkmasqdialer client no?
	SELECT SERVICE - Next to the dial button son one can select
	SERVER NAME / PORT - A couple of texy entry areas for such
	    what to dial . Clearly a primary button to have.
	CONFIGURE - This is where most of the maintainence functions will
	    go . To keep the primary function of masqdialer small and
	    fast , all Utility type functions will go in here . Masqdialer
	    will call the utility functions as a seperate process but will
	    read and modify the same configs as the primary panel . 
	SERVER STATUS / TIMER / SERVER LIST - The three were labels but
	    are linked to the internal routines that check the same .
	MUTE - To be implemented ...
	QUIT - Gotta go sometime ... 
	    
	There are two reasons for dividing the program in this manner .
    First and foremost the configure panel can 'soak up' feature bloat
    whilst the primary panel can keep on with getting the job done without
    bloat . Secondly by separating the program , a smaller text can be used
    for the opening panel . Most people just want this client to do the deed
    and get out of the way . This is the way I use it myself so I hope I dont
    inconvenience too many people with these changes . 
    
	Another important point is that I am looking at making the extra
    functions launch off from configure so that you can select what panels
    you want too see from the configuration . I can even add these to the
    main panel if needed . However , at this stage most of the extras are
    still a work in progress .