Menu
▾
▴
AW: [ndoc-devel] NDoc 1.2?
|
From: <Mar...@as...> - 2003-07-01 15:55:11
|
Hi, I m new here in Ndoc development. For my own purposes I tried to extend Ndoc with some features, that are going to be implemented now (if not already done). The Help2 support is very interesting and my workarounds are no longer needed. Before ver 1.2 is released, I'd like to mention some shortcomings in = the current build (nightly build 29.6.03). 1) The namespace of the .NET SDK Framework is not the same in every = system installation. In the german version, for instance, the default VS.NET namespace of = the framework is ms-help://MS.VSCC/MS.MSDNVS.1031/cpref/html/frlrf In the new VS.NET 2003 the CollectionCenter namespace is "MS.VSCC.2003" I'd like to have the possibility to choose between the two VS.NET = versions. The language ID is already user-definable in the existing GUI. 2) There are some "missing" entries in XML islands, that normally exist = in MS Help Collections: <MSHelp:Attr Name=3D"DevLang" Value=3D"CSharp"/> <MSHelp:Attr Name=3D"DevLang" Value=3D"VB"/> <MSHelp:Attr Name=3D"TargetOS" Value=3D"Windows"/> eventually one should consider to also include <MSHelp:Attr Name=3D"DocSet" Value=3D"C#"/> this would enable using the MSDN provided filter vor "C# and related components". 3) There is a nice feature to filter certain programming languages in = MS Help Collections A small filter icon in the upper left corner enables this feature. For this to work we will need to put some tags into the html file. within the <HEAD> tag:=20 <SCRIPT SRC=3D"ms-help:/$ndoc-sdk-doc-base-url/commoner/scripts/dtuelink.js"></S= CRIPT> within the <BODY> tag: <object id=3D"obj_cook" = classid=3D"clsid:59CC0C20-679B-11D2-88BD-0800361A1803" style=3D"display:none;"></object> The corresponding XSLT files have to be modified to comply with the MS defined syntax: Some XSLT files define the language transformation with the <DIV> = instead of <PRE> tag: e.g.:=20 <PRE class=3D"syntax"><SPAN class=3D"lang">[Visual Basic] It has to be a <PRE>, otherwise it is not clearly recognized by the filtering mechanism. 4) The integration of own titles into another existing namespace (e.g. MS.VSCC) using hxreg.exe is not the best. in the current build, a new title is directly added to the master collection.=20 Preferably we should use the plugin feature of master collections and = try registering as plugin. as far as I know there is no other possibility to achive this despite = using MSI or h2reg from Helpware.net What do you think of these proposals ? regards Markus Z=E4nglein -----Urspr=FCngliche Nachricht----- Von: Jean-Claude Manoli [mailto:jc...@ma...] Gesendet: Freitag, 27. Juni 2003 03:23 An: ndo...@li... Betreff: [ndoc-devel] NDoc 1.2? I have made a few improvements to NDoc in the last two days: - Implemented option to choose the target SDK documentation version = between v1.0, v1.1 and MsdnOnline. - Added an option to exclude members with the EditorBrowsable attribute = set to EditorBrowsableState.Never. - Enhanced atribute documentation format. - Added attribute documentation to the VB syntax. I think it is about time to release a new version of NDoc that is = compatible with the .NET Framwork 1.1 and Visual Studio 2003. Don: is the HtmlHelp2 documenter ready for beta testing? Cheers, JC ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting = Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly = Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ ndoc-devel mailing list ndo...@li... https://lists.sourceforge.net/lists/listinfo/ndoc-devel |