@@ -1,4 +1,4 @@ BooLangStudio ChangeLog: 0.1_r2937 - 5/12/2008 - * initial release \ No newline at end of file +* initial version \ No newline at end of file CHANGELOG.txt @@ -1,25 +1,20 @@ -What BooLangStudio Has: - * MsBuild integration in IDE (courtesy of the Boo team) - * Basic syntax highlighting (with caveats noted below) - * ClassLibrary and ConsoleApplication project types for boo - * Basic empty Class and Text file ProjectItems for Boo - * Auto-indentation when pressing enter after a ':' (colon) on the preceeding line +!! What BooLangStudio Has: +* MsBuild integration in IDE (courtesy of the Boo team) +* Basic syntax highlighting (with caveats noted below) +* ClassLibrary and ConsoleApplication project types for boo +* Basic empty Class and Text file ProjectItems for Boo +* Auto-indentation when pressing enter after a ':' (colon) on the preceeding line -What BooLangStudio DOES NOT Have (but if you want to implement it, PLEASE DO): - * Any form of IntelliSense, specifically: - * member listing (when you press '.' after an instance identifier or Class identifier) - * "declaration scope", where any objects/keywords in scope are displayed while typing - * valid, "in-scope" types coming after the 'as' keyword. ie: "foo as <types displayed here>" - * valid keywords by scope, ie: def, class, if, etc depending on scope/context - * valid, in-scope local/member variables - * tool tip support for types/method info - * parameter info when constructing a method call - * #region detection - * 'comment-region' functionality - * any refactoring functionality - * resolve functionality - -What BooLangStudio Has, But Needs Improvement On: - * Currently, there are some aberrations with syntax highlighting, specifically: - * multiline doc strings aren't parsed - * multiline comments have some issues with the appears of multiline comments that contain string delimiters.. something with the way that BooScanner is dealing with tokens it receives, most likely. \ No newline at end of file +!! What BooLangStudio DOES NOT Have (but if you want to implement it, PLEASE DO): +* Any form of IntelliSense, specifically: +** member listing (when you press '.' after an instance identifier or Class identifier) +** "declaration scope", where any objects/keywords in scope are displayed while typing +*** valid, "in-scope" types coming after the 'as' keyword. ie: "foo as <types displayed here>" +*** valid keywords by scope, ie: def, class, if, etc depending on scope/context +*** valid, in-scope local/member variables +** tool tip support for types/method info +** parameter info when constructing a method call +* #region detection +* 'comment-region' functionality +* any refactoring functionality +* resolve functionality \ No newline at end of file TODO.txt b51adba457f6ba67e5481e2912b3cbece5ec8685 olsonjeffery olson.jeffery@gmail.com http://github.com/jagregory/boolangstudio/commit/17c1cccc492fc2041ba9253595764b31c6b25461 17c1cccc492fc2041ba9253595764b31c6b25461 2008-05-15T13:13:17-07:00 2008-05-15T13:13:17-07:00 cleaning up documentation for CodePlex formatting 8c55618d2c5f4e8cffcbb4fb034e5d2e60bc23ed olsonjeffery olson.jeffery@gmail.com