@kbar Thank you very much for your great work, because C++ development documentation has long lacked user education, and .XDL64 files cannot be generated smoothly even for novices who have the source files.You are really great to replace the SDK-team to complete the user education.
Before you posted the video, many people posted C++ development videos for C4D, but after version R19, the API interface parameters changed, and these videos lost their user education significance.Thank you for your contribution to making more people learn how to generate .XDL64 files. This is the first and most important first step.
@ferdinand Generating the .XDL64 file is the most important first step, but in the C++ development documentation, the Project Tool chapter is very professional and prevents novices from properly generating the .XDL64 file.
Suggest additional development steps, such as 1,2,3,.....
1: Download the Project Tool.
2: Create a new .TXT file and write it to ......\cinema4d_r23_project_tool_314356_win-macos\kernel_app_64bit.exe g_updateproject=......
3: .TXT file format changed to.bat.
edit: This topic has been forked from C++ Plugin Development Tutorials [Ferdinand]
excuse my late reply. But our answer remains the same, we can give no guarantee that we will do this immediately and it is rather unlikely that we will do it. The reason being, that the information is already there, mostly in Getting Started: Introduction, it just happens to be in a slightly inconvenient form. And doing it here in the forum instead of the documentation would not be an improvement, especially if it is meant to be "detailed", as we then would do work that is not integrated with the document space users usually use to learn about concepts in the SDK, the SDK documentation hosted on develeoprs.maxon.net. As most people and companies, we have to plan where we invest our time best. And writing and maintaining the SDK documentation is only a part of our tasks. Which is why we did decide against doing it right now.
Thank you for your understanding,
thank you for reaching out to us. I did not fork your posting, but please keep things on topic here. It would be rather disrespectful towards @kbar and his tutorial-work if this would be repurposed as a general issues of the C++ documentation topic.
With that being said, we (at least some of us) agree with your sentiment to some extent. While the information you are requesting is already there, split among Project Tool, Plugin Development and most importantly Getting Started: Introduction, we do agree that the current form lacks clarity.
But this is rooted in a more fundamental problem than missing content, i.e., the organization of content. We could band-aid fix this case, but that would destabilize the current organization of the C++ SDK even more. We are aware of the general problem, i.e., the one of lack of visibility and organization of content, and working towards a solution, but that solution will take its time. I have noted down your suggestion though and when we find the time, we might add a temporary fix for it.
Hello @ferdinand :
In this transition period , can you make a small change and write a detailed C++ plug-in development process in the forum ? Collect the development details of the scattered generated compiled files into a post and place it at the top of the forum.