Directory "Resources" renamed "misc"
"/misc" : place here not compiled & not used files such as tutorials or plain doc
New directory "icons" created
"/icons" : place here icons used by the plugin
Applying naming conventions for plugin icons nit_desc.xxx
Adding an project icon : "nit_project.png"
Update of the plugin descriptor file (plugin.xml) : news icons filenames
Forget to refactor directory name in "plugin.xml" during previous, resulting in wrong path discovery. Fixed
---------------------------------------------------------------------------------------------------------------
Global project refactoring campaign
Step 1 of 3 : moving generated source files to org.nitlanguage.gen.*
---------------------------------------------------------------------------------------------------------------

Previously, "/src" directory contained flat directories as follows :

-analysis
-asthelpers
-builder
-console
-editor
-general_helpers
-launcher
-lexer
-newprojectwizard
-node
-parser
-perspective
-plugin
-preferences

These directories are also Java packages, there is no hierarchical structure.
In order to achieve the desired level of modularity, we are going to separate:
1.Generated source files (with SableCC).
This files are not related with Eclipse Plateform. They can be used interchangeably inside Eclipse Platorm or any other environment supporting Java.
- "analysis" to "org.nitlanguage.gen.analysis"
- "lexer" to "org.nitlanguage.gen.lexer"
- "node" to "org.nitlanguage.gen.node"
- "parser" to "org.nitlanguage.gen.parser"

2.UI related source files : from flat directories "/console", "/editor", "/newprojectwizard", "/perspective", "/preferences" to "org.nitlanguage.ndt.ui.*" package.

3."Core" related sources files : actually, consider "core" as all except UI, there is not enough files to justify an upper level of modularity for the moment.
Temporary xml files no more considered for commit operations
---------------------------------------------------------------------------------------------------------------
Global project refactoring campaign
Step 2 of 3 : moving UI related source files to org.nitlanguage.ndt.ui.*
---------------------------------------------------------------------------------------------------------------

Previously, "/src" directory contained flat directories as follows :

-analysis
-asthelpers
-builder
-console
-editor
-general_helpers
-launcher
-lexer
-newprojectwizard
-node
-parser
-perspective
-plugin
-preferences

These directories are also Java packages, there is no hierarchical structure.
In order to achieve the desired level of modularity, we are going to separate:
1.Generated source files (with SableCC).
This files are not related with Eclipse Plateform. They can be used interchangeably inside Eclipse Platorm or any other environment supporting Java.
- "analysis" to "org.nitlanguage.gen.analysis"
- "lexer" to "org.nitlanguage.gen.lexer"
- "node" to "org.nitlanguage.gen.node"
- "parser" to "org.nitlanguage.gen.parser"

2.UI related source files : from flat directories "/console", "/editor", "/newprojectwizard", "/perspective", "/preferences" to "org.nitlanguage.ndt.ui.*" package.
- "console" to "org.nitlanguage.ndt.ui.console"
- "editor" to "org.nitlanguage.ndt.ui.editor"
- "newprojectwizard" to "org.nitlanguage.ndt.ui.newprojectwizard"
- "perspective" to "org.nitlanguage.ndt.ui.perspective"
- "preferences" to "org.nitlanguage.ndt.ui.preferences"

3."Core" related sources files : actually, consider "core" as all except UI, there is not enough files to justify an upper level of modularity for the moment.
---------------------------------------------------------------------------------------------------------------
Global project refactoring campaign
Step 3 of 3 : moving "core" related source files to org.nitlanguage.ndt.core.*
---------------------------------------------------------------------------------------------------------------

Previously, "/src" directory contained flat directories as follows :

-analysis
-asthelpers
-builder
-console
-editor
-general_helpers
-launcher
-lexer
-newprojectwizard
-node
-parser
-perspective
-plugin
-preferences

These directories are also Java packages, there is no hierarchical structure.
In order to achieve the desired level of modularity, we are going to separate:
1.Generated source files (with SableCC).
This files are not related with Eclipse Plateform. They can be used interchangeably inside Eclipse Platorm or any other environment supporting Java.
- "analysis" to "org.nitlanguage.gen.analysis"
- "lexer" to "org.nitlanguage.gen.lexer"
- "node" to "org.nitlanguage.gen.node"
- "parser" to "org.nitlanguage.gen.parser"

2.UI related source files : from flat directories "/console", "/editor", "/newprojectwizard", "/perspective", "/preferences" to "org.nitlanguage.ndt.ui.*" package.
- "console" to "org.nitlanguage.ndt.ui.console"
- "editor" to "org.nitlanguage.ndt.ui.editor"
- "newprojectwizard" to "org.nitlanguage.ndt.ui.newprojectwizard"
- "perspective" to "org.nitlanguage.ndt.ui.perspective"
- "preferences" to "org.nitlanguage.ndt.ui.preferences"

3."Core" related sources files : actually, consider "core" as all except UI, there is not enough files to justify an upper level of modularity for the moment.
- "asthelpers" to "org.nitlanguage.ndt.core.asthelpers"
- "builder" to "org.nitlanguage.ndt.core.builder"
- "launcher" to "org.nitlanguage.ndt.core.launcher"
- "plugin" to "org.nitlanguage.ndt.core.plugin"
- "general_helpers" to "org.nitlanguage.ndt.core"
New cleaning campaign : modification of classes comments inside org.nitlanguage.ndt.core.* and ui.*
To better track who is doing what, each commiter should now indicate his name
in a chronological manner (top-bottom), using @author JavaDoc annotation
Hard coded Views Ids (e.g. "org.eclipse.ui.console.ConsoleView")
partially replaced with plateform constants.
Minor syntax and name changes made
Adding 4 preference pages (Window/Preferences/Nit/ ) to the project.
Not implemented yet.
*NitAppearancePage
*NitBuilderPathPage
*NitCodeStylePage
*NitEditorPage
Follow the Java Preferences Pages.
Trim whitespaces support (by default for the moment).
This functionnality aims to reduce useless conflicts due to end of line whitespaces.
Implemented through a DocumentProvider.

*TODO : add an entry in nit editor preference page (NitEditorPage.java)
Basic launch shortcut support
Now it is possible to launch a nit program with keyboard shortcut (Ctrl+F11 = Run, only launch mode available for the moment)
Moreove these is no need to create a run configuration if none exists.
NitLaunchShortcut complete this task by creating programmatically a run configuration which target :
-selected file in project explorer if focus is on Project Explorer view.
-file edited in text editor if focus is on Nit Editor view.

Note : for the moment this implementation isn't robust. More controls have to be done.
Even if in production Eclipse doesn't show plugin internal errors, it is possible to use a launch shortcut even if none of the previous case is met == it results in an error -- TOFIX
Manifest bundle name changed from "org.uqam.nit.ndt" to "org.nitlanguage.nit.ndt"
Changed to conform with the new package naming convention
Merge pull request #4 from nheu/master

Pull request - Janvier-Février