File: rocket_launcher

package info (click to toggle)
bottlerocket 0.05b3-17
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 404 kB
  • sloc: ansic: 1,837; sh: 170; makefile: 105; tcl: 92
file content (178 lines) | stat: -rw-r--r-- 6,727 bytes parent folder | download | duplicates (9)
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
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
#!/usr/bin/wish

#  Some variables to store desired states
set bottleRocket "/usr/bin/br"
set currentHouse "A"
set currentButton 1
set currentRange  0

#  This is a tk/tcl front end for the bottlerocket program written by
#Tymm ( tymm@acm.org )  It currently is set up just like the X-10 Powerhouse
#remote. (with radio buttons instead of a dial for the house, and radio
#buttons instead of a switch for chosing devices 1-8 or 9-16. 
#
#    (Version 0.1    Initial release)    (6/7/1999)
#    Chris Kuster (ckuster@hrair.physics.ncsu.edu)
#
#    (Version 0.1.1  1st bugfix release) (6/8/1999)
#    Chris Kuster (ckuster@hrair.physics.ncsu.edu)
#    Changes since Version 0.1
#     1) Dimmer functions actually exist
#     2) There is now a variable to store the name of the bottle_rocket function
#
#  Things to do for future versions:
#    1) A dial interface for the house selection (to be like the remote)
#    2) A little light (like on the remote)
#    3) A switch interface for the range selection (to be like the remote)
#    4) A labeling scheme (so you can tell what's what)
#    5) Better looking in general (may not be possible with tk/tcl)
#    6) A more flexible method of calling the executable (paths not hard wired)
#  Most of these are based on the assumption that it is better to have an
#    interface like the remote.  This may not be a good assumption.
#
# (c) 1999 Chris Kuster (ckuster@hrair.physics.ncsu.edu).  
#  Free Software.  GPL applies.
#  No warranties expressed or implied.

#  A procedure to turn on a given device in a given house
proc fire_ignite {House Device Range BottleRocket} {
  set currentDevice [expr {$Device + 8 * $Range}]
  exec $BottleRocket $House$currentDevice on
}

#  A procedure to turn off a given device in a given house
proc fire_dowse {House Device Range BottleRocket} {
  set currentDevice [expr {$Device + 8 * $Range}]
  exec $BottleRocket $House$currentDevice off
}

#  A procedure to dim the dimmer for a given house
proc fire_dimmer {House BottleRocket} {
  exec $BottleRocket $House dim
}

#  A procedure to brighten the dimmer for a given house
proc fire_brighter {House BottleRocket} {
  exec $BottleRocket $House bright
}

#  This procedure creates all of the widgets and associates them with the
#    desired commands.
proc fire_create_menu {} {

# Create a method of choosing the letter of the house containing
#   the desired device.
  frame .house -borderwidth 2
  pack .house -side left -fill y
  
# Title "House"
  label .house.title -text "House"
  pack .house.title

# Radio buttons for each house (would really like a dial)
  foreach h {"A" "B" "C" "D" "E" "F" "G" "H" "I" "J" "K" "L" "M" "N" "O" "P"} {
    radiobutton .house.h$h -text $h -variable currentHouse -value $h
  
    pack .house.h$h 
  } 

# Titles "On" "Off"
  frame .titles -borderwidth 2
  pack .titles -side top -fill x
  label .titles.on  -text "On"
  label .titles.off -text "Off"
  pack .titles.on  -side left
  pack .titles.off -side right

# The following lines create the on/off buttons for the devices.
# I consider the fact that I wasn't able to accomplish this with
#   a loop to be a personal failing.  If I used plain buttons
#   and a loop, there were temporal scope problems with variables.
#   I was able to create a working loop if I used radiobuttons, but
#   that didn't look right at all. (Ob)

# Device 1 on/off buttons
  frame .a1 -borderwidth 2
  pack .a1 -side top -fill x  
  button .a1.on  -text "1" -command {fire_ignite $currentHouse 1 $currentRange $bottleRocket}
  button .a1.off -text "1" -command {fire_dowse  $currentHouse 1 $currentRange $bottleRocket}
  pack .a1.on .a1.off -side left

# Device 2 on/off buttons
  frame .a2 -borderwidth 2
  pack .a2 -side top -fill x  
  button .a2.on  -text "2" -command {fire_ignite $currentHouse 2 $currentRange $bottleRocket}
  button .a2.off -text "2" -command {fire_dowse  $currentHouse 2 $currentRange $bottleRocket}
  pack .a2.on .a2.off -side left

# Device 3 on/off buttons
  frame .a3 -borderwidth 2
  pack .a3 -side top -fill x  
  button .a3.on  -text "3" -command {fire_ignite $currentHouse 3 $currentRange $bottleRocket}
  button .a3.off -text "3" -command {fire_dowse  $currentHouse 3 $currentRange $bottleRocket}
  pack .a3.on .a3.off -side left

# Device 4 on/off buttons
  frame .a4 -borderwidth 2
  pack .a4 -side top -fill x  
  button .a4.on  -text "4" -command {fire_ignite $currentHouse 4 $currentRange $bottleRocket}
  button .a4.off -text "4" -command {fire_dowse  $currentHouse 4 $currentRange $bottleRocket}
  pack .a4.on .a4.off -side left

# Device 5 on/off buttons
  frame .a5 -borderwidth 2
  pack .a5 -side top -fill x  
  button .a5.on  -text "5" -command {fire_ignite $currentHouse 5 $currentRange $bottleRocket}
  button .a5.off -text "5" -command {fire_dowse  $currentHouse 5 $currentRange $bottleRocket}
  pack .a5.on .a5.off -side left

# Device 6 on/off buttons
  frame .a6 -borderwidth 2
  pack .a6 -side top -fill x  
  button .a6.on  -text "6" -command {fire_ignite $currentHouse 6 $currentRange $bottleRocket}
  button .a6.off -text "6" -command {fire_dowse  $currentHouse 6 $currentRange $bottleRocket}
  pack .a6.on .a6.off -side left

# Device 7 on/off buttons
  frame .a7 -borderwidth 2
  pack .a7 -side top -fill x  
  button .a7.on  -text "7" -command {fire_ignite $currentHouse 7 $currentRange $bottleRocket}
  button .a7.off -text "7" -command {fire_dowse  $currentHouse 7 $currentRange $bottleRocket}
  pack .a7.on .a7.off -side left

# Device 8 on/off buttons
  frame .a8 -borderwidth 2
  pack .a8 -side top -fill x  
  button .a8.on  -text "8" -command {fire_ignite $currentHouse 8 $currentRange $bottleRocket}
  button .a8.off -text "8" -command {fire_dowse  $currentHouse 8 $currentRange $bottleRocket}
  pack .a8.on .a8.off -side left

# All right.  Now that that's over, we need buttons for the dimmer

  frame .dimmer -borderwidth 2
  pack .dimmer -side top -fill x  
  button .dimmer.brite -text "+" -command {fire_brighter $currentHouse $bottleRocket}
  button .dimmer.dim   -text "-" -command {fire_dimmer   $currentHouse $bottleRocket}
  pack .dimmer.brite .dimmer.dim -side left

# And finally, there needs to be a way to switch between devices 1-8 and 9-16

  frame .rangeSwitch -borderwidth 5
  pack .rangeSwitch -side top -fill x
  radiobutton .rangeSwitch.low  -text "1-8"  -variable currentRange -value 0
  radiobutton .rangeSwitch.high -text "9-16" -variable currentRange -value 1
  pack .rangeSwitch.low .rangeSwitch.high -side top
}

#  A procedure to actually show the window
proc fire_show_menu {} {
  if {[winfo exists .fire]} {
      wm deiconify .fire
      raise .fire
  }
}


# Actual start of the script.
fire_create_menu
fire_show_menu