Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Usage clarification #46

Open
akasolace opened this issue Mar 17, 2023 · 2 comments
Open

[Question] Usage clarification #46

akasolace opened this issue Mar 17, 2023 · 2 comments

Comments

@akasolace
Copy link

Hello @govert ,

I used to have 2 folders /Documentation and /HelpContent useful for Documentation but it seems they can now be removed (at least I haven't notice any side effects). Can you confirm?

Also is there an option to have by default all functions linked to the generated help instead of having manually to put HelpTopic = XXX on each function ? I imagine by default most people want the link to work, instead we could use something like HelpTopic=None if someone wants voluntarily to break the link? What do you think? I could give it a try if you think that is a good idea ...

PS: maybe, in the documentation you could add that Summary tag accept html code ....

@govert
Copy link
Member

govert commented Mar 17, 2023

I don't know about /Documentation - I don't see it in my little test project.
I think a HelpContent folder under your project directory can override the templates and stuff, and is used when populating HelpContent in the output directory where the html and other files are written. Then these are in turn the input to compile the .chm file. So you can delete the one in the output directory it and it will be rebuilt if needed.

Generating the HelpTopic links automatically would be nice, but I'm not sure how easy it is. We need this information both at compile time, for the help file, and at runtime when registering the functions with Excel. So we need a way to remember the HelpTopic allocations that are made at compile time when the help file is built. One way would be to modify the output assembly during the ExcelDnaDoc build step, using something like Mono.Cecil to rewrite the attribute information. Another option might be to write this information to the .dna file somehow, and use at runtime. Anyway, it seems kind of tricky and needs some thought. How would you approach it? Is it worth the effort?

@akasolace
Copy link
Author

To be honest I had no idea how to approach it. I naively thought that this could be done manipulating somehow that part of the code

string helpTopic = GetField(excelFunction, "HelpTopic");

Yesterday, meanwhile I did a quick fix on my side as part of my post-build event to add all missing HelpTopic .....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants