Feature Request #763
automatic binding of children in the case of nested views
|Assignee:||Théo de la Hogue||% Done:|
|Target version:||MVC for 0.6|
This is more a question than a real feature request.
in the case of a module containing modules (such as tracks in Théo's example), shouldn't the children views be binded to the relative sub-models when the parent binding is changed ?
easier to figure out with the attached patches (you need to have Théo's 0.6 overview in your search path..)
opinions, anyone ???
#1 Updated by Théo de la Hogue about 7 years ago
- Priority changed from Normal to Low
I would like to set the priority lower in order to observe
massive patching examples before to see if more generic
possibilities won't appears.
As I see in your example patch it seems quite easy to
avoid this missing feature and maybe you'll find other
tricks relative to /model/address binding strategy
(like declaring other /model/address.1, .2 yourself
to make a view patcher binding on more 1 model to group
Is this sounds good for you ?
#2 Updated by Pascal Baltazar almost 7 years ago
maybe this is something that should work with absolute/relative addresses ?
if there is a slash at the beginning of the argument -> the view will bind to the corresponding address
if there is no slash, then it will bind to the adress below the "parent"
of course, keeping wildcards working would be great !
(currently, wildcards are working, i.e. model/address /myModel.* will bind the view to /myModel.1, /myModel.2, etc...)