Menu
▾
▴
pymerase-cvs-commit
|
From: <mas...@us...> - 2003-08-13 23:21:22
|
Update of /cvsroot/pymerase/Docs/pymweb
In directory sc8-pr-cvs1:/tmp/cvs-serv4630
Modified Files:
ChangeLog pymweb-install.tex pymweb-manual.tex
Log Message:
Spelling/Grammar Correction
Index: ChangeLog
===================================================================
RCS file: /cvsroot/pymerase/Docs/pymweb/ChangeLog,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** ChangeLog 30 May 2003 02:44:47 -0000 1.2
--- ChangeLog 13 Aug 2003 23:19:35 -0000 1.3
***************
*** 1,2 ****
--- 1,3 ----
+ 2003-08-13 - Corrected minor grammatical errors
2003-05-29 - Pymweb Manual:
Added Debugging Information
***************
*** 8,10 ****
Removed coming soon notice
Added some URLs
! Minor wording changes
\ No newline at end of file
--- 9,11 ----
Removed coming soon notice
Added some URLs
! Minor wording changes
Index: pymweb-install.tex
===================================================================
RCS file: /cvsroot/pymerase/Docs/pymweb/pymweb-install.tex,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** pymweb-install.tex 30 May 2003 02:40:18 -0000 1.3
--- pymweb-install.tex 13 Aug 2003 23:19:35 -0000 1.4
***************
*** 28,32 ****
\author{Brandon King \\
Copyright \copyright ~2003 California Institute of Technology}
! \date{Version 0.1.3\\\today}
\maketitle
\thispagestyle{empty}
--- 28,32 ----
\author{Brandon King \\
Copyright \copyright ~2003 California Institute of Technology}
! \date{Version 0.1.4\\\today}
\maketitle
\thispagestyle{empty}
***************
*** 135,139 ****
\end{verbatim}
! Once you have made the change, you will need to restart apache. You
can do so by running the following command on a Debian system:
--- 135,139 ----
\end{verbatim}
! Once you have made the changes, you will need to restart apache. You
can do so by running the following command on a Debian system:
***************
*** 160,162 ****
questions or need help debuging.
! \end{document}
\ No newline at end of file
--- 160,162 ----
questions or need help debuging.
! \end{document}
Index: pymweb-manual.tex
===================================================================
RCS file: /cvsroot/pymerase/Docs/pymweb/pymweb-manual.tex,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** pymweb-manual.tex 30 May 2003 02:40:18 -0000 1.3
--- pymweb-manual.tex 13 Aug 2003 23:19:35 -0000 1.4
***************
*** 28,32 ****
\author{Brandon King \\
Copyright \copyright ~2003 California Institute of Technology}
! \date{Version 0.1.3\\\today}
\maketitle
\thispagestyle{empty}
--- 28,32 ----
\author{Brandon King \\
Copyright \copyright ~2003 California Institute of Technology}
! \date{Version 0.1.4\\\today}
\maketitle
\thispagestyle{empty}
***************
*** 43,48 ****
\subsection{\cb Description}
Pymweb is a web front end for Pymerase. The goal of Pymweb is to
! provide a method of allowing multiple people to use Pymerase without
! having to install Pymerase on their computer.
\subsection{\cb Installation}
--- 43,48 ----
\subsection{\cb Description}
Pymweb is a web front end for Pymerase. The goal of Pymweb is to
! provide a method for allowing multiple people to use Pymerase without
! having to install Pymerase onto their computer.
\subsection{\cb Installation}
***************
*** 64,69 ****
In Figure 1, you will find a screenshot of the Pymweb which you can
! reference as I briefly describe it's use. I will go into more detail
! in subsequent sections. There a five things you need to provide for
Pymerase to work properly. First, you need to provide a
schema. Second, choose which input module you would like to
--- 64,69 ----
In Figure 1, you will find a screenshot of the Pymweb which you can
! reference as I briefly describe its use. I will go into more detail
! in subsequent sections. There are five things you need to provide for
Pymerase to work properly. First, you need to provide a
schema. Second, choose which input module you would like to
***************
*** 74,83 ****
destination file name or directory name depending on the output module
you choose. And last but not least, you should choose what type of
! compression do you want Pymweb to use on your output file.
\subsection{\cb Schema}
In Pymerase, there are currently two methods you can use for defining
! a schema; UML or XML.
\subsubsection{\cb UML/XMI}\label{xmi}
--- 74,83 ----
destination file name or directory name depending on the output module
you choose. And last but not least, you should choose what type of
! compression you want Pymweb to use on your output file.
\subsection{\cb Schema}
In Pymerase, there are currently two methods you can use for defining
! a schema: UML or XML.
\subsubsection{\cb UML/XMI}\label{xmi}
***************
*** 98,102 ****
\subsubsection{\cb table.dtd XML}\label{table.dtd}
If you have decided to use the table.dtd XML format, things will be a
! little bit more complicate when using Pymweb, but it's still
manageable.
--- 98,102 ----
\subsubsection{\cb table.dtd XML}\label{table.dtd}
If you have decided to use the table.dtd XML format, things will be a
! little bit more complicated when using Pymweb, but it's still
manageable.
***************
*** 108,113 ****
called 'schema.tar.gz'.
! In case I have managed to confuse some people, here is a ficitious
! directory tree that I will us as an example.
\begin{verbatim}
--- 108,113 ----
called 'schema.tar.gz'.
! In case I have managed to confuse some people, here is a fictitious
! directory tree that I will use as an example.
\begin{verbatim}
***************
*** 162,180 ****
\subsection{\cb Output File/Dir Name}
Every output module has a different type of output, so you need to
! give a proper output name for them work correctly. If you take a look
at the 'Output' format column in section \ref{output}, you will see
what type of output each module generates. This table should by mostly
! sufficiant in guiding you in choosing a File or Directory
name. Although a few output modules are a little sensitive to the
! names you choose. Below is more information you will need to know
about the output modules and their output.
\subsubsection{\cb CreateDBAPI}
! CreateDBAPI creates a Python package (directory of python files) that
need to know about the name of their package.
If you are using UML/XMI, it's currently defined as the namespace, or
package. So, if you followed 'Pymerase Docs - ArgoUML for Pymerase',
! there is a step where you change the name of the namespace. What ever
you entered as the name of the namespace, is the name you should use
as the output directory name in Pymweb. If you do not do this, you
--- 162,180 ----
\subsection{\cb Output File/Dir Name}
Every output module has a different type of output, so you need to
! give a proper output name for them to work correctly. If you take a look
at the 'Output' format column in section \ref{output}, you will see
what type of output each module generates. This table should by mostly
! sufficient in guiding you to choosing a File or Directory
name. Although a few output modules are a little sensitive to the
! names you choose, below is more information you will need to know
about the output modules and their output.
\subsubsection{\cb CreateDBAPI}
! CreateDBAPI creates a Python package (directory of python files) that you
need to know about the name of their package.
If you are using UML/XMI, it's currently defined as the namespace, or
package. So, if you followed 'Pymerase Docs - ArgoUML for Pymerase',
! there is a step where you change the name of the namespace. Whatever
you entered as the name of the namespace, is the name you should use
as the output directory name in Pymweb. If you do not do this, you
***************
*** 210,214 ****
implemented in the current CreatePyTkDBWidgets. One-to-many and
many-to-many associations need to be implemented before it will be
! complete. I can still be useful in it's current state, and you can
always sub-class the Entry library files to implement your own
features.
--- 210,214 ----
implemented in the current CreatePyTkDBWidgets. One-to-many and
many-to-many associations need to be implemented before it will be
! complete. It can still be useful in it's current state, and you can
always sub-class the Entry library files to implement your own
features.
***************
*** 225,229 ****
Tar \& Gzip is most common on Linux/Unix based systems. Zip is most
! common on Windows systems. None is offered to make downloads easier
for single file downloads, and for debuging.
--- 225,229 ----
Tar \& Gzip is most common on Linux/Unix based systems. Zip is most
! common on Windows systems. Option None is offered to make downloads easier
for single file downloads, and for debuging.
***************
*** 280,282 ****
it to this documentation.
! \end{document}
\ No newline at end of file
--- 280,282 ----
it to this documentation.
! \end{document}
|
Thanks for helping keep SourceForge clean.
X