projects
/
org.ibex.core.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
d52a9cb
)
2002/06/05 20:05:52
author
megacz
<megacz@xwt.org>
Fri, 30 Jan 2004 06:48:01 +0000
(06:48 +0000)
committer
megacz
<megacz@xwt.org>
Fri, 30 Jan 2004 06:48:01 +0000
(06:48 +0000)
darcs-hash:
20040130064801
-2ba56-
ede058eca43076b87503afcf1885019a93880bfd
.gz
README
patch
|
blob
|
history
diff --git
a/README
b/README
index
7447813
..
f06e7f5
100644
(file)
--- a/
README
+++ b/
README
@@
-12,37
+12,30
@@
presented below:
Start here. Includes a map of all other documentation and a
description of the directory strucure
Start here. Includes a map of all other documentation and a
description of the directory strucure
-- The XWT home page [www/ or http://www.xwt.org/]
+- The XWT home page [http://www.xwt.org/]
- A complete copy of all static and dynamic content for
- www.xwt.org is in the xwt/www/ directory.
-
-- The XWT tutorial [www/html/tutorial.html_]:
+- The XWT tutorial [http://www.xwt.org/tutorial.html]
Gentle introduction to what XWT is, and how to write
.xwt's. Good for anybody who wants to write XWT applications.
Gentle introduction to what XWT is, and how to write
.xwt's. Good for anybody who wants to write XWT applications.
-- The XWT reference [www/html/reference.html]
+- The XWT reference [http://www.xwt.org/reference.html]
Precise, technical spec of exactly how XWT works. Assumes
familiarity with XWT (ie, you've read the tutorial). This is the
authoritative source for how an XWT engine should
behave.
Precise, technical spec of exactly how XWT works. Assumes
familiarity with XWT (ie, you've read the tutorial). This is the
authoritative source for how an XWT engine should
behave.
-- Javadoc [www/html/javadoc/package-summary.html]
+- Javadoc [http://www.xwt.org/javadoc/]
- The org.xwt.* packages are all documented with javadoc. If
- you've just checked out or downloaded a fresh copy of the XWT
- distribution, you can generate the javadoc by typing
- "./ant www" at the root directory of the distribution. You
+ The org.xwt.* packages are all documented with javadoc. You
should start by reading the package summary for org.xwt.Main,
and work your way around from there.
should start by reading the package summary for org.xwt.Main,
and work your way around from there.
-- Javasrc [www/html/javasrc/index.html]
+- Javasrc [http://www.xwt.org/javasrc]
Javasrc generates a syntax-colored and hyperlinked html copy of
Javasrc generates a syntax-colored and hyperlinked html copy of
- the XWT source code. To generate this documentation, type "./ant www"
- from the root directory of the distribution.
+ the XWT source code.
______________________________________________________________________________
______________________________________________________________________________
@@
-55,14
+48,6
@@
Directory Structure
ant - a unix shell script to launch ant
bin/ - all binary stuff generated by ant builds
build.xml - ANT build file
ant - a unix shell script to launch ant
bin/ - all binary stuff generated by ant builds
build.xml - ANT build file
- doc/ - documentation
-
- www/ - a copy of all static and dynamic content on xwt.org
- etc/ - configuration files
- html/ - static content -- files ending with an underscore get
- prefix.html/suffix.html/tagline.html added to them
- launch/ - code for launch.xwt.org
- src/ - source code for servlets running on xwt.org
lib/ - any third-party binary stuff needed during the build process
javago - a copy of the javago post-compilation bytecode inliner
lib/ - any third-party binary stuff needed during the build process
javago - a copy of the javago post-compilation bytecode inliner
@@
-117,17
+102,11
@@
list as of 20-Mar-2002:
Valid <target>s are:
build - builds a binary for the selected platform
Valid <target>s are:
build - builds a binary for the selected platform
- dist - creates deployment materials for the selected platform in dist/
- run - runs the binary for the selected platform
The following targets do not require that you specify a platform:
compile - compiles all .java's to .class'es
clean - empties bin/ and compiled binaries in dist/
The following targets do not require that you specify a platform:
compile - compiles all .java's to .class'es
clean - empties bin/ and compiled binaries in dist/
- www - rebuild www/html/
- push - push changes to the web server via ssh (RSA auth)
-
-
______________________________________________________________________________
______________________________________________________________________________