Menu
▾
▴
opengtoolkit-cvs — OpenG Toolkit CVS commits mailing list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(42) |
Nov
(368) |
Dec
(248) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(207) |
Mar
(180) |
Apr
(9) |
May
(39) |
Jun
(9) |
Jul
(22) |
Aug
(56) |
Sep
(82) |
Oct
(113) |
Nov
(236) |
Dec
(219) |
| 2005 |
Jan
(119) |
Feb
(81) |
Mar
(53) |
Apr
(177) |
May
(2) |
Jun
(67) |
Jul
(17) |
Aug
(5) |
Sep
(53) |
Oct
(17) |
Nov
(122) |
Dec
(77) |
| 2006 |
Jan
(293) |
Feb
(16) |
Mar
(32) |
Apr
(14) |
May
(29) |
Jun
(6) |
Jul
|
Aug
|
Sep
(18) |
Oct
(28) |
Nov
|
Dec
(2) |
| 2007 |
Jan
(8) |
Feb
(19) |
Mar
(4) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(37) |
Oct
(1) |
Nov
(8) |
Dec
(25) |
| 2008 |
Jan
(1) |
Feb
(13) |
Mar
(17) |
Apr
(3) |
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(19) |
Dec
(16) |
| 2009 |
Jan
(6) |
Feb
(9) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jim K. <jk...@us...> - 2004-08-18 00:43:20
|
Update of /cvsroot/opengtoolkit/deab/experimental In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29494/experimental Log Message: Directory /cvsroot/opengtoolkit/deab/experimental added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:42:56
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Release Notes In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/Release Notes Added Files: PRODUCTNAME X.Y.Z. Release Notes.mmap Log Message: initial commit --- NEW FILE: PRODUCTNAME X.Y.Z. Release Notes.mmap --- (This appears to be a binary file; contents omitted.) |
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/ReadySET-0-9-1/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/ReadySET-0-9-1/docs Added Files: HOWTO-upgrade.html faq.html recommended-tools.html release-notes-0-9-0.html release-notes-0-9-1.html Log Message: initial commit --- NEW FILE: release-notes-0-9-1.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "../templates/css/readyset.css"; @import "../templates/css/inst.css"; /* ]]> */ </style> <title>Release Notes</title> </head> <body> <h2>ReadySET 0.9.1: Release Notes</h2> <div class="app"> <div class="readyset"> <div id="releaseinfo"> <h3>Product Release Information</h3> <table border="1" cellpadding="3" cellspacing="2" class="axial"> <tr> <th>Product:</th> <td><a href="http://readyset.tigris.org/">ReadySET</a></td> </tr> <tr> <th>Release Number:</th> <td> 0.9.1 </td> </tr> <tr> <th>Release Date:</th> <td> 2004/07/08 </td> </tr> <tr> <th>Customer Support:</th> <td>For more information or support, please visit our <a href="http://readyset.tigris.org/">website</a> or email us at <a href="mailto:dev@readyset.tigris.org">dev@readyset.tigris.org</a> </td> </tr> </table> </div> <!-- /releaseinfo --> <div id="introduction"> <h3>Introduction</h3> <p>This document contains the release notes for ReadySET version 0.9.1. The following sections describe the release in detail and provide late-breaking or other information that supplements the main documentation.</p> <p>This is an early access release for wide evaluation and usage. Your feedback is important to us, please help us make this the best product possible. Keep in mind that we are continuing to work on this product and things may change in the future.</p> </div> <!-- /introduction --> <div id="whatsnew"> <h3>What's New?</h3> <ul> <li>New content in interviews, persistence design, and security checklist</li> <li>Clarified the relationship between feature specs and use cases</li> <li>Clarified the relationship between internal and external release numbers</li> <li>Refactored the interview checklists</li> <li>Images now display properly in IE</li> <li>Clicking on a link with an anchor now highlights the target element for users of Mozilla and Firefox.</li> <li>Many small quality improvements. See "Recent Changes" below for details.</li> </ul> </div> <!-- /whatsnew --> <div id="installation"> <h3>Installation and Upgrade Notes</h3> <dl> <dt>Installation</dt> <dd>ReadySET is not a program, it is just a set of XHTML templates, so no installation is needed.</dd> <dd>Just unzip the archive, copy into your project website or version control system, and edit the templates to describe your project.</dd> <dt>Manifest</dt> <dd>This release consists of the following items: <ul> <li>XHTML templates and CSS stylesheets</li> <li>FAQ, HOWTO-upgrade, recommended tools, and release notes (this file)</li> </ul> </dd> <dt>Minimum System Requirements</dt> <dd>You can use ReadySET on any computer that can run a text editor and a web browser.</dd> <dd>It is recommended that you use a text editor to edit the templates, however you may try other <a href="http://readyset.tigris.org/docs/recommended-tools.html">recommended tools</a> for XHTML editing.</dd> <dt>Version Compatibility</dt> <dd>If you've been using an earlier version of ReadySET, see the <a href="http://readyset.tigris.org/docs/HOWTO-upgrade.html">upgrade HOWTO</a>.</dd> </dl> </div> <!-- /installation --> <div id="recentchanges"> <h3>Recent Changes</h3> <table> <tr class="a"><th>ID</th><th>Type</th><th>Summary</th></tr> <tr class="a"><td>42</td><td>ENHANCEMENT</td><td>automate prackaging procedure</td></tr> <tr class="a"><td>47</td><td>ENHANCEMENT</td><td>move interview checklist out of interview-notes.html</td></tr> <tr class="a"><td>48</td><td>ENHANCEMENT</td><td>new questions in interviews</td></tr> <tr class="a"><td>50</td><td>ENHANCEMENT</td><td>clarify component.html "available interfaces"</td></tr> <tr class="a"><td>51</td><td>ENHANCEMENT</td><td>prompt for file format</td></tr> <tr class="a"><td>53</td><td>ENHANCEMENT</td><td>clarify feature vs. use case</td></tr> <tr class="a"><td>55</td><td>DEFECT</td><td>transparent images not working in IE</td></tr> <tr class="a"><td>56</td><td>DEFECT</td><td>clarify internal and external release numbers</td></tr> <tr class="a"><td>57</td><td>DEFECT</td><td>make it easier to see anchors</td></tr> <tr class="a"><td>58</td><td>DEFECT</td><td>use help cursor for links to term definitions </td></tr> </table> </div> <!-- /recentchanges --> <div id="knownproblems"> <h3>Known Problems and Workarounds</h3> <p>There are no known problems in this release.</p> </div> <!-- /knownproblems --> </div> </div> </body> </html> --- NEW FILE: release-notes-0-9-0.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "../templates/css/readyset.css"; @import "../templates/css/inst.css"; /* ]]> */ </style> <title>Release Notes</title> </head> <body> <h2>ReadySET 0.9.0: Release Notes</h2> <div class="app"> <div class="readyset"> <div id="releaseinfo"> <h3>Product Release Information</h3> <table border="1" cellpadding="3" cellspacing="2" class="axial"> <tr> <th>Product:</th> <td><a href="http://readyset.tigris.org/">ReadySET</a></td> </tr> <tr> <th>Release Number:</th> <td> 0.9.0 </td> </tr> <tr> <th>Release Date:</th> <td> 2004/03/02 </td> </tr> <tr> <th>Customer Support:</th> <td>For more information or support, please visit our <a href="http://readyset.tigris.org/">website</a> or email us at <a href="mailto:dev@readyset.tigris.org">dev@readyset.tigris.org</a> </td> </tr> </table> </div> <!-- /releaseinfo --> <div id="introduction"> <h3>Introduction</h3> <p>This document contains the release notes for ReadySET version 0.9.0. The following sections describe the release in detail and provide late-breaking or other information that supplements the main documentation.</p> <p>This is an early access release for wide evaluation and usage. Your feedback is important to us, please help us make this the best product possible. Keep in mind that we are continuing to work on this product and things may change in the future.</p> </div> <!-- /introduction --> <div id="whatsnew"> <h3>What's New?</h3> <ul> <li>Added templates to help visualize and record test runs</li> <li>Enhanced glossary with data dictionary examples and technical terms related to software quality</li> <li>Enhanced and refactored checklists and words-of-wisdom</li> <li>More consistent cross-links and page headers</li> <li>Improved and simplified XHTML markup</li> <li>Many small quality improvements. See "Recent Changes" below for details.</li> </ul> </div> <!-- /whatsnew --> <div id="installation"> <h3>Installation and Upgrade Notes</h3> <dl> <dt>Installation</dt> <dd>ReadySET is not a program, it is just a set of XHTML templates, so no installation is needed.</dd> <dd>Just unzip the archive, copy into your project website or version control system, and edit the templates to describe your project.</dd> <dt>Manifest</dt> <dd>This release consists of the following items: <ul> <li>XHTML templates and CSS stylesheets</li> <li>FAQ, HOWTO-upgrade</li> <li>Release notes (this file)</li> </ul> </dd> <dt>Minimum System Requirements</dt> <dd>You can use ReadySET on any computer that can run a text editor and a web browser.</dd> <dd>It is recommended that you use a text editor to edit the templates, however you may try other <a href="http://readyset.tigris.org/docs/recommended-tools.html">recommended tools</a> for XHTML editing.</dd> <dt>Version Compatibility</dt> <dd>If you've been using an earlier version of ReadySET, see the <a href="http://readyset.tigris.org/docs/HOWTO-upgrade.html">upgrade HOWTO</a>.</dd> </dl> </div> <!-- /installation --> <div id="recentchanges"> <h3>Recent Changes</h3> <table> <tr class="a"><th>ID</th><th>Type</th><th>Summary</th></tr> <tr class="a"><td>01</td><td>FEATURE</td><td>integrate test run report</td></tr> <tr class="a"><td>22</td><td>DEFECT</td><td>data dictionary examples</td></tr> <tr class="a"><td>28</td><td>Enhanced</td><td>checklist item: has this been communicated?</td></tr> <tr class="a"><td>30</td><td>TASK</td><td>add release notes</td></tr> <tr class="a"><td>31</td><td>FEATURE</td><td>HOW-TO upgrade ReadySET</td></tr> <tr class="a"><td>34</td><td>ENHANCEMENT</td><td>divs w/ id's</td></tr> <tr class="a"><td>36</td><td>DEFECT</td><td>more compact project overview</td></tr> <tr class="a"><td>37</td><td>DEFECT</td><td>need better defect terms</td></tr> <tr class="a"><td>38</td><td>TASK</td><td>update copyright to 2004</td></tr> <tr class="a"><td>39</td><td>DEFECT</td><td>clarify alternatives in multiple choice</td></tr> <tr class="a"><td>40</td><td>ENHANCEMENT</td><td>make the header links more consistent</td></tr> <tr class="a"><td>43</td><td>ENHANCEMENT</td><td>use linklist to simplify markup</td></tr> <tr class="a"><td>44</td><td>DEFECT</td><td>release-notes markup is inconsistent</td></tr> </table> </div> <!-- /recentchanges --> <div id="knownproblems"> <h3>Known Problems and Workarounds</h3> <p>There are no known problems in this release.</p> </div> <!-- /knownproblems --> </div> </div> </body> </html> --- NEW FILE: recommended-tools.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "../templates/css/readyset.css"; @import "../templates/css/inst.css"; /* ]]> */ </style> </script> <title>Recommended Tools</title> </head> <body> <div class="app"> <div class="readyset"> <h2>ReadySET: Recommended Tools</h2> <h3>Any Operating System</h3> <dl> <dt>Text Editors</dt> <dd> <ul> <li><a href="http://www.netbeans.org/">Netbeans</a></li> <li><a href="http://www.eclipse.org/">Eclipse</a></li> <li><a href="http://www.xemacs.org/">xemacs</a></li> </ul> </dd> <dt>HTML Editors</dt> <dd> <ul> <li><a href="http://www.mozilla.org/">Mozilla Editor</a>: Easy to use. Spellcheck module available from mozdev.org.</li> </ul> </dd> <dt>Utilities</dt> <dd> <ul> <li><a href="http://tidy.sourceforge.net/">Tidy</a>: detects errors in HTML.</li> <li><a href="http://validator.w3.org/">W3 XHTML validator</a></li> </ul> </dd> </dl> <h3>Windows Operating System</h3> <dl> <dt>Text Editors</dt> <dd> <ul> <li>Notepad: already installed on every machine, but lacks HTML support and spell check.</li> <li><a href="http://www.textpad.com/">Textpad</a>: Simple text editor. Includes HTML support and spellcheck.</li> </ul> </dd> <dt>HTML Editors</dt> <dd> <ul> <li><a href="http://www.mozilla.org/">Mozilla Editor</a>: Easy to use. Spellcheck module available from mozdev.org.</li> </ul> </dd> <dt>XML Editors</dt> <dd> <ul> <li>TBD</li> </ul> </dd> </dl> <h3>Linux Operating System</h3> <dl> <dt>Text Editors</dt> <dd> <ul> <li>Emacs, vi, etc.</li> </ul> </dd> <dt>HTML Editors</dt> <dd> <ul> <li><a href="http://quanta.sourceforge.net/">Quanta Plus</a> </li> </ul> </dd> <dt>XML Editors</dt> <dd> <ul> <li>TBD</li> </ul> </dd> </dl> <h3>Further Reading and Resources</h3> <dl> <dt>Books</dt> <dd> <ul> <li><a href="http://jrobbins.org/books/">Books on HTML and CSS</a></li> </ul> </dd> <dt>Websites</dt> <dd> <ul> <li><a href="http://www.w3.org/MarkUp/Guide/">Getting started with HTML</a>: a gentle introduction</li> <li><a href="http://w3.org/">W3C standards organization</a> </li> <li><a href="http://w3schools.com/">w3schools.com</a>: Very fast and to-the-point tutorials on web technologies</li> <li><a href="http://htmlhelp.com/">htmlhelp.com</a>: good all-around site for HTML and related info </li> <li><a href="http://directory.google.com/Top/Computers/Data_Formats/Markup_Languages/">OpenDirectory page on markup langugages</a>: Including XHTML and tools</li> </ul> </dd> </dl> </div> </div> </body> </html> --- NEW FILE: HOWTO-upgrade.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "../templates/css/readyset.css"; @import "../templates/css/inst.css"; /* ]]> */ </style> </script> <title>How to Upgrade</title> </head> <body> <div class="app"> <div class="readyset"> <h2>ReadySET: How to upgrade</h2> <h3>Disclaimer</h3> <p>ReadySET is still in fairly early releases that are rapidly evolving. The differences between any two early releases may be quite large, making upgrading difficult.</p> <p>As ReadySET matures (i.e., passes v1.0.0), the changes between minor versions should become smaller and easier to upgrade.</p> <p>Also, some of the ReadySET content that is most likely to change and grow over time is not part of the templates at all, it is the <a href="http://readyset.tigris.org/words-of-wisdom/">words of wisdom</a> hosted on the ReadySET web site.</p> <h3>Low-Tech Upgrade Proceedure</h3> <p>You may simply cut and paste sections of HTML source code between new ReadySET templates and files that you have been using in your project.</p> <p>While potentially tedious and somewhat error-prone, this method requires no training or specific tools. It also has the advantages that it is very easy to update only as many or as few files as you desire.</p> <p>Check the release-notes.html in the new release of ReadySET for a summary of changes.</p> <h3>High-Tech Upgrade Proceedure</h3> <p>For users that use CVS for their own project: you can use CVS's <a href="http://cvsbook.red-bean.com/cvsbook.html#Tracking_Third-Party_Sources__Vendor_Branches_">vendor branch</a> feature to help you merge the latest changes from the ReadySET project into your project.</p> <p>Let's assume that you are upgrading from ReadySET v0.8.2 to v0.9.1. Let's also assume that you consider "Tigris.org" to be the vendor of ReadySET. Note that CVS does not allow periods in tag names, and we do not want ReadySET version numbers to conflict with any version numbers of your projects, so we will make the names more distinctive and use underscores instead: ReadySET_0_8_2, ReadySET_0_9_1, Tigris_org.</p> <p>Let's further assume that you are using a CVS server located at cvs.yourcompany.com with a repository located at /cvs, your username is username, and that you are using ReadySET for a project named yourproject.</p> <p>Steps:</p> <ol> <li>Unpack ReadySET v0.8.2 and add it to <strong>your</strong> CVS repository on a vendor branch. <pre> unzip ReadySET-082.zip cd ReadySET-082/templates cvs -d :pserver:use...@cv...:/cvs import -m 'importing ReadySET v0.8.2' yourproject Tigris_org ReadySET_0_8_2 cd .. </pre> </li> <li>Unpack ReadySET v0.9.1 and add it to <strong>your</strong> CVS repository on the same vendor branch. <pre> unzip ReadySET-091.zip cd ReadySET-091/templates cvs -d :pserver:use...@cv...:/cvs import -m 'importing ReadySET v0.9.1' yourproject Tigris_org ReadySET_0_9_1 cd .. </pre> </li> <li>Create a working copy of your project documents (if you don't already have one). <pre> mkdir workingcopy cd workingcopy cvs -d :pserver:use...@cv...:/cvs co yourproject </pre> </li> <li>Merge the <strong>differences</strong> between the two vendor versions of ReadySET into your working copy. <pre> cd yourproject cvs update -j ReadySET_0_8_2 -j ReadySET_0_9_1 </pre> </li> <li>You are likely to see several messages from CVS about merging files and conflicts. The CVS output lines that begin with "C" indicate conflicts.</li> <li>Edit your working copy files to resolve all conflicts. Browse the files to make sure that they look OK. If any files have changed names, you will have to cut and paste content from the old filename to the new filename.</li> <li>Commit your updated files to your repository <pre> cvs commit -m 'updated project documents to use newer ReadySET templates' </pre> </li> </ol> <p>These steps are specific to CVS, but other version control systems likely provide analogous functionality.</p> </div> </div> </body> </html> --- NEW FILE: faq.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "../templates/css/readyset.css"; @import "../templates/css/inst.css"; /* ]]> */ </style> </script> <title>User FAQ</title> </head> <body> <div class="app"> <div class="readyset"> <h2>ReadySET: User FAQ</h2> <h3>General Information</h3> <dl> <dt>What is ReadySET?</dt> <dd>It is a set of ready-to-use software engineering templates. Please, see the <a href="http://readyset.tigris.org/">ReadySET homepage</a>.</dd> <dt>Where does the name "ReadySET" come from?</dt> <dd>"ReadySET" is short for "Ready-to-use Software Engineering Templates". It also sounds like the phrase "ready, set, go!" which is said at the beginning of a race to give everyone a fair start. </dd> <dt>Where did the ideas for ReadySET templates come from?</dt> <dd>The general idea came from a need for me to provide a lot of guidance to university students learning software engineering without spending time lecturing to them. This fits well with the tigris.org mission of promoting open source software engineering, and previous efforts, like <a href="http://argouml.tigris.org/">ArgoUML</a> to ease adoption of software engineering tools and practices in industry. The content of specific templates came from our understanding of software engineering literature, our experience on software development projects, and our understanding of cognitive challenges of engineering decision-making. </dd> <dt>What is the competition for ReadySET?</dt> <dd>The main alternative to ReadySET is to do it yourself and reinvent the wheel or try to generalize from whatever documents you produced on your last project. That pattern leads to many individuals in our industry trying to develop their own methodology as they move from project to project and company to company. ReadySET is an attempt to gather that same knowledge from many people and share it more effectively. There are also products such as <a href="http://www.merant.com/News/PR/PR_02182003.asp">EssentialSET</a> and <a href="http://www-306.ibm.com/software/awdtools/rup/">RUP</a>.</dd> </dl> <h3>Download and Install</h3> <dl> <dt>How can I obtain ReadySET?</dt> <dd><a href="http://readyset.tigris.org/servlets/ProjectDocumentList">Download it</a>. Please, see the <a href="http://readyset.tigris.org/">ReadySET homepage</a>.</dd> <dt>What licence covers ReadySET?</dt> <dd>The <a href="../templates/readyset-license.html">ReadySET license</a> is a BSD-style license.</dd> <dt>What do I need to use ReadySET?</dt> <dd>A web browser and a text editor or HTML editor. Please see our list of <a href="recommended-tools.html">recommended tools</a>.</dd> <dd>It is also strongly recommended that you use a web server, a version control system, and web-based issue tracking system. You can work through setting up these tools yourself, or use a Collaborative Development Environment such as <a href="http://www.collab.net/">CollabNet's SourceCast</a>.</dd> <dt>How do I install ReadySET?</dt> <dd>Simply unarchive it. Make a copy of the template files to use as your project documents.</dd> <dt>How do I upgrade from an older version of ReadySET?</dt> <dd>For any users not using CVS for their own project: simply copy-and-paste any desired text from the new templates into your project documents. </dd> <dd>For users that use CVS for their own project: you can use CVS's <a href="http://cvsbook.red-bean.com/cvsbook.html#Tracking_Third-Party_Sources__Vendor_Branches_">vendor branch</a> feature to help you merge the latest changes from the ReadySET project into your project. Follow these <a href="HOWTO-upgrade.html">upgrade steps</a>. </dd> </dl> <h3>Main Concepts</h3> <dl> <dt>What is a "ReadySET template"?</dt> <dd>It is an HTML file that with sample text that you should use to create project documents.</dd> <dt>What is a "project document"?</dt> <dd>It is an HTML file, copied from a ReadySET template, that contains specific information about your project.</dd> <dt>What is a "prompt"?</dt> <dd>In most other document template sets, the templates are basically outlines with headings and subheadings. In ReadySET subheadings are written in the form of a question or prompt. That helps make the documents more self-explanatory and easier for other stakeholders to quickly read or write an answer to.</dd> <dt>What are the colored bars in the right-hand margin?</dt> <dd>Those bars indicate sections of sample text. They are explicitly marked so that you can see at a glance which parts have been filled in and which parts are still the original sample text. Once you edit the text, you should remove the HTML attribute class="sample1" to remove the bar.</dd> <dt>Why are there multiple answers (and colored bars) to each prompt?</dt> <dd>Rather than give a long explanation of the meaning of each prompt, ReadySET includes a few sample answers to most prompts. That works best when one of the sample answers includes ideas that relate to your specific project. In many cases, much of the process of filling in a template is reduced to "chipping away" at the sample text by removing text that does not apply to your project.</dd> <dt name="chipaway">What is "chipping away"?</dt> <dd>The term "chipping away" comes from an old joke: when a sculptor is asked how he carved a marble statue of a horse, he replies "It was easy, I just started with a big block of marble and chiped away everything that did not look like a horse."</dd> <dt>What is an "attached worksheet"?</dt> <dd>The idea is similar to filling in an IRS form and using worksheets to calculate subtotals or make specific decisions. That is to say, there is a hierarchy to the templates: there are the main templates, and then worksheets for specific topics. We have divided the information into several files so that each file is focused on one topic, and so that each file can be worked on by one person in a reasonable amount of time.</dd> <dt>What is the "process impact" box about?</dt> <dd>The process impact box explains where the current template fits into the software development process. It usually includes a brief comment on who should create the document, and who would be expected to make use of it. You can change the process impact box, but you should not need to.</dd> <dt>What is a "checklist"?</dt> <dd>There are two kinds of checklists: <ul> <li>Many of the templates have a section with questions that help you check your work in that template. Often the sample answers to the questions prompt you to take some corrective action.</li> <li>For design and code review meetings, there are links to guidelines and checklists that help you identify common errors in those artifacts.</li> </ul> </dd> <dt>What is a "sticky note"?</dt> <dd>The idea is similar to a post-it note attached to a document that tells you do "sign here" or fill in a certain part. There are two types of sticky notes: <ul> <li>TODO: Instructs you on how to fill in the template. This is the minimum that you need to do. One of the main goals of ReadySET is to help your team <i>quickly</i> carry out basic software engineering activities. The TODO sticky notes make that easy by making the templates more self-explanatory.</li> <li>TIP: Helps you think of better ways to fill in the template. One of the other main goals of ReadySET is to help your team make better decisions that can make your whole project more successful. The TIP sticky notes help with that.</li> </ul> After you have done what the sticky note says, you can delete the sticky note. In the HTML file, they are marked with class="sticky". </dd> <dt>Why do some links have dashed underlines?</dt> <dd>Those are links to the definitions of terms. They are visually different so that readers whill know that they can quickly read the definition of that term without being side-tracked. Also, the dashed underlines do not appear when the document is printed.</dd> </dl> <h3>Configuring and Customizing ReadySET</h3> <dl> <dt>One of the ReadySET templates is not needed for my project. How do I remove it?</dt> <dd>Just delete it, and remove any links to it.</dd> <dt>How do I add a new file to the set?</dt> <dd>Just open a new file in your HTML editor. Save the file, and add links to it from other templates as you see fit. You may want to copy an existing template and tear out all its content and put your content there instead, that way the new template will have the proper HTML HEAD elements, but these are simple anyway.</dd> <dt>How can I use ReadySET for projects using technologie like .NET or J2EE?</dt> <dd>ReadySET does not have any complex customization tools. There are no "plug-ins" or meta-models. Those layers of abstraction make it harder to get started. ReadySET is just a set of XHTML templates. You can edit them any way you like, it is up to you and there is nothing preventing you from doing it. <a href="http://www.readysetpro.com/">ReadySET Pro</a> takes a more powerful approach that does have a bit of a learning curve, but scales well to corporate usage.</dd> <dt>How can I add "Company Proprietary" to every page?</dt> <dd>That text is already there in a paragraph with CSS class="legal1". Normally that CSS style is invisible. You can make it visible by editing css/inst.css to uncomment the line "display: block !important". If you need to change the text, you can use a global search and replace in your text editor.</dd> <dt>Who uses ReadySET?</dt> <dd>Stay tuned to the ReadySET mailing list for user testimonials.</dd> </dl> <h3>Contributing to the Project</h3> <dl> <dt>Who can contribute to this project?</dt> <dd>Everyone is welcome, especially project managers or team leads who have first-hand experience on many projects where templates like these would have helped.</dd> <dt>How can someone start to contribute?</dt> <dd>Make sure that you are familiar with the templates, then send your comments to the project mailing list and we will go from there. Only a core group of developers will have commit access, but others can make contributions via the mailing list and we will review them and integrate changes.</dd> <dd>Please do not send in any proprietary or copyrighted content. We will have to immediately delete it. E.g., if you have a document template that you use at your current company, please do not send it. Instead, you can give us a few bullet points or examples on specific things that you think help make that type of document more useful based on your general experience. Of course, you should never send in any actual document that contains any actual information about your business, product plans, schedules, budgets, personnel, or customers.</dd> <dt>Who is contributing to ReadySET?</dt> <dd>Stay tuned to the ReadySET mailing list for information.</dd> </dl> <h3>Other Questions</h3> <dl> <dt>My question is not on this page. How do I find the answer?</dt> <dd>Your question may have already been asked and answered, to find it: search the project <a href="http://readyset.tigris.org/servlets/SummarizeList?listName=dev">mail archives</a> and <a href="http://readyset.tigris.org/servlets/ProjectIssues">issue tracking system</a>. If you still don't find it, you can ask the question on the the ReadySET developers' mailing list or you can enter an issue. You must subscribe to the mailing list before you may post. For commercial support and training, see <a href="http://www.readysetpro.com/">ReadySET Pro</a>. </dd> </dl> </div> </div> </body> </html> |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:19:42
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/ReadySET-0-9-1 In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/ReadySET-0-9-1 Added Files: index.html project_nav.html Log Message: initial commit --- NEW FILE: project_nav.html --- <a href="templates/frameset.html">Browse templates</a> | <a href="http://readyset.tigris.org/servlets/ProjectDocumentList">Download</a> | <a href="http://readyset.tigris.org/words-of-wisdom/">Words-of-wisdom</a> | Translations: <a href="/es/index.html">Spanish</a> --- NEW FILE: index.html --- <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//Tigris//DTD XHTML 1.0 Transitional//EN" "http://style.tigris.org/tigris_transitional.dtd"> <html> <head> <style type="text/css"> /* <![CDATA[ */ @import "templates/css/readyset.css"; @import "templates/css/inst.css"; /* ]]> */ </style> <link rel="stylesheet" type="text/css" href="http://www.tigris.org/branding/css/print.css" media="print" /> </script> <title>ReadySET: Project Overview</title> </head> <body> <h2>ReadySET: Project Overview</h2> <div class="app"> <div class="readyset"> <h3>Mission</h3> <div align="right" style="background-color: #ffc; padding: 1em; float: right; border: #cc0 3px outset; margin: 1em; text-align: left;"> <a href="templates/frameset.html">Browse templates</a><br/> <a href="http://readyset.tigris.org/servlets/ProjectDocumentList">Download templates</a><br/> <a href="http://readyset.tigris.org/words-of-wisdom/">Words-of-wisdom</a> </div> <dl> <dt>What problem does this project address?</dt> <dd>Software development projects require a lot of "paperwork" in the form of requirements documents, design documents, test plans, schedules, checklists, release notes, etc. It seems that everyone creates the documents from a blank page, from the documents used on their last project, or from one of a handful of high-priced proprietary software engineering template libraries. For those of us who start from a blank page, it can be a lot of work and it is easy to forget important parts. That is not a very reliable basis for professional engineering projects.</dd> <dt>What is the goal of this project?</dt> <dd>ReadySET is an open source project to produce and maintain a library of reusable software engineering document templates. These templates provide a ready starting point for the documents used in software development projects. Using good templates can help developers work more quickly, but they also help to prompt discussion and avoid oversights.</dd> <dt>What are some key features that define the product?</dt> <dd> <ul> <li>High-quality outlines, sample text, and checklists.</li> <li>Uses simple web technologies: Pure XHTML and CSS.</li> <li>Templates for <i>many</i> common software engineering documents.</li> </ul> </dd> <dt>What makes this product different from others?</dt> <dd>This is an open source project that you are welcome to use for free and help make better. Existing packages of software engineering templates are highly costly and biased by the authorship of only a few people, by vendor-client relationships, or by the set of tools offered by a particular vendor.</dd> <dd>These templates are in pure XHTML with CSS, not a proprietary file format. That makes them easier to edit and to track changes using freely available tools and version control systems. The templates are designed to always be used on the web; they use hyperlinks to avoid duplicating information.</dd> <dd>The templates are not burdened with information about individual authorship or document change history. It is assumed that professional software developers will keep all project documents in version control systems that provide those capabilities.</dd> <dd>These templates are not one-size-fits-all and they do not attempt to provide prescriptive guidance on the overall development process. We are developing a broad library of template modules for many purposes and processes. The templates may be filled out in a suggested sequence or in any sequence that fits your existing process. They may be easily customized with any text or HTML editor.</dd> </dl> <h3>Scope</h3> <dl> <dt>What is the scope of this project?</dt> <dd> We will build templates for common software engineering documents inspired by our own exprience. </dd> <dt>What are the high-level assumptions or ground rules for the project?</dt> <dd> I assume that the user takes ultimate responsibility for the content of all their actual project documents. The templates are merely starting points and low-level guidance. </dd> <dt>What are we not going to do?</dt> <dd> This project does not attempt to provide powerful tools for reorganizing the templates, mapping them to a given software development process, or generating templates from a underlying process model. This project does not include any application code for any tools, users simply use text editors to fill in or customize the templates. </dd> <dt>Is this project part of a larger effort?</dt> <dd> Yes. It is part of the Tigris.org mission of promoting open source software engineering. It is also the first product in a product line that will provide even better support to professional software developers. For more information, see <a href="http://www.readysetpro.com">ReadySET Pro</a>. </dd> </dl> <h3>Status</h3> <dl> <dt>What is the status of this project?</dt> <dd>These templates are based on templates originally used to teach software engineering in a university project course. They are now being enhanced, expanded, and used more widely by professionals in industry.</dd> <dd>The template set is fairly complete and ready for use in real projects. You can <a href="http://readyset.tigris.org/servlets/ProjectDocumentList">download</a> recent releases. We welcome your feedback.</dd> <dd>For the latest news, see the <a href="http://readyset.tigris.org/servlets/ProjectNewsList">Project Announcements</a>.</dd> </dl> <h3>Applicability</h3> <dl> <dt>Who should use this product?</dt> <dd>ReadySET is aimed at software engineers who wish that their projects could go more smoothly and professionally. ReadySET can be used by anyone who is able to use an HTML editor or edit HTML in a text editor.</dd> <dt>How can users get started?</dt> <dd> <ol> <li>Briefly <a href="templates/frameset.html">browse all templates</a></li> <li><a href="http://readyset.tigris.org/servlets/ProjectDocumentList">Download</a> the templates and unarchive</li> <li>Edit the templates to fit the needs of your project</li> <li>Place the templates on a web server where all your project stakeholders can view them</li> <li>Edit the templates to fill in detailed information <ul> <li>Use a text editor or an HTML editor. Please see our list of <a href="docs/recommended-tools.html">recommended tools</a>. (You can use Word, but that is strongly discouraged.)</li> <li>Follow instructions that appead in yellow "sticky notes"</li> <li>Replace text in ALL CAPS with text that describes your project</li> <li>"<a href="docs/faq.html#chipaway">Chip away</a>" text that does not apply to your project</li> <li>Add text, diagrams, or links as needed</li> </ul> </li> <li>Use the checklists to catch common errors and improve the quality of your documents.</li> <li>Use the words-of-wisdom pages to help improve the document or deepen your understanding of relevant issues.</li> <li>Optionally, you may change fonts and colors in the file css/inst.css.</li> <li>If you have questions or insights about a templates, please read the <a href="docs/faq.html">FAQ</a> or send an email to <a href="mailto:dev@readyset.tigris.org" >dev@readyset.tigris.org</a>. You must subscribe to the mailing list before you may post.</li> </ol> </dd> </dl> <div style="display: none"> Terms to work in: <h2>8951 java tutorial web services</h2> <li>0269 software process improvement</li> <li>0284 software load testing tool</li> <h2>3418 quality software</h2> <li>0351 use case example</li> <li>0354 sample project proposal</li> <li>0368 software test plan template</li> <h2>2705 software defect tracking system</h2> <li>0403 unit testing tutorial</li> <li>0459 software requirement document</li> <li>0476 cvs version control software</li> <li>0495 automated testing tool</li> <li>0525 software development process</li> <li>0571 software requirement specification</li> <a href="#">0701 uml diagram</a> <a href="#">0726 uml tool</a> <a href="#">0964 junit</a> <a href="#">1048 uml tutorial</a> <a href="#">1083 issue tracking software</a> <h2>2116 uml use case diagram</h2> <a href="#">1255 software quality assurance</a> <a href="#">1273 sample project proposal template</a> <a href="#">1749 manual uml</a> <h2>5737 extreme programming</h2> </div> </div> </body> </html> |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:10:07
|
Update of /cvsroot/opengtoolkit/deab/example_projects/Text File Viewer/Built In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29240/example_projects/Text File Viewer/Built Modified Files: TextFileViewer-vi_lib.llb Log Message: Index: TextFileViewer-vi_lib.llb =================================================================== RCS file: /cvsroot/opengtoolkit/deab/example_projects/Text File Viewer/Built/TextFileViewer-vi_lib.llb,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 Binary files /tmp/cvsuIQ9cv and /tmp/cvs286p5O differ |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:06:01
|
Update of /cvsroot/opengtoolkit/deab In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv361 Modified Files: deab.mmap Log Message: Index: deab.mmap =================================================================== RCS file: /cvsroot/opengtoolkit/deab/deab.mmap,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 Binary files /tmp/cvsoImcZS and /tmp/cvsb02Uw0 differ |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:05:08
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/ReadySET-0-9-1/templates/css In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/ReadySET-0-9-1/templates/css Added Files: file.gif folder-closed.gif folder-open.gif gears.gif gears.png inst.css nav.css nw_maj_rond.gif print.css readyset.css tip.gif tip.png todo.gif todo.png Log Message: initial commit --- NEW FILE: file.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: tip.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: nav.css --- body, ol, li, h2 { padding:0; margin: 0; } ol#root { padding-left: 5px; margin-top: 2px; margin-bottom: 1px; list-style: none;} #root ol { padding-left: 5px; margin-top: 2px; margin-bottom: 1px; list-style: none;} #root li { margin-bottom: 1px; padding-left: 5px; margin-top: 2px; font-size: x-small; } .panel { border-bottom: 1px solid #999; margin-bottom: 2px; margin-top: 2px; background: #eee; } #root ul { margin-bottom: 1px; margin-top: 2px; list-style-position: inside; } #root a { text-decoration: none; } .folder { background: url(folder-closed.gif) no-repeat; float: left; height: 14px; width: 26px; padding-right: 3px } .doc { background: url(file.gif) no-repeat; float: left; height: 14px; width: 12px; padding-right: 3px; margin-left: 20px;} --- NEW FILE: todo.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: folder-open.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: nw_maj_rond.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: folder-closed.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: inst.css --- /* $Id: inst.css,v 1.1 2004/08/17 17:19:59 jkring Exp $ This file contains rules that extend or override the more basic formatting defined in readyset.css. Edit it to customize the fonts and colors. You are responsible for maintaining your own set of (optional) deltas from readyset.css defaults; this file is intended as an example. To make "Company Proprietary" appear on every page footer, uncomment the line "display: block !important;" in the legal1 style. */ .footnote { /* To hide footnotes, change "block" to "none". */ display: block; } body { background: #fff; color: #000; } h3, h4 { background-image: none; background: #ccc; color: #000; } h3 { border-left: solid 1.2em #666; } h4 { border-left: solid 0.7em #666; } #bodycol h3, #bodycol h4 { border: 0; } .readyset td { background: #eee !important; } .readyset .axial td { background: #fff !important; } .readyset th { background-color: #ccc; } body, th, td, input, select { font-family: Verdana, Helvetica, Arial, sans-serif; } code, pre, textarea { font-family: 'Andale Mono', Courier, monospace; } .sticky { background: #ffc; border-right-color: #aaa; border-bottom-color: #aaa; } .tip { background: #ffc; background-image: url(http://www.readysetpro.com/css/tip.gif); background-repeat: no-repeat; background-position: top left; border-right-color: #aaa; border-bottom-color: #aaa; padding-left: 36px; min-width: 30px; min-height: 30px; /* filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='tip.png',sizingMethod='scale'); */ } .todo { background: #ffc; background-image: url(http://www.readysetpro.com/css/todo.gif); background-repeat: no-repeat; background-position: top left; border-right-color: #aaa; border-bottom-color: #aaa; padding-left: 36px; min-width: 30px; min-height: 30px; /* filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(enabled=true,src='todo.png',sizingMethod=scale); */ } #processimpact { background: #eee; border-color: #aaa; background-image: url(http://www.readysetpro.com/css/gears.gif); background-repeat: no-repeat; background-position: top left; padding-left: 36px; min-width: 30px; min-height: 30px; /* filter:progid:DXImageTransform.Microsoft.AlphaImageLoader(src='gears.png',sizingMethod='scale'); */ } .reusablefragment { background: #eee; border: 2px dashed; } .sample1 { border-right: 4px double #500; } .sample2 { border-right: 4px double #050; } .sample3 { border-right: 4px double #005; } .sample4 { border-right: 4px double #505; } a.def { text-decoration: none; border-bottom: dashed 1px blue; cursor: help; } .legal1 { /* display: block !important; */ background: #eee; border-color: #aaa; } --- NEW FILE: gears.gif --- (This appears to be a binary file; contents omitted.) --- NEW FILE: todo.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: readyset.css --- /* $Id: readyset.css,v 1.1 2004/08/17 17:19:59 jkring Exp $ This file is based on tigris.css, which is available from http://style.tigris.org/. This file defines basic default formatting for HTML conforming to Tigris application style. To extend or override these rules for your instance, edit inst.css instead of this file. */ table, th, td { border: none; } .tabs th { border-right: 1px solid #333; background-color: #ddd !important; color: #fff; border-left: 3px solid #fff; } .readyset .tabs td { background-color: #999 !important; border-bottom: 1px solid #fff; border-right: 1px solid #fff; border-left: 3px solid #fff; } .tabs { border-bottom: 6px #ddd solid; } .tabs th, .tabs th a:link, .tabs th a:visited { color: #555; } .tabs td, .tabs td a:link, .tabs td a:visited { color: #fff; } .tabs a { text-decoration: none; } .axial th { background-color: #ddd; color: black; } body .grid td { border-top: 1px solid #ccc; border-left: 1px solid #ccc; background-color: transparent; } body, textarea, pre, code { font-size: x-small; voice-family: "\"}\""; voice-family: inherit; font-size: small; } small, div.tabs th, div.tabs td, input, select { font-size: xx-small; voice-family: "\"}\""; voice-family: inherit; font-size: x-small; } .tabs td, .tabs th, dt { font-weight: bold; } table { font-size: 1em; } /* box properties (exclusive of borders), positioning, alignments, list types, text-indent */ p, ul, ol, dl { margin-top: .67em; margin-bottom: .67em; } .readyset h3, .readyset h4 { padding: 3px; padding-left: 5px; margin-right: 2px; margin-left: 2px; margin-bottom: 0; clear: both; } form { margin: 0; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } td, th { padding: 2px 3px; text-align: left; vertical-align: top; } .tabs { margin-top: .67em; margin-right: 2px; margin-left: 2px; padding-left: 8px; } .tabs td, .tabs th { padding: 3px 9px; } .right { text-align: right !important; } .center { text-align: center !important; } .readyset .axial th { text-align: right; white-space: nowrap; } dd { margin-bottom: .67em; } .tier1 { margin-left: 0; } .tier2 { margin-left: 1.5em; } .tier3 { margin-left: 3em; } .tier4 { margin-left: 4.5em; } .level1 { padding-left: 0; } .level2 { padding-left: 1em; } .level3 { padding-left: 2em; } .level4 { padding-left: 3em; } .alt { display: none; } /* additions specific to ReadySET */ tr ul, tr ol, tr p { margin-top: 0; } tr ul { margin-left: 0px; padding-left: 2em; } .sticky { padding: 3px; margin-right: 2px; margin-bottom: 3px; border-right: 1px solid; border-bottom: 1px solid; } .tip { padding: 3px; margin-right: 2px; margin-bottom: 3px; border-right: 1px solid; border-bottom: 1px solid; } .todo { padding: 3px; margin-right: 2px; margin-bottom: 3px; border-right: 1px solid; border-bottom: 1px solid; } #processimpact { border: 1px solid; padding: 3px; margin-right: 2px; margin-bottom: 2px; } .footnote { width: 80%; border-top: solid #aaa 1px; font-size: x-small; padding-top: 3px; margin-top: 3em; } .reusablefragment { padding: 6px; margin-top: 3em; margin-bottom: 3em; } .sample1, .sample2, .sample3, .sample4 { padding-right: 2px; margin-bottom: 4px; } .legal1 { border: 2px solid; padding: 3px; text-align: center !important; font-size: xx-large; font-weight: bold; display: none; } .linklist a { display: block; } .sub { padding-left: 1em; } :target { border: 2px solid red; } --- NEW FILE: print.css --- /* $Id: print.css,v 1.1 2004/08/17 17:19:59 jkring Exp $ This file contains CSS sytle rules that make the document look more presentable when printed. E.g., one cannot follow hyperlinks to definitions on a printed page, so the dashed underlines are removed. */ h3, h4 { font-size: x-small; } body, textarea, pre, code { font-size: xx-small; } small, div.tabs th, div.tabs td, input, select { font-size: xx-small; } table { font-size: xx-small; } .sticky, .footnote { display: none; } a.def { text-decoration: none; border-bottom: none; color: black; } --- NEW FILE: tip.png --- (This appears to be a binary file; contents omitted.) --- NEW FILE: gears.png --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:04:13
|
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29629/DEAB RTM Testing Log Message: Directory /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:03:56
|
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/experimental/DEAB RTM Testing Added Files: Relink MNU File Example.vi Untitled 1.vi Untitled.rtm Log Message: initial commit --- NEW FILE: Untitled 1.vi --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Relink MNU File Example.vi --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Untitled.rtm --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:03:25
|
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/RTM Testing In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/experimental/DEAB RTM Testing/RTM Testing Added Files: Untitled 1.vi Untitled.rtm Untitled2.rtm Log Message: initial commit --- NEW FILE: Untitled 1.vi --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Untitled.rtm --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Untitled2.rtm --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 23:01:41
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv527/Software Project Multi-Map Added Files: Browse.mmap Summary.mmap Log Message: initial commit --- NEW FILE: Browse.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Summary.mmap --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:58:14
|
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/RTM Testing In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29783/RTM Testing Log Message: Directory /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/RTM Testing added to the repository |
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/Read-Write Linker Info from File In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/experimental/DEAB RTM Testing/Read-Write Linker Info from File Added Files: Read Linker Info from File.vi VI Tree - Read-Write Linker Info from File.vi Write Linker Info from File.vi Log Message: initial commit --- NEW FILE: VI Tree - Read-Write Linker Info from File.vi --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Read Linker Info from File.vi --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Write Linker Info from File.vi --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:55:53
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Test Cases In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30593/Test Cases Log Message: Directory /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Test Cases added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:55:35
|
Update of /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/Read-Write Linker Info from File In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29783/Read-Write Linker Info from File Log Message: Directory /cvsroot/opengtoolkit/deab/experimental/DEAB RTM Testing/Read-Write Linker Info from File added to the repository |
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map Added Files: Architecture.mmap Demo Script.mmap Design.mmap Feature Set.mmap Feature.mmap Glossary.mmap Implementation Notes.mmap Installation and Quick Start Guide.mmap Interview Checklist.mmap Legal Issues.mmap Persistence.mmap Project Overview.mmap Project Plan.mmap Project Proposal.mmap QA Plan.mmap Release Checklist.mmap Resource Needs.mmap Review Meeting Checklists.mmap Review Meeting Notes.mmap Security.mmap Software Development Methodology.mmap Software Requirements Specification.mmap Source Code Organization and Build System.mmap Status Report.mmap Target Audience and Benefits.mmap Test Case Format.mmap Test Cases.mmap Test Run Suite.mmap Test Suite.mmap Use Case Suite.mmap Use Case.mmap User FAQ.mmap User Guide.mmap User Interface.mmap User Needs.mmap Log Message: initial commit --- NEW FILE: Interview Checklist.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Demo Script.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Test Run Suite.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Glossary.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Implementation Notes.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Security.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Use Case Suite.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: User Guide.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Review Meeting Notes.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Installation and Quick Start Guide.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Feature Set.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: QA Plan.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Resource Needs.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Architecture.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Target Audience and Benefits.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Review Meeting Checklists.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: User FAQ.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: User Interface.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Project Proposal.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Status Report.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: User Needs.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Persistence.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Design.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Test Case Format.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Legal Issues.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Project Plan.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Feature.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Software Requirements Specification.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Project Overview.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Software Development Methodology.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Release Checklist.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Test Suite.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Use Case.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Source Code Organization and Build System.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: Test Cases.mmap --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:52:10
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Test Cases In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/Test Cases Added Files: unique-test-case-id1.mmap Log Message: initial commit --- NEW FILE: unique-test-case-id1.mmap --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:51:09
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30458/Software Project Multi-Map Log Message: Directory /cvsroot/opengtoolkit/deab/Software Project Multi-Map added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:51:06
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Features In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30593/Features Log Message: Directory /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Features added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:51:02
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Brainstorming Session In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv30593/Brainstorming Session Log Message: Directory /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Brainstorming Session added to the repository |
|
From: Jim K. <jk...@us...> - 2004-08-17 22:10:11
|
Update of /cvsroot/opengtoolkit/deab In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28317 Added Files: deab.mmap Log Message: initial commit --- NEW FILE: deab.mmap --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 21:21:29
|
Update of /cvsroot/opengtoolkit/deab/example_projects/Text File Viewer In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29240/example_projects/Text File Viewer Modified Files: Text File Viewer.deab Log Message: Index: Text File Viewer.deab =================================================================== RCS file: /cvsroot/opengtoolkit/deab/example_projects/Text File Viewer/Text File Viewer.deab,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** Text File Viewer.deab 3 Nov 2003 04:31:21 -0000 1.1 --- Text File Viewer.deab 17 Aug 2004 17:06:54 -0000 1.2 *************** *** 13,17 **** Target Dir="TextFileViewer.llb" Convert Target to LLB=TRUE ! Convert Target to EXE=FALSE Remove Diagrams=FALSE --- 13,17 ---- Target Dir="TextFileViewer.llb" Convert Target to LLB=TRUE ! Convert Target to EXE=TRUE Remove Diagrams=FALSE |
|
From: Jim K. <jk...@us...> - 2004-08-17 18:49:39
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/ReadySET-0-9-1/templates/js In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/ReadySET-0-9-1/templates/js Added Files: super-simple-tree.js Log Message: initial commit --- NEW FILE: super-simple-tree.js --- function toggle(elm) { var newDisplay = "none"; elm.style.background = 'url(css/folder-closed.gif)'; var e = elm.nextSibling; while (e != null) { if (e.tagName == "OL") { if (e.style.display == "none") { newDisplay = "block"; elm.style.background = 'url(css/folder-open.gif)'; } break; } e = e.nextSibling; } while (e != null) { if (e.tagName == "OL") e.style.display = newDisplay; e = e.nextSibling; } } function collapseAll() { var lists = document.getElementsByTagName("ol"); for (var i = 0; i < lists.length; i++) lists[i].style.display = "none"; e = document.getElementById("root"); e.style.display = "block"; } function openBookMark() { var h = location.hash; if (h == "") h = "default"; if (h == "#") h = "default"; var ids = h.split(/[#.]/); for (i = 0; i < ids.length; i++) { if (ids[i] != "") toggle(document.getElementById(ids[i])); } } |
|
From: Jim K. <jk...@us...> - 2004-08-17 18:49:38
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Use Cases In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/Use Cases Added Files: UC-01.mmap Log Message: initial commit --- NEW FILE: UC-01.mmap --- (This appears to be a binary file; contents omitted.) |
|
From: Jim K. <jk...@us...> - 2004-08-17 17:44:23
|
Update of /cvsroot/opengtoolkit/deab/Software Project Multi-Map/Interviews In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv31503/Software Project Multi-Map/Interviews Added Files: Interview Notes.mmap interview with INTERVIEWEE.mmap Log Message: initial commit --- NEW FILE: Interview Notes.mmap --- (This appears to be a binary file; contents omitted.) --- NEW FILE: interview with INTERVIEWEE.mmap --- (This appears to be a binary file; contents omitted.) |
;){kind=link}
;){kind=link}
;){kind=link}