Hi,

I plan to commit (when my ISP get fixed) the following new page to
Quickbook docs:
http://tinyurl.com/2ll5tk

I have some question about the structure of quickbook directory:

In my local copy I have added an "extra" dir to tools/quickbook, where
is supposed to live this kind of goodies. (I think about standard
templates, but they are important enough to get a "templates" dir)

For the installation you have to copy boost_hs_quickbook.xml to your
KatePart dir. I have included this file in "extra".
I have included boost_hs_cpp.xml because it provides support for qbk
code import comments (/*<<       >>*/ are rendered in light blue for
example)

The only syntax from boost::hs left outside is boost::hs::build, I do
not know where this belongs.

The added files will be:
-------------------------------------------------------------------
extra (dir)
extra/katepart (dir)
extra/katepart/katepart.qbk
extra/katepart/install.sh
extra/katepart/readme
extra/katepart/syntax (dir)
extra/katepart/syntax/boost_hs_quickbook.xml
extra/katepart/syntax/boost_hs_cpp.xml
extra/katepart/syntax/boost_hs_boost.xml
extra/katepart/syntax/boost_hs_std.xml

doc/html/images/extra (dir)
doc/html/images/extra/katepart (dir)
doc/html/images/extra/katepart/boost.hs.logo.png
doc/html/images/extra/katepart/table.text.editor.png
doc/html/images/extra/katepart/table.boost.hs.png

Modified files:
-------------------------------------------------------------------
doc/quickbook.qbk
+ [/ KDE Support]
+ [include ../extra/katepart/katepart.qbk]

Comments are welcome
Best Regards
Matias

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Boost-docs mailing list
[email protected]
Unsubscribe and other administrative requests: 
https://lists.sourceforge.net/lists/listinfo/boost-docs

Reply via email to