Feature Request #673
model and view should not depend on a file name convention to work
|Assignee:||Théo de la Hogue||% Done:|
|Target version:||MVC for 0.6|
In order to create the model part of MVC, we need to be able to tell the hub that the patch is the model, not depend on a naming scheme like foo.model.maxpat.
The same goes for the view, esp. since there can be several different views for the same model.
These naming conventions should also work, of course, for the simpler cases, but should be overridable by an attribute.
#3 Updated by Théo de la Hogue over 6 years ago
- Status changed from New to Resolved
The new subscription mechanism should resolve the request.
Let me know if you are agree.
(hovewer using "." inside the name of the patch should make a strange namespace...
but there is a precise place in the code to change a name like "to.upper.cased"