Card gem or the Card/Deck Split

Again, just for discussion for now.

I've looked a little at how rails does the many projects in one repo and tried to do something similar here.  My thinking now is that if we get this split right, then everything needed for the platform is in the card gem and the wagn (soon to be decko) gem is what makes it case 1, a web application that uses the card engine.

It took me a while, but I got it to load and run the few specs left behind in the wagn part.  Seems like the mods should be split, but many of them are core.  Please add your comments about what is core and what is not.  I'm thinking that things like accounts has be be with the deck as authentication is a site issue.  Default is a plain card, and then we are using card_ids as the creator/updater.  Question for all is how we want to connect to an external user model, do we always want to have a card with a card_id that is associated with the external mode?  Is that just another instance of an external model bound to a deck via a standard way of doing that?  My plan was to add card_id to the external table (making it belong to a card and the card will have_one of the external model).

The part I haven't figured out/finalized is the way the top level objects should work.  Initially I thought (wrongly) that the Engine (Card::Engine < Rails::Engine) needed to be part of the Wagn::Application < Rails::Application object, but there just isn't a way to have one object fill both roles.  And this split implies that the application will always have very simple routes that mount the Card::Engine thing, and the same thing in the platform use, but you'd have all your application's initial routes.  We may also want to split out some of the legacy routes to the application and leave only the platform standard stuff in Card::Engine routes.
I certainly see the point of wanting to use the models without the controller, but I think considering the MVC stack together is a valid modular unit as well.  Maybe we need to talk to get straight on the language.

I guess the question for me is what kind of API are we creating here?  Thinking with the new MoFoS, that's a model/view API thought of together, and the card controller is simply exposing that in a canonical controller via web oriented APIs.  That is really the industry standard for service oriented APIs and allows the bridging of language domains with ease.  I mean, why leave it out?  If you don't need it, it isn't that much code.

Maybe you want to call this card-rails, and split this part into two gems?  (I would say card-engine to be more precise, but I'm fine with either.)

It also kind-of opens up questions about the front-end components.  I see how some javascript is in mods, which is right from a dependency perspective, but I'm not sure how well it matches up with current practice in JS APIs, loading and packaging.  When we add decks to P2P (my trib project), we will already have tinymce, and there are some configuration customizations we do and may want with across any card based extension.  If we do things right different approaches can co-exist with cards.