#1: Integrate the stand-alone Library Object Manager. Probably this is much more difficult than it seems on first blush, and I will admit that I have no idea of how much LOM would have to be first modified to be useable in CAD mode with ADE. But consider this:
I have spent untold hours getting scenery objects organized and thumbnailed so I can use them, and searching the message base here, I am not the only one. I will admit this does not hold a
patch to the untold man-years invested in ADE to date. But for me, when I was frothing at the mouth to get to WORK on scenery building, this meta-work is maddening. In fact, scenery design itself (notwithstanding two released titles to my name) is meta-work: done only to increase my
flying enjoyment, and not as an end in itself. Meta-work piled on meta-work is not only maddening, but due to my busy consulting business and 5 kids, it's just not gonna happen with me very often. I'm getting too old to stay up til 3AM on recreational activities any more.
Once the work of getting LOM ready to
use for building scenery was done, it was very worthwhile, though I was VERY glad it was over. Only it
isn't over, because (how, I can't imagine) a
wonderful opportunity to import LOM into ADE went begging and now there's a parallel stream. And Jon says (in another thread) not even the databases and thumbnails can be used.

By the ADE canon, all the work I did in LOM is lost, except possibly the work of creating the thumbnails themselves.
This sounds like griping, criticism, etc., and
far be it from me to do so. I'm VERY THANKFUL for the many free and VERY USEFUL tools that have come out of ScruffyDuck. But let me remind you of the ADE manual, p12, §1.2, second sentence:
"In the past, a developer had to use multiple utilities to add or modify library objects, generic buildings, land class, flattens, exclusions, and terrain vectors in their airport projects. Most of this work can now be completed in ADE9X."
This is a
wonderful goal to me, because I actually have trouble remembering which of the dozen tools I must use (and how to use them) for different aspects of airport modification and new airport design. If the object is to make ADE (to the greatest degree possible) the single go-to software for airport design, failing to integrate LOM for the FS9 release seems to be a rather major omission.
In another thread, I read that object placement is not seen by the team as being very important compared with the aspects of airport, runway, parking, navaids, etc. Well and good, except on my Banff project (and my dozen unreleased projects), mere object placement is almost the entire reason for the project's existence! In fact, reading the manual for the first time, unless there is some workaround method I can figure out to automate getting my existing AFCAD airport into ADE in a way that can be integrated with FS approach data, it might be that the only thing ADE will be able to do
for me, and only if the requested feature is added, is create stand-alone approaches to add to my projects that FS9 ATC will recognize and assign to me and AI traffic.
However, I'm just getting started with ADE, so we'll see.
Again, I'm NOT wishing to leave the impression that I'm anything other than THRILLED to see ADE released for FS9 and (other than the learning curve) useable in an almost immediate fashion to encompass the many OTHER aspects of airport design (besides object placement). But I have too much invested in LOM to give it up now.
--The BeachComer
Stephen "Beach" Comer
Maker of Vail and Banff sceneries - the latter, impossible (for me) without LOM!