rwdziprwdwshell 0.95 → 0.96

Sign up to get free protection for your applications and to get access to all the features.
@@ -0,0 +1,216 @@
1
+ = rwdschedule - for rwdtinker and RubyWebDialogs
2
+
3
+ rwdschedule is a simple little database
4
+
5
+ The GUI interface used is RubyWebDialogs
6
+
7
+ RubyWebDialogs is a platform independent graphical user interface for Ruby applications. It generates HTML and serves it with an internal HTTP server, so you can use your favorite web browser as the front end for your Ruby application. All this means, that it can be used on almost every platform, like Ruby itself. http://www.erikveen.dds.nl/rubywebdialogs/
8
+
9
+ == Quick Start
10
+ Start the program by typing
11
+ ruby init.rb
12
+
13
+ Then point your web browser to:
14
+ http://localhost:7705/
15
+
16
+ Then enter the event date you want to search for in the browser form and press Search.
17
+ 200412december1a
18
+ browser should fill with the event information.
19
+ To exit, press the x inside the browser window.
20
+
21
+
22
+ == How to Use the Schedule Book (rwdschedule)
23
+
24
+ There are two ways to add records to schedule book.
25
+
26
+ == Adding Records
27
+
28
+ 1. Use the "Edit Event" tab
29
+ The first field is the most important. It is the filename that
30
+ will be created. I use the event date starting with yearmonthday
31
+ 2005january11
32
+
33
+ The following lines for entry are for you to fill in as you want.
34
+ When you are finished press the Save Changes button
35
+
36
+ You use this same screen for editing an already saved event
37
+
38
+ 2. Manually add an entry for a event record
39
+ You can use a text editor to create a record
40
+ put information on separate lines. You can have as many lines as you want
41
+ name the file with starting with date and end with .nam
42
+ 2005january11 6 pm dinner party.nam
43
+
44
+ Save your file to the schedules/ subdirectory
45
+
46
+
47
+ == Viewing an schedule book entry:
48
+
49
+
50
+ Go to "View event" tab
51
+
52
+ Click on the list events button.
53
+
54
+ Click on the date you want
55
+
56
+ Then click the "Open" button
57
+
58
+ If it finds the record it will open it. It displays the record
59
+ as text under the "Open" button.
60
+
61
+
62
+ == Event Utilities
63
+
64
+ Click on "Event Utilites" tab
65
+
66
+ You can rename event filenames
67
+ You can delete events
68
+
69
+ == Sync for multiple computers
70
+
71
+ If you are like me, you have more than one system
72
+ I use rwdTinker at home on my Linux laptop
73
+ at work I use it on XP
74
+ on the go I use rwdtinker on my Zaurus PDA
75
+ So I am adding schedule events on different machines.
76
+ There is a function to help sync the separate systems
77
+
78
+ in "Selection Panel" click on "Open Schedule Sync Window"
79
+
80
+ First you need your ftp details set in the
81
+ configuration/rwdschedule.cnf file
82
+
83
+ you can upload your events from your local schedules directory to the ftp site
84
+ you can download events from the ftp site to your local updates directory
85
+ you can perform a sync which finds remote events and adds them to your local
86
+ schedules directory
87
+
88
+ There is a button to delete the update directory when finished
89
+
90
+ == Show Month
91
+
92
+ Click on "Show Month" tab
93
+ enter
94
+ Year: 2005
95
+ Month: 1
96
+ Click on show month
97
+
98
+ It will display one month
99
+
100
+ == ics files
101
+
102
+ You can create an ics file
103
+ you can view a raw ics file
104
+ Rename ics File
105
+ Delete ics File
106
+
107
+ == Using over a Network
108
+
109
+ To serve the application over your local LAN,change the last line in the
110
+ init.rb file to something like:
111
+ RwdTinker.file(RWDFile).serve(8080, "-r" ? ".rwduids" : nil)
112
+ Then you should be able to login at: http://yourhostname:8080
113
+
114
+ You have to authorize yourself. The .rwuids example is a string with
115
+ the name of the authorization file, relative to the home directory
116
+ of the user that started the service. This file has to be in the form of:
117
+
118
+ user1 = password
119
+ user2 = pass phrase
120
+
121
+ Thus the file .rwduids might contain:
122
+
123
+ erik = secret
124
+
125
+ == Requirements:
126
+ RubyWebDialogs - I am using 0.0.11 2004-3-9
127
+
128
+ Ruby I am using version 1.8.2
129
+
130
+
131
+ I have tested this under Linux-Debian kernel 2.6.9
132
+
133
+ == PROBLEMS:
134
+ It is easy to type a date with a space after it. That will have a somewhat invisible space
135
+ in it.
136
+
137
+ don't type in the extension .sch
138
+
139
+ Closing the browser doesn't terminate the application. You have to use the application's close-button And terminating the application doesn't terminate the application when running in network mode. You just log out.
140
+
141
+ Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
142
+
143
+
144
+ == contacts
145
+ For more information see:
146
+ http://rwdapplications.rubyforge.org/wiki/wiki.pl
147
+
148
+
149
+ For more information about RubyWebDialogs see:
150
+ http://www.erikveen.dds.nl/rubywebdialogs/index.html
151
+
152
+
153
+ Steven Gibson
154
+ steven@superant.com
155
+
156
+ == Changelog
157
+ version 0.96
158
+ added export ics record
159
+ added end time for ics create record
160
+
161
+ version 0.95
162
+ added ics file view tab
163
+ added ics file creation tab
164
+ ics file rename and deletion tab
165
+ reorganized schedule edit screen for future isc output
166
+ corrected typo on menu tab
167
+
168
+ version 0.94
169
+ added RwdSchedule Menu tab for easier navigation
170
+ wider text boxes for contact information
171
+ Improvement to context sensitive help
172
+ updated for rwdtinker 1.51 - finds available port and remote control
173
+
174
+ version 0.93
175
+ added some context sensitive help
176
+ added edit config file and reload config variables
177
+ change to tinker context help script
178
+ updated for rwdtinker 1.47
179
+ factored month calendar display - should be more readable
180
+ fixed l10n calls for calendar for Dutch
181
+ added archive function for old events
182
+
183
+ version 0.92
184
+ Added delete update files function in sync tab
185
+
186
+ version 0.91
187
+ updated for rwdtinker 1.44 - refactored gui files
188
+ Changed gui directory names - more like Java package titles
189
+
190
+ version 0.9
191
+ added back window for sync tasks
192
+ added configuration viewing
193
+ added ftp file download for sync
194
+ added ftp file upload for sync
195
+ add update files and schedule sync compares
196
+
197
+ version 0.8
198
+ updated for rwdtinker 1.42 - semi-live updates
199
+
200
+ version 0.7
201
+ updated for rwdtinker 1.4
202
+ addition to documentation
203
+
204
+ version 0.6
205
+ updated for rwdtinker 1.3
206
+
207
+ version 0.5
208
+ added edit commands to change event record
209
+ Rename event
210
+ Delete event
211
+ changed order of event list - descending = oldest at top
212
+
213
+ version 0.4
214
+ added configuration file with location of schedules directory
215
+ add date selection to view event tab
216
+ updated to version 1.0 of rwdtinker
Binary file
data/rwdschedule.rb ADDED
@@ -0,0 +1,216 @@
1
+ = rwdschedule - for rwdtinker and RubyWebDialogs
2
+
3
+ rwdschedule is a simple little database
4
+
5
+ The GUI interface used is RubyWebDialogs
6
+
7
+ RubyWebDialogs is a platform independent graphical user interface for Ruby applications. It generates HTML and serves it with an internal HTTP server, so you can use your favorite web browser as the front end for your Ruby application. All this means, that it can be used on almost every platform, like Ruby itself. http://www.erikveen.dds.nl/rubywebdialogs/
8
+
9
+ == Quick Start
10
+ Start the program by typing
11
+ ruby init.rb
12
+
13
+ Then point your web browser to:
14
+ http://localhost:7705/
15
+
16
+ Then enter the event date you want to search for in the browser form and press Search.
17
+ 200412december1a
18
+ browser should fill with the event information.
19
+ To exit, press the x inside the browser window.
20
+
21
+
22
+ == How to Use the Schedule Book (rwdschedule)
23
+
24
+ There are two ways to add records to schedule book.
25
+
26
+ == Adding Records
27
+
28
+ 1. Use the "Edit Event" tab
29
+ The first field is the most important. It is the filename that
30
+ will be created. I use the event date starting with yearmonthday
31
+ 2005january11
32
+
33
+ The following lines for entry are for you to fill in as you want.
34
+ When you are finished press the Save Changes button
35
+
36
+ You use this same screen for editing an already saved event
37
+
38
+ 2. Manually add an entry for a event record
39
+ You can use a text editor to create a record
40
+ put information on separate lines. You can have as many lines as you want
41
+ name the file with starting with date and end with .nam
42
+ 2005january11 6 pm dinner party.nam
43
+
44
+ Save your file to the schedules/ subdirectory
45
+
46
+
47
+ == Viewing an schedule book entry:
48
+
49
+
50
+ Go to "View event" tab
51
+
52
+ Click on the list events button.
53
+
54
+ Click on the date you want
55
+
56
+ Then click the "Open" button
57
+
58
+ If it finds the record it will open it. It displays the record
59
+ as text under the "Open" button.
60
+
61
+
62
+ == Event Utilities
63
+
64
+ Click on "Event Utilites" tab
65
+
66
+ You can rename event filenames
67
+ You can delete events
68
+
69
+ == Sync for multiple computers
70
+
71
+ If you are like me, you have more than one system
72
+ I use rwdTinker at home on my Linux laptop
73
+ at work I use it on XP
74
+ on the go I use rwdtinker on my Zaurus PDA
75
+ So I am adding schedule events on different machines.
76
+ There is a function to help sync the separate systems
77
+
78
+ in "Selection Panel" click on "Open Schedule Sync Window"
79
+
80
+ First you need your ftp details set in the
81
+ configuration/rwdschedule.cnf file
82
+
83
+ you can upload your events from your local schedules directory to the ftp site
84
+ you can download events from the ftp site to your local updates directory
85
+ you can perform a sync which finds remote events and adds them to your local
86
+ schedules directory
87
+
88
+ There is a button to delete the update directory when finished
89
+
90
+ == Show Month
91
+
92
+ Click on "Show Month" tab
93
+ enter
94
+ Year: 2005
95
+ Month: 1
96
+ Click on show month
97
+
98
+ It will display one month
99
+
100
+ == ics files
101
+
102
+ You can create an ics file
103
+ you can view a raw ics file
104
+ Rename ics File
105
+ Delete ics File
106
+
107
+ == Using over a Network
108
+
109
+ To serve the application over your local LAN,change the last line in the
110
+ init.rb file to something like:
111
+ RwdTinker.file(RWDFile).serve(8080, "-r" ? ".rwduids" : nil)
112
+ Then you should be able to login at: http://yourhostname:8080
113
+
114
+ You have to authorize yourself. The .rwuids example is a string with
115
+ the name of the authorization file, relative to the home directory
116
+ of the user that started the service. This file has to be in the form of:
117
+
118
+ user1 = password
119
+ user2 = pass phrase
120
+
121
+ Thus the file .rwduids might contain:
122
+
123
+ erik = secret
124
+
125
+ == Requirements:
126
+ RubyWebDialogs - I am using 0.0.11 2004-3-9
127
+
128
+ Ruby I am using version 1.8.2
129
+
130
+
131
+ I have tested this under Linux-Debian kernel 2.6.9
132
+
133
+ == PROBLEMS:
134
+ It is easy to type a date with a space after it. That will have a somewhat invisible space
135
+ in it.
136
+
137
+ don't type in the extension .sch
138
+
139
+ Closing the browser doesn't terminate the application. You have to use the application's close-button And terminating the application doesn't terminate the application when running in network mode. You just log out.
140
+
141
+ Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
142
+
143
+
144
+ == contacts
145
+ For more information see:
146
+ http://rwdapplications.rubyforge.org/wiki/wiki.pl
147
+
148
+
149
+ For more information about RubyWebDialogs see:
150
+ http://www.erikveen.dds.nl/rubywebdialogs/index.html
151
+
152
+
153
+ Steven Gibson
154
+ steven@superant.com
155
+
156
+ == Changelog
157
+ version 0.96
158
+ added export ics record
159
+ added end time for ics create record
160
+
161
+ version 0.95
162
+ added ics file view tab
163
+ added ics file creation tab
164
+ ics file rename and deletion tab
165
+ reorganized schedule edit screen for future isc output
166
+ corrected typo on menu tab
167
+
168
+ version 0.94
169
+ added RwdSchedule Menu tab for easier navigation
170
+ wider text boxes for contact information
171
+ Improvement to context sensitive help
172
+ updated for rwdtinker 1.51 - finds available port and remote control
173
+
174
+ version 0.93
175
+ added some context sensitive help
176
+ added edit config file and reload config variables
177
+ change to tinker context help script
178
+ updated for rwdtinker 1.47
179
+ factored month calendar display - should be more readable
180
+ fixed l10n calls for calendar for Dutch
181
+ added archive function for old events
182
+
183
+ version 0.92
184
+ Added delete update files function in sync tab
185
+
186
+ version 0.91
187
+ updated for rwdtinker 1.44 - refactored gui files
188
+ Changed gui directory names - more like Java package titles
189
+
190
+ version 0.9
191
+ added back window for sync tasks
192
+ added configuration viewing
193
+ added ftp file download for sync
194
+ added ftp file upload for sync
195
+ add update files and schedule sync compares
196
+
197
+ version 0.8
198
+ updated for rwdtinker 1.42 - semi-live updates
199
+
200
+ version 0.7
201
+ updated for rwdtinker 1.4
202
+ addition to documentation
203
+
204
+ version 0.6
205
+ updated for rwdtinker 1.3
206
+
207
+ version 0.5
208
+ added edit commands to change event record
209
+ Rename event
210
+ Delete event
211
+ changed order of event list - descending = oldest at top
212
+
213
+ version 0.4
214
+ added configuration file with location of schedules directory
215
+ add date selection to view event tab
216
+ updated to version 1.0 of rwdtinker
metadata CHANGED
@@ -3,15 +3,15 @@ rubygems_version: 0.8.4
3
3
  specification_version: 1
4
4
  name: rwdziprwdwshell
5
5
  version: !ruby/object:Gem::Version
6
- version: "0.95"
7
- date: 2005-02-10
8
- summary: rwdziprwdwshell is a Ruby and Shell script running application using rwdtinker and RubyWebDialogs. Requires rwdtinker >1.51
6
+ version: "0.96"
7
+ date: 2005-02-23
8
+ summary: rwdziprwdaschedule is a event schedule application using rwdtinker and RubyWebDialogs. Requires rwdtinker >1.51
9
9
  require_paths:
10
10
  - "."
11
11
  email: steven@superant.com
12
12
  homepage: http://rubyforge.org/projects/rwdapplications/
13
13
  rubyforge_project: rwdapplications
14
- description: rwdziprwdwshell is a Ruby and Shell script running application using rwdtinker and RubyWebDialogs. Requires rwdtinker >1.51rwdcalc is calculator rwdtinker and RubyWebDialogs
14
+ description: rwdziprwdaschedule is a event schedule application using rwdtinker and RubyWebDialogs. Requires rwdtinker >1.51rwdcalc is calculator rwdtinker and RubyWebDialogs
15
15
  autorequire:
16
16
  default_executable:
17
17
  bindir: bin
@@ -26,15 +26,15 @@ required_ruby_version: !ruby/object:Gem::Version::Requirement
26
26
  platform: ruby
27
27
  authors: []
28
28
  files:
29
- - rwdwshell-0.95.zip
30
- - HowTo_Shell.txt
31
- - rwdshell.rb
29
+ - rwdaschedule-0.96.zip
30
+ - HowTo_Schedule.txt
31
+ - rwdschedule.rb
32
32
  test_files: []
33
33
  rdoc_options:
34
34
  - "--main"
35
- - HowTo_Shell.txt
35
+ - HowTo_Schedule.txt
36
36
  extra_rdoc_files:
37
- - HowTo_Shell.txt
37
+ - HowTo_Schedule.txt
38
38
  executables: []
39
39
  extensions: []
40
40
  requirements:
data/HowTo_Shell.txt DELETED
@@ -1,244 +0,0 @@
1
- = RwdShell Program
2
-
3
- How to Use the Shell Program (rwdshell)
4
-
5
- == What is is
6
-
7
- rwdshell is a web brower interface to operating system shell commands
8
-
9
-
10
- download from http://rubyforge.org/frs/?group_id=444
11
-
12
- run shell commands
13
-
14
-
15
- The GUI interface used is RubyWebDialogs
16
-
17
-
18
- Start the program by typing<br>
19
- ruby init.rb
20
-
21
- Then point your web browser to:
22
- http://localhost:7705/
23
-
24
- == using shell commands
25
-
26
-
27
-
28
- Enter the shell command you want to run for in the browser form and press execute.
29
- After a second the browser should fill with the results of the command.
30
- try ls, df, cat "filename", and other shell commands
31
- You should be able to run one command after another
32
-
33
-
34
-
35
- rwdshell scriptrunner is a web brower interface to operating system shell commands
36
-
37
-
38
- 1. run shell commands
39
- 2. run Ruby commands in the browser
40
- 3. use a calculator
41
- 4. Open brower windows with html documents
42
-
43
- The GUI interface used is RubyWebDialogs
44
-
45
-
46
- Start the program by typing
47
- ruby init.rb
48
-
49
- Then point your web browser to:
50
- http://localhost:7705/
51
-
52
-
53
- == To use a shell command
54
-
55
-
56
- Enter the shell command you want to run for in the browser form and press execute.
57
- After a second the browser should fill with the results of the command.
58
- try ls, df, cat "filename", and other shell commands
59
- You should be able to run one command after another
60
-
61
-
62
- There are two ways to add scripts to rwdshell directory.
63
-
64
-
65
-
66
- == Creating a script
67
-
68
-
69
- 1. Use the "Create New Script" tab
70
- <blockquote>
71
- The first field is the most important. It is the filename that
72
- will be created.
73
- myshellscript
74
-
75
- The following line for entry is a shell command.
76
-
77
- The last line is for comment to describe the script
78
- When you are finished press the CreateFile button
79
-
80
-
81
- 2. Manually add an entry for a script
82
-
83
- You can use a text editor to create a record
84
- put information on separate lines. You can have as many lines as you want
85
- name the file with caps and no spaces and end with .sh
86
- mynextscript.sh
87
-
88
- Save your file to the scripts/ subdirectory
89
-
90
-
91
- == Viewing a recorded script entry:
92
-
93
-
94
- * Go to "List Scripts" tab
95
-
96
-
97
- You can get a list of all scripts by clicking the listfiles button
98
-
99
- To see the text of a script
100
- Type in the name of the script you want.
101
-
102
- type it without the sh ending
103
- myscript
104
-
105
- Then click the "ViewScript" button
106
-
107
- If it finds the script it will open it. It displays the text the search box.
108
-
109
-
110
- == Ruby Commands
111
-
112
-
113
- At the Ruby tab here are some commands you might try
114
-
115
- print "hello" + "\n"
116
-
117
- bar=46; print "%s" % bar, "\n"
118
-
119
- "abc".each_byte{|c| printf "<%c>", c}; print "\n"
120
-
121
- "a\nb\nc\n".each_line{|l| print l}
122
-
123
- for l in "a\nb\nc\n" ; print l ; end
124
-
125
- print "%s" % "abcdef".length
126
- wser window, or in another browser tab.
127
-
128
- == Using over a Network
129
-
130
- To serve the application over your local LAN,change the last line in the
131
- init.rb file to something like:
132
- RwdTinker.file(RWDFile).serve(8080, "-r" ? ".rwduids" : nil)
133
- Then you should be able to login at: http://yourhostname:8080
134
-
135
- You have to authorize yourself. The .rwuids example is a string with
136
- the name of the authorization file, relative to the home directory
137
- of the user that started the service. This file has to be in the form of:
138
-
139
- user1 = password
140
- user2 = pass phrase
141
-
142
- Thus the file .rwduids might contain:
143
-
144
- erik = secret
145
-
146
-
147
- == Requirements:
148
- RubyWebDialogs - I am using 0.0.11 2004-3-9<br>
149
- This package you downloaded rwddemo should have a runtime version of
150
- the needed rubywebdialog files<br>
151
-
152
- Ruby I am using version 1.8.2
153
-
154
- I have tested this under Linux-Debian kernel 2.6.9
155
-
156
- == Operation:
157
- The code files reside in the code directory and are combined before
158
- the main Class is loaded
159
-
160
- The rwd files in gui are combined before the gui is activated
161
-
162
- == Installing:
163
-
164
- unzip the file
165
- then cd to the directory
166
- unzip rwdashell-x.y.zip
167
-
168
-
169
- == Trouble shooting:
170
-
171
- If the program is not working, try looking at the ev subdirectory. That is where
172
- the runtime of rubywebdialogs are.
173
-
174
- for long term installation, I would suggest putting most files in a lib directory
175
- like /usr/lib/rwdshell
176
- then make a writable directory the local directory for command files to be written
177
- like ~/rwdshell
178
-
179
-
180
- Closing the browser doesn't terminate the application. You have to use the application's close-button And terminating the application doesn't terminate the application when running in network mode. You just log out.
181
-
182
- Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
183
-
184
- RubyWebDialogs is a platform independent graphical user interface for Ruby applications. It generates HTML and serves it with an internal HTTP server, so you can use your favorite web browser as the front end for your Ruby application. All this means, that it can be used on almost every platform, like Ruby itself. http://www.erikveen.dds.nl/rubywebdialogs/
185
-
186
-
187
- For more information see:
188
- http://rwdapplications.rubyforge.org/wiki/wiki.pl
189
-
190
- For more information about RubyWebDialogs see:<br>
191
- http://www.erikveen.dds.nl/rubywebdialogs/index.html
192
-
193
- Thanks, Steven Gibson
194
-
195
- == Changelog
196
- version 0.95
197
- added ruby script running
198
- add back window for more control tabs
199
- beginning of context sensitive help
200
- wider text boxes for configuration information
201
- updated for rwdtinker 1.51 - finds available port and remote control
202
- updated for rwdtinker 1.52 - cam install applets from Gems
203
-
204
- version 0.94
205
- updated for rwdtinker 1.44 - refactor gui directory structure
206
-
207
- version 0.93
208
- updated for rwdtinker 1.42 - semi-live updating
209
-
210
- version 0.92
211
- added script editing
212
- script deletion
213
- script renaming
214
- added English module to RubyEval
215
- added Env module to RubyEval
216
- combined scriptrunner HowTo into shell HowTo
217
- Changed order of tabs so script are first
218
-
219
- version 0.91
220
- updated for rwdtinker version 1.3
221
-
222
- Version 0.9
223
- updated for rwdtinker version 1.23
224
-
225
- Version 0.7
226
- includes script playing and Ruby eval window.
227
-
228
- Version 0.6
229
- added script runner
230
- list scripts
231
- create scripts
232
- Replaced Readme.txt with HowTo.html
233
-
234
- Version 0.3
235
- Changed directory structure to work with rwdtinker 0.9 or greater.
236
- Improved the filename selection
237
- Changed the layout on the list screen
238
-
239
-
240
-
241
-
242
-
243
-
244
-
data/rwdshell.rb DELETED
@@ -1,244 +0,0 @@
1
- = RwdShell Program
2
-
3
- How to Use the Shell Program (rwdshell)
4
-
5
- == What is is
6
-
7
- rwdshell is a web brower interface to operating system shell commands
8
-
9
-
10
- download from http://rubyforge.org/frs/?group_id=444
11
-
12
- run shell commands
13
-
14
-
15
- The GUI interface used is RubyWebDialogs
16
-
17
-
18
- Start the program by typing<br>
19
- ruby init.rb
20
-
21
- Then point your web browser to:
22
- http://localhost:7705/
23
-
24
- == using shell commands
25
-
26
-
27
-
28
- Enter the shell command you want to run for in the browser form and press execute.
29
- After a second the browser should fill with the results of the command.
30
- try ls, df, cat "filename", and other shell commands
31
- You should be able to run one command after another
32
-
33
-
34
-
35
- rwdshell scriptrunner is a web brower interface to operating system shell commands
36
-
37
-
38
- 1. run shell commands
39
- 2. run Ruby commands in the browser
40
- 3. use a calculator
41
- 4. Open brower windows with html documents
42
-
43
- The GUI interface used is RubyWebDialogs
44
-
45
-
46
- Start the program by typing
47
- ruby init.rb
48
-
49
- Then point your web browser to:
50
- http://localhost:7705/
51
-
52
-
53
- == To use a shell command
54
-
55
-
56
- Enter the shell command you want to run for in the browser form and press execute.
57
- After a second the browser should fill with the results of the command.
58
- try ls, df, cat "filename", and other shell commands
59
- You should be able to run one command after another
60
-
61
-
62
- There are two ways to add scripts to rwdshell directory.
63
-
64
-
65
-
66
- == Creating a script
67
-
68
-
69
- 1. Use the "Create New Script" tab
70
- <blockquote>
71
- The first field is the most important. It is the filename that
72
- will be created.
73
- myshellscript
74
-
75
- The following line for entry is a shell command.
76
-
77
- The last line is for comment to describe the script
78
- When you are finished press the CreateFile button
79
-
80
-
81
- 2. Manually add an entry for a script
82
-
83
- You can use a text editor to create a record
84
- put information on separate lines. You can have as many lines as you want
85
- name the file with caps and no spaces and end with .sh
86
- mynextscript.sh
87
-
88
- Save your file to the scripts/ subdirectory
89
-
90
-
91
- == Viewing a recorded script entry:
92
-
93
-
94
- * Go to "List Scripts" tab
95
-
96
-
97
- You can get a list of all scripts by clicking the listfiles button
98
-
99
- To see the text of a script
100
- Type in the name of the script you want.
101
-
102
- type it without the sh ending
103
- myscript
104
-
105
- Then click the "ViewScript" button
106
-
107
- If it finds the script it will open it. It displays the text the search box.
108
-
109
-
110
- == Ruby Commands
111
-
112
-
113
- At the Ruby tab here are some commands you might try
114
-
115
- print "hello" + "\n"
116
-
117
- bar=46; print "%s" % bar, "\n"
118
-
119
- "abc".each_byte{|c| printf "<%c>", c}; print "\n"
120
-
121
- "a\nb\nc\n".each_line{|l| print l}
122
-
123
- for l in "a\nb\nc\n" ; print l ; end
124
-
125
- print "%s" % "abcdef".length
126
- wser window, or in another browser tab.
127
-
128
- == Using over a Network
129
-
130
- To serve the application over your local LAN,change the last line in the
131
- init.rb file to something like:
132
- RwdTinker.file(RWDFile).serve(8080, "-r" ? ".rwduids" : nil)
133
- Then you should be able to login at: http://yourhostname:8080
134
-
135
- You have to authorize yourself. The .rwuids example is a string with
136
- the name of the authorization file, relative to the home directory
137
- of the user that started the service. This file has to be in the form of:
138
-
139
- user1 = password
140
- user2 = pass phrase
141
-
142
- Thus the file .rwduids might contain:
143
-
144
- erik = secret
145
-
146
-
147
- == Requirements:
148
- RubyWebDialogs - I am using 0.0.11 2004-3-9<br>
149
- This package you downloaded rwddemo should have a runtime version of
150
- the needed rubywebdialog files<br>
151
-
152
- Ruby I am using version 1.8.2
153
-
154
- I have tested this under Linux-Debian kernel 2.6.9
155
-
156
- == Operation:
157
- The code files reside in the code directory and are combined before
158
- the main Class is loaded
159
-
160
- The rwd files in gui are combined before the gui is activated
161
-
162
- == Installing:
163
-
164
- unzip the file
165
- then cd to the directory
166
- unzip rwdashell-x.y.zip
167
-
168
-
169
- == Trouble shooting:
170
-
171
- If the program is not working, try looking at the ev subdirectory. That is where
172
- the runtime of rubywebdialogs are.
173
-
174
- for long term installation, I would suggest putting most files in a lib directory
175
- like /usr/lib/rwdshell
176
- then make a writable directory the local directory for command files to be written
177
- like ~/rwdshell
178
-
179
-
180
- Closing the browser doesn't terminate the application. You have to use the application's close-button And terminating the application doesn't terminate the application when running in network mode. You just log out.
181
-
182
- Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
183
-
184
- RubyWebDialogs is a platform independent graphical user interface for Ruby applications. It generates HTML and serves it with an internal HTTP server, so you can use your favorite web browser as the front end for your Ruby application. All this means, that it can be used on almost every platform, like Ruby itself. http://www.erikveen.dds.nl/rubywebdialogs/
185
-
186
-
187
- For more information see:
188
- http://rwdapplications.rubyforge.org/wiki/wiki.pl
189
-
190
- For more information about RubyWebDialogs see:<br>
191
- http://www.erikveen.dds.nl/rubywebdialogs/index.html
192
-
193
- Thanks, Steven Gibson
194
-
195
- == Changelog
196
- version 0.95
197
- added ruby script running
198
- add back window for more control tabs
199
- beginning of context sensitive help
200
- wider text boxes for configuration information
201
- updated for rwdtinker 1.51 - finds available port and remote control
202
- updated for rwdtinker 1.52 - cam install applets from Gems
203
-
204
- version 0.94
205
- updated for rwdtinker 1.44 - refactor gui directory structure
206
-
207
- version 0.93
208
- updated for rwdtinker 1.42 - semi-live updating
209
-
210
- version 0.92
211
- added script editing
212
- script deletion
213
- script renaming
214
- added English module to RubyEval
215
- added Env module to RubyEval
216
- combined scriptrunner HowTo into shell HowTo
217
- Changed order of tabs so script are first
218
-
219
- version 0.91
220
- updated for rwdtinker version 1.3
221
-
222
- Version 0.9
223
- updated for rwdtinker version 1.23
224
-
225
- Version 0.7
226
- includes script playing and Ruby eval window.
227
-
228
- Version 0.6
229
- added script runner
230
- list scripts
231
- create scripts
232
- Replaced Readme.txt with HowTo.html
233
-
234
- Version 0.3
235
- Changed directory structure to work with rwdtinker 0.9 or greater.
236
- Improved the filename selection
237
- Changed the layout on the list screen
238
-
239
-
240
-
241
-
242
-
243
-
244
-
data/rwdwshell-0.95.zip DELETED
Binary file