Thanks Larry. Does it help make up for my idiot-fest on missing libraries? :)
I did have to do a fair amount up front to make it work with my custom vision classes, but by doing that, I ended up with a handy-dandy and relatively painless process.
The key element is to have a kind of template for a customizable project that uses ebuild.
There is a separate .ecf file for the actual project (vs the build_project*.ecf). The vision2_application class is ignored, and replaced with my own application_root class. My template comes with a new main_window.e that still inherits main_window_imp, but is otherwise custom.
There's not much more to it than that, other than the stuff that's strictly custom. Ebuild doesn't realize I've hijacked it's output.
Once that's in place, then the main_window.e can be as custom as you'd like, and you can hand-build stuff into it, or take what ebuild gives you (from the generated main_window_imp class), and/or remove stuff that ebuild put in.
It makes whipping up gui gizmos more fun (though I don't actually _do_ fun; I know people who do)
R