Is there any library in preparation in boost to use tree data structures? If not, I would like to know where I can find a good implementation of any open source tree library. I found this one, but I'm not sure if it's good quality. It seems to be: http://www.aei.mpg.de/~peekas/tree/ Thanks for your time.
Le Sam 24 janvier 2009 00:27, Germán Diago a écrit :
Is there any library in preparation in boost to use tree data structures? If not, I would like to know where I can find a good implementation of any open source tree library.
why not using boost::graph ? A tree is no more than a special graph anyway ?
Le Sam 24 janvier 2009 00:27, Germán Diago a écrit :
Is there any library in preparation in boost to use tree data structures? If not, I would like to know where I can find a good implementation of any open source tree library.
why not using boost::graph ? A tree is no more than a special graph anyway ?
There's also a Google-Summer-of-Code tree library project in the sandbox, I believe it's quite advanced, but hasn't been readied for submission to Boost yet :-( John.
There's also a Google-Summer-of-Code tree library project in the sandbox, I believe it's quite advanced, but hasn't been readied for submission to Boost yet :-(
is it this? http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tree-so c2006.zip&directory=Containers& B/Rgds Max
There's also a Google-Summer-of-Code tree library project in the sandbox, I believe it's quite advanced, but hasn't been readied for submission to Boost yet :-(
is it this? http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tree-so c2006.zip&directory=Containers&
I believe it's http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tree-soc2006.zip&directory=Containers& or it's in SVN here: https://svn.boost.org/trac/boost/browser/sandbox/SOC/2006/tree Last commit was three days ago, so I suggest you contact the authors before diving in, HTH, John.
I believe it's http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tre e-soc2006.zip&directory=Containers&
or it's in SVN here: https://svn.boost.org/trac/boost/browser/sandbox/SOC/2006/tree
Last commit was three days ago, so I suggest you contact the authors before diving in,
HTH, John.
Thank you so much for your information. B/Rgds Max
I believe it's http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tre e-soc2006.zip&directory=Containers&
Thank you. I've downloaded the package from this link. But I cannot open the documentation by index.html after unzipping it. Am I missing anything? B/Rgds Max
I've built the quickbook tool and apply it to some of the qbk files of the lib. But I always get error like this: Generating Output File: tutorial.xml tutorial.qbk:36: error: Syntax Error near column 2. Thanks for any help. B/Rgds Max
I believe it's
http://www.boostpro.com/vault/index.php?action=downloadfile&filename=tre
e-soc2006.zip&directory=Containers&
Thank you. I've downloaded the package from this link. But I cannot open the documentation by index.html after unzipping it.
Am I missing anything?
B/Rgds Max
Hello, It's advertised that Quickbook is featured to create pdf document. But I could not find any introduction on this topic. Could anybody please tell me how to do? Thanks in advance. B/Rgds Max
It's advertised that Quickbook is featured to create pdf document. But I could not find any introduction on this topic. Could anybody please tell me how to do?
Once the necessary tools are set up then a : bjam pdf will build docs as a PDF. You will need to setup an FO processor first though, see https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted for some guidance. HTH, John.
Once the necessary tools are set up then a :
bjam pdf
will build docs as a PDF.
You will need to setup an FO processor first though, see https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted for some guidance.
Thank you John for your pointer. But I cannot open it with my browser, IE or Firefox. The error code given by FF is: sec_error_unknown_issuer. Perhaps the reason is lack of permission? B/Rgds Max
Thank you John for your pointer. But I cannot open it with my browser, IE or
Firefox. The error code given by FF is: sec_error_unknown_issuer.
Perhaps the reason is lack of permission?
Hmm, could be because I was logged in when I copied the URL :-( Try the same URL but with a http: rather than https: prefix. If that doesn't work there is a link from the main svn.boost.org page near the bottom, called "Getting Started with Boost Docs". What it says about PDF's though is: "First of all you will need an FO processor, there are basically only two free two choices here: * Apache FOP from http://xmlgraphics.apache.org/fop/ * XEP Personal edition from http://www.renderx.com/download/personal.html The XEP processor generally produces much better results, but inserts a small "built with XEP" advert in the footer of each page. You will also need a Java virtual machine to run the FO processor on. You will then need to edit your user-config.jam file to point to the location of the FO processor, for example: using fop : # path to invocation batch file: C:/Progra~1/RenderX/xep/xep.bat : # path to Java installation, this is ignored if you're using XEP: C:/PROGRA~1/Java/j2re1.4.2_12 ; You should now be able to build pdf docs via: bjam pdf Note: you may actually experience errors at this point if Java runs out of memory, whether or not this occurs depends on the complexity of the documentation being built and how you Java runtime is configured. One way to fix this error is to add the -Xmx option to the Java invocation command in the batch file that invokes the FO processor, for example -Xmx500m if you want to allow the FO processor to use 500MBytes of memory. " I've just realised that doesn't cover font configuration, but it should get you started. HTH, John.
Hmm, could be because I was logged in when I copied the URL :-(
Try the same URL but with a http: rather than https: prefix. If that doesn't work there is a link from the main svn.boost.org page near the bottom, called "Getting Started with Boost Docs".
Unfortunately, none of the means you mentioned works for me. :-(
What it says about PDF's though is:
-- snipped--
Quite complicated than what I anticipated. But with your detailed instruction, I hope I could get myself on the right way. IIRC, it seems not only me that are finding the pdf format boost documentation. And none of those folks seems not to have a satisfactory result at last. Is this an under-explained area of boost? I originally raised this question because I wanted to render the documentation of a single lib, such as tree-soc2006 or type_erasure, rather than the whole boost libs. Notwithstanding, I'll be extremely glad if I could get a pdf version doc as a whole. Thanks again for your help! B/Rgds Max
2009/1/28 John Maddock
Thank you John for your pointer. But I cannot open it with my browser, IE or
Firefox. The error code given by FF is: sec_error_unknown_issuer.
Perhaps the reason is lack of permission?
Actually, sec_error_unknown_issuer means the issuing CA is unknown to firefox. In this case the certificate for svn.boost.org was issued by the "Computer Science Departement Certificate Authority" of the Indiana University, and not by an 'official' CA like VeriSign. The workaround this in firefox, simply click on "Or you can add an exception…", "Add Exception...", "Get Certificate...", "Confirm Security Exception". Chris -- echo mailto: NOSPAM !#$.'<*>'|sed 's. ..'|tr "<*> !#:2" org@fr33z3
Actually, sec_error_unknown_issuer means the issuing CA is unknown to firefox. In this case the certificate for svn.boost.org was issued by the "Computer Science Departement Certificate Authority" of the Indiana University, and not by an 'official' CA like VeriSign.
The workaround this in firefox, simply click on "Or you can add an exception…", "Add Exception...", "Get Certificate...", "Confirm Security Exception".
Chris
Get it! Thank you for pointing this out. B/Rgds Max
What it says about PDF's though is:
"First of all you will need an FO processor, there are basically only two free two choices here:
* Apache FOP from http://xmlgraphics.apache.org/fop/ * XEP Personal edition from http://www.renderx.com/download/personal.html
The XEP processor generally produces much better results, but inserts a small "built with XEP" advert in the footer of each page. You will also need a Java virtual machine to run the FO processor on.
I've seen the RenderX's footer in other pdf doc's before. I've downloaded the XEP Personal edition and installed successfully.
You will then need to edit your user-config.jam file to point to the
location of the
FO processor, for example:
using fop : # path to invocation batch file: C:/Progra~1/RenderX/xep/xep.bat
I've changed this line to correspond to my settings: D:/Program Files/RenderX/XEP/xep.bat
: # path to Java installation, this is ignored if you're using XEP: C:/PROGRA~1/Java/j2re1.4.2_12 ;
I've added the am lines at the end of the, virtually blank, tools/build/v2/user-config.jam file. And then I invoke bjam pdf but I got nothing except an error: error: Unknown target type FO and other semmingly useless message. More help still needed. Thanks in advance. B/Rgds Max P.S. repeat the segment I added to the jam file as follows: using fop : # path to invocation batch file: D:/Program Files/RenderX/XEP/xep.bat : # path to Java installation, this is ignored if you're using XEP: C:/PROGRA~1/Java/j2re1.4.2_12 ;
What it says about PDF's though is:
"First of all you will need an FO processor, there are basically only two free two choices here:
* Apache FOP from http://xmlgraphics.apache.org/fop/ * XEP Personal edition from http://www.renderx.com/download/personal.html
The XEP processor generally produces much better results, but inserts a small "built with XEP" advert in the footer of each page. You will also need a Java virtual machine to run the FO processor on.
I've seen the RenderX's footer in other pdf doc's before. I've downloaded the XEP Personal edition and installed successfully.
You will then need to edit your user-config.jam file to point to the
location of the
FO processor, for example:
using fop : # path to invocation batch file: C:/Progra~1/RenderX/xep/xep.bat
I've changed this line to correspond to my settings: D:/Program Files/RenderX/XEP/xep.bat
: # path to Java installation, this is ignored if you're using XEP: C:/PROGRA~1/Java/j2re1.4.2_12 ;
I've added the am lines at the end of the, virtually blank, tools/build/v2/user-config.jam file. And then I invoke
bjam pdf
but I got nothing except an error:
error: Unknown target type FO
and other semmingly useless message.
More help still needed. Thanks in advance.
Hmmm, did you configure quickbook and docbook in the user-config.jam as well? If not I'll refer you back to the Wiki page ;-) BTW, building boost documentation like this is really only designed for Boost's authors and maintainers, it's not intended that end-users should have to set up such a long toolchain unless they really want to! Regards, John.
Hmmm, did you configure quickbook and docbook in the user-config.jam as
well?
If not I'll refer you back to the Wiki page ;-)
BTW, building boost documentation like this is really only designed for Boost's authors and maintainers, it's not intended that end-users should have to set up such a long toolchain unless they really want to!
Regards, John.
Facing 'such a long toolchain', I was wandering why there's such a grey corner in the boost world. :-) And, meanwhile, I'm humble with lack of the experience of doc-making. Hearing what you've said, I feel now much more relaxed. :-) I have experience of Doxygen, Ghostscript(a long time ago), am aware of that MikTeX is an implementaion of the famous system LaTEX by Knuth (or I'm wrong?). But I'm quite unfamilar with other stuffs, such as XSL style sheete, DocBook DTD, Iconv, libXslt, and so much. Perhaps finally I want to make clear that what raw materials, say scripts in code or elsewhere, through what workflow, are rendered to become a pdf file. Thanks for your help. And one more question: Is it possible to make _one_ pdf doc file for all of the boost packages by one run? yes or no? :-) B/Rgds Max
Facing 'such a long toolchain', I was wandering why there's such a grey corner in the boost world. :-) And, meanwhile, I'm humble with lack of the experience of doc-making.
Hearing what you've said, I feel now much more relaxed. :-)
I have experience of Doxygen, Ghostscript(a long time ago), am aware of that MikTeX is an implementaion of the famous system LaTEX by Knuth (or I'm wrong?). But I'm quite unfamilar with other stuffs, such as XSL style sheete, DocBook DTD, Iconv, libXslt, and so much.
Perhaps finally I want to make clear that what raw materials, say scripts in code or elsewhere, through what workflow, are rendered to become a pdf file.
The transforms are: quickbook -> BoostBook XML Doxygen -> Doxygen XML -> BoostBookXML BoostBook XML -> Docbook XML DocBook XML -> HTML DocBook XML -> FO XML -> PDF or PS
Thanks for your help. And one more question: Is it possible to make _one_ pdf doc file for all of the boost packages by one run? yes or no? :-)
Well if you want it in black and white like that, then no :-( In any case it's unlikely that a build of everything is what you really want: it would be one huge PDF!!! To build a PDF for library X, then cd into libs/X/doc and do a: bjam pdf start with something small and easy like static_assert, or else there's a "test everything" project in doc/test. Also note that not all Boost libraries are documented with quickbook/boostbook/docbook so your mileage may vary. John.
Facing 'such a long toolchain', I was wandering why there's such a grey corner in the boost world. :-) And, meanwhile, I'm humble with lack of the experience of doc-making.
Hearing what you've said, I feel now much more relaxed. :-)
I have experience of Doxygen, Ghostscript(a long time ago), am aware of that MikTeX is an implementaion of the famous system LaTEX by Knuth (or I'm wrong?). But I'm quite unfamilar with other stuffs, such as XSL style sheete, DocBook DTD, Iconv, libXslt, and so much.
Perhaps finally I want to make clear that what raw materials, say scripts in code or elsewhere, through what workflow, are rendered to become a pdf file.
The transforms are:
quickbook -> BoostBook XML Doxygen -> Doxygen XML -> BoostBookXML
BoostBook XML -> Docbook XML
DocBook XML -> HTML DocBook XML -> FO XML -> PDF or PS
It's a big step for me to get this, to depict some of the basic conceptions in my mind. Thanks.
Thanks for your help. And one more question: Is it possible to make _one_ pdf doc file for all of the boost packages by one run? yes or no? :-)
Well if you want it in black and white like that, then no :-(
Haha... :-)
In any case it's unlikely that a build of everything is what you really want: it would be one huge PDF!!!
IMO, that should not be a problem - for example, the doc of pdf format of the CGAL libs is about 3,000 pages. One doc as a whole will facilitate easy seaching of contents of interest. I prefer pdf format, it makes user able to markup.
To build a PDF for library X, then cd into libs/X/doc
I'm not aware of this before. That's why I was bjam'ing in the boost root folder and could not get the desired result. This time I select the ASIO for a trial. Things seems to work well and at last I get " ... updated 187 targets..." I noticed that there created a new html folder under the asio/doc folder, and the boost_1_37_0/bin/v2 also appears, but I just could not find the pdf doc file. Am I still missing anything?
and do a:
bjam pdf
start with something small and easy like static_assert, or else there's a
"test
everything" project in doc/test.
Also note that not all Boost libraries are documented with quickbook/boostbook/docbook so your mileage may vary.
Yes, this is a problem that I might be aware before. But is there a plan to impose more restrict/unified requirements on coding/docing of the libs? With it, more uniform appearance/feeling, as well as higher managability and lower learning curve for user will be colser, I guess. B/Rgds Max
To build a PDF for library X, then cd into libs/X/doc
I'm not aware of this before. That's why I was bjam'ing in the boost root folder and could not get the desired result.
This time I select the ASIO for a trial. Things seems to work well and at last I get " ... updated 187 targets..."
I noticed that there created a new html folder under the asio/doc folder, and the boost_1_37_0/bin/v2 also appears, but I just could not find the pdf doc file. Am I still missing anything?
If you do: bjam or bjam html then you get html docs under ./html, you need to do a bjam pdf to get a pdf, and it will be located in a deep subdirectory of the bin.v2 path (look at the final output messages from the FO processor to see exactly where). I realise this ideal, it's possible to modify the Jamfile to automatically copy the pdf into the current directory, but we haven't got that properly organised yet :-(
and do a:
bjam pdf
start with something small and easy like static_assert, or else there's a "test everything" project in doc/test.
Also note that not all Boost libraries are documented with quickbook/boostbook/docbook so your mileage may vary.
Yes, this is a problem that I might be aware before. But is there a plan to impose more restrict/unified requirements on coding/docing of the libs? With it, more uniform appearance/feeling, as well as higher managability and lower learning curve for user will be colser, I guess.
I don't think we'll do that, we just don't want to impose such a long and fragile toolchain on people at present (although most new submissions *are* using quickbook which is good to see). I guess if the tools improve we *might* revisit that, HTH, John.
I'm not aware of this before. That's why I was bjam'ing in the boost root folder and could not get the desired result.
This time I select the ASIO for a trial. Things seems to work well and at last I get " ... updated 187 targets..."
I noticed that there created a new html folder under the asio/doc folder, and the boost_1_37_0/bin/v2 also appears, but I just could not find the pdf doc file. Am I still missing anything?
If you do:
bjam
or
bjam html
then you get html docs under ./html, you need to do a
bjam pdf
to get a pdf, and it will be located in a deep subdirectory of the bin.v2 path (look at the final output messages from the FO processor to see exactly where).
I realise this ideal, it's possible to modify the Jamfile to automatically copy the pdf into the current directory, but we haven't got that properly organised yet :-(
It's not a big problem, or even a problem. But it'd be better if improved as you said.
Yes, this is a problem that I might be aware before. But is there a plan to impose more restrict/unified requirements on coding/docing of the libs? With it, more uniform appearance/feeling, as well as higher managability and lower learning curve for user will be closer, I guess.
I don't think we'll do that, we just don't want to impose such a long and fragile toolchain on people at present (although most new submissions *are* using quickbook which is good to see). I guess if the tools improve we *might* revisit that,
I look forward to the tools' getting improved and to that revisit. :-) Thanks, John. Your advices have been very fruitful. B/Rgds Max
Following the instructions on https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted I've finished all of the configuration works, including - creating boost-tools folder and child /bin, /xml folders; - unzipping relevant packages into the corresponding folders; - installing Doxygen, Ghostscript, and MikTeX; - adding a new user-fonfig.jam in a searchable folder; When I ran the command 'bjam bdf' under the <BOOSTROOT> folder I get the following message: notice: could not find main target pdf ... don't know how to make <e>pdf ... More help needed. Thanks. I'm afraid I lack some of the basic conceptions of boost doc-making, if so, any explanations for newbie at this are are welcome. B/Rgds Max
Note: you may actually experience errors at this point if Java runs out of memory, whether or not this occurs depends on the complexity of the documentation being built and how you Java runtime is configured. One way to fix this error is to add the -Xmx option to the Java invocation command in the batch file that invokes the FO processor, for example -Xmx500m if you want to allow the FO processor to use 500MBytes of memory. "
It seems that I'm one step to my goal. I get a 0-byte pdf file named standalone_doc for ASIO - your predicition comes true. But I cannot figure out where the batch file is located.
I've just realised that doesn't cover font configuration, but it should get you started.
Please elaborate, bacause now I'm close to this point. :-) Thanks B/Rgds Max
Note: you may actually experience errors at this point if Java runs out of memory, whether or not this occurs depends on the complexity of the documentation being built and how you Java runtime is configured. One way to fix this error is to add the -Xmx option to the Java invocation command in the batch file that invokes the FO processor, for example -Xmx500m if you want to allow the FO processor to use 500MBytes of memory. "
It seems that I'm one step to my goal. I get a 0-byte pdf file named standalone_doc for ASIO - your predicition comes true. But I cannot figure out where the batch file is located.
In the directory where the FO processor is installed.
I've just realised that doesn't cover font configuration, but it should get you started.
Please elaborate, bacause now I'm close to this point. :-)
Well hopefully unless you are embedding SVG images in the PDF (for example from Boost.Math) then you shouldn't need to configure any additional fonts just yet. John.
It seems that I'm one step to my goal. I get a 0-byte pdf file named standalone_doc for ASIO - your predicition comes true. But I cannot figure out where the batch file is located.
In the directory where the FO processor is installed.
Thank you, John. I finally screwed it up. But, still taking ASIO as example, I found some should-be-there figure in the document is missing and appear as a placeholder that is seen on a webpage where a link to image bacomes unavailable.
Please elaborate, bacause now I'm close to this point. :-)
Well hopefully unless you are embedding SVG images in the PDF (for example from Boost.Math) then you shouldn't need to configure any additional fonts just yet.
:-) B/Rgds Max
I finally screwed it up. But, still taking ASIO as example, I found some should-be-there figure in the document is missing and appear as a placeholder that is seen on a webpage where a link to image bacomes unavailable.
Ah :-( That requires editing the Jamfile to fix, so that the FO procesor can locate the path to the images, another one "todo" I guess, John.
I finally screwed it up. But, still taking ASIO as example, I found some should-be-there figure in the document is missing and appear as a placeholder that is seen on a webpage where a link to image bacomes unavailable.
Ah :-(
That requires editing the Jamfile to fix, so that the FO procesor can locate the path to the images, another one "todo" I guess,
John.
Should this "todo" get a higher priority? :-) Is it possible for me to get it done? Thanks for you continuous help. It's really a tough but happy journey for me. B/Rgds Max
That requires editing the Jamfile to fix, so that the FO procesor can locate the path to the images, another one "todo" I guess,
John.
Should this "todo" get a higher priority? :-) Is it possible for me to get it done? Thanks for you continuous help. It's really a tough but happy journey for me.
Up until now it's been up to individual library authors to fix up Jamfiles for PDF generation if that's something that they're interested in. One of my long standing TODO's has been to produce a central "build all the docs as individual PDF's" Jamfile so we can automatically turn out PDF's with each release. If you want to try and fix this yourself, then take a look at the changes I added to the Boost.Units Jamfile recently to support better PDF building: https://svn.boost.org/trac/boost/changeset/49620/trunk/libs/units/doc/Jamfil... John.
Up until now it's been up to individual library authors to fix up Jamfiles for PDF generation if that's something that they're interested in. One of my long standing TODO's has been to produce a central "build all the docs as individual PDF's" Jamfile so we can automatically turn out PDF's with each release. If you want to try and fix this yourself, then take a look at the changes I added to the Boost.Units Jamfile recently to support better PDF building:
https://svn.boost.org/trac/boost/changeset/49620/trunk/libs/units/doc/Jamfil
e.v2
More questions: Q1: Should the workflow be so complicated? Is it possible to get simpler? Q2: I have installed/configured the following stuff: -MikTeX -Doxygen -RenderX XEP -Ghostscript -DocBook-xml -DocBook-xsl -iconv -libxml -libxslt -xsldbg -zlib Are they all must-have's? What are they all really for? Thanks. B/Rgds Max
Q1: Should the workflow be so complicated? Is it possible to get simpler?
No, and don't know :-(
Q2: I have installed/configured the following stuff:
-MikTeX -Doxygen -RenderX XEP -Ghostscript -DocBook-xml -DocBook-xsl -iconv -libxml -libxslt -xsldbg -zlib
Are they all must-have's? What are they all really for?
I added a diagram to the wiki yesterday that shows the workflow: https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted, xsltproc is the main culprit becuase there's no easy installer for it on windows - you have to download all the libraries it depends on separately :-( Of course most Linux boxes have all this stuff by default... HTH, John.
Q1: Should the workflow be so complicated? Is it possible to get simpler?
No, and don't know :-(
Bad news. :-)
Q2: I have installed/configured the following stuff:
-MikTeX -Doxygen -RenderX XEP -Ghostscript -DocBook-xml -DocBook-xsl -iconv -libxml -libxslt -xsldbg -zlib
Are they all must-have's? What are they all really for?
I added a diagram to the wiki yesterday that shows the workflow: https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted, xsltproc is the main culprit becuase there's no easy installer for it on windows - you have to download all the libraries it depends on separately :-(
Of course most Linux boxes have all this stuff by default...
As I'm using WinXP, so I don't have that luck. So do all other Windows users. Is it possible to collect all the stuff somewhere in the boost package and add a simple tool that can deploy all of them automatically or semi-automatically? Anyway, the diagram is a great step forward, at least for me. Without it, all of the *Book stuff is a mess in my mind. :-) Thanks again. B/Rgds Max
I added a diagram to the wiki yesterday that shows the workflow: https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted, xsltproc is the main culprit becuase there's no easy installer for it on windows - you have to download all the libraries it depends on separately :-(
More questions on the diagram/wiki page: Q1: It seems that Inkscape and SVG Math in the diagram are needed to get the pictures in doc appear? If yes, why are they not included in the list as given in the wiki page? Q2: It's said by the page: <Quote> (Don't use version 2.6.32+ of libxml2, there's a bug which breaks doxygen import, 2.6.30 works. Version 2.7.x seems to work OK too, so maybe just use the latest versions again now?) <UnQuote> I'm using 2.7.2 for windows, and there seems not to be any problem. Does this imply that it could be change to: (Don't use version 2.6.32+ of libxml2, there's a bug which breaks doxygen import. Use the latest version.) or even have it deleted? Thanks for your efforts. B/Rgds Max
I added a diagram to the wiki yesterday that shows the workflow: https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted, xsltproc is the main culprit becuase there's no easy installer for it on windows - you have to download all the libraries it depends on separately :-(
More questions on the diagram/wiki page:
Q1: It seems that Inkscape and SVG Math in the diagram are needed to get the pictures in doc appear? If yes, why are they not included in the list as given in the wiki page?
Currently they're only used by Boost.Math for equations, and the png's and svg's are in SVN so these tools aren't needed except by that libraries authors (or possibly some other new library wanting MathML equations). I'll try and think of a way to make that clearer, or else just remove that "branch".
Q2: It's said by the page:
<Quote> (Don't use version 2.6.32+ of libxml2, there's a bug which breaks doxygen import, 2.6.30 works. Version 2.7.x seems to work OK too, so maybe just use the latest versions again now?) <UnQuote>
I'm using 2.7.2 for windows, and there seems not to be any problem. Does this imply that it could be change to:
(Don't use version 2.6.32+ of libxml2, there's a bug which breaks doxygen import. Use the latest version.)
or even have it deleted?
Maybe: the bug report is still open, and I don't know enough about the issue to tell whether it's been accidently fixed in the latest version, Daniel do you know about this? John.
2009/1/30 John Maddock
Maybe: the bug report is still open, and I don't know enough about the issue to tell whether it's been accidently fixed in the latest version, Daniel do you know about this?
It think it's fixed now, if the doxygen import is working okay then the note can be deleted. Daniel
Maybe: the bug report is still open, and I don't know enough about the issue to tell whether it's been accidently fixed in the latest version, Daniel do you know about this?
It think it's fixed now, if the doxygen import is working okay then the note can be deleted.
OK, deleted, also revised the diagram and added some extra links to useful reference material. John.
Maybe: the bug report is still open, and I don't know enough about the
issue
to tell whether it's been accidently fixed in the latest version, Daniel do you know about this?
It think it's fixed now, if the doxygen import is working okay then the note can be deleted.
Daniel
I agree with John (that doesn't mean I disagree with Daniel though). We should know wheather the bug is accidentally or intentionally fixed. We should take this mater deterministicly. I'm not sure what doxygen import means, and don't know what the buggy version behaves like. What I mean is that I don't want to mislead any of you, and would like the note to be there if we could not get the matter clear _definitely_. B/Rgds Max
Hello all, I've found this link while surfing, which may be of help to folks like me. :-) DocBook XSL: The Complete Guide http://www.sagehill.net/docbookxsl/index.html B/Rgds Max
That requires editing the Jamfile to fix, so that the FO procesor can locate the path to the images, another one "todo" I guess,
John.
Should this "todo" get a higher priority? :-) Is it possible for me to get it done? Thanks for you continuous help. It's really a tough but happy journey for me.
Up until now it's been up to individual library authors to fix up Jamfiles for PDF generation if that's something that they're interested in. One of my long standing TODO's has been to produce a central "build all the docs as individual PDF's" Jamfile so we can automatically turn out PDF's with each release. If you want to try and fix this yourself, then take a look at the changes I added to the Boost.Units Jamfile recently to support better PDF building:
https://svn.boost.org/trac/boost/changeset/49620/trunk/libs/units/doc/Jamfil
e.v2
Thanks. I'll have a look and give a try sometime. You are right, comparing with modifying individual jam files for corresponding libs, it's much better and more logical to do the same work with a central one as you said. I look forward to having it early. :-) B/Rgds Max
More specifically, I'm trying to translate the qbk format doc of tree-soc2006 into any other format, say html or pdf, that I'm familiar with. But a single quickbook tree.qbk doesn't work as expected. The output I got is: Generating Output File: tree.xml tree.qbk:43: warning: in column:75, [br] and \n are deprecated. tree.qbk:43: warning: in column:77, [br] and \n are deprecated. tree.qbk:41: error: Syntax Error near column 5. Thanks for any information. B/Rgds Max
Once the necessary tools are set up then a :
bjam pdf
will build docs as a PDF.
You will need to setup an FO processor first though, see https://svn.boost.org/trac/boost/wiki/BoostDocs/GettingStarted for some guidance.
Thank you John for your pointer. But I cannot open it with my browser, IE or Firefox. The error code given by FF is: sec_error_unknown_issuer.
Perhaps the reason is lack of permission?
B/Rgds Max
More specifically, I'm trying to translate the qbk format doc of tree-soc2006 into any other format, say html or pdf, that I'm familiar with.
But a single
quickbook tree.qbk
doesn't work as expected.
For me neither, your best bet is to contact the authors, John.
More specifically, I'm trying to translate the qbk format doc of tree-soc2006 into any other format, say html or pdf, that I'm familiar with.
But a single
quickbook tree.qbk
doesn't work as expected.
For me neither, your best bet is to contact the authors,
It sounds like that I was not doing anything wrong, instead, it's the lib author's fault. :-) But I got the similar message while I was processing the qbk file that comes with the type_erasure lib written by Steven Watanabe, which I downloaded from boost vault. I hope Steven is now in front of his computer and could tell me what I should do. :-) Thanks, John, and Steven, as always. B/Rgds Max
AMDG Max wrote:
It sounds like that I was not doing anything wrong, instead, it's the lib author's fault. :-)
But I got the similar message while I was processing the qbk file that comes with the type_erasure lib written by Steven Watanabe, which I downloaded from boost vault.
I hope Steven is now in front of his computer and could tell me what I should do. :-)
This is most likely caused by a backwards incompatible change in quickbook. As I recall, though the type_erasure documentation is extremely lacking, so it may not help you much.
Thanks, John, and Steven, as always.
In Christ, Steven Watanabe
why not using boost::graph ? A tree is no more than a special graph anyway ?
Because the graph interface isn't as expressive as a native tree library?
There's also a Google-Summer-of-Code tree library project in the sandbox, I believe it's quite advanced, but hasn't been readied for submission to Boost yet :-(
It looks like it was turned into a TR2 proposal. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2101.html Andrew Sutton andrew.n.sutton@gmail.com
joel falcou wrote:
why not using boost::graph ? A tree is no more than a special graph anyway ?
Are you sure? The original poster seems to have a "rooted tree" in mind, which is a special "directed acyclic graph" (DAG). I just looked at the TOC of the boost::graph documentation, and the only DAG algorithm I could find was "topological_sort". There is also the transitive_closure algorithm, which could be used to compute the "partial order" relation of the DAG, but I'm not sure whether this is really the appropriate way to compute the "partial order" relation of a DAG (because the number of edges could increase to O(V^2) and DAG's are not mentioned in the corresponding documentation). So I have the impression that DAG's and (rooted) trees are not really the main target applications of boost::graph. Regards, Thomas
second
joel falcou wrote:
why not using boost::graph ? A tree is no more than a special graph anyway ?
Are you sure? The original poster seems to have a "rooted tree" in mind,
is a special "directed acyclic graph" (DAG). I just looked at the TOC of
boost::graph documentation, and the only DAG algorithm I could find was "topological_sort". There is also the transitive_closure algorithm, which could be used to compute the "partial order" relation of the DAG, but I'm not sure whether this is really the appropriate way to compute the "partial order" relation of a DAG (because the number of edges could increase to O(V^2) and DAG's are not mentioned in the corresponding documentation).
So I have the impression that DAG's and (rooted) trees are not really the
which the main
target applications of boost::graph.
Regards, Thomas
Is there any library in preparation in boost to use tree data structures? If not, I would like to know where I can find a good implementation of any open source tree library. I found this one, but I'm not sure if it's good quality. It seems to be:
It seems to be quite straightforward and easy to use, as far as its interface is concerned. B/Rgds Max
On Sat, 24 Jan 2009 00:27:33 +0100, Germán Diago
Is there any library in preparation in boost to use tree data structures?
There is Boost.PropertyTree in the vault (look for property_tree_rev5.zip at http://www.boostpro.com/vault/). This library has been around for quite some time. I can't remember though if it was officially accepted. Boris
[...]
There is Boost.PropertyTree in the vault (look for property_tree_rev5.zip at http://www.boostpro.com/vault/). This library has been around for quite some time. I can't remember though if it was officially accepted.
Boris
Yes, this is a tree lib, but it's not only a tree lib, but also a _property_ tree lib. What I mean is the extra space needed to store the property information is probably not desired by the users that are looking for just a _tree_lib. :-) Thanks for your information. B/Rgds Max
participants (10)
-
Andrew Sutton -
Boris Schaeling -
Christoph Gysin -
Daniel James -
Germán Diago -
joel falcou -
John Maddock -
Max -
Steven Watanabe -
Thomas Klimpel