D
dbeavon
Guest
Perhaps we're using OO in ABL a bit more than most? I guess I'll go ahead and plan on reporting my bugs one-by-one thru my support account (at least the ones I've discovered myself, "the hard way"). Thank goodness for OpenEdge product support. It seems that Progress would have much to gain by disclosing more information about "find references". Otherwise the involvement of product support is certain to be longer and more resource-intensive, and won't provide any benefit to the community as a whole. It would seem to me that the disclosing of more information (surrounding the "find references" feature) would also be helpful to others who'd like to start using OO ABL and who'd benefit from having more familiarity with the available tooling in Eclipse. Nowadays if a new developer was to approach ABL and start using it for the first time, they might naturally investigate the OO side first. I think that side of things would benefit from getting more attention/investment, and would certainly benefit from more publicly available information. Unfortunately googl'ing / bing'ing on OO-ABL topics is unproductive. Whenever I encounter an issue in this area, I find there is little out there to be found on the subject. My first support case will be to find out *WHEN* a developer may start using the "find references". I know that there is a delay between the time we compile to r-code and the time we can start searching for references in the IDE, but it is unclear how long to wait. The progress/status output view (in Eclipse) provides no clues either. I guess for now I just need to use my taskmgr and wait for the java.exe cpu to slow down... or something along these lines... wish there was anyone else out there trying to use this stuff too... you would almost think we were on the bleeding edge of software development here...
Continue reading...
Continue reading...