As per our conversation yesterday, here's an initial list of capabilities that the RobotPy eclipse plugins should have:
Ideally, this plugin should have pydev as a requirement, so that when users install our plugin it automatically installs pydev too
Add an option to 'Run As' that runs the 'robot.py upload' command (this deploys the code to the robot)
This option should probably only be enabled for pydev projects
Interesting problems here:
How do you find the configured python interpreter (pydev should provide this somehow)?
What do you do for multiple robot.py in the same project? Or do we require users to right click on robot.py explicitly?
Add an option to 'Run As' that runs the 'robot.py frcsim' command (this runs the code using the simulation engine)
Add an option to 'Run As' that runs the 'robot.py test' command (this runs the code using pytest)
We should be able to distribute the example programs such that a user can create a new Python robot project via the New Project Wizard
The plugin should depend on the WPILib plugins, and use the core plugin's ability to show SmartDashboard/etc in a toolbar.
All of these are already implemented in the WPILib plugins, so it should be easy enough to copy their code, change some things around, and it should work.
As for debugging the application, if you define the project as an 'Eclipse application', then you should be able to 'Run As -> Eclipse Application' to run/debug it in your development environment.
@lleontan , @CarterFendley , @Twinters007 ... any of you can do these tasks. They really should get done before kickoff, so we can concentrate on Robot development after kickoff.
virtuald
commented
9 years ago
As per our conversation yesterday, here's an initial list of capabilities that the RobotPy eclipse plugins should have:
All of these are already implemented in the WPILib plugins, so it should be easy enough to copy their code, change some things around, and it should work.
As for debugging the application, if you define the project as an 'Eclipse application', then you should be able to 'Run As -> Eclipse Application' to run/debug it in your development environment.
@lleontan , @CarterFendley , @Twinters007 ... any of you can do these tasks. They really should get done before kickoff, so we can concentrate on Robot development after kickoff.