Feature Request #1076

jcom.view, jcom.model and jcom.node could replace jcom.hub in0.6

Added by Pascal Baltazar over 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:2012-02-14
Priority:NormalDue date:
Assignee:Théo de la Hogue% Done:

0%

Category:-Spent time:-
Target version:MVC for 0.6
Branch:

Description

as discussed on the list recently, replacing jcom.hub by jcom.view, jcom.model and jcom.node could make things more straightforward

a (virtual) jcom.node could be created for each "implicit" node, such as /preset in the case of embedded parameters...

this implies renaming the current jcom.view, e.g. by jcom.remote

History

#1 Updated by Théo de la Hogue over 5 years ago

  • Status changed from New to Resolved

the jcom.hub is now jcom.model for model patcher and jcom.view for view patcher.
the former jcom.view is now jcom.remote

we have to discuss about the jcom.node because I'm not sure we need this external ...

#2 Updated by Théo de la Hogue over 5 years ago

it is now possible to create a model or a view as a "component" (which means without all internal parameters for help, reference, autodoc, ...) :

[jcom.model component]
or
[jcom.view component]

This would be particulary usefull to create a library of external to make some standard stuffs like a transport model (to declare all play, stop, pause, ... parameters)

#3 Updated by Trond Lossius about 5 years ago

Seems to me that this is done, and the issue can be closed?

#4 Updated by Théo de la Hogue about 5 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF