Sorry but i didn't answer your question (I would like the Fossil wiki
to host at least a link to the local files
$basedir/api/index.htm?...just cannot get things working.) 

. I assume
you have this directory structure 

        * fossilckout 

        * doc 

        * html


        * src

Your Doxyfile in fossilckout/src has set
HTML_OUTPUT=../DOC/HTML . Document the source and run doxygen. Then
FOSSIL UI. Type the following url
HTTP://LOCALHOST:8080/DOC/CKOUT/DOC/HTML/INDEX.HTML. And you see the
doxygen generate html. Unfortunate you "lost" fossil. YOU HAVE TO GO
BACK IN HISTORY OR TYPE HTTP://LOCALHOST:8080/ TO GO BACK TO FOSSIL.


This is on the CHECKOUT SOURCES. If you would want to serve the
documentation from your repository you need to check in
fossilckout/doc/html/*. I think that is not what you want because the
documentation can be produced by running doxygen so there is no need to
put it in the repository.  

I tried the html way but there is no way I
can get doxygen to play nice with fossil. 

On Thu, 14 Oct 2010 09:54:38
+0200, Rene  wrote:  

On Wed, 13 Oct 2010 17:44:15 -0500, Bruce
Chidester wrote:  

What is the best way to incorporate documentation
generate by your project, like with doxygen into (or link from) the
Fossil wiki? 
I would like the Fossil wiki to host at least a link to
the local files $basedir/api/index.htm?...just cannot get things
working. 
Thanks, 
Bruce Chidester  

If documentation is to integrate
with fossill it needs to be able to generate nowiki pages. 

e.g. native
html is 

[optional javascript] 

CONTENT 

nowiki is 

CONTENT


Docbook and Lyx can be easily made to work in nowiki mode. 

Doxygen
can not be integrated with fossil because it is using javascript in its
user interface. e.g. In 

the CONTENT there are javascript and input
elements. That doesn't play nice with fossil. 

You might get away with
html. I have to try that at home. If you need instructions for docbook
and/or lyx let me know. 

-- 
Rene

-- 
Rene

20 MOST RECENT TIMELINE
ITEMS

2010-09-19  

                16:51

                 [8d79764675] [1] Leaf: Update HOT
README about when single-page vacuums happen. (user: momjian, tags:
trunk)

                15:27

                 [ec862ced60] [2] Replace last remaining $Id$ with
$PostgreSQL$. (user: tgl, tags: trunk)

                15:17

                 [391f443956] [3]
Fix several broken $PostgreSQL$ keywords. Noted while experimenting with
Magnus's script to remove these. (user: tgl, tags: trunk)

2010-09-18 


                19:10

                 [85e16d9f87] [4] Make sure we wait for protocol-level
EOF when ending binary COPY IN. The previous coding just terminated the
COPY immediately after seeing the EOF marker (-1 where a row field count
is expected). The expected CopyDone or CopyFail message just got thrown
away later, since we weren't in COPY mode anymore. This behavior
complicated matters for the JDBC driver, and arguably was the wrong
thing in any case since a CopyFail message after the marker wouldn't be
honored. Note that there is a behavioral change here: extra data after
the EOF marker was silently ignored before, but now it will cause an
error. Hence not back-patching, although this is arguably a bug. Per
report and patch by Kris Jurka. (user: tgl, tags: trunk)

                17:37

                
[cae7a33e87] [5] Give a suitable HINT when an INSERT's data source is a
RowExpr containing the same number of columns expected by the insert.
This suggests that there were extra parentheses that converted the
intended column list into a row expression. Original patch by Marko
Tiikkaja, rather heavily editorialized by me. (user: tgl, tags: trunk)




Links:
------
[1] http://localhost:8080/info/8d79764675
[2]
http://localhost:8080/info/ec862ced60
[3]
http://localhost:8080/info/391f443956
[4]
http://localhost:8080/info/85e16d9f87
[5]
http://localhost:8080/info/cae7a33e87
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to