Feature Request #673

model and view should not depend on a file name convention to work

Added by Diemo Schwarz over 9 years ago. Updated about 9 years ago.

Status:ClosedStart date:2011-02-03
Priority:UrgentDue date:
Assignee:Théo de la Hogue% Done:


Category:-Spent time:-
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.


#1 Updated by Diemo Schwarz over 9 years ago

  • Priority changed from Normal to Urgent

#2 Updated by Nils Peters over 9 years ago

+ 1

#3 Updated by Théo de la Hogue over 9 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"
into "toUpperCased")

#4 Updated by Renaud Rubiano over 9 years ago

It works great for me

#5 Updated by Pascal Baltazar about 9 years ago

  • Status changed from Resolved to Closed

works here too... closing the bug

Also available in: Atom PDF