Here's a mockup of what we need. There's no sense in trying to lock axes when they aren't the same dimension type: if two columns that are not of the same dimension contain the same data, then the user has made a mistake. So implement the lock selected axes dialogue box like a Godley Table where the columns are the Ravels being locked and the rows are the axes, arranged by dimension type, where they can be moved between the same types but not across.
We don't need to be that fancy for the first iteration--just layout a table as per the attached, with the capacity to move cells around, and without the A-L-E of course.
And a Ravel with a similar mockup in a Godley Table.
Having played a bit with locking axes in the latest beta, I realise we need another option: lock axes locations as well as values. Sometimes, you'll want to see one Ravel by date and another by (say) country at a given date. At present, if you lock, that can't be done. So it makes sense to have a checkbox for whether axes locations are locked as well as which axes to lock makes.
Looking at this in detail, what we have is already more sophisticated, except in one respect - the dropdown lists are populated by all dimensions, but really the options should only be what is compatible with the other axes - so time dimension axes should only be linked with axes with the same format, as is the case with value axes, and country ones when we get that type.
But ReallyUrgent is too high a priority, so downgrading this to normal.
Ticket moved from /p/minsky/ravel/111/
Can't be converted:
Ticket moved from /p/minsky/tickets/1814/
Can't be converted: