SoC Ideas Eclipse Plugin2011: Difference between revisions
From The Battle for Wesnoth Wiki
create page |
m a bit of info |
||
| Line 1: | Line 1: | ||
{{Template:SoC2011Idea}} | {{Template:SoC2011Idea}} | ||
= Description = | = Description = | ||
<h2> | <h2>Enhance & polish the eclipse plugin</h2> | ||
- Polish existing features in terms of: usability, performance | |||
- Add existing features | |||
{{#dpl: | {{#dpl: | ||
| Line 16: | Line 18: | ||
= Additional Information = | = Additional Information = | ||
== Support for multiple Wesnoth installations == | |||
There should be support for handling multiple Wesnoth installations, each one of them with different binaries/wml tools and so on. | |||
The user should be able to use the feature in an easy way that should restart the eclipse workspace as few as possible. | |||
== Enhance the auto complete featue == | |||
Find a way of easy specifying the tags we want autocomplete on or add autocomplete for the much used tags. | |||
Revision as of 11:20, 24 February 2011
| This page is related to Summer of Code 2011 |
| See the list of Summer of Code 2011 Ideas |
| This is a Summer of Code 2011 Idea |
Description
Enhance & polish the eclipse plugin
- Polish existing features in terms of: usability, performance - Add existing features
There are no submitted student proposals for this idea
Additional Information
Support for multiple Wesnoth installations
There should be support for handling multiple Wesnoth installations, each one of them with different binaries/wml tools and so on. The user should be able to use the feature in an easy way that should restart the eclipse workspace as few as possible.
Enhance the auto complete featue
Find a way of easy specifying the tags we want autocomplete on or add autocomplete for the much used tags.
This page was last edited on 24 February 2011, at 11:20.