Hey Nicolas,
Thanks for the quick reply.
Perhaps you may want to also add this layout function to the category/product modules. Let me give you an example why:
Let's say I have one product and 3 different modules ('full detail', 'quick sale' and 'members only'). The full detail view gives everything about the product, the quick sale only shows brief info and no picture, and the members only layout is designed specifically for members and has extra data in it (for example purposes, of course you could check for member status in php and add it to any layout).
If we default all products to 'detail view' via the product module base layout, does this mean we need to have 3 versions of the same product? Since we need a version that uses the default/inherited layout, a version that uses the quick layout and a version that uses the member layout.
However if we had 3 modules, one for quick view, one for full view and one for member view, we can assign all products assigned to these modules to have these views. So one product can be called by 3 distinct modules without having to adjust the individual products layout value for each unique display.
The way you have it now doesn't flow properly since it is at the end-point of the system. Since it is assigned only at the product screen, you cannot dynamically alter it based on which module it is part of. It will only ever have it's designated layout. This restricts design choices.
If you are forced to have 3 different products on the back-end, one for each product layout view, this just messes with inventory levels.
Also... it'd be great if you could add a layout view to the url so you can link products with a specific layout from elsewhere on the page / externally. Ie. &layout=unique_layout_alias
