Comments re. Luxor's "ramses-1.0-b8" Examples

I've volunteered to document them, so here's some comments 
and questions for y'all re. ramses-1.0-b8

- Some of the examples are essentially GUI-only, while others 
  have code "behind" them, yes ?

- Unix is not supported well, in Ant makefiles _or_ in runfiles  :-(

- There are many naming inconsistencies (i.e. directory names, 
  jnlp names, and other names do not match)

- Need a simple "Hello, World" example that handles events.  
   For example, an <vbox>, a <label>, a <text>, and a <button> 
  that appends "Hello, World!\n" to the current contents of the <text>

- Need an example of using DTD's for i18n

- Need an example of using an RDF datasource to populate an XUL object
  (btw http://www.w3.org/2000/04/maillog2rdf/email.html )

- Need content for the "slide show" example (in what format ?)

- Need an example of drag and drop (in Swing)

- That "sahara" example is nifty and could be given more prominence, 
  since it demonstrates an operating principle of Luxor, namely, how 
  GUI's are interpreted and assembled 

- In general, javadoc is lacking completely  :-(

- The directory structure is idiosyncratic and unfamiliar.

	ramses is currently structured like this:

	<pre>
	 -- (supplied jnlp files)
	 -- lib 
	    `-- (supplied jarfiles)
	 -- bin 
	    `-- (built jar files)
	 -- src 
	    |-- (build.xml)
	    |-- chrome
	    |   |-- filechooser
	    |   |   |-- images
	    |   |   |   `-- 20x20
	    |   |   |       `-- (supplied image files)
	    |   |   |-- portlet
	    |   |   |   `-- (supplied html files)
	    |   |   `-- startup
	    |   |       `-- (supplied xul files)
	    |   |-- another-app
	    [..]
	    |-- demo (Java source tree starts here)
	    |   |-- filechooser
	    |   |   |-- action
	    |   |   |   `-- (.java's in package demo.filechooser.action)
	    |   |   `-- portlet
	    |   |       `-- (.java's in package demo.filechooser.portlet)
	    |   |-- another-app
	    [..]
	</pre>

  This structure is quite confusing (IMHO), particularly in how the sample 
  applications' names appear well down in the tree, and several times each.
  In any case, this structure does not really demonstrate how to structure 
  and package an application for deployment using JWD, does it ?

  I haven't really seen a "standard" directory structure specified anywhere, 
  but Apache Jakarta has some standard structures that seem well thought-out,
  and this would make it possible to copy from their ant makefiles. Also 
  Mozilla appears to have some standards for how to structure XUL apps.

  Doing this could bring several benefits:
  - more typical/familiar for Java developers (and Mozilla XUL developers too ?)
  - easier for the person writing the ant makefile, because it follows a standard 
    form, and other ant makefiles can be copied 
  - easier for a user to navigate, when investigating a particular sample app
  - easier for a developer to copy the entire directory stucture for his/her 
    own apps

  It would (AFAIK) end up looking something like this:

	<pre>
	 -- (build.xml for all sample apps)
	 -- lib 
	    `-- (supplied jarfiles)
	 -- filechooser 
	    |-- (build.xml for filechooser)
	    |-- build 
	    |   `-- (classfiles, build jarfiles, and all other files 
	    |        end up here, in a standard directory structure; 
	    |        see http://java.sun.com/products/javawebstart/1.2/docs/downloadservletguide.html
	    |-- dist 
	    |   `-- (the packaged, <ready-to-deploy JWS app ends up here)
	    `-- src
	        |-- java 
	        |   `-- demo (Java source tree starts here)
	        |       |-- action
	        |       |   `-- (.java's in package demo.filechooser.action)
	        |       `-- portlet
	        |           `-- (.java's in package demo.filechooser.portlet)
	        `-- webapp
	            |-- locale 
	            |   `-- (future .dtd files for localisation) 
	            `-- content
	                |-- (supplied .html, .xul, .jnlp files)
	                `-- images
	                    `-- 20x20
	                        `-- (supplied image files)
	 -- another-app
	 [..]
	</pre>

-- end --

HTH,
fred
[email protected]



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com