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.
That's not correct.  I think the name is throwing you off.  The controller is **the** controller; it's current name (card_controller) is legacy.  Controllers and routes are what turn card into a web app, and thus they need to be kept outside of the card gem.

In concept, you should be able to use the card gem for all sorts of data processes *without* any sort of web interaction.  If you wanted, you could create an entirely different API for them.

Note that this will make the card gem considerably more lightweight, because it won't need actionpack, which depends on rack.  And it may not need railties?

At any rate, the key thing is that the card gem is web-stupid.  This is not an impulsive new idea; we've been working for years now to make it so that the whole card system is *independent* of the controllers.  Our gem structure will finally formalize that.