0ct0pu5/wesnoth
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

eclipse plugin: update the changelog

Browse source
This commit is contained in:
Timotei Dolean 2010-08-14 08:56:19 +00:00
parent 84ce7b142e
commit f5a8eb2ec4
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
utils/java/eclipse_plugin/changelog
View file

@ -1,19 +1,43 @@
Eclipse plugin changelog
0.3.0
* Fixed a problem in cases when the workbench isn't started and the
welcome message would have caused error starting the plugin
* Now it's possible to use a wesnoth project without the 'build.xml' build files.
If the build.xml file is missing the user can 'regenerate' it by using the
project's context menu. A file without 'build.xml' is considered to be
a data/campaigns/ project
* Removed the User Addons project
* The 'Setup workspace" action will create a project for each existing
data/campaigns/ campaign and for each directory in 'useraddons/data/add-ons'
* Wesnoth projects building was improved by:
- removing some unused properties
- caching of preprocessed files. Files that already have been preprocessed will be skipped.
- the project macros are read only at the end of the build
* The *.map files are opened automatically in the game map editor
* The grammar was updated so the editor will support a broader variety of wml code
* When there are tags that need to be closed, when the user types: '[/' the last
unclosed tag will be closed automatically
* The user can specify whether the new project wizard should create the files:
'_server.pbl' and 'build.xml'
* Added the 'Wesnoth project' View specialized for viewing wesnoth projects
* Added wizard for new wesnoth config file (.cfg)
** Helpers**
- pressing F2 on different wml elements, brings up the WMLDoc:
- macros - will display its name, definition and arguments
- tags - will display a description for the tag
** Navigation - Used with F3 or CTRL+CLICK **
- map location - opens the map in the editor
- macro calls - goes to macro definition
** Autocompletion **
* We now have priorities, so more important stuff is shown first. Currently
the following order is in place: key values > key names > tags > macro calls
- tag names
- mandatory tag keys are automatically added for each auto-completed tag
- key names
- macro calls
- key values: enums, scenarios
0.2.1
* The workspace setup is done automatically on plugin start (first usage of it's features)
* Faster launching of campaign/scenario due to some enhancement in the wmlparser