| [ajdt-dev] tool design: replacing ".lst" files |
The ".lst" files that the IDE plugins use may not be the ideal way of supporting build configurations. The following is a proposal for a better-integrated mechanism and UI. I've set up a bug report for it, please comment using bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=50454 ------------- IDE (AJDT as example, mock-up attached) * Stop using ".lst files for build configurations and use the IDE's file-filtering mechanism instead. The premise here is that exclusions are a better model for configurations than the current inclusions. AJDT provides a per-source-folder exclusion filter already (see attachment). This would be analogous to a per-project exclusion filter. * Preserve the current build configuration editor UI. * Improve the compilation configuration selection UI by making it a drop-down menu in the toolbar. This is better integrated with auto-build, and ensures that the current configuration is very visible (confusion about what was built results if that's not the case). * Allow ".lst" files to be imported/exported with a new wizard. ANT & COMMAND LINE Directory-based Task "excludes" are another convenient alternative that already has built in support (document that better?). Continue supporting ".lst" files on the command line, and making that accessible via the Ajc Ant task. Mik -- http://kerstens.org/mik
Attachment:
filter-configs-mockup.gif
Description: GIF image
