sfgen Code
General Utilities For Tcl (now: previewing | publishing: 2014/12/1)
Status: Planning
Brought to you by:
rbrogan
Menu
▾
▴
Tree [487904] master / History
| File | Date | Author | Commit |
|---|---|---|---|
| doc | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| src | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| test | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| LICENSE.html | 2014-11-25 |
Robert Brogan
|
[c63891] 0.7.0 |
| LICENSE.txt | 2014-11-25 |
Robert Brogan
|
[c63891] 0.7.0 |
| README.html | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| README.txt | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| WARNING.txt | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| index.html | 2014-11-27 |
Robert Brogan
|
[071843] 0.9.0 |
| my.css | 2014-11-30 |
Robert Brogan
|
[487904] 1.0.0 |
| roadmap.html | 2014-11-25 |
Robert Brogan
|
[c63891] 0.7.0 |
| string-2-file-preview.png | 2014-11-25 |
Robert Brogan
|
[c63891] 0.7.0 |
| wishlist.html | 2014-11-25 |
Robert Brogan
|
[c63891] 0.7.0 |
Read Me
<!DOCTYPE html> <html> <head> <link rel="stylesheet" type="text/css" href="my.css"> <title>Readme - Gen</title> </head> <body> <div id = "left"> <a href="index.html" class="navbar" >Home</a> <a href="readme.html" class="navbar" id = "current">Readme</a> <a href="doc/readme-doc.html" class="navbar" >doc / Readme</a> <a href="test/readme-test.html" class="navbar" >test / Readme</a> <a href="doc/manual-home.html" class="navbar" >Manual</a> <a href="roadmap.html" class="navbar" >Roadmap</a> <a href="wishlist.html" class="navbar">Wishlist</a> <a href="license.html" class="navbar">License</a> </div> <div id = "center"> <div id = "content"> <div id = "AppTitle">Gen</div> <div id = "PageTitle">Readme</div> <a href="#C_HOWTO">01| HOW TO USE THIS DOCUMENT</a><br> <a href="#C_INTRO">02| INTRO</a><br> <a href="#C_GETTING_STARTED">03| GETTING STARTED</a><br> <a href="#C_BUILDING">04| BUILDING</a><br> <a href="#C_INSTALLATION">05| INSTALLATION</a><br> <a href="#C_CONFIGURATION">06| CONFIGURATION</a><br> <a href="#C_MANUAL">07| MANUAL</a><br> <a href="#C_FAQ">08| FAQ</a><br> <a href="#C_PLATFORM_NOTES">09| PLATFORM NOTES</a><br> <a href="#C_TROUBLESHOOTING">10| TROUBLESHOOTING</a><br> <a href="#C_KNOWN_ISSUES">11| KNOWN ISSUES</a><br> <a href="#C_BUG_REPORTING">12| BUG REPORTING</a><br> <a href="#C_FEEDBACK">13| FEEDBACK</a><br> <a href="#C_TESTING">14| TESTING</a><br> <a href="#C_CONTRIBUTING">15| CONTRIBUTING</a><br> <a href="#C_UPDATING">16| UPDATING</a><br> <a href="#C_RECENT_CHANGES">17| RECENT CHANGES</a><br> <a href="#C_LICENSE">18| LICENSE</a><br> <a href="#C_LEGAL">19| LEGAL</a><br> <a href="#C_CREDITS">20| CREDITS</a><br> <br> <h3><a id="C_CATALOG">—01| HOW TO USE THIS DOCUMENT</a></h3> <p>(Note that this README is designed to be filled out over the course of many versions. Some sections are currently blank (e.g. Recent Changes) because it is early in the project.)</p> <p> <span class="question">What is the software about?</span><br> See <a href="#C_INTRO">INTRO</a>.<br> </p><p> <span class="question">Is it OK for me to use? OK for me to modify? OK to make copies?</span><br> See <a href="#C_LICENSE">LICENSE</a> for info about the software license. License page itself is <a href='license.html'>here</a>.<br> See <a href="#C_LEGAL">LEGAL</a> for any additional info.<br> </p><p> <span class="question">How do I get it working?</span><br> See <a href="#C_GETTING_STARTED">GETTING STARTED</a> (after you have it installed and configured) to see how to use.<br> See <a href="#C_BUILDING">BUILDING</a> for how to compile from source.<br> See <a href="#C_INSTALLATION">INSTALLATION</a> for how to install it on your system (and how to uninstall).<br> See <a href="#C_CONFIGURATION">CONFIGURATION</a> for how you can customize it for your own use.<br> </p><p> <span class="question">I cannot make it work, what now?</span><br> See <a href="#C_TROUBLESHOOTING">TROUBLESHOOTING</a> for dealing with problems with the software.<br> See <a href="#C_PLATFORM_NOTES">PLATFORM NOTES</a> for ensuring it works with your platform/OS.<br> See <a href="#C_MANUAL">MANUAL</a> to make sure you are using it correctly.<br> See <a href="#C_FAQ">FAQ</a> to see if your question has been answered.<br> See <a href="#C_KNOWN_ISSUES">KNOWN ISSUES</a> to see if your problem is already known about (and any workarounds / advice).<br> See <a href="#C_BUG_REPORTING">BUG REPORTING</a> if you want to make a report and get follow-up.<br> </p><p> <span class="question">What is in the other sections?</span><br> <a href="#C_FEEDBACK">FEEDBACK</a> - Info about things like feature requests.<br> <a href="#C_TESTING">TESTING</a> - How you can test changes you make to the code.<br> <a href="#C_CONTRIBUTING">CONTRIBUTING</a> - How you improve the product for everyone.<br> <a href="#C_UPDATING">UPDATING</a> - How to get the latest changes.<br> <a href="#C_RECENT_CHANGES">RECENT CHANGES</a> - What the latest changest are.<br> <a href="#C_CREDITS">CREDITS</a> - Third party components used.<br> </p><p> </p> <h3><a id="C_INTRO">—02| INTRO</a></h3> <p>Say you are in the middle of solving one problem and find you need to solve another. Suppose you need to write the contents of a string to a file. You could look up how to do this, but it would be nice and <i>convenient</i> if there were something that does it all for you with one command.</p> <p>Gen is about making it a little bit easier to write Tcl programs. Gen is supposed to be code that you could well write yourself but do not want to have to.</p> <p>Gen is <i>General Utilities for Tcl</i>.</p> <h3><a id="C_GETTING_STARTED">—03| GETTING STARTED</a></h3> <p> Since this is a utilities library, you do not need to do much of anything to get started. The best thing would be to try typing in the examples from the documentation.<br> </p><p> If you would like to confirm the library is installed and working then try the following from a Tcl shell.<br> </p><code> % package require gen<br> 1.0.0<br> % set Number 1<br> 1<br> % AddTo Number 2<br> 3<br> </code><p> You should be all set!<br> </p> <h3><a id="C_BUILDING">—04| BUILDING</a></h3> <p> Gen is provided as a simple Tcl package and does not need to be built.<br> </p><p> </p> <h3><a id="C_INSTALLATION">—05| INSTALLATION</a></h3> <p> If you are reading this you most likely have already successfully installed Gen.<br> </p><p> To install, extract the contents of the zip file. That will result in the following files:<br> </p><p> </p><p> </p> <table><tr><td><code>README.txt</code></td><td>Plenty of info on how to get going.</td></tr><tr><td><code>LICENSE.txt</code></td><td>Terms of use and whatnot.</td></tr><tr><td><code>WARNING.txt</code></td><td>Special notices to prevent surprises.</td></tr><tr><td><code>/src</code></td><td>Source files<br><table><tr><td><code>pkgIndex.tcl</code></td><td>Used by the Tcl package mechanism.</td></tr><tr><td><code>gen.tcl</code></td><td>Main script file.</td></tr></table></td></tr><tr><td><code>/doc</code></td><td>Any other documents (like the manual).</td></tr><tr><td><code>/test</code></td><td>Test suite</td></tr></table> <p>Take the path to the install directory you just made and with it add the following line at the bottom of your <code>init.tcl</code> file:</p><p><code>lappend auto_path YOUR_DIR_PATH</code></p> <p>See <a href="readme.html#C_CONFIGURATION">CONFIGURATION</a> for more info about <code>init.tcl</code>.</p> <p><i>What to do after you install?</i> You can check out the <a href='readme.html#C_GETTING_STARTED'>Getting Started</a> section of the README. We recommend browsing the <a href='doc/manual-home.html'>manual</a> (or even better, use the .chm file included in your download). Each command reference has at least one example. You can type that directly into your terminal and try out the command.</p> <p><i>Prefer use to git and clone the repo?</i> There are repos is posted up on <a href="https://github.com/rbrogan/Gen">GitHub</a>, <a href="https://sourceforge.net/projects/sfgen/">SourceForge</a>, and <a href="https://gitorious.org/gitorious-gen">Gitorious</a> for you.</p> <p><i>How to uninstall?</i> To uninstall you can simply delete the directory. You can also remove the <code>lappend auto_path YOUR_DIR_PATH</code> line from your Tcl init.</p> <h3><a id="C_CONFIGURATION">—06| CONFIGURATION</a></h3> <p>To configure Tcl so it can find Gen:</p> <p>Take the path to the install directory you just made and with it add the following line at the bottom of your <code>init.tcl</code> file:</p><p><code>lappend auto_path YOUR_DIR_PATH</code>.</p> <p><i>How to find init.tcl?</i> Here are some locations found for Windows and Linux. Most likely if you use the number of your version then you can find your init.tcl in a similar spot.</p> <b><code>C:\Tcl\lib\tcl8.5\init.tcl</code></b><br> <b><code>C:\Tcl\lib\tcl8.6\init.tcl</code></b><br> <b><code>/usr/share/tcltk/tcl8.4/init.tcl</code></b><br> <b><code>/usr/share/tcltk/tcl8.5/init.tcl</code></b><br> <p>Alternatively, do a search for init.tcl starting from the root directory of your installation.</p> <p>Be sure to check this space when SQL-related commands are added.</p> </p> <h3><a id="C_MANUAL">—07| MANUAL</a></h3> <p> We have a few options. You can see the <a href="http://www.robertbrogan.com/gen/doc/manual-home.html">online manual</a> (which will be the most up-to-date).</p><p>Alternatively, you can use the offline version at <code><a href="doc/manual-home.html">doc/manual-home.html</a></code> or (preferrably) use the compiled HTML Help version at <code><b>doc/gen.chm</b></code>. </p><p> </p><p> </p> <h3><a id="C_FAQ">—08| FAQ</a></h3> <p> No questions yet. We will put them here as we get them.<br> </p><p> Please send questions you have to <span class="email">gen.questions@robertbrogan.com</span> or visit <a href="http://www.robertbrogan.com/gen/feedback.html">http://www.robertbrogan.com/gen/feedback.html</a>.<br> </p><p> Also note, you may possibly find the answer to your question in <a href="#C_MANUAL">MANUAL</a>, <a href="#C_TROUBLESHOOTING">TROUBLESHOOTING</a>, or <a href="#C_KNOWN_ISSUES">KNOWN ISSUES</a>.<br> </p><p> </p> <h3><a id="C_PLATFORM_NOTES">—09| PLATFORM NOTES</a></h3> <p> If you have Tcl working for your platform, then the library should work without problem. </p> <p> None of the commands themselves include platform-specifc interactions (i.e. make system calls) beyond occasionally calling another Tcl command that is platform-specific (e.g. in an upcoming release the command <code>Reg2Dict</code> will call the Tcl command <code>registry</code>, which is Windows-specific). </p> <h3><a id="C_TROUBLESHOOTING">—10| TROUBLESHOOTING</a></h3> <p> No tips at this time. We will post them here as we get them.<br> </p><p> Also note, you may possibly find help in <a href="#C_MANUAL">MANUAL</a>, <a href="#C_FAQ">FAQ</a>, or <a href="#C_KNOWN_ISSUES">KNOWN ISSUES</a>.<br> </p><p> </p> <h3><a id="C_KNOWN_ISSUES">—11| KNOWN ISSUES</a></h3> <p> None at this time. We will post them here as they arise. <!-- </p><p> For an up-to-date list, you can visit our <a href="http://www.robertbrogan.com/gen/knownissues.html">known issues page</a>.<br> </p><p> --> </p> <h3><a id="C_BUG_REPORTING">—12| BUG REPORTING</a></h3> <p> To report a bug, you can visit <a href="http://www.robertbrogan.com/gen/feedback.html">www.robertbrogan.com/gen/feedback.html</a> and use the form there. <br> </p><p> Alternatively, you can send an email to— </p><p> <span class="email">gen.bugreport@robertbrogan.com</span> </p><p>—and we will try to get back to you ASAP. </p><p> </p> <h3><a id="C_FEEDBACK">—13| FEEDBACK</a></h3> <p> You can visit our feedback page at <a href="http://www.robertbrogan.com/gen/feedback.html">http://www.robertbrogan.com/gen/feedback.html</a>. <br> </p><p> Alternatively, you can use your own email client and send an email to one of:<br> </p><p> <span class="email">gen.<b>questions</b>@robertbrogan.com</span><br> <span class="email">gen.<b>comments</b>@robertbrogan.com</span><br> <span class="email">gen.<b>bugreport</b>@robertbrogan.com</span><br> <span class="email">gen.<b>wishlist</b>@robertbrogan.com</span><br> <span class="email">gen.<b>other</b>@robertbrogan.com</span><br> </p><p> and we will try to get back to you ASAP.<br> </p><p> </p> <h3><a id="C_TESTING">—14| TESTING</a></h3> <p> You can find tests in the /test directory. </p> <p>You will find a <a href='test/README-test.html'>README</a> file there as well, with further details on things like how to run the tests yourself.</p> <h3><a id="C_CONTRIBUTING">—15| CONTRIBUTING</a></h3> <p> Nothing formal has been set up for governing this project, yet.<br> </p><p> If you like, you may change the code yourself and submit a patch to:<br> </p><p> <span class="email">gen.bugreport@robertbrogan.com</span> (for bug fixes)<br> -or-<br> <span class="email">gen.wishlist@robertbrogan.com</span> (for features you implemented)<br> </p><p> A roadmap (planned changes) and wishlist (unplanned) are available at:<br> </p><p> <a href="roadmap.html">roadmap.html</a><br> <a href="wishlist.html">wishlist.html</a><br> </p><p> You may want to get involved by submitting wishlist items and/or offering to do work listed in the above two sites. <br> </p><p> </p> <h3><a id="C_UPDATING">—16| UPDATING</a></h3> <p> The latest version can be found at <a href="http://www.robertbrogan.com/gen/download.html">www.robertbrogan.com/gen/download.html</a>.<br> </p><p> No announcements mechanism has been set up yet. When it is, information for how to subscribe will be put here and on the above page.<br> </p><p> </p> <h3><a id="C_RECENT_CHANGES">—17| RECENT CHANGES</a></h3> <p> Initial revision. No changes yet. </p><p> As changes are made, they will appear here. </p> <h3><a id="C_LICENSE">—18| LICENSE</a></h3> <p> The license is the same as the license for Tcl, for all practical purposes. See the <a href="license.html">license page</a> or LICENSE.txt. </p> <h3><a id="C_LEGAL">—19| LEGAL</a></h3> <p> No legal notice at this time (i.e. no use of crypto). See <a href="license.html">LICENSE</a> for information about the license.<br> </p><p> </p> <h3><a id="C_CREDITS">—20| CREDITS</a></h3> <p> Information posted at wiki.tcl.tk has been helpful throughout work on Tcl projects.<br> </p><p> </p> </div> <div id = "footer"> <p id = "footer-content">General Utilities For Tcl</p> </div> </div> </body> </html>