I still haven't had a chance to experiment with Bootique to see how it would fit in yet...
I'm currently pulling in cayenne-server, cayenne-di, and cayenne-project, but don't see any issues adding more modules as-needed. On Wed, Oct 5, 2016 at 7:56 AM, Andrus Adamchik <[email protected]> wrote: > > > On Oct 5, 2016, at 2:33 PM, Michael Gentry <[email protected]> > wrote: > > > > On Mon, Oct 3, 2016 at 2:57 PM, Andrus Adamchik <[email protected]> > > wrote: > > > >> Also we'll need to spend some time on the new rev-eng tab in the > modeler. > >> It kinda works, but there are UI quirks, and simply lots of unused > >> potential in how we can present the new backend capabilities via the UI. > >> > > > > I'm still making slow, but steady, progress on the CM rewrite/prototype I > > started. Would we want to try to do this in that or continue with the > > current CM and try to reuse what we can in the future? > > > > mrg > > Yeah, I wish we'd stop spending time on the Swing version. But we have no > choice but to keep it going until the new JavaFX version is ready for an > average user and supports all main functionality. > > Not sure if we can design the new system so that it can reuse more stuff > with the old one. I'd imagine we do reuse a bunch of stuff already > (org.apache.cayenne.map, cayenne-project, cayenne-dbsync). Wonder if we can > increase this reuse somehow, e.g. via a shared Bootique service stack (??) > > Andrus
