I can live with the uppercasing or lowercasing keywords as longs as it is consistent. Personally as I am doing Java development too I stick with the naming conventions the are mostly used in the Java world ( camel case ) which includes lower case keywords ( as Java is case sensitive you can't have them uppercase - the IDE or the compiler will insist ... ). It might be subject to discussion whether that it is good or bad but at least the code I produce looks consistent regardless whether it is Java or ABL code. What I hardly can take is when dear colleguages of mine use names like filn as a variable or database field name. But, obviously I am too dumb to recognize that this is the acronym for financial instrument long name ( too dumb since this naming standard passed the code review done by another dear colleguage of mine, it surely wouldn't have passed mine ) ...
You can still use the AppBuilder / Procedure Editor to edit code with the Progress Developer Studio, but the SlickEdit ( which is a third party product ) does not come with it anymore. For that you need the OpenEdge Studio license - which obviously does not include the Eclipse plug-ins.
Heavy Regards, RealHeavyDude.