Structure Change+discussion

Thx for posting this (I don't follow all of it in gory detail, but appreciate being able to stay up on changes to the internals). Does this relate to an existing ticket on http://www.wagn.org/wagn/Wagn_1_6 or to a new ticket, say, use card_id as the linking field for all extensions ? --John

Yes, new tickets. I really should have created them before diving in, but I didn't really know exactly where I was going when I started.

The plan is to create a ticket for each major chunk of this work, and I'm not sure how many. I'll use your link to create a ticket for the first chunk when I start to document it.

Thanks,

  --Gerry Gleason.....Sun Dec 26 03:06:18 -0800 2010

It relates to this document that has notes about intended changes to the data structures in the DBs: https://spreadsheets0.google.com/ccc?key=tLm3EzjAMKlnSoIjbGOO7cQ&hl=en#gid=0 If there are tickets related to this, they may also tie in to this group of tickets.

  --Gerry Gleason.....Sun Dec 26 04:25:41 -0800 2010

Branch is card_id_codename

  --Gerry Gleason.....Fri Jan 21 08:55:34 -0800 2011

Renamed the branch to 'codename'

  --Gerry Gleason.....Wed Feb 02 05:20:19 -0800 2011

Is this an existing or new Blueprint (or part of one)?

  --John Abbe.....Wed Feb 02 12:16:17 -0800 2011

Not sure, but it probably should be. Maybe Unified view handling should be linked to the inclusion refactor.

I think we need a Blueprint for cardnames as a place for all the design elements connected to cardnames, keys, codename, plusses, etc.

  --Gerry Gleason.....Wed Feb 02 13:00:19 -0800 2011