Automatically add USING statement in a class when using code completion for a Class.

[Lieven Cardoen]

When writing for instance next Constructor, the OpenEdge eclipse plugin will search for the UltraToolbarsManager (when using Ctrl-Space) and your Ctor will look like: CONSTRUCTOR PUBLIC RibbonCustomizationDialog(ultraToolbarsManager AS Infragistics.Win.UltraWinToolbars.UltraToolbarsManager) ... After this, I always add a USING Infragistics.Win.UltraWinToolbars.UltraToolbarsManager FROM ASSEMBLY. too make the CONSTRUCTOR signature smaller. However, this is very annoying and like in most IDE's, it would be great to be able to choose whether I want to use the fully qualified name or let the plugin add a USING at the top and make the Ctor signature automatically: CONSTRUCTOR PUBLIC RibbonCustomizationDialog(ultraToolbarsManager AS UltraToolbarsManager) This is a great idea, but is Progress actually looking into these ideas? Or do I have to create a Support Case for this? There are other ideas as well for the Ecilpse Plugin like: - Fix usings -- removes unused usings, puts them in alphabetical order, ... - Refactoring... methods, variables, ... - Code completion/snippets for things like a DO WHILE, FOR statements, FIND statements, ... For instance, if in an IDE like Visual Studio or IntelliJ you whould type foreach with a TAB after it, you would get the whole structure. - Please provide a way to go over a collection like a FOREACH. I'm sure there's room for an extra keyword in Progress... As an example, In C#, iterating over a collection: foreach (var item in collection) { //Do something with the item } In ABL: DEFINE VARIABLE item AS Class NO-UNDO . DEFINE VARIABLE ItemEnumerator AS System.Collections.IEnumerator NO-UNDO . ASSIGN ItemEnumerator = CAST(THIS-OBJECT:Collection, System.Collections.IEnumerable):GetEnumerator() . ItemEnumerator:Reset() . DO WHILE ItemEnumerator:MoveNext() ON ERROR UNDO, THROW: ASSIGN item = CAST(ItemEnumerator:Current, Class) . END. Ow man, so ugly, compared to Java or C#... Maybe with a keyword FOREACH this could be improved... Ok, there are ways to do this shorter with an include file, but please, get rid of the include files for things like this.

Continue reading...