on 7/6/01 9:53 PM, Craig R. McClanahan [EMAIL PROTECTED] wrote:
It would sure be nice to have a little HOWTO on what tags (like document
and section) Anakia recognizes, and what they do :-).
Anakia recognizes *any* tags. It is the Jakarta-Site2 module's stylesheet
which is the key. Needless
On Sat, Jul 07, 2001 at 05:11:04PM -0700, Pier Fumagalli wrote:
Quoting Aaron Bannert [EMAIL PROTECTED]:
d) jakarta-tomcat-connectors (* Pier is working on this, I've
submitted
Hold it... Pier is working on the new build for the WebApp Module, and the
documentation related to it... I
On Fri, Jul 06, 2001 at 10:06:21PM -0700, Craig R. McClanahan wrote:
* Docs should live in the source tree of the project that they
are about. Although Henri's suggestion for jakarta-tomcat-docs
is noble, what you'll find in practice is that there is very little
documentation that is
Providing Tomcat documentation in a WAR file is a little like providing
a VHS tape on how to setup your VCR. It may seem really elegant to have
on-the-fly style-generating documentation, and I may be alone on this,
but I think that the majority of the user-oriented documentation should
just
On Sat, Jul 07, 2001 at 09:25:46AM -0700, Craig R. McClanahan wrote:
Yes, we obviously need pointers in a top-level README on where the docs
went.
I'm willing to collaborate on these types of docs. On a slight tangent,
I'd like to point out that we could use more STATUS and README documents,
Quoting Aaron Bannert [EMAIL PROTECTED]:
d) jakarta-tomcat-connectors (* Pier is working on this, I've
submitted
Hold it... Pier is working on the new build for the WebApp Module, and the
documentation related to it... I never said I'm going to take care of the
documentation of all
On Fri, Jul 06, 2001 at 10:06:21PM -0700, Craig R. McClanahan wrote:
* Tomcat docs for a particular version should be delivered as one or more
web apps (not necessarily the root webapp as is current practice). That
way, the corresponding WAR files could be dropped into *any* container,
Jon Stevens wrote:
on 7/2/01 6:04 PM, Christopher Cain [EMAIL PROTECTED] wrote:
I
have no interest in Anakia, and quite frankly, as has been pointed out
very astutely by Costin, I have no interest in bothering with XML for
the purposes of documentation. I will produce HTML docs
on 7/3/01 11:50 AM, Christopher Cain [EMAIL PROTECTED] wrote:
The more (most) people have to
try and learn an extensive DTD or templating system, the less likely
they are to bother.
I agree. That is why I came up with Anakia. It is brain dead simple to use
and runs extremely quickly. The DTD
Jon Stevens wrote:
on 7/3/01 11:50 AM, Christopher Cain [EMAIL PROTECTED] wrote:
The more (most) people have to
try and learn an extensive DTD or templating system, the less likely
they are to bother.
I agree. That is why I came up with Anakia. It is brain dead simple to use
and
On Mon, 2 Jul 2001, Rob S. wrote:
1) People don't like to write docs, and for an open-source project, I'd say
that's perfectly cool so long as those same people are willing to have a
read through the docs after a major update to make sure they're coherent ;)
For ours especially, to author
I'm not sure I understand that. There are plenty of HTML editors, and 99%
of the people on this list know a bit of html. Nobody asked for good
looking documentation or cool formats, the content is missing.
Agreed, but using Note/Text/Whatever/Pad is what the majority of people end
up using
If we can't get people to write documentation in HTML using any of the
existing editors, I guess it'll be much harder to ask them to learn a
XML DTD ( especially since the dtd is used only in apache,
while the rest
of the world is using the docbook ). And of course, force them to use
notepad
At 10:09 AM -0400 7/2/01, Rob S. wrote:
1) Developers don't write them in lieu of coding.
2) Users don't read them
3...) ?
http://www.c2.com/cgi-bin/wiki has a novel way of getting at the
problem. Not a panacea obviously, but what is? The one at that
address is perl-based; I can provide a
We should try to hire some XML/XSL writers which could send us
skeleton XML and XSL ?)
Look a everyother project ( almost ) in Jakarta, a quick peek will give
a brief of what is doing people , and almost everybody is documenting
projects in xml.., doing the processing in a mix of
The Tomcat website is already generated with Anakia. It is trivial to add
more .xml files to the site and there is absolutely no excuse to not just go
that route.
I just don't see the merits of this discussion. Go write documentation
instead.
-jon
on 7/2/01 6:04 PM, Christopher Cain [EMAIL PROTECTED] wrote:
I
have no interest in Anakia, and quite frankly, as has been pointed out
very astutely by Costin, I have no interest in bothering with XML for
the purposes of documentation. I will produce HTML docs with my favorite
editor and
on 7/2/01 6:22 PM, Remy Maucherat [EMAIL PROTECTED] wrote:
I was also wondering if it would be possible to add support for new tags.
For example, tags to make it easier to write changelogs, status pages, news
pages ...
Remy
Of course.
We've started writing some new docs in XML (catalina/docs/dev/xdocs). The
HTML generation is done with XSL, but the DTD should be the same
as the one
used by Anakia.
I noticed the xdocs directory, but I didn't see anything in there. I sent
Craig an email about it a week ago, but haven't
We've started writing some new docs in XML (catalina/docs/dev/xdocs).
The
HTML generation is done with XSL, but the DTD should be the same
as the one
used by Anakia.
I noticed the xdocs directory, but I didn't see anything in there. I sent
Craig an email about it a week ago, but
Rob S. at [EMAIL PROTECTED] wrote:
This seems to be one of the questions that comes up and never gets answered
(re: docs, not Jon's behavior ;) I'm not sure what magical solution will
get people to read docs. Frankly, I'd just like to get started. Anakia
works for Jakarta, it works for
Rob S. at [EMAIL PROTECTED] wrote:
I noticed the xdocs directory, but I didn't see anything in there. I sent
Craig an email about it a week ago, but haven't heard back from him. Am I
doing something wrong? (re: CVS, not emailing Craig =)
Hmm... Craig didn't answer since he's on vacation
on 7/2/01 6:45 PM, Pier P. Fumagalli [EMAIL PROTECTED] wrote:
Anakia has been proven to be a good option when it came down to the problem
of building our website, and thank god that Jon made it... And so, by big +1
on using Anakia for our docs...
(And if something gets out in the future
Jon Stevens at [EMAIL PROTECTED] wrote:
+1 on both points. Anakia isn't gods solution yet, but it does the job just
fine for about 10 different Jakarta projects and like Pier says...if someone
comes up with a better solution tomorrow, it is easy to switch to it.
That's why I _love_ XML so
GOMEZ Henri at [EMAIL PROTECTED] wrote:
Good idea,
We could have a tomcat-doc mailing-list, but we'll still
need to commit the material.
I'd rather keep the documentation together with the project. When I
(don't :) write the docs, I don't want to update two CVSes, we can give
access to
25 matches
Mail list logo
