This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Describe input/output architecture by answering NetBeans Arch Questions as described at http://openide.netbeans.org/tutorial/api.html
If you go to openide/arch directory, there is a build.xml prepared for you. If you invoke "ant <nameofyourapi>" a arch-openide-yourapi.xml file should be generated and you can start answer the questions there. When you are ready, run the ant script once more -> html page is generated (you have to change questionsverion to the right value). After that check the .xml into CVS. You can delete .html
I'll do this one if no one else wants to.
Done.
Hello Jesse, I have some comments to version 1.4 of your answers: 1. how we will document term? As part of this issue or separate one? Can you do it? If separate, then this module depends on it. Btw. is not the "api" part of term too big? Should not we make more classes non-public? 2. dep-nb: this project also depends on windowsystem private API: org.netbeans.core.windows.*, please document that with same stability level as windowsystem assigns to this API 3. resources-file: Is not there an action "Start Redirection To A File?" 4. format-clipboard: There is a copy action in term console. 5. scalabilty is achieved by limiting the buffer memory of term? But I am not sure. 6. please use <api> tag to define API that you export (org.openide.windows)
Should be better now.