1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Roadmap:Eclipse

From lejos

(Difference between revisions)
Jump to: navigation, search
(short term goals)
 
(19 intermediate revisions not shown)
Line 1: Line 1:
== short term goals ==
== short term goals ==
-
* create a simple and extendible interface, between leJOS and the plugin
+
* make a decision on whether the plugin is self-contained or relies on an existing leJOS NXJ installation
-
* use the leJOS installation at the location provided in the settings. (Sven: please explain. I am sure <atthias woiuld say this is already done).
+
** create a simple and extendible interface, between leJOS and the plugin
-
* use a customized classloader so that native libraries are found without settings any LD_LIBRARY_PATH stuff
+
** use jar files from the leJOS installation rather than including them in the plugin
-
* Create leJOS projects by New > leJOS Project rather than convert exising projects
+
** use a customized classloader so that native libraries are found without settings any LD_LIBRARY_PATH stuff
-
* Support multiple options for project upload (debug, usb, bluetooth, verbose, etc) from the context menu and avoid having to set options on the preferences page
+
* create leJOS projects by New > leJOS Project rather than convert existing projects, but keep an option to convert an existing project
-
* Ensue that all errors and progress messages are reported in the leJOS NXJ console log window. (Some errors from the linker currently go to System.out and are not seen by the user)
+
* support multiple options for program upload (debug, usb, bluetooth, verbose, etc) from the context menu and avoid having to set options on the preferences page
-
* Make it easy to upgrade individual projects to a new version of leJOS. (Could just be documentation).
+
* support a context menu option that puts up a dialog to set options including the name or address of the NXT to connect to
 +
* ensure that all errors and progress messages are reported in the leJOS NXJ console log window. (Some errors from the linker currently go to System.out and are not seen by the user)
 +
* make it easy to upgrade individual projects to a new version of leJOS. (Could just be documentation)
 +
* set the --classpath and --bootclasspath for the linker correctly for all entry types including source folders dependent projects
 +
* ensure that created projects reference the source and API docs for classes.jar
 +
* make it easy to get to the leJOS tutorial, possibly by referencing it from the plugin help text
 +
* make it possible to link class to binary file with a "save as" dialog
 +
* link/upload without creating temporary files (Needs support in jtools)
 +
* storing debug information (mapping of numbers to methods/classes) in an external file (Needs support in jtools)
 +
* make the leJOS context menus work, when rightclicking on a class (rather than a file) which contains a main-method
== long term goals ==
== long term goals ==
* keep a list of installed leJOS environments (like JDT keeps a list of installed JDKs, makes it easier to use snapshots along with release builds)
* keep a list of installed leJOS environments (like JDT keeps a list of installed JDKs, makes it easier to use snapshots along with release builds)
-
* provide a class library instead of adding the classes.jar using and absolute path
+
* provide a class library instead of adding the classes.jar using an absolute path
-
* Create projects for running on the NXT, the PC and a Phone
+
* include options to create projects for running on the NXT, the PC and a JME device (such as a mobile phone)
-
* Install the example, the samples, the pcsamples and the j2mesamples by New > Lejos Sample/Example Project
+
* install the example, the samples, the pcsamples and the j2mesamples by New > Lejos Sample/Example Project
 +
* implement the equivalent of NXJControl as a built-in tool
 +
* make other tools available as integrated tools or by automatically installing them as external tools
 +
* create a leJOS toolbar with iconized buttons to trigger the actions from
 +
* create a leJOS NXJ perspective
 +
 
 +
== Other possible developments ==
 +
 
 +
* install the API docs within Eclipse so that they can be browsed from within Eclipse
 +
* have an option to generate an ant build file for a project

Current revision as of 08:43, 4 September 2009

short term goals

  • make a decision on whether the plugin is self-contained or relies on an existing leJOS NXJ installation
    • create a simple and extendible interface, between leJOS and the plugin
    • use jar files from the leJOS installation rather than including them in the plugin
    • use a customized classloader so that native libraries are found without settings any LD_LIBRARY_PATH stuff
  • create leJOS projects by New > leJOS Project rather than convert existing projects, but keep an option to convert an existing project
  • support multiple options for program upload (debug, usb, bluetooth, verbose, etc) from the context menu and avoid having to set options on the preferences page
  • support a context menu option that puts up a dialog to set options including the name or address of the NXT to connect to
  • ensure that all errors and progress messages are reported in the leJOS NXJ console log window. (Some errors from the linker currently go to System.out and are not seen by the user)
  • make it easy to upgrade individual projects to a new version of leJOS. (Could just be documentation)
  • set the --classpath and --bootclasspath for the linker correctly for all entry types including source folders dependent projects
  • ensure that created projects reference the source and API docs for classes.jar
  • make it easy to get to the leJOS tutorial, possibly by referencing it from the plugin help text
  • make it possible to link class to binary file with a "save as" dialog
  • link/upload without creating temporary files (Needs support in jtools)
  • storing debug information (mapping of numbers to methods/classes) in an external file (Needs support in jtools)
  • make the leJOS context menus work, when rightclicking on a class (rather than a file) which contains a main-method

long term goals

  • keep a list of installed leJOS environments (like JDT keeps a list of installed JDKs, makes it easier to use snapshots along with release builds)
  • provide a class library instead of adding the classes.jar using an absolute path
  • include options to create projects for running on the NXT, the PC and a JME device (such as a mobile phone)
  • install the example, the samples, the pcsamples and the j2mesamples by New > Lejos Sample/Example Project
  • implement the equivalent of NXJControl as a built-in tool
  • make other tools available as integrated tools or by automatically installing them as external tools
  • create a leJOS toolbar with iconized buttons to trigger the actions from
  • create a leJOS NXJ perspective

Other possible developments

  • install the API docs within Eclipse so that they can be browsed from within Eclipse
  • have an option to generate an ant build file for a project
Personal tools