I love using FileEdit and CodeProcessor with topcoder. It makes a huge difference in submission time.
However, ther is one enhancement I'd like to see. In Java I like having a separate test class. But the naming convention is a little different than what's currently supplied. For a problem class named "Solution" I want a test class named "SolutionTest".
My question is. Should I just get the source and make the modifications for myself, or is that something others would find helpful and should be added to the project?
Let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the feedback! Sorry I didn't respond immediately.
The purpose of the separate test class was to make the code work for .Net. I submitted Java code from IntelliJ Idea, and one class for both production code and test code worked fine. When the file gets saved to the directory structure in this environment (and I imagine other Java environments), the file also appears in the project tree in the GUI automagically.
This doesn't occur when you compete from .Net, and it is pretty ridiculous to add the files to the project workspace during a competition, so I found an alternative almost as good. The project file could be a permanent file and would endure through multiple problems. It would be a permanent part of the project and would get focused on whichever problem file you were working on currently via text replacements. The problem file would be auto-generated and have the test code included, rather than putting it in the project file, which simply has a generic test function stub.
Because of the stub replacement aspects for the project file and the original purpose of the project file, I would suggest that it would be simpler to think of splitting the problem file to get what you want and ignoring the current separate file if you want this feature. Of course, we now get down to the question, why do you like this feature in the first place. I would suggest that any valid reason involves editing of code as opposed to the submission of code to the engine, because as far as I know, the mechanisms for stripping code out are adequate.
With that in mind, I would first suggest you see if your editor has a function collapse method. In Codewright, it is <Ctrl-G>. Idea has one too, but I forget what it is. I re-mapped it to <Ctrl-G>. Second, I would look at the code changes needed and whether they can be applied to a language like C++ where you have to decide whether code goes in a .h file or a .cpp file. Third, let me know whether this can be done with relatively clean UI changes and generally what you plan.
My gut feeling is that the modifications wouldn't be that popular, but you never know. I don't claim to be 'In touch' ;).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am interested in hearing about environments people are using with FileEdit and issues they have.
I love using FileEdit and CodeProcessor with topcoder. It makes a huge difference in submission time.
However, ther is one enhancement I'd like to see. In Java I like having a separate test class. But the naming convention is a little different than what's currently supplied. For a problem class named "Solution" I want a test class named "SolutionTest".
My question is. Should I just get the source and make the modifications for myself, or is that something others would find helpful and should be added to the project?
Let me know.
Thanks for the feedback! Sorry I didn't respond immediately.
The purpose of the separate test class was to make the code work for .Net. I submitted Java code from IntelliJ Idea, and one class for both production code and test code worked fine. When the file gets saved to the directory structure in this environment (and I imagine other Java environments), the file also appears in the project tree in the GUI automagically.
This doesn't occur when you compete from .Net, and it is pretty ridiculous to add the files to the project workspace during a competition, so I found an alternative almost as good. The project file could be a permanent file and would endure through multiple problems. It would be a permanent part of the project and would get focused on whichever problem file you were working on currently via text replacements. The problem file would be auto-generated and have the test code included, rather than putting it in the project file, which simply has a generic test function stub.
Because of the stub replacement aspects for the project file and the original purpose of the project file, I would suggest that it would be simpler to think of splitting the problem file to get what you want and ignoring the current separate file if you want this feature. Of course, we now get down to the question, why do you like this feature in the first place. I would suggest that any valid reason involves editing of code as opposed to the submission of code to the engine, because as far as I know, the mechanisms for stripping code out are adequate.
With that in mind, I would first suggest you see if your editor has a function collapse method. In Codewright, it is <Ctrl-G>. Idea has one too, but I forget what it is. I re-mapped it to <Ctrl-G>. Second, I would look at the code changes needed and whether they can be applied to a language like C++ where you have to decide whether code goes in a .h file or a .cpp file. Third, let me know whether this can be done with relatively clean UI changes and generally what you plan.
My gut feeling is that the modifications wouldn't be that popular, but you never know. I don't claim to be 'In touch' ;).