I have been looking for a library that will expose functionality to allow me to generate CHM files. As far as I can tell, that does not exist and I will have to rely on CHMBuilder (in SandCastle) but I thought I would ask before going that route.
Microsoft HTML Help SDK
http://msdn.microsoft.com/en-us/library/ms670169(VS.85).aspx
There is a lib, and a (cross-platfomr) commandtool in Free Pascal. It is in Pascal (Delphi dialect) though.
Related
I am trying to use Zorba XQuery parser with C++ for my project. I have downloaded and installed Zorba, but I can't seem to find a way to use it in my C++ programs. The documentation doesn't say a word. So if anyone here is good with it, can you please provide me your two cents?
Thank you
You can find examples at their Website
The general way to use an external library is to include its headers into your sourcefiles and add include its library in your link-step.
A C++ (native) application I'm working on uses a COM interface for its modules.
In the .odl file there are tonnes of documentation providing information outlining the function/parameters, etc..
Between the typelib generation, and subsequent tlbimp.exe importation; the interop assembly I get back to use in .NET includes only the function/interface names and a list of their parameters and types.
I'm wondering if there is any way (format documentation in a specific way / third party applications / parameters for tlbimp.exe / ???) that I could transfer this documentation across so that it appears in the Visual Studio object browser, or even better, the .NET intellisense.
Thanks,
You author auto-completion help for a COM automation component with the [helpstring] attribute in the IDL file. Unfortunately Tlbimp.exe does not support that, there is no mechanism in .NET to embed help text inside an assembly. .NET IntelliSense use .xml files, they are normally auto-generated from the source code with the /doc compiler option. They are much easier to localize.
While it sounds feasible to auto-generate the .xml file from the type library, I don't know anybody that has tackled this yet. A starting point would be the managed tlbimp project located here.
somewhere, I found a simple source to read something, and that source includes
"PkunZip.cpp" and "Pkunzip.h" to read zip-file.
However, I could not find the website about PkunZip.cpp ( sourceforge or codeproject etc ).
where can I find the website that describe 'pkunzip.cpp' and a manual about it?
If you search google for either of these files nothing is returned. That is a pretty bad sign. If you need code to handle zip archives, I have used libarchive in the past with great success. Their website has great documentation and the code is cross platform (Windows, *BSD, Linux, etc).
You should be able to replace any missing functionality with libarchive.
The standard way of reading zip files is zlib, or considering you tagged c++, the zipios. But if you want your particular files, have you tried Google Codesearch?
I'm a total noob when it comes to linking and building with Visual Studio. I would like to integrate Lua into my C++ console application.
Can someone give a step by step on how to do this from getting the Lua dependencies from lua.org, to actually running a "Hello World from Lua" in VS, and all the steps in between.
Finding something like this online has been very difficult since most require prerequisite knowledge of building Lua and such.
Thanks :)
Start with the Lua for Windows package. It will get you a self-contained batteries included Lua installation. Lua for Windows is not an official distribution, but it is well respected by the Lua user community. You can use its lua.exe to gain experience with the language in a Windows environment, and its rich collection of tested extension modules is also available for use.
If you add its include and lib folders to your VS project configuration, you should be able to compile and link against Lua in short order.
One possible complication is that the LfW distribution is built against VC8's C runtime library. If that becomes a problem, then you can either compile Lua yourself as part of your Solution, or get a known good DLL that matches your specific version of Visual Studio from the Lua Binaries project.
Do remember that if you are using one of the distributed DLLs, it will have been compiled as C, and not C++. That means that you must wrap any references to the Lua include files in extern "C" {...} or you will have problems with linkage.
It really helps to have some experience with VS project configuration and building. In particular, experience with mixing C and C++ in a VS project is very helpful.
I heartily recommend following the advice already given about learning C and C++ and mixing the two together. Once you have that under your belt, you may want to check out LuaBind or LuaPlus for connecting C++ and Lua. You can do it manually (and you probably should, at first, to understand what's going on under the hood), but it's more efficient and cleaner, code-wise, to use one of those binding libraries. For debugging purposes, Decoda is a good choice; it can attach to processes started in VS which contain Lua code you want to check.
In stackoverflow.com I have found a question where a user was suggesting to use this libraries of KDE in order to export-inport RTF files. But, when I downloaded I saw that there are lot of files that are included in the .cc and .h files that are missing. So please give a hint how to download all necessary files and is there any guide that gives and example how to use the RTF exporting example(or instructions)?
BTW if you have ever done RTF exporting programmatically in a better way, please tell me how I can do that.
First off, as you mention, that code is part of the KDE project. Its code base is very large, so in the worst case you'd have to provide most of kdebase-dev. The following link contains a tutorial for building KWord from SVN, which will pull in all the dependencies you need (then you can start deleting them as you find they aren't relevant):
http://wiki.koffice.org/index.php?title=Build_KOffice
Browsing the sources, I note a few things.
The #includes pretty much just reference QObjects, so be sure that Qt is installed.
The RTF classes you're looking for seem to subclass KDE objects. This means you may have to go through significant work to separate the base code from KDE if you can't have KDE as a dependency for your project.
edit: Looks like you could probably pull much of the algorithm from ExportFilter.cc, for example, and modify it to your needs. Looks like much of the work is being done via QString rather than KDE methonds.