Hi 健文,
Based on your description, it seems you are developing a software package that is distributed as a web program and deployed to a server and your software includes a folder with PDF files that need to be accessed within the code using ".\path\". You have raised three key questions, please see my answers to your questions below.
1. If you publish to the web program for others to use, when someone else accesses the server to use the program, the statement ".\path\" will access someone else's computer or the server, if it is someone else's computer, how to implement my software to call the pdf file.
When your software is published for others to use on the server, the statement ".\path\" will access the server's current folder path, not the user's computer. This means that the PDF files will be accessed from the server itself. To ensure seamless access to these files for all users, you should specify the absolute path of the folder containing the PDF files in your code rather than using a relative path like ".\path\".
2. My requirement is to implement the fact that when others use it, you can download pdf files or other files (png files), how to achieve this.
To allow users to download PDF files or other files like PNG files when using your software, you can implement functionality that enables file downloads through your web program. This can be achieved by providing download links or buttons within your software's interface that trigger file downloads when clicked by users. Additionally, you can use server-side scripting languages like PHP or frameworks like Node.js to handle file downloads securely.
3. When others use it, the address of the save,load,imread,imewrite function access is my server or someone else's computer, if it is someone else's computer, go back to the first question, how to preload the file when the software is opened.
The functions save, load, imread, and imwrite in your software will access files on the server where the software is deployed, not on the user's computer. Therefore, there is no need to preload files from users' computers when the software is opened. Users will interact with files stored on the server directly through your web program.
Please make sure that your software references absolute paths for accessing files on the server, implement file download functionality for users, and understand that file operations in your software will interact with files on the server itself. Hopefully, if you follow these guidelines, you can effectively manage file access and interactions within your web-based software package. Please let me know if you have further questions.
