javacavemaps-developers Mailing List for Java Cave Maps (Page 3)
Status: Pre-Alpha
Brought to you by:
caverdude
Menu
▾
▴
javacavemaps-developers — Will be talk about packages, public classes and public methods
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(7) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(39) |
| 2009 |
Jan
(79) |
Feb
(26) |
Mar
(8) |
Apr
(6) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Larry G. <jav...@ya...> - 2009-01-26 23:49:52
|
http://www.amazon.com/Elements-Java-Style-Reference-Library/dp/B001KBY7XY/ref=pd_bbs_1?ie=UTF8&s=books&qid=1233013651&sr=8-1 Just thought I'd show you guys the amazon link. I'm about to begin working on the style.xml file in the specifications module of the svn repository. Larry Gray la...@ar... |
|
From: Larry G. <jav...@ya...> - 2009-01-25 06:39:25
|
I'll be starting a style.xml file which will list recommended style guidelines for this project, it will be based on the book, "Elements of Java Style". It will go in the specifications module of the SVN repository.
Thanks.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-25 05:58:46
|
I mostly finished the database.xml file which shows they type of information our database coding will keep track of when we get to that part. This file is in the specifications module of the svn repository.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-25 04:59:28
|
Rest areas and Information Areas around your state on the Interstates usually have brochures for the states attractions. Commercial caves in operation always have some amongst them. So if you are interested take a look. You pay a small fee and a guide will walk you on a lighted trail, or a cart or a boat even in some cases.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-25 04:49:14
|
I have not researched all the various methodologies. In my early years of coding I heard of no such thing. I though it went something like [specify][code][test][bug fix][done] end of story. If the end users wanted something different they put up with what they had until new software could be developed under a different contract with a different set of programmers usually.
I don't have time to research the various methodologies. But the analogy I can best use is this.
"Lets play ball!" uh what does this mean? Basket ball, Football, Soccer, Baseball? Cricket? Golf? or any of many other types of ball games. XP or agile style is a type of game. Its the one we are playing on this project. If you don't want to play this game then hang out and be tech support or write some free form demo code in the sandbox area. (cavemaps.casetest.sf_id.case1 case2 case3 etc.)
Everything is appreciated yet noting is expected (except communication) which can be "I don't have time to send another email for the next few months or year" In which case we can mark your developer record in developers.xml to be inactive showing the best guess time for when you might be active again.
Thanks
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-23 19:47:25
|
I added a database.xml file to the specifications module to show what kinds of data will be needed when we get to the database work. Take a look. Its not finished, only about half finished.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-23 18:36:06
|
I have created some Interfaces and classes in the parser, the method coding is on the TODO list right now.
You will see *Parser.java which are Interfaces
You will see Abstract*Parser.java which will be extended to form the final specialized classes.
You will see Survey*Parser.java which will use the final specialized parsing classes to specifically parse data into the Survey*Model.java classes.
Under Models I added FlatFileModel.java This will be used by the Parsers. I made it responsible for loading and saving data. Save to File, Load From File or Read from a Resource.
Our XML work is currently in SurveyParser.java
We will have to rethink what we should do with this code in the next iteration.
A SurveyLineParser should parse from a single text line or xml tag parent node <surveyLine></surveyLine> into the
SurveyLineModel.java class
A SurveyStationParser should parse from a single text line or xml tag parent node<surveyStation></surveyStation>
A SurveyParser should parse a set of Lines and a Set of Stations. We need to keep reworking the structure of this unil it is smple and works for both xml and flat files for our purposes.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-23 03:34:11
|
Uh, I'm making an entry for each developer, so look for your sf_id then edit that record entry. Thanks.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-23 02:26:35
|
TEAM (Together Everyone Achieves More)
1. A desire to work together.
2. A game plan for success.
3. We will talk about the plan.
4. Mutual goals, common source of motivation.
1. Means working together on various levels and various roles. The military has a teaching that once a leader makes a decision he sticks by that until the smoke clears. Then he can next time choose an alternate decision if he saw that it was a mistake the first time. This is to prevent indecisiveness based on emotion.
Anyway as a person who has the final say in this project, I feel I must make some decisions and stick to my guns so to speak. We have several levels of working together based on experience or mileage. Programmer Role with Developer Role with Architect role. Developer with Admin role or Editor roles. In basket ball you have guards and various other positions, same in football, quarterback, linemen etc. Why should it be different in TEAM programming. But like Sean said, we have the sandbox area the javacavemaps.sf_id.case1 .. case2 ..case3 In this area you may place any source related to the project and free form at that. Try to figure out where you might fit in best. For example if you feel you are best at hacking method logic but not much more, then hey the developers can make work for you.
2. I mostly have set the game plan as XP style development of the project. I utterly feel this can work out if we just say, "it probably won't work but we are going to do it anyway, we will try to make it work." I feel more strongly about it than that however. Especially the limiting scope/scale/granularity. Its tough to do, I've been that cowboy coder so much myself. Software is developed meaning it grows and it doesnt grow so fast that it needs total rewrites. Communication via rapid firing of emails will be the main way to make this XP style work out. With the 2 to 4 week iterative development cycle we need to stay in close contact if you have been assigned a task in the task manager. Any situational changed that develop which would limit your ability to complete the task means we need to drop the task, reduct its scale/scope or split it up or assign it to someone else.. Simple as that. This means no preasure at all really. If we have to it will
just get done on a later iteration. Also this would mean sticking to the XP principle of collective code ownership. Meaning if we have to split the task, or assign it to someone else and no one should have hurt feelings. I still expect notes in source to be made if someone makes some edit, they can claim it's their edit with a comment. Or if you create a class the by all means fill out the author tags. Also make notes in the main Javadoc for the class if you author some part of it but didn't create it intially.
3. Tell me your gripes and then tell me you'll help out according to the plan anyway. I'm not toally inflexible. Input is apreciated. It will help me to be better able to define the plan as well.
4. Mutial goals of playing or learning when it comes to hacking source, designing classes, interfaces, enumerations and pacakages. Playing and learning when it comes to software design and development. Playing and learning when it comes to managing a software project. Playing and learning when it comes to dealing with end-users. Playing and learning when it comes to using tools such as junit, ant, eclipse, jedit, xalan or whatever.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 18:25:38
|
I am now beginning to feel that use of Docbook may be overkill at this point. We have successfully converted a file now. But I have recruited a couple of xml guru's So we might just need some transformation files to convert our xml to a html list/sublist with a simple jump table at the top for jumping to major branches. This docbook xml is kindof ugly for our purposes. I probalby need to learn it more before I use it on this project.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 18:21:42
|
I feel our project could get a wider audiance if we support English first, French second and then Italian and Spanish. Later I may recruit some translators and we would then put all string literals in xml files which we will do anyway from the start. The user may then select the language. We will have to do something similar with the math. Standard vs Metric.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 17:32:45
|
There is programming then there is software development and then there is software engineering. Three different concepts really. Though some guys can be a one man band, many can't.
It gripes me that I only have the choice of "Developer" in the sf web interface project role when I join to the project. I would like to see "Programmer", "Developer", "Architect"
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 17:23:46
|
When I create a task I will prepend in this order PDA for level of difficulty of the task. P is programmer, D is developer, A is architect. I may sometimes use one, two or three of those. P D A or PD or DA or PDA
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 16:54:32
|
There is a reason I'm pushing us to use the sf web interface as much as we can. Sf project activity ranking is mostly based on the use of the web interface. 3% is based on svn and cvs commits.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 04:04:46
|
In the case that you get swamped by work or school, your task may be reassigned to someone else for that iteration. This is in effect putting you on the bench to warm it while someone else shoots the baskets. No big problem just communicate with admins as to your situation. In some cases the task may be removed from the iteration.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 03:42:58
|
In the svn specifications module there is a file called developers.xml
I started this with 3 entries. One has comments, one is blank and one is my record entry for caverdude as
an example. You may also view this to gain info about who your working with as a project admin and developer.
Please copy the blank record down in the file to the bottom and edit your personal entry into it, in order to help admin and other developers to know more about who you are. Make commits regularly by first doing a svn syncronization. This is to avoid svn commit conflicts. So copy paste the blank one and fill in the <sf_id> tag then commit. fill in some more tags and commit. Especially if you copy paste the skills or api tags commit on each copy paste operation.
Thanks.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-20 00:20:09
|
I like sports metaphors even though I never played team sports as I suspect most programmers have not. I could be wrong. I gained my team work experiences via U.S. Army Reserve 7 years, and from various jobs and from cave mapping projects. I once read a book on coach Wooden of the University of California LA Bruins. He used this line on his players all the time, "Be quick, but don't hurry!".
I'd say that applies quite well to XP style programming. Be quick, but don't hurry!.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-19 22:32:25
|
XP methodology has a very good concept where the project's growth of source code and complexity is controlled. This control process is called the iteration. It is also controlled via the adjustments to [time][resources][quality][scope/scale]. So if the controls are set correctly then a situation occurs where the project moves along at a steady rate. Compare this to the solo cowboy coder. He wants a task, not time goals, no scope or scale, no help[additional resources], and by all means his code is perfect no need to question quality. Fun Fun.
I have a few analogies for you. A group of 8 guys get together to play basketball from the neighborhood. 4 are skins, 4 are shirts. They are having fun working as teams killing time, no need for pay. In our case the skins are the developers and the shirts are the end users.
Another analogy to how this thing should work would be the Mounted Horse Cavalry. One guy leads the movement and pace, calls cadences, and the group move along together towards each milestones in their journey. One guy calls the charge, retreat, dismount, mount, etc. Their pace always remains the same. The milestones in our case are, iteration, minor releases, milestone releases.
Another analogy for the uncontrolled fun non team work cowboy coder technique. On farms they have a weed killer called 2-4D. This thing kills weeds by actually fertilizing them so that they grow so fast they can't get enough water and nutrients and die. (Purely trivial info, this is a broad leaf killer, it will kill grape vineyards withing 1000's of feet of a corn field.) Anyway, this is what uncontrolled grown to source code and projects can lead too. Project death. Unmanageable, crap that's only good in the eyes of the cowboy coder and not all that great for the end users.
So now lets talk about scale and scope. Same thing just different analogies. Scale would be like map scale and scope would be like Telescope, Binoculars, Zoom lenses etc. And one more thing I call Granularity, which is a similar concept. These principals can be applied to any part of the project, any branch, any feature, any module and to the project as a whole. What this is really talking about is planning and tasking. In XP this is called story cards and task cards. We can make up many story and task cards but you only select the ones that can be completed in the next iteration for that iteration. In our case again we are talking about the feature request, bug fix request, specifications and task management.
Lets say a task is assigned to an individual and his situation changes, this means that resource is eliminated or reduced. In this case the task must be scaled down for that individual or assigned to someone else. It may have to be split into multiple task so that the scale of each task is therefore reduced, then it can be assigned to different developers. Let me give you an example of scale.
Small. Task: Write a class that can read and write to a text file.
Slightly larger. Task: Write a class that can read and write a pipe delimited text file.
Even Larger. Task: Write a few Classes that can read and write 3 kinds of text files. Fixed width, Pipe delimited and simple "","", CSV style. This is tabular and data is to be expected in tabular form when read.
Super Large scale. Task:Write me an API that can handle almost every common case of text file parsing.
Extra Super Large: Eh, you know what to do, we need file IO here Lots of it, go for it, get some work done.
Granularity. Fine grained and Course grained. Example in this case a Pixel editor.
Course grained. We write one class, that uses the standard Java2D API to allow us to edit a simple GIF and save it using a single standard color pallet. This thing only edits small icon images.
Medium grained. We write a few helper classes to assist with the various parts of the view. A Menu class. An Editor Panel Class and a Color Selection Panel Class.
Fine grained. We write a core section with many classes and some packages. We add on extra component sections to assist in say some common special effects. The components have many classes and package each.
Extra Fine grained. We write a class for everything. A pixel even gets its own class.
Get the picture? The finer grained solutions have cost and trade offs. So do larger scale or scope solutions. Some adjustment to scope or scale can be made based on the developer himself and his mileage with this API or that API, this technique or that technique. But the fact remains until coding is being done, no adjust to up scope or scale or granularity can be made. Also granularity has more consequences because of its burden on the computer system. Adjustments to granularity must be carefully thought out on the developer or architect level.
Another example of this is that we have programmer type or size task, developer type or size task and archtect type or size task.
Programmer task: Hacking code logic in a method. Write local documentation. Writing test cases.
Developer task: Writing Javadocs and Class or Interface Definitions. Perform refactoring task. Deciding scale or scope of small task within the project.
Architech task: Deciding what paterns to use as well as other major design decisions, such as what package name scheme to use, what coding style standards to go by, and what class naming scheme would be used. Major refactoring issues as well. Deciding overall scale and scope and granularity.
Now have I totally confused you guys and scared you off by now? Don't worry, it's as serious as a neighborhood basket ball game. So get the shirts off. Lets sweat a little. And enjoy a sunny day.
P.S. Don't judge my programming abilities by the source thats on this project at the moment. Things will impove and become more interesting over time.
Thanks, and everything is apreciated though nothing is truely expected.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-18 23:28:35
|
large update on the source, I put /* This source is Licensed CPL 1.0 and belongs to the * Java Cave Maps Project. * * http://www.opensource.org/licenses/cpl1.0.txt * * http://www.sourceforge.net/projects/javacavemaps */ In the top of every file. Larry Gray la...@ar... |
|
From: Larry G. <jav...@ya...> - 2009-01-18 21:20:52
|
oops, should have read the error message closer, wrong path. Anyway here is the latest which makes me
think that the DTD's are wrong now.
C:\java\WORKSP~1\SPECIF~1>make_html.bat
C:\java\WORKSP~1\SPECIF~1>java org.apache.xalan.xslt.Process -out specs.html -in
calculator1.0.xml -xsl c:/java/docbook/docbook-xsl/html/docbook.xsl
file:///C:/java/WORKSP~1/SPECIF~1/calstblx.dtd; Line #196; Column #38; A '(' cha
racter or an element type is required in the declaration of element type "entry"
.
Larry Gray
la...@ar...
________________________________
From: Larry Gray <jav...@ya...>
To: jav...@li...
Sent: Sunday, January 18, 2009 2:58:40 PM
Subject: Re: [Javacavemaps-developers] xalan-j
Volume in drive C has no label.
Volume Serial Number is 2444-0DD1
Directory of C:\java\WORKSP~1\SPECIF~1
01/18/2009 02:46 PM <DIR> .
01/18/2009 02:46 PM <DIR> ..
01/04/2009 12:59 AM 218 .project
01/11/2009 11:59 PM 6,087 calculator1.0.xml
01/04/2009 01:12 AM 9,174 calstblx.dtd
01/04/2009 05:02 AM 4,805 catalog.xml
01/04/2009 05:02 AM 2,937 ChangeLog
01/04/2009 05:01 AM 4,010 docbook.cat
01/04/2009 01:11 AM 5,791 docbookx.dtd
01/11/2009 05:09 PM 2,494 iteration1.xml
01/18/2009 02:46 PM 138 make_html.bat
01/04/2009 01:12 AM 13,150 soextblx.dtd
01/18/2009 02:46 PM 0 specs.html
11 File(s) 48,804 bytes
2 Dir(s) 28,315,693,056 bytes free
C:\java\WORKSP~1\SPECIF~1>edit make_html.bat
C:\java\WORKSP~1\SPECIF~1>edit make_html.bat
C:\java\WORKSP~1\SPECIF~1>notepad make_html.bat
C:\java\WORKSP~1\SPECIF~1>make_html.bat
C:\java\WORKSP~1\SPECIF~1>java org.apache.xalan.xslt.Process -out specs.html -in
calculator1.0.xml -xsl c:/java/docbook/docbook-xsl/docbook.xsl -param use.exten
sions 1
(Location of error unknown)java.io.FileNotFoundException: c:\java\docbook\docboo
k-xsl\docbook.xsl (The system cannot find the file specified)
[Fatal Error] calstblx.dtd:196:38: A '(' character or an element type is require
d in the declaration of element type "entry".
file:///C:/java/WORKSP%7E1/SPECIF%7E1/calstblx.dtd; Line #196; Column #38; XSLT
Error (javax.xml.transform.TransformerConfigurationException): getAssociatedStyl
esheets failed
Exception in thread "main" java.lang.RuntimeException: getAssociatedStylesheets
failed
at org.apache.xalan.xslt.Process.doExit(Process.java:1155)
at org.apache.xalan.xslt.Process.main(Process.java:1128)
C:\java\WORKSP~1\SPECIF~1>dir
Volume in drive C has no label.
Volume Serial Number is 2444-0DD1
Directory of C:\java\WORKSP~1\SPECIF~1
01/18/2009 02:46 PM <DIR> .
01/18/2009 02:46 PM <DIR> ..
01/04/2009 12:59 AM 218 .project
01/11/2009 11:59 PM 6,087 calculator1.0.xml
01/04/2009 01:12 AM 9,174 calstblx.dtd
01/04/2009 05:02 AM 4,805 catalog.xml
01/04/2009 05:02 AM 2,937 ChangeLog
01/04/2009 05:01 AM 4,010 docbook.cat
01/04/2009 01:11 AM 5,791 docbookx.dtd
01/11/2009 05:09 PM 2,494 iteration1.xml
01/18/2009 02:55 PM 145 make_html.bat
01/04/2009 01:12 AM 13,150 soextblx.dtd
01/18/2009 02:55 PM 0 specs.html
11 File(s) 48,811 bytes
2 Dir(s) 28,315,365,376 bytes free
C:\java\WORKSP~1\SPECIF~1>notepad make_html.bat
C:\java\WORKSP~1\SPECIF~1>make_html.bat
C:\java\WORKSP~1\SPECIF~1>java org.apache.xalan.xslt.Process -out specs.html -in
calculator1.0.xml -xsl c:/java/docbook/docbook-xsl/docbook.xsl
(Location of error unknown)java.io.FileNotFoundException: c:\java\docbook\docboo
k-xsl\docbook.xsl (The system cannot find the file specified)
[Fatal Error] calstblx.dtd:196:38: A '(' character or an element type is require
d in the declaration of element type "entry".
file:///C:/java/WORKSP%7E1/SPECIF%7E1/calstblx.dtd; Line #196; Column #38; XSLT
Error (javax.xml.transform.TransformerConfigurationException): getAssociatedStyl
esheets failed
Exception in thread "main" java.lang.RuntimeException: getAssociatedStylesheets
failed
at org.apache.xalan.xslt.Process.doExit(Process.java:1155)
at org.apache.xalan.xslt.Process.main(Process.java:1128)
C:\java\WORKSP~1\SPECIF~1>
Thats it, no more time for this today. If anyone figures this out please reply to this.
Larry Gray
la...@ar...
________________________________
From: Larry Gray <jav...@ya...>
To: jav...@li...
Sent: Sunday, January 18, 2009 2:52:17 PM
Subject: Re: [Javacavemaps-developers] xalan-j
Ok I'm run xalanj giving it these parameters. I had found a html folder that was full of xsl files.
java org.apache.xalan.xslt.Process -out specs.html -in calculator1.0.xml -xsl c:/java/docbook/html/docbook.xsl -param use.extensions 1
I got errors and finally null pointer exception. I will try one more thing.
Larry Gray
la...@ar...
________________________________
From: Larry Gray <jav...@ya...>
To: jav...@li...
Sent: Sunday, January 18, 2009 2:32:11 PM
Subject: [Javacavemaps-developers] xalan-j
I installed xalan-j (apache.org) and set it up in my class path. Its there and working, but it didn't come with docbook xsl files or xslt files or whatever is needed. I'm hunting for those one http://www.sourceforge.net/projects/docbook downloads.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-18 20:58:41
|
Volume in drive C has no label.
Volume Serial Number is 2444-0DD1
Directory of C:\java\WORKSP~1\SPECIF~1
01/18/2009 02:46 PM <DIR> .
01/18/2009 02:46 PM <DIR> ..
01/04/2009 12:59 AM 218 .project
01/11/2009 11:59 PM 6,087 calculator1.0.xml
01/04/2009 01:12 AM 9,174 calstblx.dtd
01/04/2009 05:02 AM 4,805 catalog.xml
01/04/2009 05:02 AM 2,937 ChangeLog
01/04/2009 05:01 AM 4,010 docbook.cat
01/04/2009 01:11 AM 5,791 docbookx.dtd
01/11/2009 05:09 PM 2,494 iteration1.xml
01/18/2009 02:46 PM 138 make_html.bat
01/04/2009 01:12 AM 13,150 soextblx.dtd
01/18/2009 02:46 PM 0 specs.html
11 File(s) 48,804 bytes
2 Dir(s) 28,315,693,056 bytes free
C:\java\WORKSP~1\SPECIF~1>edit make_html.bat
C:\java\WORKSP~1\SPECIF~1>edit make_html.bat
C:\java\WORKSP~1\SPECIF~1>notepad make_html.bat
C:\java\WORKSP~1\SPECIF~1>make_html.bat
C:\java\WORKSP~1\SPECIF~1>java org.apache.xalan.xslt.Process -out specs.html -in
calculator1.0.xml -xsl c:/java/docbook/docbook-xsl/docbook.xsl -param use.exten
sions 1
(Location of error unknown)java.io.FileNotFoundException: c:\java\docbook\docboo
k-xsl\docbook.xsl (The system cannot find the file specified)
[Fatal Error] calstblx.dtd:196:38: A '(' character or an element type is require
d in the declaration of element type "entry".
file:///C:/java/WORKSP%7E1/SPECIF%7E1/calstblx.dtd; Line #196; Column #38; XSLT
Error (javax.xml.transform.TransformerConfigurationException): getAssociatedStyl
esheets failed
Exception in thread "main" java.lang.RuntimeException: getAssociatedStylesheets
failed
at org.apache.xalan.xslt.Process.doExit(Process.java:1155)
at org.apache.xalan.xslt.Process.main(Process.java:1128)
C:\java\WORKSP~1\SPECIF~1>dir
Volume in drive C has no label.
Volume Serial Number is 2444-0DD1
Directory of C:\java\WORKSP~1\SPECIF~1
01/18/2009 02:46 PM <DIR> .
01/18/2009 02:46 PM <DIR> ..
01/04/2009 12:59 AM 218 .project
01/11/2009 11:59 PM 6,087 calculator1.0.xml
01/04/2009 01:12 AM 9,174 calstblx.dtd
01/04/2009 05:02 AM 4,805 catalog.xml
01/04/2009 05:02 AM 2,937 ChangeLog
01/04/2009 05:01 AM 4,010 docbook.cat
01/04/2009 01:11 AM 5,791 docbookx.dtd
01/11/2009 05:09 PM 2,494 iteration1.xml
01/18/2009 02:55 PM 145 make_html.bat
01/04/2009 01:12 AM 13,150 soextblx.dtd
01/18/2009 02:55 PM 0 specs.html
11 File(s) 48,811 bytes
2 Dir(s) 28,315,365,376 bytes free
C:\java\WORKSP~1\SPECIF~1>notepad make_html.bat
C:\java\WORKSP~1\SPECIF~1>make_html.bat
C:\java\WORKSP~1\SPECIF~1>java org.apache.xalan.xslt.Process -out specs.html -in
calculator1.0.xml -xsl c:/java/docbook/docbook-xsl/docbook.xsl
(Location of error unknown)java.io.FileNotFoundException: c:\java\docbook\docboo
k-xsl\docbook.xsl (The system cannot find the file specified)
[Fatal Error] calstblx.dtd:196:38: A '(' character or an element type is require
d in the declaration of element type "entry".
file:///C:/java/WORKSP%7E1/SPECIF%7E1/calstblx.dtd; Line #196; Column #38; XSLT
Error (javax.xml.transform.TransformerConfigurationException): getAssociatedStyl
esheets failed
Exception in thread "main" java.lang.RuntimeException: getAssociatedStylesheets
failed
at org.apache.xalan.xslt.Process.doExit(Process.java:1155)
at org.apache.xalan.xslt.Process.main(Process.java:1128)
C:\java\WORKSP~1\SPECIF~1>
Thats it, no more time for this today. If anyone figures this out please reply to this.
Larry Gray
la...@ar...
________________________________
From: Larry Gray <jav...@ya...>
To: jav...@li...
Sent: Sunday, January 18, 2009 2:52:17 PM
Subject: Re: [Javacavemaps-developers] xalan-j
Ok I'm run xalanj giving it these parameters. I had found a html folder that was full of xsl files.
java org.apache.xalan.xslt.Process -out specs.html -in calculator1.0.xml -xsl c:/java/docbook/html/docbook.xsl -param use.extensions 1
I got errors and finally null pointer exception. I will try one more thing.
Larry Gray
la...@ar...
________________________________
From: Larry Gray <jav...@ya...>
To: jav...@li...
Sent: Sunday, January 18, 2009 2:32:11 PM
Subject: [Javacavemaps-developers] xalan-j
I installed xalan-j (apache.org) and set it up in my class path. Its there and working, but it didn't come with docbook xsl files or xslt files or whatever is needed. I'm hunting for those one http://www.sourceforge.net/projects/docbook downloads.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-18 20:52:22
|
Ok I'm run xalanj giving it these parameters. I had found a html folder that was full of xsl files. java org.apache.xalan.xslt.Process -out specs.html -in calculator1.0.xml -xsl c:/java/docbook/html/docbook.xsl -param use.extensions 1 I got errors and finally null pointer exception. I will try one more thing. Larry Gray la...@ar... ________________________________ From: Larry Gray <jav...@ya...> To: jav...@li... Sent: Sunday, January 18, 2009 2:32:11 PM Subject: [Javacavemaps-developers] xalan-j I installed xalan-j (apache.org) and set it up in my class path. Its there and working, but it didn't come with docbook xsl files or xslt files or whatever is needed. I'm hunting for those one http://www.sourceforge.net/projects/docbook downloads. Larry Gray la...@ar... |
|
From: Larry G. <jav...@ya...> - 2009-01-18 20:32:20
|
I installed xalan-j (apache.org) and set it up in my class path. Its there and working, but it didn't come with docbook xsl files or xslt files or whatever is needed. I'm hunting for those one http://www.sourceforge.net/projects/docbook downloads. Larry Gray la...@ar... |
|
From: Larry G. <jav...@ya...> - 2009-01-18 19:46:51
|
I'll be on irce for a few more hours after you get this message if you want to catch me live. dalnet, undernet, freenode #java, nick caverdude.
Larry Gray
la...@ar...
|
|
From: Larry G. <jav...@ya...> - 2009-01-18 14:52:52
|
https://apps.sourceforge.net/limesurvey/javacavemaps/index.php?sid=61972&lang=en I only have 3 surveys, if you have no cave/caving experience, and know nothing of caves just say 'none' and be done with it. Anway this was just a test of the survey tool Larry Gray la...@ar... |
2 messages has been excluded from this view by a project administrator.
