rwdtorrent 0.01

data/rwd_files/HowTo_TinkerWin2.txt

@@ -0,0 +1,202 @@
+= RwdTinker 2nd Window
+
+
+RwdTinker Win2 has the applet adding and removal functions and a diagnostic tab
+
+== Usage
+
+
+How to Use the Tinker framework Program (rwdtinker)
+
+
+1. stand alone application
+2. framework for building applications
+3. Open brower windows with html documents
+
+The GUI interface used is RubyWebDialogs 
+
+
+Start the program by typing 
+ruby init.rb
+
+Then point your web browser to:
+http://localhost:7705/
+
+== Installing Applets
+
+* unzip an applet
+
+      You can download an applet created by someone else
+      put the file in the zips directory
+      unzip the directory into the program directoy
+      unzip randomapplet.zip
+      
+      This should right the needed files in the correct directories
+      
+      
+
+
+
+Viewing a installed Applets:
+
+
+Go to "List Scripts" tab
+
+
+     You can get a list of all installed applets by clicking the listfiles button
+     
+      To see the text of a install file
+       Type in the name of the file you want.
+      
+       type it without the inf ending
+       rwdapplet-0.1
+       
+       Then click the "View Installed File" button
+       
+       If it finds the file it will open it. It displays the text the search box.
+
+
+
+== Adding Applets
+
+To add code, commands and gui tabs
+
+Move program files into a directory under the code directory.
+Move gui files into a directory under the gui directory.
+ The gui directory name you create is important, because the gui
+ rwd file is built in alpha order by directory name
+
+
+There are two ways to add applets to the directories.
+
+ Creating code
+
+
+* Manually write code and gui files
+
+      The files go into your code directory
+      the filenames for code do not matter
+      
+      The gui files go into your gui directory
+      The gui files need to be in order by name and end with .rwd
+        
+
+      
+      If you need a config file that goes in the configuration directory
+
+ internationalization and localization are helped by replacing the
+  gui files in the subdirectories under gui
+ 
+      
+
+
+
+  
+== Documents
+  
+  
+  when you click on a document name, the document should pop up in a 
+  browser window, or in another browser tab.
+
+To exit, press the x inside the browser window.
+
+
+
+== Languages
+
+
+ You can add tranlations in the lang subdirectory
+ You change the $lang constant in Tinker config file in the configuration directory
+ You can see one translation on the install applet tab, after you have installed and applet
+ 
+== Requirements:
+RubyWebDialogs - I am using 0.1.2 
+ This package you downloaded should have a runtime version of 
+ the needed rubywebdialog files
+
+Ruby I am using version 1.8.2
+
+I have tested this under Linux-Debian kernel 2.6.9
+
+= Operation:
+The code files reside in the code directory and are combined before 
+the main Class is loaded
+
+The rwd files in gui are combined before the gui is activated
+
+Translated text reside in the lang directory
+
+== Installing:
+
+untar the file
+tar zxvf rwdtinker-x.y.tar.gz
+then cd to the directory
+cd rwdshell-x.y
+then start the init.rb program file
+ruby init.rb
+Then point your browser at http://localhost:7705
+or where it tells you.
+Trouble shooting:
+
+If the program is not working, try looking at the ev subdirectory. That is where
+the runtime of rubywebdialogs are.
+
+for long term installation, I would suggest putting most files in a lib directory
+like /usr/lib/rwdshell
+then make a writable directory the local directory for command files to be written
+like ~/rwdshell
+
+
+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.
+
+Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
+
+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/
+
+== Credits
+
+Thanks go to:
+
+* Matz, for creating Ruby in the first place.
+* Erik, for creating RubyWebDialogs.
+* Charlotte, my wife for coming up for the name Tinker.
+
+== License
+
+rwdtinker is copyright (c) 2004 Steven Gibson.  It is free software, and may be redistributed
+under the terms of the GPL licence: 
+
+  For more information see:
+http://rwdapplications.rubyforge.org/wiki/wiki.pl
+
+
+For more information about RubyWebDialogs see:
+http://www.erikveen.dds.nl/rubywebdialogs/index.html
+
+Thanks, Steven Gibson
+
+== Changelog:
+version 0.5
+ changing version on help screen to be button
+ added version window
+ added diagnostic tab
+ changed order on remove applets tab
+
+version 0.4
+ changed order of elements on install applet tab
+ Add more i81n ablility - added lang directorys for language hash files
+ Improved name selection in zips and applet screens
+
+version 0.3
+ changed location of code files 
+ only directory of code files needs to be added to inf file
+ changed location of gui files 
+ only directory of gui files needs to be added to inf file
+ 
+
+version 0.2
+ added zip listing and installing - Linux only
+ This version is a dropin replacement for a applet 
+ in the core rwdtinker
+
+

data/rwd_files/HowTo_Torrent.txt

@@ -0,0 +1,146 @@
+= RwdTorrent Program
+
+How to Use the Torrent Program (rwdtorrent)
+
+== What is is
+
+rwdtorrent is a web brower interface to BitTorrent commands
+
+
+download from http://rubyforge.org/frs/?group_id=444
+
+ run BitTorrent commands
+
+You can select a torrent file in the torrentfile directory and download it
+ 
+ There are tabs to view file sizes  and edit configurations
+ 
+ 'View Torrent Metafiles' - to view and select torrent files before downloading
+ 
+ 'View Torrent' - to view file size of downloaded file
+ 
+ 'Torrent Download Display' the tab to start a download and open the torrent download window
+ 
+ 'Edit Configuration' - to change the configuration of rwdtorrent
+
+
+ BitTorrent is a technology used for sharing large files. 
+ It is very effective because when there are more people downloading a file,
+ your download speed will be even faster.
+ 
+ You need BitTorrent installed in order to use this program
+ BitTorrent can downloaded at:
+ http://www.bittorrent.com/index.html
+ 
+ There are many BitTorrent links at:
+ http://spesb.com/link2u/
+
+The GUI interface used is RubyWebDialogs 
+
+Start the program by typing<br> 
+ruby init.rb
+
+Then point your web browser to:
+http://localhost:7705/
+
+== using shell commands
+
+
+
+Enter the shell command you want to run for in the browser form and press execute.
+After a second the browser should fill with the results of the command.
+try ls, df, cat "filename", and other shell commands
+You should be able to run one command after another
+
+
+The GUI interface used is RubyWebDialogs 
+
+
+Start the program by typing 
+ruby init.rb
+
+Then point your web browser to:
+http://localhost:7705/
+
+
+
+== Using over a Network
+  
+To serve the application over your local LAN,change the last line in the
+init.rb file to something like:
+RwdTinker.file(RWDFile).serve(8080, "-r" ? ".rwduids" : nil)
+Then you should be able to login at: http://yourhostname:8080
+
+You have to authorize yourself. The .rwuids example is a string with
+the name of the authorization file, relative to the home directory
+of the user that started the service. This file has to be in the form of:
+
+user1 = password
+user2 = pass phrase
+
+Thus the file .rwduids might contain:
+
+erik = secret
+
+
+== Requirements:
+ RubyWebDialogs - I am using 0.0.11 2004-3-9<br>
+ This package you downloaded rwddemo should have a runtime version of 
+ the needed rubywebdialog files<br>
+
+Ruby I am using version 1.8.2
+
+I have tested this under Linux-Debian kernel 2.6.9
+
+== Operation:
+ The code files reside in the code directory and are combined before 
+ the main Class is loaded
+
+ The rwd files in gui are combined before the gui is activated
+
+== Installing:
+
+unzip the file
+then cd to the directory
+unzip rwdashell-x.y.zip
+
+
+== Trouble shooting:
+
+If the program is not working, try looking at the ev subdirectory. That is where
+the runtime of rubywebdialogs are.
+
+for long term installation, I would suggest putting most files in a lib directory
+like /usr/lib/rwdshell
+then make a writable directory the local directory for command files to be written
+like ~/rwdshell
+
+
+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.
+
+Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
+
+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/
+
+
+  For more information see:
+http://rwdapplications.rubyforge.org/wiki/wiki.pl
+
+For more information about RubyWebDialogs see:<br>
+http://www.erikveen.dds.nl/rubywebdialogs/index.html
+
+Thanks, Steven Gibson
+
+== Changelog
+Version 0.01
+ initial release
+ view torrent metafile details
+ download torrents from local torrent metafiles
+ uses http://rubyforge.org/projects/rubytorrent/
+ and http://rubyforge.org/projects/aversa/
+
+
+
+ 
+
+

data/rwd_files/Readme.txt

@@ -0,0 +1,57 @@
+rwdapplications are web brower applications
+
+The GUI interface used is RubyWebDialogs 
+
+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/
+
+
+Start the program by:
+changing to the directory and
+ruby init.rb
+
+Then point your web browser to:
+http://localhost:7701/
+
+Or to the port that shows on the console or in the config.cnf file
+
+Requirements:
+RubyWebDialogs - I am using 0.0.11 2004-3-9
+ This package you downloaded should have a runtime version of 
+ the needed rubywebdialog files
+
+Ruby I am using version 1.8.2
+
+I have tested this under Linux-Debian kernel 2.6.9
+
+Operation:
+The code files reside in the code directory and are combined before 
+the main Class is loaded
+
+The rwd files in gui are combined before the gui is activated
+
+Trouble shooting:
+
+untar the file
+tar zxvf rwdapplication-x.y.tar.gz
+then cd to the directory
+cd rwdapplication-x.y
+then start the init.rb program file
+ruby init.rb
+
+
+If the program is not working, try looking at the ev subdirectory. That is where
+the runtime of rubywebdialogs are.
+
+for long term installation, I would suggest putting most files in a lib directory
+like /usr/lib/rwdshell
+then make a writable directory the local directory for command files to be written
+like ~/rwdshell
+
+
+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.
+
+Don't use the back-button of the browser! Strange and unpredictable things may and will happen!
+
+Steven Gibson
+stevengibson@superant.com
+http://rwdapplications.rubyforge.org/

data/rwd_files/rdoc-style.css

@@ -0,0 +1,175 @@
+
+body {
+    margin: 0;
+    padding: 0;
+    background: white;
+}
+
+h1,h2,h3,h4 { margin: 0; color: #efefef; background: transparent; }
+h1 { font-size: 120%; }
+h2,h3,h4 { margin-top: 1em; }
+
+a { background: #eef; color: #039; text-decoration: none; }
+a:hover { background: #039; color: #eef; }
+
+/* Override the base stylesheet's Anchor inside a table cell */
+td > a {
+	background: transparent;
+	color: #039;
+	text-decoration: none;
+}
+
+/* === Structural elements =================================== */
+
+div#index {
+    margin: 0;
+    padding: 0;
+    font-size: 0.9em;
+}
+
+div#index a {
+    margin-left: 0.7em;
+}
+
+div#classHeader {
+    width: auto;
+    background: #039;
+    color: white;
+    padding: 0.5em 1.5em 0.5em 1.5em;
+    margin: 0;
+    border-bottom: 3px solid #006;
+}
+
+div#classHeader a {
+    background: inherit;
+    color: white;
+}
+
+div#classHeader td {
+    background: inherit;
+    color: white;
+}
+
+div#fileHeader {
+    width: auto;
+    background: #039;
+    color: white;
+    padding: 0.5em 1.5em 0.5em 1.5em;
+    margin: 0;
+    border-bottom: 3px solid #006;
+}
+
+div#fileHeader a {
+    background: inherit;
+    color: white;
+}
+
+div#fileHeader td {
+    background: inherit;
+    color: white;
+}
+
+div#bodyContent {
+    padding: 0 1.5em 0 1.5em;
+}
+
+div#description {
+    padding: 0.5em 1.5em;
+    background: #efefef;
+    border: 1px dotted #999;
+}
+
+div#description h1,h2,h3,h4,h5,h6 {
+    color: black;
+    background: transparent;
+}
+
+div#validator-badges {
+    text-align: center;
+}
+div#validator-badges img { border: 0; }
+
+div#copyright {
+    color: #333;
+    background: #efefef;
+    font: 0.75em sans-serif;
+    margin-top: 5em;
+    margin-bottom: 0;
+    padding: 0.5em 2em;
+}
+
+
+/* === Classes =================================== */
+
+table.header-table {
+    color: white;
+    font-size: small;
+}
+
+.type-note {
+    font-size: small;
+    color: #DEDEDE;
+}
+
+.section-bar {
+    background: #eee;
+    color: #333;
+    padding: 3px;
+    border: 1px solid #999;
+}
+
+.top-aligned-row { vertical-align: vertical-align: top }
+
+/* --- Context section classes ----------------------- */
+
+.context-row { }
+.context-item-name { font-family: monospace; font-weight: bold; color: black; }
+.context-item-value { font-size: x-small; color: #448; }
+.context-item-desc { background: #efefef; }
+
+/* --- Method classes -------------------------- */
+.method-detail {
+    background: #EFEFEF;
+    padding: 0;
+    margin-top: 0.5em;
+    margin-bottom: 0.5em;
+    border: 1px dotted #DDD;
+}
+.method-heading {
+	color: black;
+	background: #AAA;
+	border-bottom: 1px solid #666;
+	padding: 0.2em 0.5em 0 0.5em;
+}
+.method-signature { color: black; background: inherit; }
+.method-name { font-weight: bold; }
+.method-args { font-style: italic; }
+.method-description { padding: 0 0.5em 0 0.5em; }
+
+/* --- Source code sections -------------------- */
+
+a.source-toggle { font-size: 90%; }
+div.method-source-code {
+    background: #262626;
+    color: #ffdead;
+	margin: 1em;
+    padding: 0.5em;
+    border: 1px dashed #999;
+    overflow: hidden;
+}
+
+div.method-source-code pre { color: #ffdead; overflow: hidden; }
+
+/* --- Ruby keyword styles --------------------- */
+
+.standalone-code { background: #221111; color: #ffdead; overflow: hidden; }
+
+.ruby-constant	{ color: #7fffd4; background: transparent; }
+.ruby-keyword	{ color: #00ffff; background: transparent; }
+.ruby-ivar		{ color: #eedd82; background: transparent; }
+.ruby-operator	{ color: #00ffee; background: transparent; }
+.ruby-identifier { color: #ffdead; background: transparent; }
+.ruby-node		{ color: #ffa07a; background: transparent; }
+.ruby-comment	{ color: #b22222; font-weight: bold; background: transparent; }
+.ruby-regexp	{ color: #ffa07a; background: transparent; }
+.ruby-value		{ color: #7fffd4; background: transparent; }