You are viewing a plain text version of this content. The canonical link for it is here.
Posted to tdk-dev@turbine.apache.org by mp...@apache.org on 2002/10/05 20:58:16 UTC
cvs commit: jakarta-turbine-tdk/xdocs tdk-howto.xml
mpoeschl 2002/10/05 11:58:16
Modified: xdocs tdk-howto.xml
Log:
TDKD1: Fix urls in tdk-howto
patch by Scott Eade
Revision Changes Path
1.4 +24 -19 jakarta-turbine-tdk/xdocs/tdk-howto.xml
Index: tdk-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-tdk/xdocs/tdk-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- tdk-howto.xml 24 Jul 2002 23:58:06 -0000 1.3
+++ tdk-howto.xml 5 Oct 2002 18:58:16 -0000 1.4
@@ -49,16 +49,20 @@
<p>
In order to do anything interesting with the TDK, you are also going to need a
database that is compatable with the JDBC standard. The TDK currently comes
-with drivers for Hypersonic, InstantDB, MySQL, Postgres and SAPDB. Other drivers can be
-downloaded from the vendor's websites located here:
+with drivers for Hypersonic, InstantDB, MySQL, Postgres and SAPDB. Other drivers
+can be downloaded from the vendor's websites located here:
</p>
<ul>
<li>
- <a href="http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm">Oracle JDBC Drivers</a>.
+ <a href="http://technet.oracle.com/software/tech/java/sqlj_jdbc/software_index.htm">
+ Oracle JDBC Drivers
+ </a>.
</li>
<li>
- <a href="http://www.sybase.com/products/middleware/jconnectforjdbc/">Sybase JDBC Drivers</a>.
+ <a href="http://www.sybase.com/products/middleware/jconnectforjdbc/">
+ Sybase JDBC Drivers
+ </a>.
</li>
</ul>
@@ -289,26 +293,26 @@
Look at the example app that you now have on your screen. The view that you are
seeing actually consists of 4 different parts (top, bottom, menu and index) that
were assembled for you on the fly by Velocity. In order to see how this works,
-you have to edit the file "webapps/APPNAME/templates/app/layouts/Default.vm" This
-file defines how the default layout is shown on your screen. As you can see,
-it is written as a fragment of HTML that will eventually be integrated into your
-final page. Editing this file will affect the layout of your entire
+you have to edit the file "webapps/APPNAME/templates/app/layouts/Default.vm"
+This file defines how the default layout is shown on your screen. As you can
+see, it is written as a fragment of HTML that will eventually be integrated into
+your final page. Editing this file will affect the layout of your entire
application.
</p>
<p>
Knowing now how the page is laid out, go to the directory
-"webapps/APPNAME/templates/app/navigations" to see the files that will be inserted
-into the layout template above. Edit the file "DefaultBottom.vm", save your
-changes back, and reload your page. By doing this you should see whatever
+"webapps/APPNAME/templates/app/navigations" to see the files that will be
+inserted into the layout template above. Edit the file "DefaultBottom.vm", save
+your changes back, and reload your page. By doing this you should see whatever
changes you have made to the file appear at the bottom of your layout. This
change will also occur in all of the other pages on your site. Navigate to a
different page in order to confirm this behavior.
</p>
<p>
-Now go into the directory "webapps/APPNAME/templates/app/screens" The files in this
-directory are the ones that replace the "$screen_placeholder" variable in
+Now go into the directory "webapps/APPNAME/templates/app/screens" The files in
+this directory are the ones that replace the "$screen_placeholder" variable in
the original layout. Open up the file "Index.vm" and you will see that a
variable is defined called "$headings" that holds the strings for each of the
headings on the Index page and that a variable called "$entries" is used
@@ -334,7 +338,7 @@
handle for it into our session context so that it can be accessed from our
Index.vm page. You would edit this file to change the behavior of a given
page. More information on building sites with Velocity is available
-<a href="howto/velocity-site-howto.html">here.</a>
+<a href="../turbine-2/howto/velocity-site-howto.html">here.</a>
</p>
</section>
@@ -350,7 +354,7 @@
SQL.java. In fact, when you did your Insert of the data, Turbine called a
method called "doInsert" inside of the SQL class in order to insert the data.
A full explaination of how actions work is available
-<a href="action-event-howto.html">here.</a>
+<a href="../turbine-2/howto/action-event-howto.html">here.</a>
</p>
</section>
@@ -395,10 +399,11 @@
You now have your first Turbine application up and running and you now know
how to edit the Java and .vm files in the TDK in order to begin building a
specific application. In order to recompile any Java files that you change
-or create in the TDK, move to "webapps/APPNAME/WEB-INF/build" and run "ant compile".
-This will recompile all of the Java files that have changed in your project.
-You may also wish to join the Turbine Users mailing list. Instructions for
-doing so can be found <a href="http://jakarta.apache.org/site/mail.html">here.</a>
+or create in the TDK, move to "webapps/APPNAME/WEB-INF/build" and run "ant
+compile". This will recompile all of the Java files that have changed in your
+project. You may also wish to join the Turbine Users mailing list. Instructions
+for doing so can be accessed via the <a href="project-info.html">Project Info
+</a> page.
</p>
</section>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>